Junos OS

Interfaces Fundamentals for Routing Devices

Release

14.2

Published: 2014-10-30

Copyright 2014, Juniper Networks, Inc.

Juniper Networks, Inc.

1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, 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 Interfaces Fundamentals for Routing Devices

14.2
Copyright 2014, 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
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.

ii

Copyright 2014, Juniper Networks, Inc.

Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xliii
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xliii
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xliii
Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xliv
Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xliv
Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlv
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlv
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlvii
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlviii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . xlviii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlviii

Part 1

Router Interfaces

Chapter 1

Router Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Router Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Types of Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Understanding Permanent Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Understanding Transient Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Understanding Services Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Understanding Container Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Understanding Traditional APS Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Container Interfaces Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
APS Support for Container-Based Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Autocopy of APS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Understanding Management Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 10
TX Matrix Plus and T1600 Router (Routing Matrix) Management Ethernet
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Understanding Internal Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
T1600 Routers (Routing Matrix) Internal Ethernet Interfaces . . . . . . . . . . . . . . . . 14
Supported Routing Engines by Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
M7i Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
M10i Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
M40e Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
M120 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
M320 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
MX104 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
MX240 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MX480 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MX960 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
MX2010 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Copyright 2014, Juniper Networks, Inc.

iii

Interfaces Fundamentals for Routing Devices

MX2020 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

PTX3000 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
PTX5000 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
T320 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
T640 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
T1600 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
T4000 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
TX Matrix Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
TX Matrix Plus Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
TX Matrix Plus (with 3D SIBs) Supported Routing Engines . . . . . . . . . . . . . . 25
Interface Naming Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Physical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Logical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Separators in an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Channel Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Interface Naming for a Routing Matrix Based on a TX Matrix Router . . . . . . . 33
Interface Naming for a Routing Matrix Based on a TX Matrix Plus Router . . . 35
Chassis Interface Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Examples: Interface Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Interface Encapsulations Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Interface Descriptors Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Physical Part of an Interface Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Interface Names for ACX Series Universal Access Routers . . . . . . . . . . . . . . . 52
J Series Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Interface Names for M Series and T Series Routers . . . . . . . . . . . . . . . . . . . . 53
MX Series Router Interface Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Interface Names for PTX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Displaying Interface Configurations Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 2

Configuring Physical Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Physical Interface Configuration Statements Overview . . . . . . . . . . . . . . . . . . . . . 56
Physical Interfaces Properties Statements List . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Configuring Interface Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Expanding Interface Range Member and Member Range Statements . . . . . 86
Configuration Inheritance for Member Interfaces . . . . . . . . . . . . . . . . . . . . . . 88
Member Interfaces Inheriting Configuration from Configuration Groups . . . . 89
Interfaces Inheriting Common Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuring Inheritance Range Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configuration Expansion Where Interface Range Is Used . . . . . . . . . . . . . . . . 91
Specifying an Aggregated Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Configuring Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Configuring the Media MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Media MTU Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
How to Configure the Media MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Encapsulation Overhead by Encapsulation Type . . . . . . . . . . . . . . . . . . . . . . 96
Media MTU Sizes by Interface Type for M5 and M7i Routers with CFEB, M10
and M10i Routers with CFEB, and M20 and M40 Routers . . . . . . . . . . . . 97
Media MTU Sizes by Interface Type for M40e Routers . . . . . . . . . . . . . . . . . . 97

iv

Copyright 2014, Juniper Networks, Inc.

Table of Contents

Media MTU Sizes by Interface Type for M160 Routers . . . . . . . . . . . . . . . . . . 99

Media MTU Sizes by Interface Type for M7i Routers with CFEB-E, M10i
Routers with CFEB-E, and M320 and M120 Routers . . . . . . . . . . . . . . . . 99
Media MTU Sizes by Interface Type for MX Series Routers . . . . . . . . . . . . . . 100
Media MTU Sizes by Interface Type for T320 Routers . . . . . . . . . . . . . . . . . . 101
Media MTU Sizes by Interface Type for T640 Platforms . . . . . . . . . . . . . . . . 101
Media MTU Sizes by Interface Type for J2300 Platforms . . . . . . . . . . . . . . . 102
Media MTU Sizes by Interface Type for J4300 and J6300 Platforms . . . . . . 102
Media MTU Sizes by Interface Type for J4350 and J6350 Platforms . . . . . . 103
Media MTU Sizes by Interface Type for EX Series Switches and ACX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Media MTU Sizes by Interface Type for PTX Series Packet Transport
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuring the Interface Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configuring the Speed of Management Ethernet Interfaces on M Series and
T Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Configuring the Speed of Gigabit Ethernet Interfaces on J Series Routers . . 106
Configuring the Speed of Fast Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . 107
Configuring the Speed of Tri-Rate Ethernet Copper Interfaces . . . . . . . . . . . 107
Configuring the Speed of SONET/SDH Interfaces . . . . . . . . . . . . . . . . . . . . . 108
Configuring the Link Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Interface Alias Names Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Example: Adding an Interface Alias Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Clock Source Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Configuring the Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configuring Interface Encapsulation on Physical Interfaces . . . . . . . . . . . . . . . . . 117
Configuring the Encapsulation on a Physical Interface . . . . . . . . . . . . . . . . . . 117
Encapsulation Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Example: Configuring the Encapsulation on a Physical Interface . . . . . . 122
Configuring Interface Encapsulation on PTX Series Packet Transport
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Configuring Keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Configuring the PPP Challenge Handshake Authentication Protocol . . . . . . . . . 126
Assigning an Access Profile to an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Configuring a Default CHAP Secret . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuring the Local Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuring Passive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Example: Configuring the PPP Challenge Handshake Authentication
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuring the PPP Password Authentication Protocol . . . . . . . . . . . . . . . . . . . 129
Configuring the Local Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Configuring the Local Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Configuring Passive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Example: Configuring PAP Authentication Protocol . . . . . . . . . . . . . . . . . . . . 131
Configuring PPP Address and Control Field Compression . . . . . . . . . . . . . . . . . . 133
Configuring the PPP Protocol Field Compression . . . . . . . . . . . . . . . . . . . . . . . . . 135
Monitoring a PPP Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Tracing Operations of the pppd Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Configuring the Router as a DCE with Frame Relay Encapsulation . . . . . . . . . . . 138

Copyright 2014, Juniper Networks, Inc.

Interfaces Fundamentals for Routing Devices

Receive and Transmit Leaky Bucket Properties Overview . . . . . . . . . . . . . . . . . . 138

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network
Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Understanding Unidirectional Traffic Flow on Physical Interfaces . . . . . . . . . . . . 141
Enabling Unidirectional Traffic Flow on Physical Interfaces . . . . . . . . . . . . . . . . . 142
Physical Interface Damping Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Damping Overview for Shorter Physical Interface Transitions . . . . . . . . . . . . 143
Damping Overview for Longer Physical Interface Transitions . . . . . . . . . . . . 144
Damping Shorter Physical Interface Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Damping Longer Physical Interface Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Example: Configuring Physical Interface Damping . . . . . . . . . . . . . . . . . . . . . . . . . 151
Configuring Multiservice Physical Interface Properties . . . . . . . . . . . . . . . . . . . . . 153
Enabling or Disabling SNMP Notifications on Physical Interfaces . . . . . . . . . . . . 154
Configuring Accounting for the Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . 155
Applying an Accounting Profile to the Physical Interface . . . . . . . . . . . . . . . . 155
Example: Applying an Accounting Profile to the Physical Interface . . . . 155
Disabling a Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Example: Disabling a Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Chapter 3

Configuring Logical Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Logical Interfaces Configuration Properties Overview . . . . . . . . . . . . . . . . . . . . . 159
Logical Interfaces Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Logical Interfaces Statements List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Specifying the Logical Interface Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Adding a Logical Unit Description to the Configuration . . . . . . . . . . . . . . . . . . . . . 171
Configuring the Interface Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Configuring Interface Encapsulation on Logical Interfaces . . . . . . . . . . . . . . . . . . 172
Configuring the Encapsulation on a Logical Interface . . . . . . . . . . . . . . . . . . 173
Configuring Interface Encapsulation on PTX Series Packet Transport
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Configuring a Point-to-Point Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Configuring a Multipoint Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Configuring the PPP Restart Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Configuring the PPP Clear Loop Detected Timer . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Configuring the LCP Configure-Request Maximum Sent . . . . . . . . . . . . . . . . . . . . 177
Configuring the NCP Configure-Request Maximum Sent . . . . . . . . . . . . . . . . . . . 177
Configuring Dynamic Profiles for PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Configuring PPP CHAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Configuring PPP PAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Configuring a Default PAP Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Configuring the Local Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Configuring the Local Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Configuring Passive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Configuring Dynamic Call Admission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Example: Configuring Dynamic CAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Configuring Accounting for the Logical Interface . . . . . . . . . . . . . . . . . . . . . . . . . 182
Applying an Accounting Profile to the Logical Interface . . . . . . . . . . . . . . . . 182
Example: Applying an Accounting Profile to the Logical Interface . . . . . 183
Enabling or Disabling SNMP Notifications on Logical Interfaces . . . . . . . . . . . . . 183

vi

Copyright 2014, Juniper Networks, Inc.

Table of Contents

Disabling a Logical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Configuring Logical System Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . 184
Example: Configuring Logical System Interface Properties . . . . . . . . . . . . . . 185

Chapter 4

Configuring Protocol Family and Interface Address Properties . . . . . . . . . 187

Protocol Family Configuration and Interface Address Statements . . . . . . . . . . . . 187
Configuring the Protocol Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
IPv6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
IPv4-to-IPv6 Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
VRRP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Configuring the Interface Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Configuring Interface IPv4 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Operational Behavior of Interfaces when the Same IPv4 Address is
Assigned to Them . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Configuring Interface IPv6 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Configuring Default, Primary, and Preferred Addresses and Interfaces . . . . . . . . 197
Configuring the Primary Interface for the Router . . . . . . . . . . . . . . . . . . . . . . 197
Configuring the Primary Address for an Interface . . . . . . . . . . . . . . . . . . . . . 198
Configuring the Preferred Address for an Interface . . . . . . . . . . . . . . . . . . . . 198
Configuring ICCP for MC-LAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Configuring IPCP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Configuring an IP Address for an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Negotiating an IP Address Assignment from the Remote End . . . . . . . . . . . 201
Configuring an Interface to Be Unnumbered . . . . . . . . . . . . . . . . . . . . . . . . . 202
Assigning a Destination Profile to the Remote End . . . . . . . . . . . . . . . . . . . . 202
Configuring an Unnumbered Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Configuring an Unnumbered Point-to-Point Interface . . . . . . . . . . . . . . . . . 203
Example: Configuring an Unnumbered Point-to-Point Interface . . . . . 204
Configuring an Unnumbered Ethernet or Demux Interface . . . . . . . . . . . . . 204
Configuring a Preferred Source Address for Unnumbered Ethernet or
Demux Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Configuring Static Routes on Unnumbered Ethernet Interfaces . . . . . . 206
Restrictions for Configuring Unnumbered Ethernet Interfaces . . . . . . . 206
Example: Configuring an Unnumbered Ethernet Interface . . . . . . . . . . 207
Example: Configuring the Preferred Source Address for an Unnumbered
Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Example: Configuring an Unnumbered Ethernet Interface as the Next
Hop for a Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Setting the Protocol MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Disabling the Removal of Address and Control Bytes . . . . . . . . . . . . . . . . . . . . . 209
Disabling the Transmission of Redirect Messages on an Interface . . . . . . . . . . . . 210
Applying Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Applying Aggregate Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Example: Applying Aggregate Policers . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Applying Hierarchical Policers on Enhanced Intelligent Queuing PICs . . . . . 214
Hierarchical Policer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Hierarchical Policing Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Configuring Hierarchical Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Configuring a Single-Rate Two-Color Policer . . . . . . . . . . . . . . . . . . . . . 217

Copyright 2014, Juniper Networks, Inc.

vii

Interfaces Fundamentals for Routing Devices

Configuring a Single-Rate Tricolor Policer . . . . . . . . . . . . . . . . . . . . . . . . 217

Configuring a Two-Rate Tricolor Marker Policer . . . . . . . . . . . . . . . . . . . 218
Applying a Filter to an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Defining Interface Groups in Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Filter-Based Forwarding on the Output Interface . . . . . . . . . . . . . . . . . . . . . 222
Example: Applying a Filter to an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Configuring Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Unicast RPF and Default Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Unicast RPF Behavior with a Default Route . . . . . . . . . . . . . . . . . . . . . . 226
Unicast RPF Behavior Without a Default Route . . . . . . . . . . . . . . . . . . . 226
Unicast RPF with Routing Asymmetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Configuring Unicast RPF Strict Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Example: Configuring Unicast RPF Strict Mode . . . . . . . . . . . . . . . . . . . 228
Configuring Unicast RPF Loose Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Example: Configuring Unicast RPF Loose Mode . . . . . . . . . . . . . . . . . . 229
Configuring Unicast RPF Loose Mode with Ability to Discard Packets . . . . . 230
Example: Configuring Unicast RPF Loose Mode with Ability to Discard
Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Configuring Unicast RPF on a VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Example: Configuring Unicast RPF on a VPN . . . . . . . . . . . . . . . . . . . . . 232
Example: Configuring Unicast RPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Example: Configuring Unicast Reverse-Path-Forwarding Check . . . . . . . . . . . . . 234
Understanding Unicast Reverse Path Forwarding . . . . . . . . . . . . . . . . . . . . . 234
Example: Configuring Unicast Reverse-Path-Forwarding Check . . . . . . . . . 234
Enabling Source Class and Destination Class Usage . . . . . . . . . . . . . . . . . . . . . . 242
Examples: Enabling Source Class and Destination Class Usage . . . . . . . . . 246
Understanding Targeted Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configuring Targeted Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Configuring Targeted Broadcast and Its Options . . . . . . . . . . . . . . . . . . . . . . 251
Display Targeted Broadcast Configuration Options . . . . . . . . . . . . . . . . . . . . 252
Forward IP Packets On the Egress Interface and To the Routing
Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Forward IP Packets On the Egress Interface Only . . . . . . . . . . . . . . . . . 253

Chapter 5

Configuring Circuit and Translational Cross-Connects . . . . . . . . . . . . . . . . 255

Circuit and Translational Cross-Connects Overview . . . . . . . . . . . . . . . . . . . . . . 255
Defining the Encapsulation for Switching Cross-Connects . . . . . . . . . . . . . . . . . 257
Configuring PPP or Cisco HDLC Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Configuring ATM Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Configuring Frame Relay Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Configuring Ethernet CCC Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Configuring Ethernet VLAN Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Defining the Connection for Switching Cross-Connects . . . . . . . . . . . . . . . . . . . . 261
Configuring MPLS for Switching Cross-Connects . . . . . . . . . . . . . . . . . . . . . . . . . 261
Configuring IS-IS or MPLS Traffic for TCC Interfaces . . . . . . . . . . . . . . . . . . . . . . 261
Configuring ATM-to-Ethernet Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Enabling ATM-to-Ethernet Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Configuring the Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Configuring Ethernet Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

viii

Copyright 2014, Juniper Networks, Inc.

Table of Contents

Configuring the Outer VLAN Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Configuring the Inner VLAN Identifier Range . . . . . . . . . . . . . . . . . . . . . . . . . 264
Configuring the Physical Interface VPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Configuring the ATM Logical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Configuring the Protocol Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Configuring the Logical Interface VPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Configuring the Logical Interface VCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Example: Configuring a CCC over Frame Relay Encapsulated Interface . . . . . . . 266
Example: Configuring a TCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Example: Configuring CCC over Aggregated Ethernet . . . . . . . . . . . . . . . . . . . . . 268
Example: Configuring a Remote LSP CCC over Aggregated Ethernet . . . . . . . . . 270
Example: Configuring ATM-to-Ethernet Interworking . . . . . . . . . . . . . . . . . . . . . . 272

Part 2

Special Router Interfaces

Chapter 6

Configuring Discard Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Discard Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Understanding Discard Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Guidelines to Follow When Configuring a Discard Interface . . . . . . . . . . . . . 277
Configuring Discard Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Configure a Discard Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Configure an Input Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Configure an Output Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Chapter 7

Configuring IP Demultiplexing Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Demultiplexing Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
IP Demux Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
VLAN Demux Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Guidelines to Remember When Configuring A Demux Interface . . . . . . . . . 282
Points to Remember When Configuring an IP Demux Interface . . . . . . 282
Points to Remember When Configuring a VLAN Demux Interface . . . . 283
MAC Address Validation on Static Demux Interfaces . . . . . . . . . . . . . . . . . . 283
Loose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Strict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Configuring an IP Demultiplexing Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Configuring an IP Demux Underlying Interface . . . . . . . . . . . . . . . . . . . . . . . 284
Configuring the IP Demux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Configuring MAC Address Validation on Static IP Demux Interfaces . . . . . . 287
Configuring a VLAN Demultiplexing Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Configuring a VLAN Demux Underlying Interface . . . . . . . . . . . . . . . . . . . . . 288
Configuring the VLAN Demux Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Configuring MAC Address Validation on Static VLAN Demux Interfaces . . . 291
Verifying a Demux Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Chapter 8

Configuring the Loopback Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Configuring the Loopback Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Example: Configuring the Loopback Interface . . . . . . . . . . . . . . . . . . . . . . . 296

Copyright 2014, Juniper Networks, Inc.

ix

Interfaces Fundamentals for Routing Devices

Part 3

Serial Interfaces

Chapter 9

Serial Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Serial Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Chapter 10

Configuring Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Example: Physical Interface Configuration Statements for Serial Interfaces . . . 303
Configuring the Serial Line Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Serial Interface Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
EIA-530 Interface Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
V.35 Interface Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
X.21 Interface Default Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Invalid Serial Interface Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Invalid EIA-530 Interface Statements . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Invalid V.35 interface Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Invalid X.21 Interface Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Configuring the Serial Clocking Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Inverting the Serial Interface Transmit Clock . . . . . . . . . . . . . . . . . . . . . . . . 308
Configuring the DTE Clock Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Configuring the Serial Idle Cycle Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Configuring the Serial Signal Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Configuring the Serial DTR Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Configuring Serial Signal Polarities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Configuring Serial Loopback Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Example: Configuring Serial Loopback Capability . . . . . . . . . . . . . . . . . . . . . 315
Configuring Serial Line Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Specifying a USB Modem Interface on J Series Routers . . . . . . . . . . . . . . . . . . . . 316

Part 4

Monitoring and Troubleshooting Interfaces

Chapter 11

Monitoring Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Tracing Interface Operations Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Tracing Operations of an Individual Router Interface . . . . . . . . . . . . . . . . . . . . . . 321
Tracing Operations of the Interface Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Monitoring a PPP Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Tracing Operations of the pppd Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

Chapter 12

Troubleshooting Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Interface Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Configuring Loopback Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Interface Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Starting and Stopping a BERT Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Example: Configuring Bit Error Rate Testing . . . . . . . . . . . . . . . . . . . . . . 333
Troubleshooting: em0 Management Interface Link is Down . . . . . . . . . . . . . . . . 334
Troubleshooting: fxp0 Management Interface Link is Down . . . . . . . . . . . . . . . . 335
Troubleshooting: Faulty Ethernet Physical Interface on an M Series, an MX Series,
or a T Series Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Checking the Cable Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Checking the Physical Link Status of the Interface . . . . . . . . . . . . . . . . . . . . 338
Checking the Interface Statistics in Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

Copyright 2014, Juniper Networks, Inc.

Table of Contents

Performing the Loopback Diagnostic Test . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Checking Other Possibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
To Enable a Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

Part 5

Configuration Statements and Operational Commands

Chapter 13

Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

[edit chassis] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
[edit firewall] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
[edit interfaces] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
[edit logical-systems] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
[edit protocols connections] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
[edit protocols dot1x] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
[edit protocols iccp] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
[edit protocols lacp] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
[edit protocols oam] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
[edit protocols ppp] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
[edit protocols pppoe] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
[edit protocols protection-group] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . 394
[edit protocols vrrp] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
[edit system processes] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
802.3ad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
accept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
accept-source-mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
access-concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
access-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
accounting-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
acfc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
acknowledge-retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
acknowledge-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
action (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
action (Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
action-profile (Applying to CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
action-profile (Defining for CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
action-profile (Defining for LFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
action-red-differential-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
activation-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
activation-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
advertise-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
agent-specifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
aggregate (Gigabit Ethernet CoS Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
aggregate (Hierarchical Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
aggregate (SONET/SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
aggregate-ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
aggregated-ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
aggregated-sonet-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

Copyright 2014, Juniper Networks, Inc.

xi

Interfaces Fundamentals for Routing Devices

alarm (optics-options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

alias (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
allow-any-vci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
allow-fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
allow-remote-loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
apply-action-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
aps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
arp (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
asynchronous-notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
atm-encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
atm-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
atm-scheduler-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
authentication-profile-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
authenticator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
auto-configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
auto-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
auto-negotiation (J Series uPIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
auto-reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
backup-destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
backup-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
backup-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
bandwidth (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
bandwidth-limit (Hierarchical Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
bandwidth-limit (Policer for Gigabit Ethernet Interfaces) . . . . . . . . . . . . . . . . . . 441
bchannel-allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
bearer-bandwidth-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
bert-algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
bert-error-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
bert-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
bridge-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
buildout (E3 or T3 over ATM Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
buildout (T1 Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
burst-size-limit (Hierarchical Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
burst-size-limit (Policer for Gigabit Ethernet Interfaces) . . . . . . . . . . . . . . . . . . . 454
byte-encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
calculation-weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
callback-wait-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
caller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
calling-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
cbit-parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
cbr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462

xii

Copyright 2014, Juniper Networks, Inc.

Table of Contents

cell-bundle-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
chap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
chap-secret . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
circuit-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
cisco-interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
classifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
clear-dont-fragment-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
clock-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
clocking-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
community (Policy Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
compatibility-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
compression (PPP Properties) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
compression (Voice Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
compression-device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
connection-protection-tlv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
connectivity-fault-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
container-devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
container-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
container-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
container-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
continuity-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
control-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
control-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
control-signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
copy-tos-to-outer-ip-header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
core-dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
crc-major-alarm-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
crc-minor-alarm-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
cts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
cts-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
cycle-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
damping (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
data-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
data-input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
data-tlv-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
dcd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
dcd-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
dce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
dce-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
deactivation-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
default-actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
default-chap-secret . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
default-pap-password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
delimiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
demux-destination (Underlying Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

Copyright 2014, Juniper Networks, Inc.

xiii

Interfaces Fundamentals for Routing Devices

demux-destination (Demux Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

demux-options (Static Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
demux-source (Demux Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
demux-source (Underlying Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
demux0 (Static Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
demux0 (Dynamic Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
description (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
destination (IPCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
destination (Routing Instance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
destination (Tunnels) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
destination-class-usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
destination-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
dial-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
dial-string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
dialer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
dialer-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
dialin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
disable (Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
disable (Link Protection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
disable-mlppp-inner-ppp-pfc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
dlci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
do-not-fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
domain-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
dot1x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
down-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
drop (PPPoE Service Name Tables) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
drop-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
ds0-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
dsl-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
dsr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
dsr-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
dte-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
dtr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
dtr-circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
dtr-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
dump-on-flow-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
dynamic-call-admission-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
dynamic-profile (PPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
dynamic-profile (PPPoE Service Name Tables) . . . . . . . . . . . . . . . . . . . . . . . . . . 528
dynamic-profile (Stacked VLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
dynamic-profile (VLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
dynamic-profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
e1-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
e3-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
east-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
egress-policer-overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
encapsulation (Container Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
encapsulation (Logical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543

xiv

Copyright 2014, Juniper Networks, Inc.

Table of Contents

encapsulation (Physical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
epd-threshold (Logical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
epd-threshold (Physical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
es-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
ethernet (Protocols OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
ethernet-policer-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
ethernet-ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
ethernet-switch-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
eui-64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
evcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
event (LFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
event-thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
fast-aps-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
f-max-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
facility-override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
failover-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
family (Dynamic Standard Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
fastether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
fcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
feac-loop-respond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
filter (Applying to an Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
flexible-vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
flow-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
flow-control-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
force . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
forward-and-send-to-re . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
forwarding-class (ATM2 IQ Scheduler Maps) . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
forwarding-class (Gigabit Ethernet IQ Classifier) . . . . . . . . . . . . . . . . . . . . . . . . . 581
forward-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
fragment-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
frame-error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
frame-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
frame-period-summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
framing (E1, E3, and T1 Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
framing (10-Gigabit Ethernet Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
framing (SONET and SDH Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
gigether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
gratuitous-arp-reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
guard-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
hardware-assisted-timestamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
high-plp-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
hello-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
hierarchical-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
hierarchical-scheduler (Subscriber Interfaces on MX Series Routers) . . . . . . . . 595
high-plp-max-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
high-plp-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

Copyright 2014, Juniper Networks, Inc.

xv

Interfaces Fundamentals for Routing Devices

hold-interval (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

hold-interval (Protection Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
hold-time (APS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
hold-time (Physical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
hold-time (SONET/SDH Defect Triggers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
host (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
iccp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
idle-cycle-flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
idle-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
ieee802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
if-exceeding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
igmp-snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
ignore-all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
ignore-l3-incompletes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
ilmi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
ima-group-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
ima-link-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
inactivity-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
incoming-called-number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
incoming-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
indication-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
ingress-policer-overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
ingress-rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
init-command-string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
initial-route-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
inner-tag-protocol-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
inner-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
inner-vlan-id-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
input-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
input-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
input-priority-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
input-three-color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
input-vlan-map (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
input-vlan-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
interface (Hierarchical CoS Schedulers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
interface (IEEE 802.1x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
interface (IEEE 802.1ag OAM Connectivity-Fault Management) . . . . . . . . . . . . 630
interface (OAM Link-Fault Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
interface (Port Mirroring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
interface-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
interface-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
interface-none . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
interface-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
interface-transmit-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
interface-set (Ethernet Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

xvi

Copyright 2014, Juniper Networks, Inc.

Table of Contents

interface-set (IP Demux Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

interface-shared-with . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
interface-status-tlv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
interface-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
interface-type (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
interfaces (Static and Dynamic Subscribers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
interleave-fragments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
inverse-arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
invert-data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
ipsec-sa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
isdn-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
iteration-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
iteration-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
keep-address-and-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
l2tp-interface-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
lacp (802.3ad) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
lacp (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
layer2-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
lcp-max-conf-req . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
lcp-restart-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
line-encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
line-protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
line-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
linear-red-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
linear-red-profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
link-adjacency-loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
link-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
link-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
link-event-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
link-fault-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
link-layer-overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
link-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
link-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
link-speed (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
link-speed (Aggregated SONET/SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
linktrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
lmi (Frame Relay) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
lmi (Ethernet OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
lmi-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
load-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
load-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
local-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
local-password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681

Copyright 2014, Juniper Networks, Inc.

xvii

Interfaces Fundamentals for Routing Devices

log-prefix (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

logical-interface-fpc-redundancy (Aggregated Ethernet Subscriber
Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
logical-interface-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
logical-systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
long-buildout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
loop-timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3) . . . . . . . . . . . . 686
loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) . . . . . . . 688
loopback (Serial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
loopback-clear-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
loss-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
loss-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
low-plp-max-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
low-plp-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
lowest-priority-defect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
lsq-failure-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
mac-address (Accept Source Mac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
mac-address (VLAN and Stacked VLAN Interfaces) . . . . . . . . . . . . . . . . . . . . . . 695
mac-learn-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
mac-validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
maintenance-association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
maintenance-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
master-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
maximum-contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
maximum-requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
maximum-vcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
mc-ae . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
member-interface-speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
member-interface-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
mep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
minimum-links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
mip-half-function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
mlfr-uni-nni-bundle-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
mode (Dynamic Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
mode (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
modem-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
monitor-session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
mpls (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
mrru . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
multi-chassis-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
multicast-dlci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
multicast-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
multicast-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
multicast-vci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
multilink-max-classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
multipoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

xviii

Copyright 2014, Juniper Networks, Inc.

Table of Contents

multipoint-destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
multiservice-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
n391 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
n392 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
n393 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
name-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
native-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
ncp-max-conf-req . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
ncp-restart-timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
nd6-stale-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
negotiate-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
negotiation-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
neighbor (Automatic Protection Switching for SONET/SDH) . . . . . . . . . . . . . . . 735
no-allow-link-events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
no-aggregate-delegate-processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
asynchronous-notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
no-auto-mdix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
auto-negotiation (J Series uPIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
cbit-parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
core-dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
feac-loop-respond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
flow-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
gratuitous-arp-reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
no-gratuitous-arp-request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
no-keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
long-buildout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) . . . . . . . . 746
mac-learn-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
no-partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
payload-scrambler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
no-pre-classifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
no-redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
source-filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
syslog (Monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
no-termination-request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
translate-discard-eligible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
translate-fecn-and-becn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
unframed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
z0-increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
node-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
non-revertive (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
oam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
oam-liveness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
oam-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
oc-slice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
open-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
operating-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
optics-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765

Copyright 2014, Juniper Networks, Inc.

xix

Interfaces Fundamentals for Routing Devices

option-82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
otn-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
output-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
output-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
output-priority-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
output-three-color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
output-vlan-map (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
output-vlan-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
overflow (Receive Bucket) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
overflow (Transmit Bucket) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
pado-advertise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
paired-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
pap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
pap-password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
passive (CHAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
passive (PAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
passive-monitor-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
password (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
path-database-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
path-trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
payload-scrambler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
payload-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
pdu-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
pdu-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
peer-unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
per-unit-scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
performance-monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
periodic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
pfc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
pic-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
plp-to-clp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
plp1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
point-to-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
policer (CFM Firewall) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
policer (CFM Global) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
policer (CFM Session) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
policer (CoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
policer (Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
policer (MAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
policy-statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801
pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
pop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
pop-all-labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
pop-pop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
pop-swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809

xx

Copyright 2014, Juniper Networks, Inc.

Table of Contents

port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
port-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
port-status-tlv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
post-service-filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
ppp-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
pppoe-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
pppoe-underlying-options (Static and Dynamic Subscribers) . . . . . . . . . . . . . . 814
preferred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
preferred-source-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
premium (Hierarchical Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
premium (Output Priority Map) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
premium (Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
preserve-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
primary (Address on Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
primary (AS PIC or Multiservices PIC Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . 820
priority (OAM Connectivity-Fault Management) . . . . . . . . . . . . . . . . . . . . . . . . . . 821
priority (Schedulers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
promiscuous-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
protect-circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
protection-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
protocol-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
proxy-arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
push-push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
queue-depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
queue-length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
quiet-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
radius-realm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
ranges (Dynamic Stacked VLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
ranges (Dynamic VLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
rdi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
reassemble-packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
receive-bucket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
receive-options-packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
receive-ttl-exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
red-differential-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
redial-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
redundancy-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
remote-loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
remote-loopback-respond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
remote-mep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
remove-when-no-subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844

Copyright 2014, Juniper Networks, Inc.

xxi

Interfaces Fundamentals for Routing Devices

request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
required-depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
restore-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
revert-time (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
revertive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
rfc-2615 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
ring-protection-link-end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
ring-protection-link-owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
routing-instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
routing-instance (PPPoE Service Name Tables) . . . . . . . . . . . . . . . . . . . . . . . . . 852
rpf-check (Dynamic Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
rpf-check (interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
rpf-loose-mode-discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
rtp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
rts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
rts-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
rtvbr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
sa-multicast (100-Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
sampling (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
satop-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
shared-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
scheduler-maps (For ATM2 IQ Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
schedulers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
secondary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
send-critical-event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
serial-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
server-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
service (Logical Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
service (PPPoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
service-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
service-filter (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
service-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
service-name-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
service-name-tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
service-set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
services (Priority Level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
services-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
shdsl-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
short-name-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
short-sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
sla-iterator-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
sla-iterator-profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
snext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882
snr-margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
sonet-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886

xxii

Copyright 2014, Juniper Networks, Inc.

Table of Contents

source-address-filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
source-class-usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
source-filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
speed (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
speed (MX Series DPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
speed (SONET/SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
spid1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
spid2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
stacked-vlan-ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
stacked-vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
start-end-flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
static-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
static-tei-val . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
supplicant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
supplicant-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
swap-push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
swap-swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
switch-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
switch-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
switch-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
switching-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
symbol-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
syslog (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
syslog (Monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
syslog (OAM Action) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
system-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
t1-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
t310 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
t391 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
t392 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
t3-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913
tag-protocol-id (TPIDs Expected to Be Sent or Received) . . . . . . . . . . . . . . . . . . 914
tag-protocol-id (TPID to Rewrite) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
targeted-broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
targeted-distribution (Static Interfaces over Aggregated Ethernet) . . . . . . . . . . . 917
tei-option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
terminate (PPPoE Service Name Tables) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
then . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
tm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
tm-polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
traceoptions (Individual Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
traceoptions (Interface Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
traceoptions (LACP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
traceoptions (PPP Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
traceoptions (PPPoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
translate-discard-eligible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933

Copyright 2014, Juniper Networks, Inc.

xxiii

Interfaces Fundamentals for Routing Devices

translate-fecn-and-becn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
translate-plp-control-word-de . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
transmit-bucket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
transmit-clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
transmit-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
transmit-weight (ATM2 IQ CoS Forwarding Class) . . . . . . . . . . . . . . . . . . . . . . . 937
transmit-weight (ATM2 IQ Virtual Circuit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
trigger-link-failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
trunk-bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 940
trunk-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
underlying-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943
unframed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
unidirectional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
unit (Dynamic Profiles Standard Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945
unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
unnumbered-address (Demux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
unnumbered-address (Dynamic Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
unnumbered-address (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
unnumbered-address (PPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958
up-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
user-prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
username-include . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
vbr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
vc-cos-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
vci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
vci-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
virtual-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
vlan-id (Logical Port in Bridge Domain) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
vlan-id (Outer VLAN ID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
vlan-id (VLAN ID to Be Bound to a Logical Interface) . . . . . . . . . . . . . . . . . . . . . 967
vlan-id (VLAN ID to Rewrite) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
vlan-id-list (Ethernet VLAN Circuit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
vlan-id-list (Interface in Bridge Domain) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
vlan-id-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
vlan-ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
vlan-rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
vlan-rule (100-Gigabit Ethernet Type 4 PIC with CFP) . . . . . . . . . . . . . . . . . . . . 974
vlan-steering (100-Gigabit Ethernet Type 4 PIC with CFP) . . . . . . . . . . . . . . . . . 975
vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
vlan-tags (Dual-Tagged Logical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
vlan-tags (Stacked VLAN Tags) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
vlan-tags-outer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
vlan-vci-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
vpi (ATM CCC Cell-Relay Promiscuous Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
vpi (Define Virtual Path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982

xxiv

Copyright 2014, Juniper Networks, Inc.

Table of Contents

vpi (Logical Interface and Interworking) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983

vtmapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
watch-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
wavelength . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
west-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
working-circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
yellow-differential-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
z0-increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992

Chapter 14

Interface Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993

Common Output Fields Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Damping Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Destination Class Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Enabled Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Filters Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Flags Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Addresses, Flags Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Device Flags Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Family Flags Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Interface Flags Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Link Flags Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Logical Interface Flags Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
Label-Switched Interface Traffic Statistics Field . . . . . . . . . . . . . . . . . . . . . 999
Policer Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
Protocol Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
RPF Failures Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
Source Class Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
Improvements to Interface Transmit Statistics Reporting . . . . . . . . . . . . . . . . . 1001
show interfaces (10-Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
show interfaces (ATM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
show interfaces (ATM-over-ADSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
show interfaces (ATM-over-SHDSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
show interfaces (Channelized DS3-to-DS0) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079
show interfaces (Channelized DS3-to-DS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1090
show interfaces (Channelized E1 IQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
show interfaces (Channelized E1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
show interfaces (Channelized OC12 IQ and IQE) . . . . . . . . . . . . . . . . . . . . . . . . . 1108
show interfaces (Channelized OC12) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
show interfaces (Channelized OC3 IQ and IQE) . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
show interfaces (Channelized STM1 IQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1135
show interfaces (Channelized STM1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
show interfaces (Channelized T1 IQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
show interfaces (Channelized T3 IQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
show interfaces (Discard) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
show interfaces (Fast Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
show interfaces (Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
show interfaces (ISDN B-Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1213
show interfaces (ISDN BRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219

Copyright 2014, Juniper Networks, Inc.

xxv

Interfaces Fundamentals for Routing Devices

show interfaces (ISDN D-channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1223

show interfaces (ISDN Dialer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1229
show interfaces (M Series, MX Series and T Series Routers, and PTX Series
Packet Transport Routers Management and Internal Ethernet) . . . . . . . . . 1239
show interfaces (PPPoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255
show interfaces (PTX Series Packet Transport Routers) . . . . . . . . . . . . . . . . . . 1266
show interfaces (SONET/SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1280
show interfaces (Serial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1308
show interfaces (T1, E1, or DS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1321
show interfaces (T3 or E3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346
show interfaces demux0 (Demux Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
show interfaces extensive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1372
show interfaces lsi (Label-Switched Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . 1401
show interfaces media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404
show interfaces terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407

Chapter 15

ANCP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1411

clear ancp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1412
clear ancp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414
clear ancp subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1416
request ancp oam interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1418
request ancp oam neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1419
show ancp cos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1420
show ancp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
show ancp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1433
show ancp subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1438
show ancp summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1443
show ancp summary neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1445
show ancp summary subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1447

Chapter 16

BFD Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1449

clear bfd adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1450
clear bfd session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
show bfd session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1452

Chapter 17

BGP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461

clear bgp damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1462
clear bgp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1463
clear bgp table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465
show bgp bmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
show bgp group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469
show bgp group traffic-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1476
show bgp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478
show bgp replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1492
show bgp summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1495
show policy damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501

Chapter 18

ES-IS Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503

clear esis adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504
clear esis statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1505

xxvi

Copyright 2014, Juniper Networks, Inc.

Table of Contents

show esis adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506

show esis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508
show esis statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1510

Chapter 19

IP Multicast Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513

clear amt statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516
clear amt tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517
clear igmp membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1518
clear igmp snooping membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521
clear igmp snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522
clear igmp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1523
clear mld membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1525
clear mld statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526
clear msdp cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1527
clear msdp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1528
clear multicast bandwidth-admission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1529
clear multicast forwarding-cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1531
clear multicast scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532
clear multicast sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1533
clear multicast snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534
clear multicast statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1535
clear pgm negative-acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1536
clear pgm source-path-messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1537
clear pgm statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538
clear pim join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1539
clear pim join-distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541
clear pim register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543
clear pim snooping join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545
clear pim snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1547
clear pim statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1549
request pim multicast-tunnel rebalance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1552
show amt statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553
show amt summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
show amt tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
show dvmrp interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
show dvmrp neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1563
show dvmrp prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565
show dvmrp prunes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1567
show igmp group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569
show igmp interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573
show igmp snooping interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1577
show igmp snooping membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1582
show igmp snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1586
show igmp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591
show mld group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594
show mld interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598
show mld statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
show msdp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1605
show msdp source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1607

Copyright 2014, Juniper Networks, Inc.

xxvii

Interfaces Fundamentals for Routing Devices

show msdp source-active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1609

show msdp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1612
show multicast backup-pe-groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1616
show multicast flow-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1618
show multicast forwarding-cache statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1620
show multicast interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1622
show multicast mrinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624
show multicast next-hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1626
show multicast pim-to-igmp-proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1629
show multicast pim-to-mld-proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631
show multicast route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1633
show multicast rpf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1640
show multicast scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644
show multicast snooping next-hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1646
show multicast sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1648
show multicast snooping route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651
show multicast statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655
show multicast usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1658
show pgm negative-acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661
show pgm source-path-messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1664
show pgm statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1666
show pim bootstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670
show pim interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1672
show pim join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675
show pim mdt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
show pim mdt data-mdt-joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701
show pim mdt data-mdt-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1703
show pim neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705
show pim rps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709
show pim snooping interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1716
show pim snooping join . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719
show pim snooping neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1723
show pim snooping statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728
show pim source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1733
show pim statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1736
show sap listen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1749
test msdp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751

Chapter 20

IPv6 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753

clear ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754
clear ipv6 router-advertisement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1755
show ipv6 neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1756
show ipv6 router-advertisement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1758

Chapter 21

IS-IS Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761

clear isis adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1762
clear isis database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764
clear isis overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1766
clear isis statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1768
show isis adjacency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1770

xxviii

Copyright 2014, Juniper Networks, Inc.

Table of Contents

show isis authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774

show isis backup coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1776
show isis backup label-switched-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1778
show isis backup spf results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1780
show isis context-identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1783
show isis database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1785
show isis hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797
show isis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1799
show isis overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1803
show isis route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1806
show isis spf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1810
show isis statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1815

Chapter 22

LLDP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1819

clear lldp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1820
clear lldp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1821
show lldp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1822
show lldp local-information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1825
show lldp neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1828
show lldp remote-global-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834
show lldp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1836

Chapter 23

MVRP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839

show mvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840
show mvrp applicant-state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1842
show mvrp dynamic-vlan-memberships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1844
show mvrp interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1845
show mvrp registration-state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846
show mvrp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1848

Chapter 24

OSPF Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1851

clear (ospf | ospf3) database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1852
clear (ospf | ospf3) io-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1855
clear (ospf | ospf3) neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1856
clear (ospf | ospf3) overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1858
clear (ospf | ospf3) statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1859
show (ospf | ospf3) backup coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1861
show (ospf | ospf3) backup lsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1864
show (ospf | ospf3) backup neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1866
show (ospf | ospf3) backup spf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1868
show ospf context-identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1875
show ospf database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1877
show ospf3 database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1886
show (ospf | ospf3) interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1897
show (ospf | ospf3) io-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1903
show (ospf | ospf3) log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905
show (ospf | ospf3) neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1908
show (ospf | ospf3) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914
show (ospf | ospf3) route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1919
show (ospf | ospf3) statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925

Copyright 2014, Juniper Networks, Inc.

xxix

Interfaces Fundamentals for Routing Devices

Chapter 25

Protocol-Independent Routing Operational Commands . . . . . . . . . . . . . 1929

show as-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1931
show as-path domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935
show as-path summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1938
show route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1940
show route active-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1946
show route advertising-protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1951
show route all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1956
show route aspath-regex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1958
show route best . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1960
show route brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1963
show route ccc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965
show route community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1966
show route community-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1968
show route damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1970
show route detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975
show route exact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992
show route export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1994
show route export vrf-target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1997
show route extensive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1999
show route flow validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2016
show route forwarding-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2018
show route forwarding-table interface-name . . . . . . . . . . . . . . . . . . . . . . . . . . 2032
show route hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035
show route inactive-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2038
show route inactive-prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2041
show route instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2043
show route label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2051
show route label-switched-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2054
show route localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2056
show route martians . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2058
show route match-prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2060
show route next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2061
show route no-community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2067
show route output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2070
show route protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075
show route range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087
show route receive-protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2091
show route resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2099
show route snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2102
show route source-gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2105
show route summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
show route table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2115
show route terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2129

Chapter 26

RIP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2133

clear rip general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2134
clear rip statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2135
show rip general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2136

xxx

Copyright 2014, Juniper Networks, Inc.

Table of Contents

show rip neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2138

show rip statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2140

Chapter 27

RIPng Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2143

clear ripng general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2144
clear ripng statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2145
show ripng general-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2146
show ripng neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2148
show ripng statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2150

Chapter 28

Firewall Filter Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2153

clear firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154
show firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2156
show firewall filter version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2163
show firewall log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2164
show firewall prefix-action-stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2167
show firewall templates-in-use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2169
show policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2171

Chapter 29

Layer 2 Bridging and Switching Operational Commands . . . . . . . . . . . . . . 2175

clear bridge mac-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2176
clear error bpdu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2177
clear error mac-rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2178
show bridge domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2179
show bridge flood . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2181
show bridge mac-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2188
show bridge statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2192
show l2-learning global-information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2195
show l2-learning global-mac-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2197
show l2-learning instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2198
show l2-learning interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2200
show mac-rewrite interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2202

Chapter 30

VPN Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2205

clear vpls mac-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2206
clear vpls mac-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2207
request l2circuit-switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2208
show dynamic-tunnels database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2209
show hfrr profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2212
show ingress-replication mvpn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2214
show l2circuit connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2216
show l2vpn connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2223
show mvpn c-multicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2229
show mvpn instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2231
show mvpn neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2235
show vpls connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2239
show vpls flood event-queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2251
show vpls flood instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2253
show vpls flood route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2255
show vpls mac-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2257

Copyright 2014, Juniper Networks, Inc.

xxxi

Interfaces Fundamentals for Routing Devices

show vpls statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2262

Part 6

Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2267

xxxii

Copyright 2014, Juniper Networks, Inc.

List of Figures
Part 1

Router Interfaces

Chapter 1

Router Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 1: APS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2: Container Interface . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3: Routing Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4: Routing Matrix Based on a TX Matrix Plus Router .
Figure 5: Interface Slot, PIC, and Port Locations . . . . . . . . . .

Chapter 2

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.8
.9
34
36
39

Configuring Physical Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 6: Two Router Interfaces Connected Through Transport Equipment . . . . 143
Figure 7: Multiple Flaps of Short Duration (Milliseconds) . . . . . . . . . . . . . . . . . . . 144
Figure 8: Periodic Flaps of Long Duration (Seconds) . . . . . . . . . . . . . . . . . . . . . . 145
Figure 9: Physical-Level Link Is Down When the Penalty Falls Below the Reuse
Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 10: Physical-Level Link Is Up When the Penalty Falls Below the Reuse
Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Chapter 4

Configuring Protocol Family and Interface Address Properties . . . . . . . . . 187

Figure 11: Hierarchical Policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 12: Unicast RPF with Routing Asymmetry . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 13: Unicast RPF Sample Topoolgy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 14: Prefix Accounting with Source and Destination Classes . . . . . . . . . . . 243

Chapter 5

Configuring Circuit and Translational Cross-Connects . . . . . . . . . . . . . . . . 255

Figure 15: Layer 2 Switching Circuit Cross-Connect . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 16: Example Topology of a Switching Circuit Cross-Connect with Frame
Relay CCC Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Figure 17: Layer 2.5 Switching Translational Cross-Connect . . . . . . . . . . . . . . . . . 267
Figure 18: Interface-to-Interface Circuit Cross-Connect over Aggregated
Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 19: Remote Interface-LSP-Interface Circuit Cross-Connect over Aggregated
Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Figure 20: ATM-to-Ethernet Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Part 3

Serial Interfaces

Chapter 10

Configuring Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Figure 21: Serial Interface Clocking Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Figure 22: Serial Interface LIU Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Figure 23: Serial Interface Local Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Copyright 2014, Juniper Networks, Inc.

xxxiii

Interfaces Fundamentals for Routing Devices

xxxiv

Copyright 2014, Juniper Networks, Inc.

List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xliii
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlvi
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlvi

Part 1

Router Interfaces

Chapter 1

Router Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Table 3: M7i Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 4: M10I Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 5: M40e Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 6: M120 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 7: M320 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 8: MX104 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 9: MX240 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 10: MX480 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 11: MX960 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 12: MX2010 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 13: MX2020 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 14: PTX3000 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 15: PTX5000 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 16: T320 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 17: T640 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 18: T1600 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 19: T4000 Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 20: TX Matrix Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 21: TX Matrix Plus Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . 25
Table 22: Routing Engines Supported on TX Matrix Plus with 3D SIBs . . . . . . . . . 26
Table 23: FPC Numbering for T640 Routers in a Routing Matrix . . . . . . . . . . . . . . 35
Table 24: One-to-One FPC Numbering for T640 Routers in a Routing Matrix . . . 35
Table 25: FPC Numbering for T1600 Routers in a Routing Matrix . . . . . . . . . . . . . 37
Table 26: One-to-One FPC Numbering for T1600 Routers in a Routing Matrix . . . 37
Table 27: Encapsulation Support by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 2

Configuring Physical Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Table 28: Statements for Physical Interface Properties . . . . . . . . . . . . . . . . . . . . . 66
Table 29: Encapsulation Overhead by Encapsulation Type . . . . . . . . . . . . . . . . . . 96
Table 30: Media MTU Sizes by Interface Type for M5 and M7i Routers with CFEB,
M10 and M10i Routers with CFEB, and M20 and M40 Routers . . . . . . . . . . . . 97
Table 31: Media MTU Sizes by Interface Type for M40e Routers . . . . . . . . . . . . . . 97
Table 32: Media MTU Sizes by Interface Type for M160 Routers . . . . . . . . . . . . . . 99

Copyright 2014, Juniper Networks, Inc.

xxxv

Interfaces Fundamentals for Routing Devices

Table 33: Media MTU Sizes by Interface Type for M7i Routers with CFEB-E, M10i
Routers with CFEB-E, and M320 and M120 Routers . . . . . . . . . . . . . . . . . . . . 99
Table 34: Media MTU Sizes by Interface Type for MX Series Routers . . . . . . . . . 100
Table 35: Media MTU Sizes by Interface Type for T320 Routers . . . . . . . . . . . . . . 101
Table 36: Media MTU Sizes by Interface Type for T640 Platforms . . . . . . . . . . . . 101
Table 37: Media MTU Sizes by Interface Type for J2300 Platforms . . . . . . . . . . . 102
Table 38: Media MTU Sizes by Interface Type for J4300 and J6300
Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Table 39: Media MTU Sizes by Interface Type for J4350 and J6350
Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Table 40: Media MTU Sizes by Interface Type for EX Series Switches and ACX
Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Table 41: Media MTU Sizes by Interface Type for PTX Series Packet Transport
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Table 42: Type 1 PIC Mode Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 43: Type 2 PIC Mode Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 44: Effect of set interfaces disable <interface_name> on T series PICs . . 156

Chapter 3

Configuring Logical Interface Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Table 45: Statements for Logical Interface Properties . . . . . . . . . . . . . . . . . . . . . 163

Part 3

Serial Interfaces

Chapter 10

Configuring Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

Table 46: Signal Handling by Serial Interface Type . . . . . . . . . . . . . . . . . . . . . . . . 310

Part 4

Monitoring and Troubleshooting Interfaces

Chapter 12

Troubleshooting Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

Table 47: Loopback Modes by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Table 48: BERT Capabilities by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

Part 5

Configuration Statements and Operational Commands

Chapter 14

Interface Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993

Table 49: show interfaces Gigabit Ethernet Output Fields . . . . . . . . . . . . . . . . . 1004
Table 50: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
Table 51: ATM show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
Table 52: ATM-over-ADSL show interfaces Output Fields . . . . . . . . . . . . . . . . . 1063
Table 53: ATM-over-SHDSL show interfaces Output Fields . . . . . . . . . . . . . . . . 1072
Table 54: Channelized DS3 show interfaces Output Fields . . . . . . . . . . . . . . . . 1079
Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output
Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
Table 56: Channelized OC show interfaces Output Fields . . . . . . . . . . . . . . . . . . 1117
Table 57: Channelized STM1 show interfaces Output Fields . . . . . . . . . . . . . . . . 1138
Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields . . . . . . . . 1153
Table 59: Discard show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1167
Table 60: show interfaces Fast Ethernet Output Fields . . . . . . . . . . . . . . . . . . . . 1172
Table 61: show interfaces Gigabit Ethernet Output Fields . . . . . . . . . . . . . . . . . . 1190

xxxvi

Copyright 2014, Juniper Networks, Inc.

List of Tables

Table 62: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
Table 63: ISDN B-Channel show interfaces Output Fields . . . . . . . . . . . . . . . . . . 1213
Table 64: ISDN BRI show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1219
Table 65: ISDN D-Channel show interfaces Output Fields . . . . . . . . . . . . . . . . . 1223
Table 66: ISDN Dialer show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . 1229
Table 67: M Series and T Series Router Management and Internal Ethernet show
interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
Table 68: show interfaces (PPPoE) Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1255
Table 69: show interfaces PTX Series Output Fields . . . . . . . . . . . . . . . . . . . . . . 1267
Table 70: SONET/SDH show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . 1281
Table 71: show interfaces (Serial) Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1308
Table 72: T1 or E1 show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1322
Table 73: T3 or E3 show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 1346
Table 74: Demux show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1363
Table 75: Logical Tunnel show interfaces Output Fields . . . . . . . . . . . . . . . . . . . 1401
Table 76: show interfaces terse Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1407

Chapter 15

ANCP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1411

Table 77: show ancp cos Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1420
Table 78: show ancp neighbor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425
Table 79: show ancp statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1433
Table 80: show ancp subscriber Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1438
Table 81: show ancp summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1443
Table 82: show ancp summary neighbor Output Fields . . . . . . . . . . . . . . . . . . . 1445
Table 83: show ancp summary subscriber Output Fields . . . . . . . . . . . . . . . . . . 1447

Chapter 16

BFD Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1449

Table 84: show bfd session Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1453

Chapter 17

BGP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1461

Table 85: show bgp bmp Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1467
Table 86: show bgp group Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1470
Table 87: show bgp group traffic-statistics Output Fields . . . . . . . . . . . . . . . . . 1476
Table 88: show bgp neighbor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
Table 89: show bgp replication Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1492
Table 90: show bgp summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496
Table 91: show policy damping Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1502

Chapter 18

ES-IS Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1503

Table 92: show esis adjacency Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506
Table 93: show esis interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508
Table 94: show esis statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1510

Chapter 19

IP Multicast Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1513

Table 95: show amt statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1553
Table 96: show amt summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1556
Table 97: show amt tunnel Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558
Table 98: show dvmrp interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1561
Table 99: show dvmrp neighbors Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1563
Table 100: show dvmrp prefix Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1565

Copyright 2014, Juniper Networks, Inc.

xxxvii

Interfaces Fundamentals for Routing Devices

Table 101: show dvmrp prunes Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1567

Table 102: show igmp group Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1569
Table 103: show igmp interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1573
Table 104: show igmp snooping interface Output Fields . . . . . . . . . . . . . . . . . . . 1577
Table 105: show igmp snooping membership Output Fields . . . . . . . . . . . . . . . 1582
Table 106: show igmp snooping statistics Output Fields . . . . . . . . . . . . . . . . . . 1586
Table 107: show igmp statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591
Table 108: show mld group Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594
Table 109: show mld interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1598
Table 110: show mld statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1602
Table 111: show msdp Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1605
Table 112: show msdp source Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1608
Table 113: show msdp source-active Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1610
Table 114: show msdp statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1612
Table 115: show multicast backup-pe-groups Output Fields . . . . . . . . . . . . . . . . 1616
Table 116: show multicast flow-map Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1618
Table 117: show multicast forwarding-cache statistics Output Fields . . . . . . . . 1620
Table 118: show multicast interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1622
Table 119: show multicast mrinfo Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1624
Table 120: show multicast next-hops Output Fields . . . . . . . . . . . . . . . . . . . . . . 1627
Table 121: show multicast pim-to-igmp-proxy Output Fields . . . . . . . . . . . . . . . 1629
Table 122: show multicast pim-to-mld-proxy Output Fields . . . . . . . . . . . . . . . . 1631
Table 123: show multicast route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1634
Table 124: show multicast rpf Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1641
Table 125: show multicast scope Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1644
Table 126: show multicast snooping next-hops Output Fields . . . . . . . . . . . . . . 1646
Table 127: show multicast sessions Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1648
Table 128: show multicast snooping route Output Fields . . . . . . . . . . . . . . . . . . 1652
Table 129: show multicast statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1655
Table 130: show multicast usage Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1659
Table 131: show pgm negative-acknowledgments Output Fields . . . . . . . . . . . . 1661
Table 132: show pgm source-path-messages Output Fields . . . . . . . . . . . . . . . 1664
Table 133: show pgm statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1667
Table 134: show pim bootstrap Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670
Table 135: show pim interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1672
Table 136: show pim join Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677
Table 137: show pim mdt Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1697
Table 138: show pim mdt data-mdt-joins Output Fields . . . . . . . . . . . . . . . . . . . 1701
Table 139: show pim mdt data-mdt-limit Output Fields . . . . . . . . . . . . . . . . . . 1703
Table 140: show pim neighbors Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1706
Table 141: show pim rps Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1710
Table 142: show pim snooping interface Output Fields . . . . . . . . . . . . . . . . . . . . 1716
Table 143: show pim snooping join Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 1719
Table 144: show pim snooping neighbors Output Fields . . . . . . . . . . . . . . . . . . . 1724
Table 145: show pim snooping statistics Output Fields . . . . . . . . . . . . . . . . . . . . 1728
Table 146: show pim source Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1734
Table 147: show pim statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1737
Table 148: show sap listen Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1749

Chapter 20

xxxviii

IPv6 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1753

Copyright 2014, Juniper Networks, Inc.

List of Tables

Table 149: show ipv6 neighbors Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1756

Table 150: show ipv6 router-advertisement Output Fields . . . . . . . . . . . . . . . . . 1758

Chapter 21

IS-IS Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761

Table 151: show isis adjacency Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771
Table 152: show isis authentication Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 1774
Table 153: show isis backup coverage Output Fields . . . . . . . . . . . . . . . . . . . . . . 1776
Table 154: show isis backup label-switched-path Output Fields . . . . . . . . . . . . 1778
Table 155: show isis backup spf results Output Fields . . . . . . . . . . . . . . . . . . . . . 1781
Table 156: show isis context-identifier Output Fields . . . . . . . . . . . . . . . . . . . . . 1783
Table 157: show isis database Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1786
Table 158: show isis hostname Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797
Table 159: show isis interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1800
Table 160: show isis overview Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1803
Table 161: show isis route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1807
Table 162: show isis spf Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1810
Table 163: show isis statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1816

Chapter 22

LLDP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1819

Table 164: show lldp Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1822
Table 165: show lldp local-information Output Fields . . . . . . . . . . . . . . . . . . . . 1825
Table 166: show lldp neighbors Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1828
Table 167: show lldp remote-global-statistics Output Fields . . . . . . . . . . . . . . . 1834
Table 168: show lldp statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1836

Chapter 23

MVRP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1839

Table 169: show mvrp Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1840
Table 170: show mvrp applicant-state Output Fields . . . . . . . . . . . . . . . . . . . . . 1842
Table 171: show mvrp dynamic-vlan-memberships Output Fields . . . . . . . . . . . 1844
Table 172: show mvrp interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1845
Table 173: show mvrp registration-state Output Fields . . . . . . . . . . . . . . . . . . . 1846
Table 174: show mvrp statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1848

Chapter 24

OSPF Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1851

Table 175: show (ospf | ospf3) backup coverage Output Fields . . . . . . . . . . . . . 1861
Table 176: show (ospf | ospf3) backup lsp Output Fields . . . . . . . . . . . . . . . . . . 1864
Table 177: show (ospf |ospf3) backup neighbor Output Fields . . . . . . . . . . . . . 1866
Table 178: show (ospf |ospf3) backup spf Output Fields . . . . . . . . . . . . . . . . . . 1869
Table 179: show ospf context-identifier Output Fields . . . . . . . . . . . . . . . . . . . . 1876
Table 180: show ospf database Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1878
Table 181: show ospf3 database Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1887
Table 182: show (ospf | ospf3) interface Output Fields . . . . . . . . . . . . . . . . . . . 1898
Table 183: show (ospf | ospf3) io-statistics Output Fields . . . . . . . . . . . . . . . . . 1903
Table 184: show (ospf | ospf3) log Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 1905
Table 185: show (ospf | ospf3) neighbor Output Fields . . . . . . . . . . . . . . . . . . . 1909
Table 186: show ospf overview Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1915
Table 187: show (ospf | ospf3) route Output Fields . . . . . . . . . . . . . . . . . . . . . . 1920
Table 188: show (ospf | ospf3) statistics Output Fields . . . . . . . . . . . . . . . . . . . 1925

Chapter 25

Protocol-Independent Routing Operational Commands . . . . . . . . . . . . . 1929

Table 189: show as-path Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932

Copyright 2014, Juniper Networks, Inc.

xxxix

Interfaces Fundamentals for Routing Devices

Table 190: show as-path domain Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 1935

Table 191: show as-path summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 1938
Table 192: show route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1941
Table 193: show route advertising-protocol Output Fields . . . . . . . . . . . . . . . . . 1952
Table 194: show route damping Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1971
Table 195: show route detail Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975
Table 196: Next-hop Types Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . 1980
Table 197: State Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1981
Table 198: Communities Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 1983
Table 199: show route export Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1994
Table 200: show route export vrf-target Output Fields . . . . . . . . . . . . . . . . . . . 1997
Table 201: show route extensive Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1999
Table 202: show route flow validation Output Fields . . . . . . . . . . . . . . . . . . . . . 2016
Table 203: show route forwarding-table Output Fields . . . . . . . . . . . . . . . . . . . 2021
Table 204: show route forwarding-table interface-name Output Fields . . . . . 2032
Table 205: show route instance Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 2044
Table 206: show route localization Output Fields . . . . . . . . . . . . . . . . . . . . . . . 2056
Table 207: show route martians Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 2058
Table 208: show route receive-protocol Output Fields . . . . . . . . . . . . . . . . . . . 2091
Table 209: show route resolution Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 2100
Table 210: show route summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 2111
Table 211: show route terse Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2129

Chapter 26

RIP Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2133

Table 212: show rip general-statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . 2136
Table 213: show rip neighbor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2139
Table 214: show rip statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2141

Chapter 27

RIPng Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2143

Table 215: show ripng general-statistics Output Fields . . . . . . . . . . . . . . . . . . . . 2146
Table 216: show ripng neighbor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 2148
Table 217: show ripng statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 2150

Chapter 28

Firewall Filter Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2153

Table 218: show firewall Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2158
Table 219: show firewall filter version Output Fields . . . . . . . . . . . . . . . . . . . . . . 2163
Table 220: show firewall log Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2164
Table 221: show firewall prefix-action-stats Output Fields . . . . . . . . . . . . . . . . 2168
Table 222: show firewall templates-in-use Output Fields . . . . . . . . . . . . . . . . . 2169
Table 223: show policer Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2171

Chapter 29

Layer 2 Bridging and Switching Operational Commands . . . . . . . . . . . . . . 2175

Table 224: show bridge mac-table Output fields . . . . . . . . . . . . . . . . . . . . . . . . 2189
Table 225: show l2-learning global-information Output Fields . . . . . . . . . . . . . 2195
Table 226: show l2-learning instance Output Fields . . . . . . . . . . . . . . . . . . . . . . 2198
Table 227: show l2-learning interfaceOutput Fields . . . . . . . . . . . . . . . . . . . . . . 2200
Table 228: show mac-rewrite interface Output Fields . . . . . . . . . . . . . . . . . . . . 2202

Chapter 30

VPN Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2205

Table 229: show dynamic-tunnels database Output Fields . . . . . . . . . . . . . . . 2209
Table 230: show hfrr profiles Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2212

xl

Copyright 2014, Juniper Networks, Inc.

List of Tables

Table 231: show ingress-replication mvpn Output Fields . . . . . . . . . . . . . . . . . . 2214

Table 232: show l2circuit connections Output Fields . . . . . . . . . . . . . . . . . . . . . . 2217
Table 233: show l2vpn connections Output Fields . . . . . . . . . . . . . . . . . . . . . . . 2224
Table 234: show mvpn c-multicast Output Fields . . . . . . . . . . . . . . . . . . . . . . . 2229
Table 235: show mvpn instance Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 2231
Table 236: show mvpn neighbor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 2235
Table 237: show vpls connections Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 2240
Table 238: show vpls flood event-queue Output Fields . . . . . . . . . . . . . . . . . . . 2251
Table 239: show vpls flood instance Output Fields . . . . . . . . . . . . . . . . . . . . . . 2253
Table 240: show vpls flood route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 2255
Table 241: show vpls mac-table Output fields . . . . . . . . . . . . . . . . . . . . . . . . . . 2257
Table 242: show vpls statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 2262

Copyright 2014, Juniper Networks, Inc.

xli

Interfaces Fundamentals for Routing Devices

xlii

Copyright 2014, Juniper Networks, Inc.

About the Documentation

Documentation and Release Notes on page xliii

Supported Platforms on page xliii

Using the Examples in This Manual on page xliv

Documentation Conventions on page xlv

Documentation Feedback on page xlvii

Requesting Technical Support on page xlviii

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
http://www.juniper.net/techpubs/.
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 http://www.juniper.net/books.

Supported Platforms
For the features described in this document, the following platforms are supported:

ACX Series

M Series

MX Series

T Series

J Series

PTX Series

Copyright 2014, Juniper Networks, Inc.

xliii

Interfaces Fundamentals for Routing Devices

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.
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

xliv

Copyright 2014, Juniper Networks, Inc.

About the Documentation

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 the CLI User Guide.

Documentation Conventions
Table 1 on page xlvi defines notice icons used in this guide.

Copyright 2014, Juniper Networks, Inc.

xlv

Interfaces Fundamentals for Routing Devices

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 xlvi 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

Italic text like this

Italic text like this

xlvi

Represents output that appears on the

terminal screen.

user@host> show chassis alarms

Introduces or emphasizes important

new terms.

Identifies guide names.

A policy term is a named structure

that defines match conditions and
actions.

Identifies RFC and Internet draft titles.

Junos OS CLI User Guide

RFC 1997, BGP Communities Attribute

Represents variables (options for which

you substitute a value) in commands or
configuration statements.

No alarms currently active

Configure the machines domain name:

[edit]
root@# set system domain-name
domain-name

Copyright 2014, Juniper Networks, Inc.

About the Documentation

Table 2: Text and Syntax Conventions (continued)

Convention

Description

Examples

Text like this

Represents names of configuration

statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.

To configure a stub area, include the

stub statement at the [edit protocols
ospf area area-id] hierarchy level.

The console port is labeled CONSOLE.

< > (angle brackets)

Encloses optional keywords or variables.

stub <default-metric metric>;

| (pipe symbol)

Indicates a choice between the mutually

exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.

broadcast | multicast

# (pound sign)

Indicates a comment specified on the

same line as the configuration statement
to which it applies.

rsvp { # Required for dynamic MPLS only

[ ] (square brackets)

Encloses a variable for which you can

substitute one or more values.

community name members [

community-ids ]

Indention and braces ( { } )

Identifies a level in the configuration

hierarchy.

; (semicolon)

Identifies a leaf statement at a

configuration hierarchy level.

(string1 | string2 | string3)

[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}

GUI Conventions
Bold text like this

Represents graphical user interface (GUI)

items you click or select.

> (bold right angle bracket)

Separates levels in a hierarchy of menu

selections.

In the Logical Interfaces box, select

All Interfaces.

To cancel the configuration, click

Cancel.

In the configuration editor hierarchy,

select Protocols>Ospf.

Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:

Online feedback rating systemOn any page at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate the content, and use the pop-up form to provide us with information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.

Copyright 2014, Juniper Networks, Inc.

xlvii

Interfaces Fundamentals for Routing Devices

E-mailSend your comments to [email protected]. 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 J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.

JTAC policiesFor a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

Product warrantiesFor product warranty information, visit

http://www.juniper.net/support/warranty/.

JTAC hours of operationThe 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: http://www.juniper.net/customers/support/

Search for known bugs: http://www2.juniper.net/kb/

Find product documentation: http://www.juniper.net/techpubs/

Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

Search technical bulletins for relevant hardware and software notifications:

http://kb.juniper.net/InfoCenter/

Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

xlviii

Use the Case Management tool in the CSC at http://www.juniper.net/cm/.

Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

Copyright 2014, Juniper Networks, Inc.

About the Documentation

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html.

Copyright 2014, Juniper Networks, Inc.

xlix

Interfaces Fundamentals for Routing Devices

Copyright 2014, Juniper Networks, Inc.

PART 1

Router Interfaces

Router Interfaces Overview on page 3

Configuring Physical Interface Properties on page 55

Configuring Logical Interface Properties on page 159

Configuring Protocol Family and Interface Address Properties on page 187

Configuring Circuit and Translational Cross-Connects on page 255

Copyright 2014, Juniper Networks, Inc.

Interfaces Fundamentals for Routing Devices

Copyright 2014, Juniper Networks, Inc.

CHAPTER 1

Router Interfaces Overview

Router Interfaces Overview on page 4

Types of Interfaces Overview on page 4

Understanding Permanent Interfaces on page 5

Understanding Transient Interfaces on page 5

Understanding Services Interfaces on page 6

Understanding Container Interfaces on page 8

Understanding Management Ethernet Interfaces on page 10

TX Matrix Plus and T1600 Router (Routing Matrix) Management Ethernet

Interfaces on page 11

Understanding Internal Ethernet Interfaces on page 12

T1600 Routers (Routing Matrix) Internal Ethernet Interfaces on page 14

Supported Routing Engines by Router on page 14

Interface Naming Overview on page 26

Interface Encapsulations Overview on page 40

Interface Descriptors Overview on page 51

Physical Part of an Interface Name on page 52

Displaying Interface Configurations Overview on page 54

Copyright 2014, Juniper Networks, Inc.

Interfaces Fundamentals for Routing Devices

Router Interfaces Overview

Routers typically contain several different types of interfaces suited to various functions.
For the interfaces on a router to function, you must configure them, specifying properties
such as the interface location (that is, the slot in which the Flexible PIC Concentrator
[FPC] or Dense Port Concentrator [DPC] is installed, and the location where the Physical
Interface Card [PIC] is installed), the interface type (such as SONET/SDH, Asynchronous
Transfer Mode [ATM], or Ethernet), encapsulation, and interface-specific properties.
You can configure the interfaces that are currently present in the router, and you can also
configure interfaces that are not currently present but that you might add in the future.
When a configured interface appears, the Junos OS detects its presence and applies the
appropriate configuration to it.
To determine which interfaces are currently installed in the router, issue the show
interfaces terse operational mode command. If an interface is listed in the output, it is
installed in the router. If an interface is not listed in the output, it is not installed in the
router.
For information about which PICs are supported on your router, see your routers PIC
guide.
You can configure Junos class-of-service (CoS) properties to provide a variety of classes
of service for different applications, including multiple forwarding classes for managing
packet transmission, congestion management, and CoS-based forwarding. For more
information about configuring CoS properties, see the Class of Service Feature Guide for
Routing Devices.
Related
Documentation

Interfaces Fundamentals for Routing Devices

Types of Interfaces Overview

Interfaces can be permanent or transient, and are used for networking or services:

Permanent interfacesInterfaces that are always present in the router.

Transient interfacesInterfaces that can be inserted into or removed from the router
depending on your network configuration needs.

Networking interfacesInterfaces, such as Ethernet or SONET/SDH interfaces, that

primarily provide traffic connectivity.

Services interfacesInterfaces that provide specific capabilities for manipulating traffic

before it is delivered to its destination.

Container interfacesInterfaces that support automatic protection switching (APS)

on physical SONET links using a virtual container infrastructure.

Junos OS internally generates nonconfigurable interfaces which are described in Interfaces

Command Reference and Services Interfaces.

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Related
Documentation

Understanding Permanent Interfaces on page 5

Understanding Transient Interfaces on page 5

Understanding Services Interfaces on page 6 and Junos OS Services Interfaces Library

for Routing Devices

Understanding Container Interfaces on page 8

See also the following sections regarding specific networking interface technologies
used in your routers:

ATM Interfaces Overview

Channelized Interfaces Overview

Circuit Emulation Interfaces: Understanding Mobile Backhaul

E1 Interfaces Overview and E3 Interfaces Overview

Ethernet Interfaces Overview

Frame Relay Overview

ISDN Interfaces Overview

SONET/SDH Interfaces Overview

T1 Interfaces Overview and T3 Interfaces Overview

Understanding Permanent Interfaces

Permanent interfaces in the router consist of management Ethernet interfaces and
internal Ethernet interfaces, which are described separately in the following topics:

Understanding Management Ethernet Interfaces on page 10

Understanding Internal Ethernet Interfaces on page 12

Understanding Transient Interfaces

The M Series, MX Series, and T Series routers contain slots for installing FPCs. PICs can
be installed in FPCs. The number of PICs that can be installed varies by router and type
of FPC. The PICs provide the actual physical interfaces to the network. The MX Series
routers contain slots for installing either DPC boards that provide the physical interfaces
to the network or for installing FPCs in which PICs can be installed. These physical
interfaces are transient interfaces of the router. They are referred to as transient because
you can hot-swap a DPC or FPC and its PICs at any time.
You can insert any DPC or FPC into any slot that supports them in the appropriate router.
Typically, you can place any combination of PICs, compatible with your router, in any
location on an FPC. (You are limited by the total FPC bandwidth, and by the fact that
some PICs physically require two or four of the PIC locations on the FPC. In some cases,
power limitations or microcode limitations may also apply.) To determine DPC and PIC
compatibility, see the Hardware Guide, DPC Guide, and PIC Guide for your router.

Copyright 2014, Juniper Networks, Inc.

Interfaces Fundamentals for Routing Devices

You must configure each transient interface based on the slot in which the FPC is installed,
the location in which the PIC is installed, and for multiple port PICs, the port to which you
are connecting.
You can configure the interfaces on PICs that are already installed in the router as well
as interfaces on PICs that you plan to install later. The Junos OS detects which interfaces
are actually present, so when the software activates its configuration, it activates only
the present interfaces and retains the configuration information for the interfaces that
are not present. When the Junos OS detects that an FPC containing PICs has been inserted
into the router, the software activates the configuration for those interfaces.
Related
Documentation

Types of Interfaces Overview on page 4

Understanding Permanent Interfaces on page 5

Understanding Management Ethernet Interfaces on page 10

Understanding Internal Ethernet Interfaces on page 12

Supported Routing Engines by Router on page 14

Understanding Services Interfaces on page 6

Understanding Container Interfaces on page 8

Interface Encapsulations Overview on page 40

Interface Descriptors Overview on page 51

Interface Naming Overview on page 26

Displaying Interface Configurations Overview on page 54

Understanding Services Interfaces

Services interfaces enable you to incrementally add services to your network. The Junos
OS supports the following services PICs:

Adaptive Services (AS) PICsAllow you to provide multiple services on a single PIC
by configuring a set of services and applications. The AS PICs offer a special range of
services you configure in one or more service sets.

ES PICProvides a security suite for the IP version 4 (IPv4) and IP version 6 (IPv6)
network layers. The suite provides functionality such as authentication of origin, data
integrity, confidentiality, replay protection, and nonrepudiation of source. It also defines
mechanisms for key generation and exchange, management of security associations,
and support for digital certificates.

Monitoring Services PICsEnable you to monitor traffic flow and export the monitored
traffic. Monitoring traffic allows you to gather and export detailed information about
IPv4 traffic flows between source and destination nodes in your network; sample all
incoming IPv4 traffic on the monitoring interface and present the data in cflowd record
format; perform discard accounting on an incoming traffic flow; encrypt or tunnel
outgoing cflowd records, intercepted IPv4 traffic, or both; and direct filtered traffic to
different packet analyzers and present the data in its original format. On a Monitoring

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Services II PIC, you can configure either monitoring interfaces or collector interfaces.
A collector interface allows you to combine multiple cflowd records into a compressed
ASCII data file and export the file to an FTP server.

Multilink Services, MultiServices, Link Services, and Voice Services PICsEnable you
to split, recombine, and sequence datagrams across multiple logical data links. The
goal of multilink operation is to coordinate multiple independent links between a fixed
pair of systems, providing a virtual link with greater bandwidth than any of the members.

Tunnel Services PICBy encapsulating arbitrary packets inside a transport protocol,

tunneling provides a private, secure path through an otherwise public network. Tunnels
connect discontinuous subnetworks and enable encryption interfaces, virtual private
networks (VPNs), and Multiprotocol Label Switching (MPLS).

On M Series and T Series routers, logical tunnel interfaces allow you to connect logical
systems, virtual routers, or VPN instances. For more information about VPNs, see the
Junos OS VPNs Library for Routing Devices. For more information about configuring
tunnels, see the Junos OS Services Interfaces Library for Routing Devices.

Services (J Series)On J Series Services Routers, the lt interface is an internal interface

only and is not associated with a physical medium or PIM. You can configure the logical
tunnel interface to provide class-of-service (CoS) support for real-time performance
monitoring (RPM) probe packets. For more information, see the Junos OS Interfaces
and Routing Configuration Guide.

NOTE: The lt interface on the J Series router does not support logical
systems.

Related
Documentation

Types of Interfaces Overview on page 4

Copyright 2014, Juniper Networks, Inc.

Interfaces Fundamentals for Routing Devices

Understanding Container Interfaces

Container interfaces provide the following features:

Automatic protection switching (APS) on SONET/SDH and ATM links are supported
using the container infrastructure.

Container physical interfaces and logical interfaces remain up on switchover.

APS parameters are auto-copied from the container interface to the member links.

NOTE: Paired groups and true unidirectional APS are not currently supported.
For more information on SONET/SDH configuration, see Configuring Container
Interfaces for APS on SONET Links.

Container interfaces features are described in the following sections:

Understanding Traditional APS Concept on page 8

Container Interfaces Concept on page 9

APS Support for Container-Based Interfaces on page 9

Autocopy of APS Parameters on page 9

Understanding Traditional APS Concept

Traditional APS is configured on two independent physical SONET/SDH interfaces: one
configured as the working circuit and the other as the protect circuit (see
Figure 1 on page 8). The circuit, named Circuit X in the figure, is the link between the two
SONET interfaces.

Figure 1: APS Interface

Traditional APS uses routing protocols that run on each individual SONET/SDH interface
(since circuit is an abstract construct, instead of being an actual interface). When the
working link goes down, the APS infrastructure brings up the protect link and its underlying
logical interfaces, and brings down the working link and its underlying logical interfaces,

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

causing the routing protocols to reconverge. This consumes time and leads to traffic loss
even though the APS infrastructure has performed the switch quickly.

Container Interfaces Concept

To solve this problem, the Junos OS provides a soft interface construct called a container
interface (see Figure 2 on page 9).

Figure 2: Container Interface

The container interface allows routing protocols to run on the logical interfaces associated
with a virtual container interface instead of on the physical SONET/SDH and ATM
interfaces. When APS switches the underlying physical link based on a fault condition,
the container interface remains up, and the logical interface on the container interface
does not flap. The routing protocols remain unaware of the APS switching.

APS Support for Container-Based Interfaces

With the container interface, APS is configured on the container interface itself. Individual
member SONET/SDH and ATM links are either marked as primary (corresponding to the
working circuit) or standby (corresponding to the protect circuit) in the configuration. No
circuit or group name is specified in the container interface model; physical SONET/SDH
and ATM links are put in an APS group by linking them to a single container interface.
APS parameters are specified at the container interface level, and are propagated to the
individual SONET/SDH and ATM links by the APS daemon.

Autocopy of APS Parameters

Typical applications require copying APS parameters from the working circuit to the
protect circuit, since most of the parameters must be the same for both circuits. This is
automatically done in the container interface. APS parameters are specified only once
under the container physical interface configuration, and are internally copied over to
the individual physical SONET/SDH and ATM links.
Related
Documentation

Configuring Container Interfaces for APS on SONET Links

Displaying APS Using a Container Interface with ATM Encapsulation

Copyright 2014, Juniper Networks, Inc.

Interfaces Fundamentals for Routing Devices

Understanding Management Ethernet Interfaces

Management interfaces are the primary interfaces for accessing the device remotely.
Typically, a management interface is not connected to the in-band network, but is
connected instead to the device's internal network. Through a management interface
you can access the device over the network using utilities such as ssh and telnet and
configure the device from anywhere, regardless of its physical location. SNMP can use
the management interface to gather statistics from the device.
A management interface lets authorized users and management systems connect to
the device over the network. Some Juniper Networks devices have a dedicated
management port on the front panel. For other types of platforms, you can configure a
management interface on one of the network interfaces. This interface can be dedicated
to management or shared with other traffic. Before users can access the management
interface, you must configure it. Information required to set up the management interface
includes its IP address and prefix. In many types of Junos OS devices (or recommended
configurations), it is not possible to route traffic between the management interface and
the other ports. Therefore, you should select an IP address in a separate (logical) network,
with a separate prefix (netmask).
For devices with dedicated management ports, Junos OS automatically configures the
routers management Ethernet interface, as either em0 or fxp0. You can use the show
interfaces terse | match fxp0 or show interfaces terse | match em0 command to display
management interface information.
To use the management Ethernet interface as a management port, you must configure
its logical port, em0.0 or fxp0.0, with a valid IP address.
For some SRX Series Services Gateways and J Series Services Routers, you can use any
of the built-in Ethernet ports as a management interface. To use a built-in interface as
a management Ethernet interface, configure it with a valid IP address. The factory
configuration for the J4350 and J6350 Services Routers automatically enables the J-Web
user interface on the ge-0/0/0, ge-0/0/1, ge-0/0/2, and ge-0/0/3 interfaces. To manually
configure J-Web access, include the interface interface-name statement at the [edit
system services web-management http] hierarchy level.
For PTX Series Packet Transport Routers, the Junos OS automatically creates the routers
management Ethernet interface, em0. To use em0 as an out-of-band management port,
you must configure its logical port (for example, em0.0) with a valid IP address.
Internal Ethernet interfaces are automatically created to connect the Routing Engines
to the Packet Forwarding Engines in the FPCs.
When you enter the show interfaces command on a PTX Series Packet Transport Router,
the management Ethernet interface and internal Ethernet interfaces (and logical
interfaces) are displayed:
user@host> show interfaces ?
...
em0
em0.0

10

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

ixgbe0
ixgbe0.0
ixgbe1
ixgbe1.0
...

NOTE: Routing Engine upgrade considerationsWhen upgrading to a Routing

Engine that supports em0 from a Routing Engine that supports fxp0, you
must convert existing management Ethernet interface references in the router
configuration files from fxp0, fxp1, or fxp2 interfaces to em0 interfaces.
Whether you use an automated script or edit the configuration files manually,
you must revise any command lines that reference the fxp0 management
Ethernet interface by replacing fxp0 with em0.
Reusing scripts for standalone T1600 routers on T1600 routers in a routing
matrixAutomated scripts that you have developed for standalone T1600
routers (T1600 routers that are not in a routing matrix) might contain
references to the fxp0 management Ethernet interface. Before reusing the
scripts on T1600 routers in a routing matrix, edit the command lines that
reference the fxp0 management Ethernet interface so that the commands
reference the em0 management Ethernet interface instead.
Restricted load-sharing next hops with fxp0On M Series Multiservices Edge
Routers and T Series Core Routers running Junos OS later than Release 7.0R2.7
or Release 7.1R2.2, the fxp0 interface does not support load-sharing next
hops. This restriction only affects fxp0 routes.
CoS not supported on fxp0The fxp0 interface does not support class of
service (CoS).
The Routing Engines in the PTX Series Packet Transport Routers do not
support the management Ethernet interface fxp0, or the internal Ethernet
interfaces fxp1 or fxp2.

Related
Documentation

Supported Routing Engines by Router on page 14

TX Matrix Plus and T1600 Router (Routing Matrix) Management Ethernet Interfaces
For TX Matrix Plus Routers and for T1600 Core Routers with RE-C1800 configured in a
routing matrix, the Junos OS automatically creates the routers management Ethernet
interface, em0. To use em0 as a management port, you must configure its logical port,
em0.0, with a valid IP address.
When you enter the show interfaces command on a TX Matrix Plus router, the
management Ethernet interfaces (and logical interfaces) are displayed:
user@host> show interfaces ?
...
em0

Copyright 2014, Juniper Networks, Inc.

11

Interfaces Fundamentals for Routing Devices

em0.0
...

NOTE: The Routing Engines in the TX Matrix Plus router and in the T1600
routers with RE-C1800 configured in a routing matrix do not support the
management Ethernet interface fxp0, or the internal Ethernet interfaces fxp1
or fxp2.

Related
Documentation

Understanding Internal Ethernet Interfaces on page 12

T1600 Routers (Routing Matrix) Internal Ethernet Interfaces on page 14

Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus Router

show interfaces (M Series, MX Series and T Series Routers, and PTX Series Packet
Transport Routers Management and Internal Ethernet) on page 1239

Understanding Internal Ethernet Interfaces

Within a router or packet transport router, internal Ethernet interfaces provide
communication between the Routing Engine and the Packet Forwarding Engines. The
Junos OS automatically configures internal Ethernet interfaces when the Junos OS boots.
The Junos OS boots the packet-forwarding component hardware. When these
components are running, the Control Board uses the internal Ethernet interface to transmit
hardware status information to the Routing Engine. Information transmitted includes
the internal router temperature, the condition of the fans, whether an FPC has been
removed or inserted, and information from the LCD on thecraft interface.
To determine the supported internal Ethernet interfaces for your router, see Supported
Routing Engines by Router on page 14.

NOTE: Do not modify or remove the configuration for the internal Ethernet
interface that the Junos OS automatically configures. If you do, the router or
packet transport routerwill stop functioning.

J Series, M Series, and MX Series routers and T Series routersThe Junos OS creates
the internal Ethernet interface. The internal Ethernet interface connects the Routing
Engine re0 to the Packet Forwarding Engines.
If the router has redundant Routing Engines, another internal Ethernet interface is
created on each Routing Engine (re0 and re1) in order to support fault tolerance, two
physical links between re0 and re1 connect the independent control planes. If one of
the links fails, both Routing Engines can use the other link for IP communication.

12

TX Matrix Plus routersOn a TX Matrix Plus router, the Routing Engine and Control
Board function as a unit, or host subsystem. For each host subsystem in the router, the
Junos OS automatically creates two internal Ethernet interfaces, ixgbe0 and ixgbe1.

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

The ixgbe0 and ixgbe1 interfaces connect the TX Matrix Plus Routing Engine to the
Routing Engines of every line-card chassis (LCC) configured in the routing matrix.
The TX Matrix Plus Routing Engine connects to a high-speed switch through a 10-Gbps
link within the host subsystem. The switch provides a 1-Gbps link to each T1600 Routing
Engine. The 1-Gbps links are provided through the UTP Category 5 Ethernet cable
connections between the TXP-CBs and the LCC-CBs in the LCCs.

The TX Matrix Plus Routing Engine connects to a high-speed switch in the local
Control Board through a 10-Gbps link within the host subsystem.

The Gigabit Ethernet switch connects the Control Board to the remote Routing
Engines of every LCC configured in the routing matrix.

If a TX Matrix Plus router contains redundant host subsystems, the independent control
planes are connected by two physical links between the two 10-Gigabit Ethernet ports
on their respective Routing Engines.

The primary link to the remote Routing Engine is at the ixgbe0 interface; the 10-Gigabit
Ethernet switch on the local Control Board also connects the Routing Engine to the
10-Gigabit Ethernet port accessed by the ixgbe1 interface on the remote Routing
Engine.

The alternate link to the remote Routing Engine is the 10-Gigabit Ethernet port at
the ixgbe1 interface. This second port connects the Routing Engine to the 10-Gigabit
Ethernet switch on the remote Control Board, which connects to the 10-Gigabit
Ethernet port at the ixgbe0 interface on the remote Routing Engine.

If one of the two links between the host subsystems fails, both Routing Engines can
use the other link for IP communication.

LCC in a routing matrixOn an LCC configured in a routing matrix, the Routing Engine
and Control Board function as a unit, or host subsystem. For each host subsystem in
the LCC, the Junos OS automatically creates two internal Ethernet interfaces, bcm0
and em1, for the two Gigabit Ethernet ports on the Routing Engine.
The bcm0 interface connects the Routing Engine in each LCCto the Routing Engines
of every other LCC configured in the routing matrix.

The Routing Engine connects to a Gigabit Ethernet switch on the local Control Board
through a.

The switch connects the Control Board to the remote Routing Engines of every other
LCC configured in the routing matrix.

If an LCC in a routing matrix contains redundant host subsystems, the independent

control planes are connected by two physical links between the Gigabit Ethernet ports
on their respective Routing Engines.

The primary link to the remote Routing Engine is at the bcm0 interface; the Gigabit
Ethernet switch on the local Control Board also connects the Routing Engine to the
Gigabit Ethernet port accessed by the em1 interface on the remote Routing Engine.

Copyright 2014, Juniper Networks, Inc.

13

Interfaces Fundamentals for Routing Devices

The alternate link to the remote Routing Engine is at the em1 interface. This second
port connects the Routing Engine to the Gigabit Ethernet switch on the remote
Control Board, which connects to the Gigabit Ethernet port at the bcm0 interface
on the remote Routing Engine.

If one of the two links between the host subsystems fails, both Routing Engines can
use the other link for IP communication.
Each router also has two serial ports, labeled console and auxiliary, for connecting tty type
terminals to the router using standard PC-type tty cables. Although these ports are not
network interfaces, they do provide access to the router.
Related
Documentation

Understanding Permanent Interfaces on page 5

Supported Routing Engines by Router on page 14

TX Matrix Plus and T1600 Router (Routing Matrix) Management Ethernet Interfaces
on page 11

T1600 Routers (Routing Matrix) Internal Ethernet Interfaces on page 14

Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus Router

show interfaces (M Series, MX Series and T Series Routers, and PTX Series Packet
Transport Routers Management and Internal Ethernet) on page 1239

T1600 Routers (Routing Matrix) Internal Ethernet Interfaces

On a T1600 router configured in a routing matrix, the Routing Engine (RE-TXP-LCC) and
Control Board (LCC-CB) function as a unit, or host subsystem. For each host subsystem
in the router, the Junos OS automatically creates two internal Ethernet interfaces, bcm0
and em1, for the two Gigabit Ethernet ports on the Routing Engine.
Related
Documentation

Understanding Internal Ethernet Interfaces on page 12

Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus Router

show interfaces (M Series, MX Series and T Series Routers, and PTX Series Packet
Transport Routers Management and Internal Ethernet) on page 1239

Supported Routing Engines by Router

The following tables list the Routing Engines that each router supports, the first supported
release for the Routing Engine in the specified router, the management Ethernet interface,
and the internal Ethernet interfaces for each Routing Engine.

14

M7i Supported Routing Engines on page 15

M10i Supported Routing Engines on page 15

M40e Supported Routing Engines on page 16

M120 Supported Routing Engines on page 16

M320 Supported Routing Engines on page 17

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

MX104 Supported Routing Engines on page 17

MX240 Supported Routing Engines on page 18

MX480 Supported Routing Engines on page 18

MX960 Supported Routing Engines on page 19

MX2010 Supported Routing Engines on page 20

MX2020 Supported Routing Engines on page 21

PTX3000 Supported Routing Engines on page 21

PTX5000 Supported Routing Engines on page 21

T320 Supported Routing Engines on page 22

T640 Supported Routing Engines on page 22

T1600 Supported Routing Engines on page 23

T4000 Supported Routing Engines on page 24

TX Matrix Supported Routing Engines on page 25

TX Matrix Plus Supported Routing Engines on page 25

TX Matrix Plus (with 3D SIBs) Supported Routing Engines on page 25

M7i Supported Routing Engines

Table 3 on page 15 lists the Routing Engines supported by the M7i router. The M7I router
supports 32-bit Junos OS only.

Table 3: M7i Supported Routing Engines

Name in CLI
Output

First Supported 32-bit Junos

OS Release

Supported
Management
Ethernet
Interface

RE-400-768 (EOL details:

TSB16445)

RE-5.0

9.0

fxp0

fxp1

RE-850-1536

RE-850

7.2

fxp0

fxp1

RE-B-1800X1-4G

RE-B-1800x1

11.4R4

fxp0

em0

Model Number

Supported
Internal
Ethernet
Interface

12.1R2

M10i Supported Routing Engines

Table 4 on page 16 lists the Routing Engines supported by the M10i router. The M10I
router supports 32-bit Junos OS only.

Copyright 2014, Juniper Networks, Inc.

15

Interfaces Fundamentals for Routing Devices

Table 4: M10I Supported Routing Engines

Model Number
RE-400-768 (EOL details:
TSB16445)

Name in CLI
Output

First Supported 32-bit

Junos OS Release

Supported
Management
Ethernet
Interface

RE-5.0

9.0

fxp0

Supported
Internal Ethernet
Interface
fxp1
fxp2

RE-850-1536

7.2

RE-850

fxp0

fxp1
fxp2

RE-B-1800X1-4G

11.4R4

RE-B-1800x1

fxp0

em0

12.1R2

M40e Supported Routing Engines

Table 5 on page 16 lists the Routing Engines supported by the M40e router.

Table 5: M40e Supported Routing Engines

Model Number

Name in CLI
Output

First Supported Junos OS

Release

Supported
Management
Ethernet
Interface

RE-600-2048 (EOL details:

PSN-2008-02-018)

RE-3.0 or RE-3.0
(RE-600)

5.3

fxp0

Supported
Internal
Ethernet
Interface
fxp1
fxp2

RE-A-1000-2048

8.1

RE-A-1000

fxp0

fxp1
fxp2

M120 Supported Routing Engines

Table 6 on page 16 lists the Routing Engines supported by the M120 router.

Table 6: M120 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported
32-bit Junos OS
Release

RE-A-1000-2048

RE-A-1000

8.0R2

First
Supported
64-bit Junos
OS Release

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

fxp0

fxp1
fxp2

RE-A-2000-4096

RE-A-2000

8.0R2

fxp0

em0
bcm0

16

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 6: M120 Supported Routing Engines (continued)

Model Number

Name in CLI
Output

First Supported
32-bit Junos OS
Release

RE-A-1800x2-8G

RE-A-1800x2

11.4R5

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

RE-A-1800x2-16G

RE-A-1800x4-16G

RE-A-1800x2

RE-A-1800x4

First
Supported
64-bit Junos
OS Release

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

10.4

fxp0

fxp1
fxp2

10.4

fxp0

fxp1
fxp2

10.4

fxp0

em0
em1

M320 Supported Routing Engines

Table 7 on page 17 lists the Routing Engines supported by the M320 router.

Table 7: M320 Supported Routing Engines

Name in CLI
Output

First Supported
32-bit Junos OS
Release

First Supported
64-bit Junos OS
Release

Supported
Management
Ethernet Interface

Supported
Internal
Ethernet
Interface

RE-1600-2048 (EOL
details:
PSN-2008-02-019)

RE-4.0

6.2

fxp0

fxp1

RE-A-2000-4096

RE-A-2000

Model Number

fxp2
8.1

fxp0

em0
bcm0

RE-A-1800x2-8G

RE-A-1800x2-16G

RE-A-1800x4-8G

RE-A-1800x2

RE-A-1800x2

RE-A-1800X4

11.4R5

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

12.2

10.4

fxp0

em0
bcm0

10.4

fxp0

em0
bcm0

10.4

fxp0

em0
em1

MX104 Supported Routing Engines

Table 8 on page 18 lists the Routing Engines supported by MX104 routers.

Copyright 2014, Juniper Networks, Inc.

17

Interfaces Fundamentals for Routing Devices

Table 8: MX104 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported
32-bit Junos OS
Release

First Supported
64-bit Junos OS
Release

Supported
Management
Ethernet
Interface

Supported
Internal Ethernet
Interface

RE-S-MX104

Routing Engine

13.2

fxp0

fxp1
fxp2

MX240 Supported Routing Engines

Table 9 on page 18 lists the Routing Engines supported by MX240 routers.

Table 9: MX240 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported
32-bit Junos OS
Release

First Supported
64-bit Junos OS
Release

Supported
Management
Ethernet
Interface

Supported
Internal Ethernet
Interface

RE-S-1300-2048

RE-S-1300

9.0

fxp0

fxp1
fxp2

RE-S-2000-4096

RE-S-2000

9.0

fxp0

fxp1
fxp2

RE-S-1800x2-8G

RE-S-1800x2-16G

RE-S-1800x4-8G

RE-S-1800x4-16G

RE-S-1800X4-32G-S

RE-S-1800x2

RE-S-1800X2

RE-S-1800X4

RE-S-1800x4

RE-S-1800X4

11.4R5

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

12.3R4

12.3R4

13.2R1

13.2R1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

fxp0

em0,
em1

MX480 Supported Routing Engines

Table 10 on page 19 lists the Routing Engines supported by MX480 routers.

18

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 10: MX480 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported
32-bit Junos OS
Release

First Supported
64-bit Junos OS
Release

Supported
Management
Ethernet
Interface

Supported
Internal Ethernet
Interface

RE-S-1300-2048

RE-S-1300

8.4

fxp0

fxp1
fxp2

RE-S-2000-4096

RE-S-2000

8.4

fxp0

fxp1
fxp2

RE-S-1800x2-8G

RE-S-1800x2-16G

RE-S-1800x4-8G

RE-S-1800x4-16G

RE-S-1800X4-32G-S

RE-S-1800x2

RE-S-1800X2

RE-S-1800X4

RE-S-1800x4

RE-S-1800X4

11.4R5

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

12.3R4

12.3R4

13.2R1

13.2R1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

fxp0

em0
em1

MX960 Supported Routing Engines

Table 11 on page 19 lists the Routing Engines supported by MX960 routers.

Table 11: MX960 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 32-bit

Junos OS Release

First
Supported
64-bit Junos
OS Release

RE-S-1300-2048

RE-S-1300

8.2

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

fxp0

fxp1
fxp2

RE-S-2000-4096

RE-S-2000

8.2

fxp0

fxp1
fxp2

Copyright 2014, Juniper Networks, Inc.

19

Interfaces Fundamentals for Routing Devices

Table 11: MX960 Supported Routing Engines (continued)

Model Number

Name in CLI
Output

First Supported 32-bit

Junos OS Release

First
Supported
64-bit Junos
OS Release

RE-S-1800x2-8G

RE-S-1800x2

11.4R5

10.4

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

11.4R5

12.1R3

12.3R4

12.3R4

13.2R1

13.2R1

RE-S-1800x2-16G

RE-S-1800x4-8G

RE-S-1800x4-16G

RE-S-1800X4-32G-S

RE-S-1800X2

RE-S-1800X4

RE-S-1800x4

RE-S-1800X4

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

fxp0

em0
em1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

10.4

fxp0

em0
em1

fxp0

em0
em1

MX2010 Supported Routing Engines

Table 12 on page 20 lists the Routing Engines supported by MX2010 routers.

Table 12: MX2010 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 64-bit Junos

OS Release

Supported
Management
Ethernet
Interface

MX2000-RE-1800x4

RE-S-1800x4

12.3R2

fxp0

Supported
Internal
Ethernet
Interface
em0
em1

REMX2K-1800-32G-S

20

RE-S-1800X4

12.3R4

13.2R1

fxp0

em0
em1

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

MX2020 Supported Routing Engines

Table 13: MX2020 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 64-bit Junos

OS Release

Supported
Management
Ethernet
Interface

MX2000-RE-1800x4

RE-S-1800x4

12.3R2

fxp0

Supported
Internal
Ethernet
Interface
em0
em1

REMX2K-1800-32G-S

RE-S-1800X4

12.3R4

13.2R1

fxp0

em0
em1

PTX3000 Supported Routing Engines

Table 14 on page 21 lists the Routing Engines supported by the PTX3000 Packet Transport
Router. The PTX3000 Packet Transport Router supports 64-bit Junos OS only.

Table 14: PTX3000 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 64-bit Junos

OS Release

Supported
Management
Ethernet
Interface

RE-DUO-C2600-16G

RE-DUO-2600

13.2R2

em0

Supported
Internal
Ethernet
Interface
ixgbe0
ixgbe1

PTX5000 Supported Routing Engines

Table 15 on page 21 lists the Routing Engines supported by the PTX5000 Packet Transport
Router. The PTX5000 Packet Transport Router supports 64-bit Junos OS only.

Table 15: PTX5000 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 64-bit Junos

OS Release

Supported
Management
Ethernet
Interface

RE-DUO-C2600-16G

RE-DUO-2600

12.1x48

em0

12.3

Supported
Internal
Ethernet
Interface
ixgbe0
ixgbe1

13.2
NOTE: PTX5000 does not
support Junos OS Releases 12.1,
12.2, or 13.1.

Copyright 2014, Juniper Networks, Inc.

21

Interfaces Fundamentals for Routing Devices

T320 Supported Routing Engines

Table 16 on page 22 lists the Routing Engines supported by the T320 router.

Table 16: T320 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 32-bit Junos

OS Release

Supported
Management
Ethernet
Interface

RE-600-2048 (EOL details:

PSN-2008-02-018)

RE-3.0 or RE-3.0
(RE-600)

5.3

fxp0

Supported
Internal
Ethernet
Interface
fxp1
fxp2

RE-1600-2048 (EOL details:

6.2

RE-4.0

fxp0

fxp1

PSN-2008-02-019
fxp2
RE-A-2000-4096

RE-A-2000

8.1

fxp0

fxp1
fxp2

T640 Supported Routing Engines

Table 17 on page 22 lists the Routing Engines supported by the T640 router.

Table 17: T640 Supported Routing Engines

Name in CLI
Output

First Supported 32-bit

Junos OS Release

First Supported
64-bit Junos OS
Release

RE-3.0 or
RE-3.0
(RE-600)

5.3

RE-1600-2048 (EOL
details:
PSN-2008-02-019)

RE-4.0

6.2

RE-A-2000-4096

RE-A-2000

Model Number
RE-600-2048 (EOL
details:

PSN-2008-02-018)

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

fxp0

fxp1
fxp2

fxp0

fxp1
fxp2

8.1

fxp0

em0
bcm0

RE-DUO-C1800-8G

22

RE-DUO-1800

32-bit Junos OS on a
standalone T640 router:
11.2

64-bit Junos OS
on a standalone
T640 router: 11.3

32-bit Junos OS on a
T640 router in a routing
matrix: 11.4R9

64-bit Junos OS
on a T640 router
in a routing
matrix: 11.4R9

em0

bcm0
em1

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 17: T640 Supported Routing Engines (continued)

Model Number

Name in CLI
Output

First Supported 32-bit

Junos OS Release

RE-DUO-C1800-16G

RE-DUO-1800

32-bit Junos OS on a
standalone T640 router:
11.4R2
32-bit Junos OS on a
T640 router in a routing
matrix: 11.4R9

First Supported
64-bit Junos OS
Release
64-bit Junos OS
on a standalone
T640 router:
11.4R2

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

em0

bcm0
em1

64-bit Junos OS
on a T640 router
in a routing
matrix: 11.4R9

T1600 Supported Routing Engines

Table 18 on page 23 lists the Routing Engines supported by the T1600 router.

NOTE: (Two RE-DUO-C1800-8G or two RE-DUO-C1800-16G are required

to connect to a Routing Matrix)

Table 18: T1600 Supported Routing Engines

Name in CLI
Output

First Supported 32-bit

Junos OS Release

First Supported
64-bit Junos OS
Release

RE-3.0 or
RE-3.0
(RE-600)

8.5

RE-1600-2048 (EOL
details:
PSN-2008-02-019)

RE-4.0
(RE-1600)

8.5

RE-A-2000-4096

RE-A-2000

Model Number
RE-600-2048 (EOL
details:

PSN-2008-02-018)

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

fxp0

fxp1
fxp2

fxp0

fxp1
fxp2

8.5

fxp0

em0
bcm0

Copyright 2014, Juniper Networks, Inc.

23

Interfaces Fundamentals for Routing Devices

Table 18: T1600 Supported Routing Engines (continued)

Model Number

Name in CLI
Output

First Supported 32-bit

Junos OS Release

RE-DUO-C1800-8G

RE-TXP-LCC

32-bit Junos OS on a
T1600 router in a routing
matrix: 9.6

or
RE-DUO-1800

NOTE: Junos OS
Releases 9.6 through 10.4
support
RE-DUO-C1800-8G only
during upgrade to a
line-card chassis (LCC) in
a routing matrix.

First Supported
64-bit Junos OS
Release
64-bit Junos OS
on a T1600
router in a
routing matrix:
9.6

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

em0

bcm0
em1

64-bit Junos OS
on a standalone
T1600 router: 11.1

32-bit Junos OS on a
standalone T1600 router:
11.1
RE-DUO-C1800-16G

RE-DUO-1800

32-bit Junos OS on a
standalone T1600 router:
11.4R2
32-bit Junos OS on a
T1600 router in a routing
matrix: 11.4R2

64-bit Junos OS
on a standalone
T1600 router:
11.4R2

em0

bcm0
em1

64-bit Junos OS
on a T1600
router in a
routing matrix:
11.4R2

T4000 Supported Routing Engines

Table 19 on page 24 lists the Routing Engines supported by the T4000 router.

NOTE: The T4000 router supports 64-bit Junos OS only.

Table 19: T4000 Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 64-bit Junos

OS Release

Supported
Management
Ethernet
Interface

RE-DUO-C1800-8G

RE-DUO-1800

Standalone T4000 router: 12.1

em0

T4000 router in a routing matrix:

13.1
RE-DUO-C1800-16G

RE-DUO-1800

Standalone T4000 router: 12.1R2

T4000 router in a routing matrix:
13.1

24

Supported Internal
Ethernet Interface
bcm0
em1

em0

bcm0
em1

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

TX Matrix Supported Routing Engines

Table 20 on page 25 lists the Routing Engines supported by the TX Matrix router.

Table 20: TX Matrix Supported Routing Engines

Name in CLI
Output

First Supported 32-bit

Junos OS Release

First
Supported
64-bit Junos
OS Release

RE-3.0 or
RE-3.0
(RE-600)

7.0

RE-1600-2048 (EOL
details:
PSN-2008-02-019)

RE-4.0
(RE-1600)

7.0

RE-A-2000-4096

RE-A-2000

Model Number
RE-600-2048 (EOL
details:

PSN-2008-02-018)

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

fxp0

fxp1
fxp2

fxp0

fxp1
fxp2

8.5

fxp0

em0
bcm0

RE-DUO-C1800-8G

RE-DUO-1800

11.4R9

11.4R9

em0

bcm0
em1

RE-DUO-C1800-16G

RE-DUO-1800

11.4R9

11.4R9

em0

bcm0
em1

TX Matrix Plus Supported Routing Engines

Table 21 on page 25 lists the Routing Engines supported by the TX Matrix Plus router.

Table 21: TX Matrix Plus Supported Routing Engines

Model Number

Name in CLI
Output

First Supported 32-bit

Junos OS Release

RE-DUO-C2600-16G

RE-TXP-SFC

32-bit Junos OS: 9.6

or

First Supported
64-bit Junos OS
Release
64-bit Junos OS:
11.4

RE-DUO-2600

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

em0

ixgbe0
ixgbe1

TX Matrix Plus (with 3D SIBs) Supported Routing Engines

Table 22 on page 26 lists the Routing Engines supported by the TX Matrix Plus router
with 3D SIBs.

Copyright 2014, Juniper Networks, Inc.

25

Interfaces Fundamentals for Routing Devices

Table 22: Routing Engines Supported on TX Matrix Plus with 3D SIBs

Model Number

Name in CLI
Output

First Supported 32-bit

Junos OS Release

RE-DUO-C2600-16G

RE-TXP-SFC

or

First Supported
64-bit Junos OS
Release
64-bit Junos OS:
11.4

Supported
Management
Ethernet
Interface

Supported
Internal
Ethernet
Interface

em0

ixgbe0
ixgbe1

RE-DUO-2600

Related
Documentation

Routing Engine Specifications

Understanding Internal Ethernet Interfaces on page 12

Understanding Management Ethernet Interfaces on page 10

Interface Naming Overview

Each interface has an interface name, which specifies the media type, the slot in which
the FPC or DPC is located, the location on the FPC where the PIC is installed, and the PIC
or DPC port. The interface name uniquely identifies an individual network connector in
the system. You use the interface name when configuring interfaces and when enabling
various functions and properties, such as routing protocols, on individual interfaces. The
system uses the interface name when displaying information about the interface, for
example, in the show interfaces command.
The interface name is represented by a physical part, a channel part, and a logical part
in the following format:
physical<:channel>.logical

The channel part of the name is optional for all interfaces except channelized DS3, E1,
OC12, and STM1 interfaces.
The following sections provide interface naming configuration guidelines:

Physical Part of an Interface Name on page 26

Logical Part of an Interface Name on page 32

Separators in an Interface Name on page 32

Channel Part of an Interface Name on page 32

Interface Naming for a Routing Matrix Based on a TX Matrix Router on page 33

Interface Naming for a Routing Matrix Based on a TX Matrix Plus Router on page 35

Chassis Interface Naming on page 38

Examples: Interface Naming on page 38

Physical Part of an Interface Name

The physical part of an interface name identifies the physical device, which corresponds
to a single physical network connector.

26

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

NOTE:
The internal interface is dependent on the Routing Engine. To identify if the
Routing Engine is using this type of interface, use the following command:
user@host> show interfaces terse
Interface
Admin Link Proto
Local
pfe-1/0/0
up
up
pfe-1/0/0.16383
up
up
inet
inet6
pfh-1/0/0
up
up
pfh-1/0/0.16383
up
up
inet
[..........]
bcm0
up
up <---------------bcm0.0
up
up
inet 10.0.0.1/8
[..........]
lsi
up
up
mtun
up
up
pimd
up
up
pime
up
up
tap
up
up

Remote

For more information on the Routing Engines that each chassis supports, the
first supported release for the Routing Engine in the specified chassis, the
management Ethernet interface, and the internal Ethernet interfaces for each
Routing Engine, please refer the link titled Supported Routing Engines by
Chassis under Related Documentation section.

This part of the interface name has the following format:

type-fpc/pic/port
type is the media type, which identifies the network device that can be one of the following:

aeAggregated Ethernet interface. This is a virtual aggregated link and has a different

naming format from most PICs; for more information, see Aggregated Ethernet Interfaces
Overview.

asAggregated SONET/SDH interface. This is a virtual aggregated link and has a

different naming format from most PICs; for more information, see Configuring
Aggregated SONET/SDH Interfaces.

atATM1 or ATM2 intelligent queuing (IQ) interface or a virtual ATM interface on a

circuit emulation (CE) interface.

bcmThe bcm0 internal Ethernet process is supported on specific Routing engines

for various M series and T series routers. For more information please refer the link
titled Supported Routing Engines by Chassis under Related Documentation section.

brIntegrated Services Digital Network (ISDN) interface (configured on a 1-port or

4-port ISDN Basic Rate Interface (BRI) card). This interface has a different naming
format from most PICs: br-pim/0/port. The second number is always 0. For more
information, see Configuring ISDN Physical Interface Properties.

Copyright 2014, Juniper Networks, Inc.

27

Interfaces Fundamentals for Routing Devices

cau4Channelized AU-4 IQ interface (configured on the Channelized STM1 IQ or IQE

PIC or Channelized OC12 IQ and IQE PICs).

ce1Channelized E1 IQ interface (configured on the Channelized E1 IQ PIC or Channelized

STM1 IQ or IQE PIC).

ciContainer interface.

coc1Channelized OC1 IQ interface (configured on the Channelized OC12 IQ and IQE

or Channelized OC3 IQ and IQE PICs).

coc3Channelized OC3 IQ interface (configured on the Channelized OC3 IQ and IQE

PICs).

coc12Channelized OC12 IQ interface (configured on the Channelized OC12 IQ and IQE

PICs).

coc48Channelized OC48 interface (configured on the Channelized OC48 and

Channelized OC48 IQE PICs).

cpCollector interface (configured on the Monitoring Services II PIC).

cstm1Channelized STM1 IQ interface (configured on the Channelized STM1 IQ or IQE

PIC).

cstm4Channelized STM4 IQ interface (configured on the Channelized OC12 IQ and

IQE PICs).

cstm16Channelized STM16 IQ interface (configured on the Channelized OC48/STM16

and Channelized OC48/STM16 IQE PICs).

ct1Channelized T1 IQ interface (configured on the Channelized DS3 IQ and IQE PICs,

Channelized OC3 IQ and IQE PICs, Channelized OC12 IQ and IQE PICs, or Channelized
T1 IQ PIC).

ct3Channelized T3 IQ interface (configured on the Channelized DS3 IQ and IQE PICs,

Channelized OC3 IQ and IQE PICs, or Channelized OC12 IQ and IQE PICs).

demuxInterface that supports logical IP interfaces that use the IP source or destination

address to demultiplex received packets. Only one demux interface (demux0) exists
per chassis. All demux logical interfaces must be associated with an underlying logical
interface.

dfcInterface that supports dynamic flow capture processing on T Series or M320

routers containing one or more Monitoring Services III PICs. Dynamic flow capture
enables you to capture packet flows on the basis of dynamic filtering criteria.
Specifically, you can use this feature to forward passively monitored packet flows that
match a particular filter list to one or more destinations using an on-demand control
protocol.

dsDS0 interface (configured on the Multichannel DS3 PIC, Channelized E1 PIC,

Channelized OC3 IQ and IQE PICs, Channelized OC12 IQ and IQE PICs, Channelized
DS3 IQ and IQE PICs, Channelized E1 IQ PIC, Channelized STM1 IQ or IQE PIC, or
Channelized T1 IQ).

28

dscDiscard interface.

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

e1E1 interface (including channelized STM1-to-E1 interfaces).

e3E3 interface (including E3 IQ interfaces).

emManagement and internal Ethernet interfaces. For M Series routers, MX Series

routers, T Series routers, and TX Series routers, you can use the show chassis hardware
command to display hardware information about the router, including its Routing
Engine model. To determine which management interface is supported on your router
and Routing Engine combination, see Understanding Management Ethernet Interfaces
on page 10 and Supported Routing Engines by Router on page 14.

esEncryption interface.

et100-Gigabit Ethernet interfaces (10, 40, and 100-Gigabit Ethernet interface for

PTX Series Packet Transport Routers only).

feFast Ethernet interface.

fxpManagement and internal Ethernet interfaces. For M Series routers, MX Series

routers, T Series routers, and TX Series routers, you can use the show chassis hardware
command to display hardware information about the router, including its Routing
Engine model. To determine which management interface is supported on your router
and Routing Engine combination, see Understanding Management Ethernet Interfaces
on page 10 and Supported Routing Engines by Router on page 14.

geGigabit Ethernet interface. Some older 10-Gigabit Ethernet interfaces use the ge

media type to identify the physical part of the network device, but newer 10-Gigabit
Ethernet interfaces use the xe media type.

NOTE: For configuration, the ge interface name should be used instead of

the xe interface name in XENPAK 10-Gigabit Ethernet interface PICs. Refer
the following show commands for more information:
user@host> show chassis hardware
..
FPC 4
REV 02
710-015839
3
PIC 0
REV 09
750-009567
10GE(LAN),XENPAK
Xcvr 0
REV 01
740-012045

CZ1853

M120 FPC Type

NH1857

1x

535TFZX6

XENPAK-SR

user@host> show configuration interfaces ge-4/0/0

unit 0 {
family inet {
address 100.0.0.1/24;
}
}

grGeneric routing encapsulation (GRE) tunnel interface.

greInternally generated interface that is configurable only as the control channel for

Generalized MPLS (GMPLS). For more information about GMPLS, see the Junos OS
MPLS Applications Library for Routing Devices and the Junos OS, Release 14.2.

Copyright 2014, Juniper Networks, Inc.

29

Interfaces Fundamentals for Routing Devices

NOTE: You can configure GRE interfaces (gre-x/y/z) only for GMPLS control
channels. GRE interfaces are not supported or configurable for other
applications..

ipIP-over-IP encapsulation tunnel interface.

ipipInternally generated interface that is not configurable.

ixgbeThe internal Ethernet process ixgbe0 and ixgbe1 are used by the

RE-DUO-C2600-16G Routing Engine, which is supported on TX Matrix Plus and

PTX5000.

iwLogical interfaces associated with the endpoints of Layer 2 circuit and Layer 2 VPN

connections (pseudowire stitching Layer 2 VPNs). For more information about VPNs,
see the Junos OS VPNs Library for Routing Devices.

lcInternally generated interface that is not configurable.

loLoopback interface. The Junos OS automatically configures one loopback interface

(lo0). The logical interface lo0.16383 is a nonconfigurable interface for router control
traffic.

lsLink services interface.

lsiInternally generated interface that is not configurable.

mlMultilink interface (including Multilink Frame Relay and MLPPP).

moMonitoring services interface (including monitoring services and monitoring services

II). The logical interface mo-fpc/pic/port.16383 is an internally generated,

nonconfigurable interface for router control traffic.

msMultiservices interface.

mtMulticast tunnel interface (internal router interface for VPNs). If your router has

a Tunnel PIC, the Junos OS automatically configures one multicast tunnel interface
(mt) for each virtual private network (VPN) you configure. Although it is not necessary
to configure multicast interfaces, you can use the multicast-only statement to configure
the unit and family so that the tunnel can transmit and receive multicast traffic only.
For more information, see multicast-only.

mtunInternally generated interface that is not configurable.

oc3OC3 IQ interface (configured on the Channelized OC12 IQ and IQE PICs or

Channelized OC3 IQ and IQE PICs).

pdInterface on the rendezvous point (RP) that de-encapsulates packets.

peInterface on the first-hop PIM router that encapsulates packets destined for the

RP router.

30

pimdInternally generated interface that is not configurable.

pimeInternally generated interface that is not configurable.

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

rlsqContainer interface, numbered from 0 through 127, used to tie the primary and

secondary LSQ PICs together in high availability configurations. Any failure of the
primary PIC results in a switch to the secondary PIC and vice versa.

rmsRedundant interface for two multiservices interfaces.

rspRedundant virtual interface for the adaptive services interface.

seSerial interface (including EIA-530, V.35, and X.21 interfaces).

siServices-inline interface, which is hosted on a Trio-based line card.

soSONET/SDH interface.

spAdaptive services interface. The logical interface sp-fpc/pic/port.16383 is an

internally generated, nonconfigurable interface for router control traffic.

stm1STM1 interface (configured on the OC3/STM1 interfaces).

stm4STM4 interface (configured on the OC12/STM4 interfaces).

stm16STM16 interface (configured on the OC48/STM16 interfaces).

t1T1 interface (including channelized DS3-to-DS1 interfaces).

t3T3 interface (including channelized OC12-to-DS3 interfaces).

tapInternally generated interface that is not configurable.

umdUSB modem interface.

vspVoice services interface.

vc4Virtually concatenated interface.

vtVirtual loopback tunnel interface.

xe10-Gigabit Ethernet interface. Some older 10-Gigabit Ethernet interfaces use the
ge media type (rather than xe) to identify the physical part of the network device.

xtLogical interface for Protected System Domains to establish a Layer 2 tunnel

connection.
fpc identifies the number of the FPC or DPC card on which the physical interface is located.

Specifically, it is the number of the slot in which the card is installed.

M40, M40e, M160, M320, M120, T320, T640, and T1600 routers each have eight FPC
slots that are numbered 0 through 7, from left to right as you are facing the front of the
chassis. For information about compatible FPCs and PICs, see the hardware guide for
your router.
The M20 router has four FPC slots that are numbered 0 through 3, from top to bottom
as you are facing the front of the chassis. The slot number is printed adjacent to each
slot.
MX Series routers support DPCs, FPCs, and Modular Interface Cards (MICs). For
information about compatible DPCs, FPCs, PICs, and MICs, see the MX Series Interface
Module Reference.

Copyright 2014, Juniper Networks, Inc.

31

Interfaces Fundamentals for Routing Devices

For M5, M7i, M10, and M10i routers, the FPCs are built into the chassis; you install the PICs
into the chassis.
The M5 and M7i routers have space for up to four PICs. The M7i router also comes with
an integrated Tunnel PIC, or an optional integrated AS PIC, or an optional integrated MS
PIC.
The M10 and M10i routers have space for up to eight PICs.
A routing matrix can have up to 32 FPCs (numbered 0 through 31).
For more information about interface naming for a routing matrix, see Interface Naming
for a Routing Matrix Based on a TX Matrix Router on page 33.
pic identifies the number of the PIC on which the physical interface is located. Specifically,

it is the number of the PIC location on the FPC. FPCs with four PIC slots are numbered 0
through 3. FPCs with three PIC slots are numbered 0 through 2. The PIC location is printed
on the FPC carrier board. For PICs that occupy more than one PIC slot, the lower PIC slot
number identifies the PIC location.
port identifies a specific port on a PIC or DPC. The number of ports varies depending on

the PIC. The port numbers are printed on the PIC.

Logical Part of an Interface Name

The logical unit part of the interface name corresponds to the logical unit number, which
can be a number from 0 through 16,385 for all interface types except demux and PPPoE.
For these two interface types only, the range is 0 through 65,535.
In the virtual part of the name, a period (.) separates the port and logical unit numbers:

J Series routers:
type-pim/0/port.logical

Other platforms:
type-fpc/pic/port.logical

Separators in an Interface Name

There is a separator between each element of an interface name.
In the physical part of the name, a hyphen (-) separates the media type from the FPC
number, and a slash (/) separates the FPC, PIC, and port numbers.
In the virtual part of the name, a period (.) separates the channel and logical unit numbers.
A colon (:) separates the physical and virtual parts of the interface name.

Channel Part of an Interface Name

The channel identifier part of the interface name is required only on channelized interfaces.
For channelized interfaces, channel 0 identifies the first channelized interface. For
channelized IQ and channelized IQE interfaces, channel 1 identifies the first channelized

32

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

interface. A nonconcatenated (that is, channelized) SONET/SDH OC48 interface has

four OC12 channels, numbered 0 through 3.
To determine which types of channelized PICs are currently installed in the router, use
the show chassis hardware command from the top level of the command-line interface
(CLI). Channelized IQ and IQE PICs are listed in the output with intelligent queuing IQ
or enhanced intelligent queuing IQE in the description. For more information, see
Channelized Interfaces Overview.
For ISDN interfaces, you specify the B-channel in the form bc-pim/0/port:n. n is the
B-channel ID and can be 1 or 2. You specify the D-channel in the form dc-pim/0/port:0.

NOTE: For ISDN, the B-channel and D-channel interfaces do not have any
configurable parameters. However, when interface statistics are displayed,
B-channel and D-channel interfaces have statistical values.

NOTE: In the Junos OS implementation, the term logical interfaces generally

refers to interfaces you configure by including the unit statement at the [edit
interfaces interface-name] hierarchy level. Logical interfaces have the .logical
descriptor at the end of the interface name, as in ge-0/0/0.1 or t1-0/0/0:0.1,
where the logical unit number is 1.
Although channelized interfaces are generally thought of as logical or virtual,
the Junos OS sees T3, T1, and NxDS0 interfaces within a channelized IQ or
IQE PIC as physical interfaces. For example, both t3-0/0/0 and t3-0/0/0:1
are treated as physical interfaces by the Junos OS. In contrast, t3-0/0/0.2
and t3-0/0/0:1.2 are considered logical interfaces because they have the .2
at the end of the interface names.

Interface Naming for a Routing Matrix Based on a TX Matrix Router

A routing matrix based on a Juniper Networks TX Matrix router is a multichassis
architecture composed of one TX Matrix router and from one to four interconnected
T640 routers. From the perspective of the user interface, the routing matrix appears as
a single router. The TX Matrix router controls all the T640 routers, as shown in
Figure 3 on page 34.

Copyright 2014, Juniper Networks, Inc.

33

Interfaces Fundamentals for Routing Devices

Figure 3: Routing Matrix

T640

(LCC 0)

(LCC 1)

T640

(LCC 3)

T640

T640

(LCC 2)

Data path
Control path

g003173

TX Matrix
(SCC)

A TX Matrix router is also referred to as a switch-card chassis (SCC). The CLI uses scc to
refer to the TX Matrix router. A T640 router in a routing matrix is also referred to as a
line-card chassis (LCC). The CLI uses lcc as a prefix to refer to a specific T640 router.
LCCs are assigned numbers 0 through 3, depending on the hardware setup and
connectivity to the TX Matrix router. For more information, see the TX Matrix Router
Hardware Guide. A routing matrix can have up to four T640 routers, and each T640 router
has up to eight FPCs. Therefore, the routing matrix as a whole can have up to 32 FPCs
(0 through 31).
In the Junos OS CLI, an interface name has the following format:
type-fpc/pic/port

When you specify the fpc number for a T640 router in a routing matrix, the Junos OS
determines which T640 router contains the specified FPC based on the following
assignment:

On LCC 0, FPC hardware slots 0 through 7 are configured as 0 through 7.

On LCC 1, FPC hardware slots 0 through 7 are configured as 8 through 15.

On LCC 2, FPC hardware slots 0 through 7 are configured as 16 through 23.

On LCC 3, FPC hardware slots 0 through 7 are configured as 24 through 31.

For example, the 1 in se-1/0/0 refers to FPC hardware slot 1 on the T640 router labeled
lcc0. The 11 in t1-11/2/0 refers to FPC hardware slot 3 on the T640 router labeled lcc1. The
20 in so-20/0/1 refers to FPC hardware slot 4 on the T640 router labeled lcc2. The 31 in
t3-31/1/0 refers to FPC hardware slot 7 on the T640 router labeled lcc3.
Table 23 on page 35 summarizes the FPC numbering for a T640 router in a routing matrix.

34

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 23: FPC Numbering for T640 Routers in a Routing Matrix

LCC Numbers Assigned to the T640
Router

Configuration Numbers

0 through 7

8 through 15

16 through 23

24 through 31

Table 24 on page 35 lists each FPC hardware slot and the corresponding configuration
numbers for LCCs 0 through 3.

Table 24: One-to-One FPC Numbering for T640 Routers in a Routing

Matrix
FPC Numbering

T640 Routers
LCC 0

Hardware Slots

Configuration
Numbers

LCC 1
Hardware Slots

Configuration
Numbers

10

11

12

13

14

15

LCC 2
Hardware Slots

Configuration
Numbers

16

17

18

19

20

21

22

23

LCC 3
Hardware Slots

Configuration
Numbers

24

25

26

27

28

29

30

31

Interface Naming for a Routing Matrix Based on a TX Matrix Plus Router

A routing matrix based on a Juniper Networks TX Matrix Plus Router is a multichassis
architecture composed of one TX Matrix Plus router and from one to four interconnected
T1600 routers. From the perspective of the user interface, the routing matrix appears as
a single router. The TX Matrix Plus router controls all the T1600 routers, as shown in
Figure 4 on page 36.

Copyright 2014, Juniper Networks, Inc.

35

Interfaces Fundamentals for Routing Devices

Figure 4: Routing Matrix Based on a TX Matrix Plus Router

T1600 Router
(LCC 0)

T1600 Router
(LCC 1)

T1600 Router
Node (LCC 2)

T1600 Router
(LCC 3)

g004588

TX Matrix
Plus
Router
(SFC)

Data path
Control path

A TX Matrix Plus router is also referred to as a switch-fabric chassis (SFC). The CLI uses
sfc to refer to the TX Matrix Plus router. A T1600 router in a routing matrix is also referred
to as a line-card chassis (LCC). The CLI uses lcc as a prefix to refer to a specific T1600
router.
LCCs are assigned numbers, 0 through 3, depending on the hardware setup and
connectivity to the TX Matrix Plus router. For more information, see the TX Matrix Plus
Router Hardware Guide. A routing matrix based on a TX Matrix Plus router can have up
to four T1600 routers, and each T1600 router has up to eight FPCs. Therefore, the routing
matrix as a whole can have up to 32 FPCs (0 through 31).
In the Junos OS CLI, an interface name has the following format:
type-fpc/pic/port

When you specify the fpc number for a T1600 router in a routing matrix, the Junos OS
determines which T1600 router contains the specified FPC based on the following
assignment:

On LCC 0, FPC hardware slots 0 through 7 are configured as 0 through 7.

On LCC 1, FPC hardware slots 0 through 7 are configured as 8 through 15.

On LCC 2, FPC hardware slots 0 through 7 are configured as 16 through 23.

On LCC 3, FPC hardware slots 0 through 7 are configured as 24 through 31.

For example, the 1 in se-1/0/0 refers to FPC hardware slot 1 on the T1600 router labeled
lcc0. The 11 in t1-11/2/0 refers to FPC hardware slot 3 on the T1600 router labeled lcc1.
The 20 in so-20/0/1 refers to FPC hardware slot 4 on the T1600 router labeled lcc2. The
31 in t3-31/1/0 refers to FPC hardware slot 7 on the T1600 router labeled lcc3.

36

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 25 on page 37 summarizes the FPC numbering for a routing matrix based on a TX
Matrix Plus router.

Table 25: FPC Numbering for T1600 Routers in a Routing Matrix

LCC Numbers Assigned to the T1600
Router

Configuration Numbers

0 through 7

8 through 15

16 through 23

24 through 31

Table 26 on page 37 lists each FPC hardware slot and the corresponding configuration
numbers for LCCs 0 through 3.

Table 26: One-to-One FPC Numbering for T1600 Routers in a Routing

Matrix
FPC Numbering

T1600 Routers
LCC 0

Hardware Slots

Configuration
Numbers

LCC 1
Hardware Slots

Configuration
Numbers

10

11

12

13

14

15

LCC 2
Hardware Slots

Configuration
Numbers

16

17

18

19

20

21

22

23

LCC 3
Hardware Slots

Configuration
Numbers

24

25

26

27

28

29

30

31

Copyright 2014, Juniper Networks, Inc.

37

Interfaces Fundamentals for Routing Devices

Chassis Interface Naming

You configure some PIC properties, such as framing, at the [edit chassis] hierarchy level.
Chassis interface naming varies depending on the routing hardware.

To configure PIC properties for a standalone router, you must specify the FPC and PIC
numbers, as follows:
[edit chassis]
fpc slot-number {
pic pic-number {
...
}
}

To configure PIC properties for a T640 or T1600 router configured in a routing matrix,
you must specify the LCC, FPC, and PIC numbers, as follows:
[edit chassis]
lcc lcc-number {
fpc slot-number { # Use the hardware FPC slot number
pic pic-number {
...
}
}
}

For the FPC slot in a T640 router in a routing matrix, specify the actual hardware slot
number, as labeled on the T640 router chassis. Do not use the corresponding software
FPC configuration numbers shown in Table 24 on page 35.
For the FPC slot in a T1600 router in a routing matrix, specify the actual hardware slot
number, as labeled on the T1600 router chassis. Do not use the corresponding software
FPC configuration numbers shown in Table 25 on page 37.
For more information about the [edit chassis] hierarchy, see the Junos OS Administration
Library for Routing Devices.

Examples: Interface Naming

This section provides examples of naming interfaces. For an illustration of where slots,
PICs, and ports are located, see Figure 5 on page 39.

38

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Figure 5: Interface Slot, PIC, and Port Locations

For an FPC in slot 1 with two OC3 SONET/SDH PICs in PIC positions 0 and 1, each PIC
with two ports uses the following names:
so-1/0/0.0
so-1/0/1.0
so-1/1/0.0
so-1/1/1.0

An OC48 SONET/SDH PIC in slot 1 and in concatenated mode appears as a single FPC
with a single PIC, which has a single port. If this interface has a single logical unit, it has
the following name:
so-1/0/0.0

An OC48 SONET/SDH PIC in slot 1 and in channelized mode has a number for each
channel. For example:
so-1/0/0:0
so-1/0/0:1

For an FPC in slot 1 with a Channelized OC12 PIC in PIC position 2, the DS3 channels have
the following names:
t3-1/2/0:0
t3-1/2/0:1
t3-1/2/0:2
...
t3-1/2/0:11

For an FPC in slot 1 with four OC12 ATM PICs (the FPC is fully populated), the four PICs,
each with a single port and a single logical unit, have the following names:
at-1/0/0.0
at-1/1/0.0
at-1/2/0.0

Copyright 2014, Juniper Networks, Inc.

39

Interfaces Fundamentals for Routing Devices

at-1/3/0.0

In a routing matrix on the T640 router labeled lcc1, for an FPC in slot 5 with four SONET
OC192 PICs, the four PICs, each with a single port and a single logical unit, have the
following names:
so-13/0/0.0
so-13/1/0.0
so-13/2/0.0
so-13/3/0.0

For an FPC in slot 1 with one 4-port ISDN BRI interface card, port 4 has the following
name:
br-1/0/4

The first B-channel, the second B-channel, and the control channel have the following
names:
bc-1/0/4:1
bc-1/0/4:2
dc-1/0/4:0

Related
Documentation

Router Interfaces Overview on page 4

Physical Part of an Interface Name on page 52

Supported Routing Engines by Chassis

Interface Encapsulations Overview

Table 27 on page 40 lists encapsulation support by interface type.

Table 27: Encapsulation Support by Interface Type

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

aeAggregated Ethernet

ethernet-cccEthernet cross-connect

dixEthernet DIXv2 (RFC 894)

extended-vlan-cccNonstandard TPID tagging

vlan-ccc802.1Q tagging for a cross-connect

interface
for a cross-connect
extended-vlan-vplsExtended VLAN virtual

private LAN service

flexible-ethernet-servicesAllows per-unit

Ethernet encapsulation configuration

vlan-ccc802.1Q tagging for a cross-connect
ethernet-vplsEthernet virtual private LAN

service
vlan-vplsVLAN virtual private LAN service

40

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

asAggregated

cisco-hdlcCisco-compatible HDLC framing

NA

SONET/SDH interface
pppSerial PPP device
atATM1 interface

atm-ccc-cell-relayATM cell relay

atm-ccc-cell-relayATM cell relay for CCC

encapsulation for a cross-connect

atm-ccc-vc-muxATM VC for CCC
atm-pvcATM permanent virtual circuits
atm-cisco-nlpidCisco-compatible ATM NLPID
ethernet-over-atmEthernet over ATM

encapsulation

encapsulation
atm-nlpidATM NLPID encapsulation
atm-snapATM LLC/SNAP encapsulation
atm-tcc-snapATM LLC/SNAP for a

translational cross-connect
atm-tcc-vc-muxATM VC for a translational

cross-connect
atm-vc-muxATM VC multiplexing
ether-over-atm-llcEthernet over ATM

(LLC/SNAP) encapsulation
atATM2 intelligent

atm-ccc-cell-relayATM cell relay

queuing (IQ) interface

encapsulation for a cross-connect

atm-ccc-cell-relayATM cell relay for CCC

atm-ccc-vc-muxATM VC for CCC

atm-pvcATM permanent virtual circuits

atm-cisco-nlpidCisco-compatible ATM NLPID
ethernet-over-atmEthernet over ATM

encapsulation

encapsulation
atm-mlppp-llcATM MLPPP over AAL5/LLC
atm-nlpidATM NLPID encapsulation
atm-ppp-llcATM PPP over AAL5/LLC
atm-ppp-vc-muxATM PPP over raw AAL5
atm-snapATM LLC/SNAP encapsulation
atm-tcc-snapATM LLC/SNAP for a

translational cross-connect
atm-tcc-vc-muxATM VC for a translational

cross-connect
atm-vc-muxATM VC multiplexing
ether-over-atm-llcEthernet over ATM

(LLC/SNAP) encapsulation
ether-vpls-over-atm-llcEthernet VPLS over

ATM (bridging) encapsulation

Copyright 2014, Juniper Networks, Inc.

41

Interfaces Fundamentals for Routing Devices

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

bcmGigabit Ethernet

NA

NA

NA

NA

cisco-hdlcCisco-compatible HDLC framing

apsSONET interface required for APS

internal interfaces
brIntegrated Services

Digital Network (ISDN)

interface
ciContainer interface

configuration.
pppSerial PPP device
dsDS0 interface

cisco-hdlcCisco-compatible HDLC framing

frame-relay-cccFrame Relay DLCI for CCC

cisco-hdlc-cccCisco-compatible HDLC

frame-relay-pppPPP over Frame Relay

framing for a cross-connect

frame-relay-tccFrame Relay DLCI for a
cisco-hdlc-tccCisco-compatible HDLC framing

translational cross-connect

for a translational cross-connect

extended-frame-relay-cccAny Frame Relay

DLCI for a cross-connect

extended-frame-relay-tccAny Frame Relay

DLCI for a translational cross-connect

flexible-frame-relayMultiple Frame Relay

encapsulations
frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
frame-relay-port-cccFrame Relay port

encapsulation for a cross-connect

frame-relay-tccFrame Relay for a translational

cross-connect
multilink-frame-relay-uni-nniMultilink Frame

Relay UNI NNI (FRF.16) encapsulation

pppSerial PPP device
ppp-cccSerial PPP device for a cross-connect
ppp-tccSerial PPP device for a translational

cross-connect
dscDiscard interface

42

NA

NA

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

e1E1 interface (including

cisco-hdlcCisco-compatible HDLC framing

frame-relay-cccFrame Relay DLCI for CCC

channelized STM1-to-E1
interfaces)

cisco-hdlc-cccCisco-compatible HDLC

frame-relay-pppPPP over Frame Relay

framing for a cross-connect

frame-relay-tccFrame Relay DLCI for a
cisco-hdlc-tccCisco-compatible HDLC framing

translational cross-connect

for a translational cross-connect

extended-frame-relay-cccAny Frame Relay

DLCI for a cross-connect

extended-frame-relay-tccAny Frame Relay

DLCI for a translational cross-connect

flexible-frame-relayMultiple Frame Relay

encapsulations
frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
frame-relay-port-cccFrame Relay port

encapsulation for a cross-connect

frame-relay-tccFrame Relay for a translational

cross-connect
multilink-frame-relay-uni-nniMultilink Frame

Relay UNI NNI (FRF.16) encapsulation

pppSerial PPP device
ppp-cccSerial PPP device for a cross-connect
ppp-tccSerial PPP device for a translational

cross-connect

Copyright 2014, Juniper Networks, Inc.

43

Interfaces Fundamentals for Routing Devices

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

e3E3 interface (including

cisco-hdlcCisco-compatible HDLC framing

frame-relay-cccFrame Relay DLCI for CCC

cisco-hdlc-cccCisco-compatible HDLC

frame-relay-pppPPP over Frame Relay

E3 IQ and IQE interfaces)

framing for a cross-connect
frame-relay-tccFrame Relay DLCI for a
cisco-hdlc-tccCisco-compatible HDLC framing

translational cross-connect

for a translational cross-connect

extended-frame-relay-cccAny Frame Relay

DLCI for a cross-connect

extended-frame-relay-tccAny Frame Relay

DLCI for a translational cross-connect

flexible-frame-relayMultiple Frame Relay

encapsulations
frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
frame-relay-port-cccFrame Relay port

encapsulation for a cross-connect

frame-relay-tccFrame Relay for a translational

cross-connect
pppSerial PPP device
ppp-cccSerial PPP device for a cross-connect
ppp-tccSerial PPP device for a translational

cross-connect
emManagement and

NA

NA

internal Ethernet interfaces

44

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

feFast Ethernet interface

ethernet-cccEthernet cross-connect

dixEthernet DIXv2 (RFC 894)

ethernet-tccEthernet translational

vlan-ccc802.1Q tagging for a cross-connect

cross-connect
vlan-vplsVLAN virtual private LAN service
ethernet-vplsEthernet virtual private LAN

service
extended-vlan-cccNonstandard TPID tagging

for a cross-connect
extended-vlan-tcc802.1Q tagging for a

translational cross-connect
extended-vlan-vplsExtended VLAN virtual

private LAN service

vlan-ccc802.1Q tagging for a cross-connect
vlan-vplsVLAN virtual private LAN service
fxpManagement and

NA

NA

geGigabit Ethernet

ethernet-cccEthernet cross-connect

dixEthernet DIXv2 (RFC 894)

interface (including Gigabit

Ethernet IQ interfaces)

ethernet-tccEthernet translational

vlan-ccc802.1Q tagging for a cross-connect

internal Ethernet interfaces

cross-connect
vlan-tcc802.1Q tagging for a translational
ethernet-vplsEthernet virtual private LAN

cross-connect

service
vlan-vplsVLAN virtual private LAN service
extended-vlan-cccNonstandard TPID tagging

for a cross-connect
extended-vlan-tcc802.1Q tagging for a

translational cross-connect
extended-vlan-vplsExtended VLAN virtual

private LAN service

flexible-ethernet-servicesAllows per-unit

Ethernet encapsulation configuration

vlan-ccc802.1Q tagging for a cross-connect
vlan-vplsVLAN virtual private LAN service
ixgbe10-Gigabit Ethernet

NA

NA

NA

NA

internal interfaces
loLoopback interface;

the Junos OS automatically

configures one loopback
interface (lo0)

Copyright 2014, Juniper Networks, Inc.

45

Interfaces Fundamentals for Routing Devices

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

lsLink services interface

multilink-frame-relay-uni-nniMultilink Frame

multilink-frame-relay-end-to-endMultilink

Relay UNI NNI (FRF.16) encapsulation

Frame Relay end-to-end (FRF.15)

multilink-pppMultilink PPP

lsqLink services IQ

multilink-frame-relay-uni-nniMultilink Frame

multilink-frame-relay-end-to-endMultilink

interface

Relay UNI NNI (FRF.16) encapsulation

Frame Relay end-to-end (FRF.15)

multilink-pppMultilink PPP

ltLogical tunnel interface

NA

ethernetEthernet service
ethernet-vplsEthernet virtual private LAN

service
ethernet-cccEthernet cross-connect
frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
vlanVLAN service
vlan-ccc802.1Q tagging for a cross-connect
vlan-vplsVLAN virtual private LAN service
mlMultilink interface

(including Multilink Frame

Relay and MLPPP)

NA

multilink-frame-relay-end-to-endMultilink

Frame Relay end-to-end (FRF.15)

multilink-pppMultilink PPP

46

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

seSerial interface

cisco-hdlcCisco-compatible HDLC framing

frame-relay-cccFrame Relay DLCI for CCC

(including EIA-530, V.35,

and X.21 interfaces)

cisco-hdlc-cccCisco-compatible HDLC

frame-relay-pppPPP over Frame Relay

framing for a cross-connect

frame-relay-tccFrame Relay DLCI for a
cisco-hdlc-tccCisco-compatible HDLC framing

translational cross-connect

for a translational cross-connect

frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
frame-relay-port-cccFrame Relay port

encapsulation for a cross-connect

frame-relay-tccFrame Relay for a translational

cross-connect
pppSerial PPP device
ppp-cccSerial PPP device for a cross-connect
ppp-tccSerial PPP device for a translational

cross-connect

Copyright 2014, Juniper Networks, Inc.

47

Interfaces Fundamentals for Routing Devices

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

soSONET/SDH interface

cisco-hdlcCisco-compatible HDLC framing

frame-relay-cccFrame Relay DLCI for CCC

cisco-hdlc-cccCisco-compatible HDLC

frame-relay-pppPPP over Frame Relay

framing for a cross-connect

frame-relay-tccFrame Relay DLCI for a
cisco-hdlc-tccCisco-compatible HDLC framing

translational cross-connect

for a translational cross-connect

multilink-frame-relay-end-to-endIQE SONET
extended-frame-relay-cccAny Frame Relay

DLCI for a cross-connect

PICs support Multilink Frame Relay end-to-end

(FRF.15)

extended-frame-relay-tccAny Frame Relay

multilink-pppIQE SONET PICs support

DLCI for a translational cross-connect

Multilink PPP

flexible-frame-relayMultiple Frame Relay

encapsulations
frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
frame-relay-port-cccFrame Relay port

encapsulation for a cross-connect

frame-relay-tccFrame Relay for a translational

cross-connect
pppSerial PPP device
ppp-cccSerial PPP device for a cross-connect
ppp-tccSerial PPP device for a translational

cross-connect

48

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

t1T1 interface (including

cisco-hdlcCisco-compatible HDLC framing

frame-relay-cccFrame Relay DLCI for CCC

channelized DS3-to-DS1
interfaces)

cisco-hdlc-cccCisco-compatible HDLC

frame-relay-pppPPP over Frame Relay

framing for a cross-connect

frame-relay-tccFrame Relay DLCI for a
cisco-hdlc-tccCisco-compatible HDLC framing

translational cross-connect

for a translational cross-connect

extended-frame-relay-cccAny Frame Relay

DLCI for a cross-connect

extended-frame-relay-tccAny Frame Relay

DLCI for a translational cross-connect

flexible-frame-relayMultiple Frame Relay

encapsulations
frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
frame-relay-port-cccFrame Relay port

encapsulation for a cross-connect

frame-relay-tccFrame Relay for a translational

cross-connect
multilink-frame-relay-uni-nniMultilink Frame

Relay UNI NNI (FRF.16) encapsulation

pppSerial PPP device
ppp-cccSerial PPP device for a cross-connect
ppp-tccSerial PPP device for a translational

cross-connect

Copyright 2014, Juniper Networks, Inc.

49

Interfaces Fundamentals for Routing Devices

Table 27: Encapsulation Support by Interface Type (continued)

Interface Type

Physical Interface Encapsulation

Logical Interface Encapsulation

t3T3 interface (including

cisco-hdlcCisco-compatible HDLC framing

frame-relay-cccFrame Relay DLCI for CCC

channelized OC12-to-DS3
interfaces)

cisco-hdlc-cccCisco-compatible HDLC

frame-relay-pppPPP over Frame Relay

framing for a cross-connect

frame-relay-tccFrame Relay DLCI for a
cisco-hdlc-tccCisco-compatible HDLC framing

translational cross-connect

for a translational cross-connect

extended-frame-relay-cccAny Frame Relay

DLCI for a cross-connect

extended-frame-relay-tccAny Frame Relay

DLCI for a translational cross-connect

flexible-frame-relayMultiple Frame Relay

encapsulations
frame-relayFrame Relay encapsulation
frame-relay-cccFrame Relay for a

cross-connect
frame-relay-port-cccFrame Relay port

encapsulation for a cross-connect

frame-relay-tccFrame Relay for a translational

cross-connect
pppSerial PPP device
ppp-cccSerial PPP device for a cross-connect
ppp-tccSerial PPP device for a translational

cross-connect
Controller-level
channelized IQ interfaces
(cau4, coc1, coc3, coc12,
cstm1, ct1, ct3, ce1)

NA

NA

Services interfaces (cp, gr,

ip, mo, vt, es, mo, rsp, sp)

NA

NA

Unconfigurable, internally
generated interfaces (gre,
ipip, learning-chip (lc), lsi,
tap, mt, mtun, pd, pe, pimd,
pime)

NA

NA

NOTE: You can configure GRE interfaces (gre-x/y/z) only for GMPLS control
channels. GRE interfaces are not supported or configurable for other
applications. For more information about GMPLS, see the Junos OS MPLS
Applications Library for Routing Devices and the Junos OS, Release 14.2.

50

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

Related
Documentation

Understanding Transient Interfaces on page 5

Router Interfaces Overview on page 4

Types of Interfaces Overview on page 4

Interface Descriptors Overview

When you configure an interface, you are effectively specifying the properties for a physical
interface descriptor. In most cases, the physical interface descriptor corresponds to a
single physical device and consists of the following parts:

The interface name, which defines the media type

The slot in which the FPC or DPC is located

The location on the FPC in which the PIC is installed

The PIC or DPC port

The interfaces channel and logical unit numbers (optional)

Each physical interface descriptor can contain one or more logical interface descriptors.
These allow you to map one or more logical (or virtual) interfaces to a single physical
device. Creating multiple logical interfaces is useful for ATM, Frame Relay, and Gigabit
Ethernet networks, in which you can associate multiple virtual circuits, data-link
connections, or virtual LANs (VLANs) with a single interface device.
Each logical interface descriptor can have one or more family descriptors to define the
protocol family that is associated with and allowed to run over the logical interface.
The following protocol families are supported:

Internet Protocol version 4 (IPv4) suite (inet)

Internet Protocol version 6 (IPv6) suite (inet6)

Circuit cross-connect (CCC)

Translational cross-connect (TCC)

International Organization for Standardization (ISO)

Multilink Frame Relay end-to-end (MLFR end-to-end)

Multilink Frame Relay user-to-network interface network-to-network interface (MLFR

UNI NNI)

Multilink Point-to-Point Protocol (MLPPP)

Multiprotocol Label Switching (MPLS)

Trivial Network Protocol (TNP)

(M Series, T Series, and MX Series routers only) Virtual private LAN service (VPLS)

Copyright 2014, Juniper Networks, Inc.

51

Interfaces Fundamentals for Routing Devices

Finally, each family descriptor can have one or more address entries, which associate a
network address with a logical interface and hence with the physical interface.
You configure the various interface descriptors as follows:

You configure the physical interface descriptor by including the interfaces interface-name
statement.

You configure the logical interface descriptor by including the unit statement within
the interfaces interface-name statement or by including the .logical descriptor at the
end of the interface name, as in t3-0/0/0.1, where the logical unit number is 1, as shown
in the following examples:
[edit]
user@host# set interfaces t3-0/0/0 unit 1
[edit]
user@host# edit interfaces t3-0/0/0.1
[edit interfaces t3-0/0/0]
user@host# set unit 1

You configure the family descriptor by including the family statement within the unit
statement.

You configure address entries by including the address statement within the family
statement.

You configure tunnels by including the tunnel statement within the unit statement.

NOTE: The address of a logical interface cannot be the same as a tunnel

interfaces source or destination address. If you try to configure a logical
interface with a tunnel interfaces address or vice versa, a commit failure will
occur.

Related
Documentation

Router Interfaces Overview on page 4

Physical Part of an Interface Name

Interface Names for ACX Series Universal Access Routers on page 52

J Series Interface Names on page 53

Interface Names for M Series and T Series Routers on page 53

MX Series Router Interface Names on page 53

Interface Names for PTX Series Routers on page 54

Interface Names for ACX Series Universal Access Routers

ACX Series routers do not have actual PIC devices. Instead they have built-in network
ports on the front panel of the router. These ports are named using the same naming
convention used for routers with PIC devices with the understanding that the FPC, PIC
and port are pseudo devices. When you display information about one of these ports,

52

Copyright 2014, Juniper Networks, Inc.

Chapter 1: Router Interfaces Overview

you specify the interface type, the slot for the Flexible PIC Concentrator (FPC), the slot
on the FPC for the Physical Interface Card (PIC), and the configured port number.
In the physical part of the interface name, a hyphen (-) separates the media type from
the FPC number, and a slash (/) separates the FPC, PIC, and port numbers:
type-fpc/pic/port

J Series Interface Names

On J Series routers, when you display information about an interface, you specify the
interface type, the slot in which the Physical Interface Module (PIM) is installed, 0, and
the configured port number.
In the physical part of the interface name, a hyphen (-) separates the media type from
the PIM number, and a slash (/) separates the PIM, 0, and port numbers:
type-pim/0/port

NOTE: An exception to the type-pim/0/port physical description is the

Integrated Services Digital Network (ISDN) dialer interface, which uses the
syntax dlnumber.

Interface Names for M Series and T Series Routers

On M Series and T Series routers, when you display information about an interface, you
specify the interface type, the slot in which the Flexible PIC Concentrator (FPC) is installed,
the slot on the FPC in which the Physical Interface Card (PIC) is located, and the
configured port number.
In the physical part of the interface name, a hyphen (-) separates the media type from
the FPC number, and a slash (/) separates the FPC, PIC, and port numbers:
type-fpc/pic/port

NOTE: Exceptions to the type-fpc/pic/port physical description include the

aggregated Ethernet and aggregated SONET/SDH interfaces, which use the
syntax ae number and as number, respectively.

MX Series Router Interface Names

On MX Series routers when you display information about an interface, you specify the
interface type, the Dense Port Concentrator (DPC), Flexible PIC Concentrator (FPC), or
Modular Port Concentrator (MPC) slot, the PIC or MIC slot, and the configured port
number.

NOTE: Although the MX Series routers use DPCs, FPCs, MPCs, MICs, and
PICs, command syntax in this book is shown as fpc/pic/port for simplicity.

Copyright 2014, Juniper Networks, Inc.

53

Interfaces Fundamentals for Routing Devices

In the physical part of the interface name, a hyphen (-) separates the media type from
the FPC number, and a slash (/) separates the DPC, FPC or MPC, MIC or PIC, and port
numbers:
type-fpc/pic/port

fpcSlot in which the DPC, FPC, or MPC is installed.

picSlot on the FPC in which the PIC is located.

For DPCs, MICs, and the 16-port MPC, the PIC value is a logical grouping of ports and
varies on different platforms.

portPort number on the DPC, PIC, MPC, or MIC.

Interface Names for PTX Series Routers

On PTX Series Packet Transport Routers, when you display information about an interface,
you specify the interface type, the slot in which the Flexible PIC Concentrator (FPC) is
installed, the slot on the FPC in which the Physical Interface Card (PIC) is located, and
the configured port number.

NOTE:

The PTX router supports Ethernet type interfaces only. The media type
portion of the physical interface name,type supports the Ethernet interface
type only: et.

In the CLI, all PTX3000 PICs are represented as pic0. For more information,
see PTX3000 PIC Description

In the physical part of the interface name, a hyphen (-) separates the media type (et)
from the FPC number, and a slash (/) separates the FPC, PIC, and port numbers:
type-fpc/pic/port

Related
Documentation

Interface Naming Overview on page 26

Logical Part of an Interface Name on page 32

Displaying Interface Configurations Overview

To display a configuration, use either the show command in configuration mode or the
show configuration top-level command. Interfaces are listed in numerical order, from
lowest to highest slot number, then from lowest to highest PIC number, and finally from
lowest to highest port number.
Related
Documentation

54

Router Interfaces Overview on page 4

Copyright 2014, Juniper Networks, Inc.

CHAPTER 2

Configuring Physical Interface Properties

Physical Interface Configuration Statements Overview on page 56

Physical Interfaces Properties Statements List on page 65

Interface Ranges on page 82

Specifying an Aggregated Interface on page 92

Configuring Interface Description on page 92

Configuring the Media MTU on page 93

Configuring the Interface Speed on page 106

Configuring the Link Characteristics on page 109

Interface Alias Names Overview on page 110

Example: Adding an Interface Alias Name on page 111

Clock Source Overview on page 115

Configuring the Clock Source on page 116

Configuring Interface Encapsulation on Physical Interfaces on page 117

Configuring Interface Encapsulation on PTX Series Packet Transport Routers on page 123

Configuring Keepalives on page 124

Configuring the PPP Challenge Handshake Authentication Protocol on page 126

Configuring the PPP Password Authentication Protocol on page 129

Configuring PPP Address and Control Field Compression on page 133

Configuring the PPP Protocol Field Compression on page 135

Monitoring a PPP Session on page 136

Tracing Operations of the pppd Process on page 137

Configuring the Router as a DCE with Frame Relay Encapsulation on page 138

Receive and Transmit Leaky Bucket Properties Overview on page 138

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

Understanding Unidirectional Traffic Flow on Physical Interfaces on page 141

Enabling Unidirectional Traffic Flow on Physical Interfaces on page 142

Physical Interface Damping Overview on page 143

Copyright 2014, Juniper Networks, Inc.

55

Interfaces Fundamentals for Routing Devices

Damping Shorter Physical Interface Transitions on page 149

Damping Longer Physical Interface Transitions on page 150

Example: Configuring Physical Interface Damping on page 151

Configuring Multiservice Physical Interface Properties on page 153

Enabling or Disabling SNMP Notifications on Physical Interfaces on page 154

Configuring Accounting for the Physical Interface on page 155

Disabling a Physical Interface on page 156

Physical Interface Configuration Statements Overview

The software driver for each network media type sets reasonable default values for
general interface properties, such as the interfaces maximum transmission unit (MTU)
size, receive and transmit leaky bucket properties, link operational mode, and clock source.
M Series, MX Series, T Series, and J Series routers are factory configured according to the
specific router, its features, and its physical interfaces. This section includes a default
configuration example showing the statements used to configure the physical interfaces
properties. Additional statements are used to set properties for specific interface types
and are described in Physical Interfaces Properties Statements List on page 65.
To modify any of the default general interface properties, include the appropriate
statements at the [edit interfaces interface-name] hierarchy level:

NOTE: The following configuration hierarchy and its included statements

are shown only as an example of a configuration statement hierarchy and
should not be referenced for resolving actual configurations. For information
on a specific hierarchy level, see the hierarchy level document for that specific
hierarchy, for example [edit interfaces] Hierarchy Level on page 368.

interfaces {
traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
flag flag <disable>;
}
interface-name {
accounting-profile name;
aggregated-ether-options {
(flow-control | no-flow-control);
lacp {
(active | passive);
link-protection{
disable;
(revertive | non-revertive (Interfaces));
periodic interval;
system-priority priority;
}
link-protection;
link-speed speed;

56

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

(loopback | no-loopback);
minimum-links number;
source-address-filter {
mac-address
}
(source-filtering | no-source-filtering);
}
aggregated-sonet-options {
link-speed speed | mixed;
minimum-links number;
}
atm-options {
cell-bundle-size cells;
ilmi;
linear-red-profiles profile-name {
high-plp-max-threshold percent;
low-plp-max-threshold percent;
queue-depth cells high-plp-threshold percent low-plp-threshold percent;
}
mpls {
pop-all-labels {
required-depth number;
}
}
pic-type (atm1 | atm2);
plp-to-clp;
promiscuous-mode {
vpi vpi-identifier;
}
scheduler-maps map-name {
forwarding-class class-name {
epd-threshold cells plp1 cells;
linear-red-profile profile-name;
priority (high | low);
transmit-weight (cells number | percent number);
}
vc-cos-mode (alternate | strict);
}
vpi vpi-identifier {
maximum-vcs maximum-vcs;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained
rate burst length);
queue-length number;
}
}
}
clocking clock-source;
data-input (system | interface interface-name);
dce;
serial-options {

Copyright 2014, Juniper Networks, Inc.

57

Interfaces Fundamentals for Routing Devices

clock-rate rate;
clocking-mode (dce | internal | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
description text;
dialer-options {
pool pool-name <priority priority>;
}
disable;
ds0-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
byte-encoding (nx56 | nx64);
fcs (16 | 32);
idle-cycle-flag (flags | ones);
invert-data;
loopback payload;
start-end-flag (filler | shared);
}
e1-options {
bert-error-rate rate;

58

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

bert-period seconds;
fcs (16 | 32);
framing (g704 | g704-no-crc4 | unframed);
idle-cycle-flag (flags | ones);
invert-data;
loopback (local | remote);
start-end-flag (filler | shared);
timeslots time-slot-range;
}
e3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout feet;
compatibility-mode (digital-link | kentrox | larscom) <subrate value>;
fcs (16 | 32);
framing (g.751 | g.832);
idle-cycle-flag (filler | shared);
invert-data;
loopback (local | remote);
(payload-scrambler | no-payload-scrambler);
start-end-flag (filler | shared);
(unframed | no-unframed);
}
encapsulation type;
es-options {
backup-interface es-fpc/pic/port;
}
fastether-options {
802.3ad aex;
(flow-control | no-flow-control);
ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
flexible-vlan-tagging;
gigether-options {
802.3ad aex;
(asynchronous-notification | no-asynchronous-notification);
(auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online |
local-interface-offline>;
auto-reconnect seconds;
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
mpls {

Copyright 2014, Juniper Networks, Inc.

59

Interfaces Fundamentals for Routing Devices

pop-all-labels {
required-depth number;
}
}
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
ethernet-switch-profile {
(mac-learn-enable | no-mac-learn-enable);
tag-protocol-id [ tpids ];
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
}
}
}
(gratuitous-arp-reply | no-gratuitous-arp-reply);
hold-time up milliseconds down milliseconds;
interface-set interface-set-name {
interface ethernet-interface-name {
(unit unit-number | vlan-tags-outer vlan-tag);
}
}
isdn-options {
bchannel-allocation (ascending | descending);
calling-number number;
pool pool-name <priority priority>;
spid1 spid-string;
spid2 spid-string;
static-tei-val value;
switch-type (att5e | etsi | ni1 | ntdms100 | ntt);
t310 seconds;
tei-option (first-call | power-up);
}
keepalives <down-count number> <interval seconds> <up-count number>;

60

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

link-mode mode;
lmi {
lmi-type (ansi | itu | c-lmi);
n391dte number;
n392dce number;
n392dte number;
n393dce number;
n393dte number;
t391dte seconds;
t392dce seconds;
}
lsq-failure-options {
no-termination-request;
[ trigger-link-failure interface-name ];
}
mac mac-address;
mlfr-uni-nni-bundle-options {
acknowledge-retries number;
acknowledge-timer milliseconds;
action-red-differential-delay (disable-tx | remove-link);
cisco-interoperability send-lip-remove-link-for-link-reject;
drop-timeout milliseconds;
fragment-threshold bytes;
hello-timer milliseconds;
link-layer-overhead percent;
lmi-type (ansi | itu | c-lmi);
minimum-links number;
mrru bytes;
n391 number;
n392 number;
n393 number;
red-differential-delay milliseconds;
t391 seconds;
t392 seconds;
yellow-differential-delay milliseconds;
encapsulation type;
}
modem-options {
dialin (console | routable);
init-command-string initialization-command-string;
}
mtu bytes;
multiservice-options {
(core-dump | no-core-dump);
(syslog | no-syslog);
(dump-on-flow-control);
flow-control-options {
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
}
}
native-vlan-id number;
no-gratuitous-arp-request;
no-keepalives;
no-partition {

Copyright 2014, Juniper Networks, Inc.

61

Interfaces Fundamentals for Routing Devices

interface-type type;
}
optics-options {
wavelength nm;
alarmalarm-name {
(syslog | link-down);
}
warningwarning-name {
(syslog | link-down);
}
}
partition partition-number oc-slice oc-slice-range interface-type type;
timeslots time-slot-range;
passive-monitor-mode;
per-unit-scheduler;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
dynamic-profile profile-name;
no-termination-request;
pap {
access-profile name;
local-name name;
local-password password;
passive;
}
}
receive-bucket {
overflow (discard | tag);
rate percentage;
threshold bytes;
}
redundancy-options {
primary sp-fpc/pic/port;
secondary sp-fpc/pic/port;
}
schedulers number;
serial-options {
clock-rate rate;
clocking-mode (dce | internal | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);

62

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopbackmode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
services-options {
inactivity-timeout seconds;
open-timeout seconds;
syslog {
host hostname {
facility-override facility-name;
log-prefix prefix-number;
services priority-level;
}
}
}
shdsl-options {
annex (annex-a | annex-b);
line-rate line-rate;
loopback (local | remote);
snr-margin {
current margin;
snext margin;
}
}
sonet-options {
aggregate asx;
aps {
advertise-interval milliseconds;
authentication-key key;
force;
hold-time milliseconds;
lockout;

Copyright 2014, Juniper Networks, Inc.

63

Interfaces Fundamentals for Routing Devices

neighbor address;
paired-group group-name;
preserve-interface;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
bytes {
c2 value;
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
fcs (16 | 32);
loopback (local | remote);
mpls {
pop-all-labels {
required-depth number;
}
}
path-trace trace-string;
(payload-scrambler | no-payload-scrambler);
rfc-2615;
trigger {
defect ignore;
hold-time up milliseconds down milliseconds;
}
vtmapping (itu-t | klm);
(z0-increment | no-z0-increment);
}
(speed (10m | 100m | 1g | auto) | speed (auto | 1Gbps | 100Mbps | 10Mbps) | speed
(oc3 | oc12 | oc48));
stacked-vlan-tagging;
switch-options {
switch-port port-number {
(auto-negotiation | no-auto-negotiation);
speed (10m | 100m | 1g);
link-mode (full-duplex | half-duplex);
}
}
multicast-statistics
t1-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout value;
byte-encoding (nx56 | nx64);
crc-major-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5);
crc-minor-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5 | 5e-6 | 1e-6);
fcs (16 | 32);
framing (esf | sf);

64

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

idle-cycle-flag (flags | ones);

invert-data;
line-encoding (ami | b8zs);
loopback (local | payload | remote);
remote-loopback-respond;
start-end-flag (filler | shared);
timeslots time-slot-range;
}
t3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout feet;
(cbit-parity | no-cbit-parity);
compatibility-mode (adtran | digital-link | kentrox | larscom | verilink) <subrate
value>;
fcs (16 | 32);
(feac-loop-respond | no-feac-loop-respond);
idle-cycle-flag value;
(long-buildout | no-long-buildout);
(loop-timing | no-loop-timing);
loopback (local | payload | remote);
(mac | no-mac);
(payload-scrambler | no-payload-scrambler);
start-end-flag (filler | shared);
}
traceoptions {
flag flag <flag-modifier> <disable>;
}
transmit-bucket {
overflow discard;
rate percentage;
threshold bytes;
}
(traps | no-traps);
unidirectional;
vlan-tagging;
vlan-vci-tagging;
unit logical-unit-number {
logical-interface-statements;
}
}
}

Related
Documentation

Router Interfaces Overview on page 4

Physical Interfaces Properties Statements List

Table 28 on page 66 lists statements that you can use to configure physical interfaces.

Copyright 2014, Juniper Networks, Inc.

65

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties

Statement

Interface Types

Usage Guidelines

802.3ad aex

Aggregated Ethernet interfaces

Aggregated Ethernet Interfaces Overview

access-profile name

Interfaces with Point-to-Point Protocol

(PPP) encapsulation

Configuring the PPP Challenge

Handshake Authentication Protocol on
page 126

accounting-profile name

All

Configuring Accounting for the Physical

Interface on page 155

acfc

Interfaces with PPP encapsulation

Configuring PPPoE

acknowledge-retries number

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

acknowledge-timer milliseconds

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

action-red-differential-delay

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

advertise-interval milliseconds

SONET/SDH interfaces

Configuring APS Timers

aggregate

Gigabit Ethernet intelligent queuing (IQ

and IQE) interfaces and Gigabit Ethernet
interfaces with small form-factor
pluggable transceivers (SFPs) (except the
10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i
router)

Configuring Gigabit Ethernet Policers

aggregate asx

Aggregated SONET/SDH interfaces

Configuring Aggregated SONET/SDH

Interfaces

aggregated-ether-options

Aggregated Ethernet interfaces

Aggregated Ethernet Interfaces Overview

aggregate-ports

SONET/SDH interfaces

Configuring 4-Port OC192 PIC to Operate

in OC768-over-OC192 Mode

aggregated-sonet-options

Aggregated SONET/SDH interfaces

Configuring Aggregated SONET/SDH

Interfaces

alarmalarm-name

10-Gigabit Ethernet interfaces

Configuring 10-Gigabit Ethernet Link Down

Notification for Optics Options Alarm or
Warning

All

Example: Adding an Interface Alias Name

on page 111

(disable-tx | remove-link)

(syslog | link-down)

alias alias-name;

66

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement
annex (annex-a | annex-b)

Interface Types

Usage Guidelines

ATM interfaces on J Series routers

Configuring SHDSL Operating Mode on an

ATM Physical Interface

SONET interfaces using annex-b for MSP

switching on M320 and M120 Routers

Configuring Basic Automatic Protect

Switching

aps

SONET/SDH interfaces

SONET/SDH Interfaces Overview

atm-encapsulation (direct | plcp)

E3 and T3 traffic over Asynchronous

Transfer Mode (ATM) interfaces

Configuring E3 and T3 Parameters on ATM

Interfaces

atm-options

ATM1 and ATM2 IQ interfaces

Interface Encapsulations Overview on

page 40

authentication-key key

SONET/SDH interfaces

SONET/SDH Interfaces Overview

backup-interface

E1, E3, T1, T3 and Fast Ethernet

Configuring ISDN Logical Interface

Properties

bandwidth-limit bps

Gigabit Ethernet and Gigabit Ethernet IQ

and IQE PICs with SFPs (except the
10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i
router)

Configuring Gigabit Ethernet Policers

bchannel-allocation (ascending |

J Series routers equipped with a Dual-Port

Channelized T1/E1 PIM; for Integrated
Services Digital Network Primary Rate
Interfaces (ISDN PRI)

Allocating B-Channels for Dialout

bert-algorithm algorithm

E3, T1, T3, multichannel DS3, channelized

interfaces (DS3, OC12, and STM1), and
channelized IQ and IQE interfaces (E1 and
DS3)

Interface Diagnostics on page 329

bert-error-rate rate

E1, E3, T1, T3, and channelized interfaces

(DS3, OC3, OC12, and STM1)

Interface Diagnostics on page 329

bert-period seconds

E1, E3, T1, T3, and channelized interfaces

(DS3, OC12, and STM1)

Interface Diagnostics on page 329

Configuring the T1 Buildout value

T1 interfaces

Configuring the T1 Buildout

buildout feet

E3 and T3 traffic over ATM interfaces

Configuring E3 and T3 Parameters on ATM

Interfaces

burst-size-limit bytes

Gigabit Ethernet and Gigabit Ethernet IQ

and IQE PICs with SFPs (except the
10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i
router)

Configuring Gigabit Ethernet Policers

descending)

Copyright 2014, Juniper Networks, Inc.

67

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

byte-encoding (nx56 | nx64)

DS0 and T1 interfaces

Configuring T1 Byte Encoding

bytes [ values

SONET/SDH interfaces

Configuring SONET/SDH Header Byte

Values to Identify Error Conditions

cbit-parity | no-cbit-parity

T3 interfaces

Disabling T3 C-Bit Parity Mode

cbr rate

ATM interfaces

Defining the ATM Traffic-Shaping Profile

cell-bundle-size cells

ATM2 IQ interfaces using ATM Layer 2

circuit cell-relay transport mode

Configuring the Layer 2 Circuit Cell-Relay

Cell Maximum

chap

Interfaces with PPP encapsulation

Configuring the PPP Challenge

Handshake Authentication Protocol on
page 126

cisco-interoperability

link services IQ (lsq) interfaces

Junos OS Services Interfaces Library for

Routing Devices

classifier

Gigabit Ethernet IQ interfaces

Configuring Gigabit Ethernet Policers

clocking clock-source

ATM, DS0, E1, E3, SONET/SDH, T1, and T3

interfaces

Configuring the Clock Source on page 116

clocking-mode (dce | internal |

Serial interfaces (EIA-530 and V.35)

Configuring the Serial Clocking Mode on

page 307

clock-rate rate

Serial interfaces (EIA-530 and V.35)

Configuring the DTE Clock Rate on

page 309

compatibility-mode mode

E3 and T3 interfaces

Configuring the E3 CSU Compatibility Mode

and Configuring the T3 CSU Compatibility
Mode

compression

Interfaces with PPP encapsulation

Configuring the PPP Protocol Field

Compression on page 135

control-polarity (negative |

Serial interfaces (X.21)

Configuring Serial Signal Polarities on

page 313

Serial interfaces (X.21)

Configuring the Serial Signal Handling

on page 310

core-dump | no-core-dump)

Adaptive services, monitoring services, and

collector interfaces

Configuring Multiservice Physical Interface

Properties on page 153

cts (ignore | normal | require)

Serial interfaces (EIA-530 and V.35)

Configuring the Serial Signal Handling

on page 310

send-lip-remove-link-for-link-reject

loop)

positive)
control-signal (assert | de-assert |

normal)

68

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

cts-polarity (negative | positive)

Serial interfaces (EIA-530 and V.35)

Configuring Serial Signal Polarities on

page 313

current margin

ATM interfaces on J Series routers

Configuring SHDSL Operating Mode on an

ATM Physical Interface

dcd (ignore | normal | require)

Serial interfaces (EIA-530 and V.35)

Configuring the Serial Signal Handling

on page 310

dcd-polarity (negative | positive)

Serial interfaces (EIA-530 and V.35)

Configuring Serial Signal Polarities on

page 313

dce

Interfaces with Frame Relay encapsulation

Configuring the Router as a DCE with

Frame Relay Encapsulation on page 138

dce-options

Serial interfaces (EIA-530, V.35, and X.21)

on J Series routers

Configuring the Serial Signal Handling

on page 310

default-chap-secret name

Interfaces with Point-to-Point Protocol

(PPP) encapsulation

Configuring a Default CHAP Secret on

page 128

description text

All

Configuring Interface Description on

page 92

dialer-options

ISDN interfaces

Configuring ISDN Physical Interface

Properties

disable

All

Disabling a Physical Interface on page 156

and Tracing Operations of an Individual
Router Interface on page 321

dot1x

802.1x Port-Based Network Access Control

IEEE 802.1x Port-Based Network Access

Control Overview

down-count

ATM interfaces

Configuring the ATM OAM F5 Loopback Cell

Threshold

drop-timeout milliseconds

Multilink, link services, and voice services

interfaces

Junos OS Services Interfaces Library for

Routing Devices

ds0-options

DS0 interfaces

Channelized Interfaces Overview

dsr (ignore | normal | require)

Serial interfaces (EIA-530 and V.35)

Configuring the Serial Signal Handling

on page 310

dsr-polarity (negative | positive)

Serial interfaces (EIA-530 and V.35)

Configuring Serial Signal Polarities on

page 313

dte-options

Serial interfaces (EIA-530, V.35, and X.21)

on M Series and T Series routers

Configuring the Serial Signal Handling

on page 310

Copyright 2014, Juniper Networks, Inc.

69

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

70

Interface Types

Usage Guidelines

dtr signal-handling-option

Serial interfaces (EIA-530 and V.35)

Configuring the Serial Signal Handling

on page 310

dtr-circuit (balanced | unbalanced)

Serial interfaces (EIA-530 and V.35)

Configuring the Serial DTR Circuit on

page 313

dtr-polarity (negative | positive)

Serial interfaces (EIA-530 and V.35)

Configuring Serial Signal Polarities on

page 313

e1-options

E1 interfaces

E1 Interfaces Overview

e3-options

E3 interfaces

E3 Interfaces Overview

encapsulation type

All interfaces, except loopback and

multicast tunnel

Configuring Interface Encapsulation on

Physical Interfaces on page 117

encoding (nrz | nrzi)

Serial interfaces (EIA-530, V.35, and X.21)

Configuring Serial Line Encoding on

page 315

epd-threshold cells

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

es-options

ES interfaces

Junos OS Services Interfaces Library for

Routing Devices

ethernet-policer-profile

Gigabit Ethernet and Gigabit Ethernet IQ

and IQE PICs with SFPs (except the
10-port Gigabit Ethernet PIC, and the
built-in Gigabit Ethernet port on the M7i
router)

Configuring Gigabit Ethernet Policers

ethernet-switch-profile

Gigabit Ethernet and Gigabit Ethernet IQ

and IQE PICs with SFPs (except the
10-port Gigabit Ethernet PIC, Aggregated
Ethernet with Gigabit Ethernet IQ
interfaces, and the built-in Gigabit Ethernet
port on the M7i router)

Configuring Gigabit Ethernet Policers,

Configuring MAC Address Filtering, and
Configuring the Management Ethernet
Interface

facility-override facility-name

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

fastether-options

Fast Ethernet interfaces

Ethernet Interfaces Overview

fcs (16 | 32)

E1/E3, SONET/SDH, and T1/T3 interfaces

Configuring the E1 Frame Checksum,

Configuring the E3 Frame Checksum,
Configuring the SONET/SDH Frame
Checksum, Configuring the T1 Frame
Checksum, and Configuring the T3 Frame
Checksum

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

T3 interfaces

Configuring the T3 FEAC Response

flow-control | no-flow-control)

Aggregated Ethernet, Fast Ethernet, and

Gigabit Ethernet interfaces

Configuring Flow Control

force

SONET/SDH interfaces

Configuring Switching Between the Working

and Protect Circuits

forwarding-class class-name

ATM2 IQ interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

forwarding-class class-name

Gigabit Ethernet IQ interfaces

Configuring Gigabit Ethernet Policers

fragment-threshold bytes

Multilink, link services, and voice services

interfaces

Junos OS Services Interfaces Library for

Routing Devices

framingframing-type

E1, E3, and T1 interfaces

Configuring E3 and T3 Parameters on ATM

Interfaces, Configuring E1 Framing, and
Configuring T1 Framing

framing framing-type

10-Gigabit Ethernet interfaces

10-Gigabit Ethernet Framing Overview

framing framing-type

SONET interfaces

Configuring SONET/SDH Framing Mode for

Ports

gigether-options

Gigabit Ethernet and Tri-Rate Ethernet

copper interfaces

Ethernet Interfaces Overview

(gratuitous-arp-reply |
no-gratuitous-arp-reply)

Ethernet interfaces

Configuring Gratuitous ARP

hello-timer milliseconds

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

high-plp-max-threshold

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

high-plp-threshold percent

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

hold-time milliseconds

SONET/SDH interfaces

SONET/SDH Interfaces Overview

hold-time up milliseconds down

All interfaces, except aggregated

SONET/SDH, generalized routing
encapsulation (GRE) tunnel, and IP tunnel

Configuring SONET/SDH Defect Triggers

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

feac-loop-respond |

no-feac-loop-respond)

milliseconds

host hostname

Copyright 2014, Juniper Networks, Inc.

71

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

ieee802.1p premium [values]

Gigabit Ethernet IQ interfaces

Configuring Gigabit Ethernet Policers

idle-cycle-flag value

E1, E3, T1, and T3 interfaces

Configuring the E1 Idle Cycle Flag,

Configuring the E3 Idle Cycle Flag,
Configuring the T1 Idle Cycle Flag, and
Configuring the T3 Idle Cycle Flag

ignore-all

Serial interfaces (EIA-530, V.35, and X.21)

Configuring the Serial Signal Handling

on page 310

ilmi

ATM interfaces

Configuring Communication with Directly

Attached ATM Switches and Routers

inactivity-timeout seconds

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

indication (ignore | normal |

Serial interfaces (X.21)

Configuring the Serial Signal Handling

on page 310

Serial interfaces (X.21)

Configuring Serial Signal Polarities on

page 313

ingress-rate-limit rate

8-port, 12-port, and 48-port Fast Ethernet

interfaces

Configuring the Ingress Rate Limit

input-priority-map

Gigabit Ethernet IQ interfaces

Configuring Gigabit Ethernet Policers

interface-type type

Channelized IQ and IQE interfaces, ISDN

interfaces

Channelized Interfaces Overview and

Configuring ISDN Physical Interface
Properties

invert-data

DS0, E1, E3, and T1 interfaces

Configuring E1 Data Inversion, Configuring

E3 Data Inversion, and Configuring T1 Data
Inversion

isdn-options

ISDN interfaces

Configuring ISDN Logical Interface

Properties

keepalives <down-count number

Aggregated SONET/SDH, DS0, E1, E3,

SONET/SDH, T1, and T3 interfaces

Configuring Keepalives on page 124

lacp mode

Aggregated Ethernet interfaces

Configuring LACP for Aggregated Ethernet

Interfaces

line-encoding (ami | b8zs)

T1 interfaces

Configuring T1 Line Encoding

line-protocol protocol

Serial interfaces (EIA-530, V.35, and X.21)

Configuring the Serial Line Protocol on

page 304

require)
indication-polarity (negative |

positive)

<interval seconds> <up-count

number>

72

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

line-rate line-rate

ATM interfaces on J Series routers

Configuring SHDSL Operating Mode on an

ATM Physical Interface

linear-red-profile profile-name

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

linear-red-profiles profile-name

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

link-layer-overhead percent

AS PIC link services IQ interfaces (lsq)

Junos OS Services Interfaces Library for

Routing Devices

link-mode mode

Management Ethernet (fxp0 or em0) and

Fast Ethernet interfaces

Configuring the Link Characteristics on

page 109, Understanding Management
Ethernet Interfaces on page 10

link-speed speed

Aggregated Ethernet interfaces

Configuring Aggregated Ethernet Link Speed

link-speed speed

Aggregated SONET/SDH interfaces

Configuring Aggregated SONET/SDH

Interfaces

lmi lmi-options

Interfaces with Frame Relay encapsulation

Configuring Frame Relay Keepalives and

Junos OS Services Interfaces Library for
Routing Devices

lmi

OAM CFM Ethernet Local Management

Interface

Configuring Ethernet Local Management

Interface

lmi-type (ansi | itu | c-lmi)

Link services interfaces and interfaces with

Frame Relay encapsulation

Configuring Frame Relay Keepalives

local-name name

Interfaces with PPP encapsulation

Configuring the PPP Challenge

Handshake Authentication Protocol on
page 126

lockout

SONET/SDH interfaces

Configuring a Lockout of Protection for SDH

Interfaces

log-prefix prefix-number

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

(long-buildout | no-long-buildout)

T3 interfaces

Configuring the T3 Line Buildout

(loop-timing | no-loop-timing)

Channelized IQ interfaces

Configuring the Channelized T3 Loop Timing

Copyright 2014, Juniper Networks, Inc.

73

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

loopback mode

DS0, E1, E3, T1, T3, SHDSL on ATM and

ATM interfaces on J Series routers, and
SONET/SDH interfaces

Configuring E1 Loopback Capability,

Configuring E3 Loopback Capability,
Configuring T1 Loopback Capability,
Configuring T3 Loopback Capability,
Configuring SHDSL Operating Mode on an
ATM Physical Interface,Configuring
SONET/SDH Loopback Capability to
Identify a Problem as Internal or External,
and Configuring Ethernet Loopback
Capability

loopback mode

Ethernet and 10-Gigabit Ethernet

interfaces in WAN PHY mode

Configuring Ethernet Loopback Capability

loopback mode

Serial interfaces

Configuring Serial Loopback Capability

on page 314

(loopback | no-loopback)

Aggregated Ethernet, Fast Ethernet, and

Gigabit Ethernet interfaces

Configuring Ethernet Loopback Capability

loss-priority (high | low)

Gigabit Ethernet IQ interfaces

Configuring Gigabit Ethernet Policers

lowest-priority-defect (all-defects

Configuring IEEE 802.1ag OAM

connectivity-fault management

Configuring a Maintenance Endpoint

low-plp-max-threshold percent

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

low-plp-threshold percent

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

lsq-failure-options

Link services IQ (lsq) interfaces

Junos OS Services Interfaces Library for

Routing Devices

mac mac-address

Management Ethernet interface (fxp0 or

em0)

Configuring the MAC Address on the

Management Ethernet Interface,
Understanding Management Ethernet
Interfaces on page 10

(mac-learn-enable |
no-mac-learn-enable)

Gigabit Ethernet IQ and IQE, Tri-Rate

Ethernet copper, and Gigabit Ethernet PICs
with SFPs (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit
Ethernet port on the M7i router)

Configuring Gigabit Ethernet Policers

master-only;

Management Ethernet (fxp0 or em0) and

Fast Ethernet interfaces

Configuring a Consistent Management IP

Address, Understanding Management
Ethernet Interfaces on page 10

maximum-vcs maximum-vcs

ATM interfaces

Configuring the Maximum Number of ATM1

VCs on a VP

| err-xcon | mac-rem-err-xcon |
no-defect | rem-err-xcon | xcon)

74

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

mc-ae

Aggregated Ethernet interfaces

Configuring Multichassis Link Aggregation

minimum-links number

Multilink, link services, and voice services

interfaces

Junos OS Services Interfaces Library for

Routing Devices

mip-half-function

Connectivity Fault Management

Configuring IEEE 802.3ah OAM Link-Fault

Management

mlfr-uni-nni-bundle-options

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

mpls

10-Gigabit Ethernet interfaces in WAN PHY

mode and ATM and SONET/SDH
interfaces in passive monitoring mode

Removing MPLS Labels from Incoming

Packets, Enabling Packet Flow Monitoring
on SONET/SDH Interfaces, and
SONET/SDH Interfaces Overview

mrru bytes

Link services and voice services interfaces

Junos Services Interfaces Configuration

Guide

mtu bytes

All interfaces, except management

Ethernet (fxp0 or em0), loopback,
multilink, and multicast tunnel

Configuring the Media MTU on page 93,

Understanding Management Ethernet
Interfaces on page 10

multicast-statistics

Ethernet, SONET, aggregated Ethernet,

and aggregated SONET interfaces.

Configuring Multicast Statistics Collection

on Aggregated Ethernet Interfaces,
Configuring Multicast Statistics Collection
on SONET Interfaces,Configuring Multicast
Statistics Collection on Ethernet Interfaces,
and Configuring Multicast Statistics
Collection on Aggregated SONET Interfaces

multiservice-options

Adaptive services, monitoring services, and

collector interfaces

Configuring Multiservice Physical Interface

Properties on page 153

n391 number

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

n392 number

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

n393 number

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

neighbor address

SONET/SDH interfaces

SONET/SDH Interfaces Overview

no-gratuitous-arp-request

Ethernet interfaces

Configuring Gratuitous ARP

bundle-options

Copyright 2014, Juniper Networks, Inc.

75

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

no-keepalives

Interfaces with PPP, Frame Relay, or Cisco

High-level Data Link Control (HDLC)
encapsulation

Configuring Keepalives on page 124

no-partition

Channelized IQ interfaces

Channelized Interfaces Overview

no-termination-request

Link Services IQ (LSQ) interfaces

Junos OS Services Interfaces Library for

Routing Devices

oam-liveness

ATM interfaces

Configuring the OAM F4 Cell Flows

oam-period (seconds | disable)

ATM interfaces

Defining the ATM OAM F5 Loopback Cell

Period

oc-slice oc-slice-range

Channelized OC12 IQ interfaces

Channelized OC12/STM4 IQ and IQE

Interfaces Overview

open-timeout seconds

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

optics-options

Gigabit Ethernet dense

wavelength-division multiplexing (DWDM)
interfaces

Ethernet DWDM Interface Wavelength

Overview

output-priority-map

Gigabit Ethernet IQ interfaces

Configuring Gigabit Ethernet Policers

overflow (discard | tag)

All interfaces, except ATM, channelized E1,

E1, Fast Ethernet, Gigabit Ethernet, and
channelized IQ interfaces

Configuring Receive and Transmit Leaky

Bucket Properties to Reduce Network
Congestion on page 139

paired-group group-name

SONET/SDH interfaces

Configuring APS Load Sharing

partition partition-number

Channelized IQ interfaces

Channelized Interfaces Overview

passive

Interfaces with PPP encapsulation

Configuring the PPP Challenge

Handshake Authentication Protocol on
page 126

passive-monitor-mode

SONET/SDH interfaces

Enabling Packet Flow Monitoring on

SONET/SDH Interfaces

path-trace trace-string

10-Gigabit Ethernet interfaces in WAN PHY

mode and SONET/SDH interfaces

Configuring the SONET/SDH Path Trace

Identifier for a Circuit

(Receive bucket)
overflow (discard)

(Transmit bucket)

76

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

(payload-scrambler |
no-payload-scrambler)

E3, SONET/SDH, and T3 interfaces

Configuring E3 and T3 Parameters on ATM

Interfaces, Configuring E3 HDLC Payload
Scrambling, Configuring SONET/SDH HDLC
Payload Scrambling for Link Stability, and
Configuring T3 HDLC Payload Scrambling

periodic interval

Aggregated Ethernet interfaces

Configuring LACP for Aggregated Ethernet

Interfaces

per-unit-scheduler

IQ interfaces

Junos OS Services Interfaces Library for

Routing Devices

pfc

Interfaces with PPP encapsulation

Configuring the PPP Protocol Field

Compression on page 135

pic-type (atm1 | atm2)

ATM2 IQ interfaces

Configuring the ATM PIC Type

plp1 cells

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

plp-to-clp

ATM2 IQ interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

policer cos-policer-name

Gigabit Ethernet and Gigabit Ethernet IQ

and IQE PICs with SFPs (except the
10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i
router)

Configuring Gigabit Ethernet Policers

pop-all-labels

ATM and SONET/SDH interfaces in

passive monitoring mode

Removing MPLS Labels from Incoming

Packets and Enabling Packet Flow
Monitoring on SONET/SDH Interfaces

ppp-options

Interfaces with PPP encapsulation

Configuring the PPP Challenge

Handshake Authentication Protocol on
page 126

premium

Enhanced Intelligent Queuing (IQE)

interfaces (hierarchical policer)

Applying Policers on page 210 and Class

of Service Feature Guide for Routing Devices

premium

Gigabit Ethernet IQ interfaces (policer)

Configuring Gigabit Ethernet Policers

premium

Gigabit Ethernet IQ interfaces (output

priority map)

Configuring Gigabit Ethernet Policers

primary sp-fpc/pic/port

Redundant interfaces for adaptive services

interfaces (rsp-)

Junos OS Services Interfaces Library for

Routing Devices

priority (high | low)

ATM2 IQ interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

Copyright 2014, Juniper Networks, Inc.

77

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

priority number

Ethernet protocols (OAM CFM)

Configuring a Maintenance Endpoint

promiscuous-mode

ATM2 IQ interfaces

Configuring ATM Cell-Relay Promiscuous

Mode

protect-circuit group-name

SONET/SDH interfaces

Configuring Switching Between the Working

and Protect Circuits

queue-depth cells

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

queue-length number

ATM1 interfaces

Configuring the ATM1 Queue Length

rate percentage

All interfaces, except ATM, channelized E1,

E1, Fast Ethernet, Gigabit Ethernet, and
channelized IQ

Configuring Receive and Transmit Leaky

Bucket Properties to Reduce Network
Congestion on page 139

receive-bucket

All interfaces, except ATM, Fast Ethernet,

and Gigabit Ethernet

Configuring Receive and Transmit Leaky

Bucket Properties to Reduce Network
Congestion on page 139

red-differential-delay milliseconds

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

redundancy-options

Redundant interfaces for adaptive services

interfaces (rsp-)

Junos OS Services Interfaces Library for

Routing Devices

remote-loopback-respond

T1 interfaces

Configuring the T1 Remote Loopback

Response

request

SONET/SDH interfaces

Configuring Switching Between the Working

and Protect Circuits

required-depth number

ATM and SONET/SDH interfaces in

passive monitoring mode

Removing MPLS Labels from Incoming

Packets and Enabling Packet Flow
Monitoring on SONET/SDH Interfaces

revert-time seconds

SONET/SDH interfaces

Configuring Revertive Mode

rfc-2615

SONET/SDH interfaces

Configuring PPP Support on SONET/SDH

Interfaces

rts (assert | de-assert | normal)

Serial interfaces (EIA-530 and V.35)

Configuring the Serial Signal Handling

on page 310

rts-polarity (negative | positive)

Serial interfaces (EIA-530 and V.35)

Configuring Serial Signal Polarities on

page 313

rtvbr peak rate sustained rate burst

ATM interfaces

Defining the ATM Traffic-Shaping Profile

length

78

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

scheduler-maps map-name

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

schedulers number

Ethernet IQ2 and IQ2-E PICs port

interfaces

Junos OS Services Interfaces Library for

Routing Devices

secondary sp-fpc/pic/port

Redundant interfaces for adaptive services

interfaces (rsp-)

Junos OS Services Interfaces Library for

Routing Devices

services-options

Services interfaces

Junos OS Services Interfaces Library for

Routing Devices

serial-options

Serial interfaces (EIA-530, V.35, and X.21)

Serial Interfaces Overview on page 301

services priority-level

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

shdsl-options

ATM interfaces on J Series routers

Configuring SHDSL Operating Mode on an

ATM Physical Interface

size

All

Tracing Operations of the Interface

Process on page 322

shaping

ATM interfaces

Defining the ATM Traffic-Shaping Profile

shaping

Circuit Emulation PICs

Configuring ATM QoS or Shaping

snext margin

ATM interfaces on J Series routers

Configuring SHDSL Operating Mode on an

ATM Physical Interface

snr-margin

ATM interfaces on J Series routers

Configuring SHDSL Operating Mode on an

ATM Physical Interface

sonet-options

SONET/SDH interfaces

SONET/SDH Interfaces Overview

source-address-filter mac-address

Aggregated Ethernet, Fast Ethernet,

Tri-Rate Ethernet copper, and Gigabit
Ethernet interfaces

Enabling Ethernet MAC Address Filtering

(source-filtering |
no-source-filtering)

Aggregated Ethernet, Fast Ethernet,

Tri-Rate Ethernet copper, Gigabit Ethernet,
Gigabit Ethernet IQ and IQE, and Gigabit
Ethernet interfaces with SFPs (except the
10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i
router)

Enabling Ethernet MAC Address Filtering

Copyright 2014, Juniper Networks, Inc.

79

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

speed (10m | 100m | 1g | auto)

Management Ethernet interface (fxp0 or

em0), Tri-Rate Ethernet copper interfaces,
and 12-port and 48-port Fast Ethernet
interfaces

Configuring the Interface Speed on Ethernet

Interfaces, Understanding Management
Ethernet Interfaces on page 10

speed (oc3 | oc12 | oc48)

SONET/SDH PICs with SFP

Configuring SONET/SDH Interface Speed

spid1spid2

ISDN interfaces

Configuring ISDN Physical Interface

Properties and Configuring ISDN Logical
Interface Properties

stacked-vlan-tagging

Gigabit Ethernet IQ interfaces

Stacking and Rewriting Gigabit Ethernet

VLAN Tags Overview

start-end-flag (filler | shared)

DS0, E1, E3, T1, and T3 interfaces

Configuring E1 Start and End Flags,

Configuring the E3 Start and End Flags,
Configuring T1 Start and End Flags, and
Configuring T3 Start and End Flags

switching-mode (bidirectional |

Unchannelized OC3, OC12, and OC48

SONET/SDH interfaces on T Series routers

Configuring Switching Mode

syslog

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

(syslog | no-syslog)

Adaptive services, monitoring services, and

collector interfaces

Configuring Multiservice Physical Interface

Properties on page 153

t1-options

T1 interfaces

T1 Interfaces Overview

t3-options

T3 interfaces

T3 Interfaces Overview

t310

ISDN interfaces

Configuring ISDN Physical Interface

Properties

t391 seconds

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

t392 number

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

tei-option (first-call | power-up)

ISDN interfaces

Configuring ISDN Physical Interface

Properties

threshold bytes

All interfaces, except ATM, channelized E1,

E1, Fast Ethernet, Gigabit Ethernet, and
channelized IQ

Configuring Receive and Transmit Leaky

Bucket Properties to Reduce Network
Congestion on page 139

timeslots time-slot-range

Channelized T1 IQ and channelized E1 IQ

interfaces

Channelized Interfaces Overview

unidirectional)

80

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

tm (ignore | normal | require)

Serial interfaces (EIA-530)

Configuring the Serial Signal Handling

on page 310

tm-polarity (negative | positive)

Serial interfaces (EIA-530)

Configuring Serial Signal Polarities on

page 313

traceoptions

All

Tracing Operations of an Individual Router

Interface on page 321

traceoptions

All

Tracing Operations of the Interface

Process on page 322

transmit-bucket

All interfaces, except ATM, Fast Ethernet,

Tri-Rate Ethernet copper, and Gigabit
Ethernet

Configuring Receive and Transmit Leaky

Bucket Properties to Reduce Network
Congestion on page 139

transmit-clock invert

Serial interfaces (EIA-530, V.35, and X.21)

Configuring the Serial Clocking Mode on

page 307

transmit-weight (cells number |

ATM2 IQ interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

(traps | no-traps)

All

Enabling or Disabling SNMP Notifications

on Physical Interfaces on page 154

trigger defect ignore | defect

hold-time up milliseconds down

10-Gigabit Ethernet interfaces in WAN PHY

mode and ATM over SONET/SDH and
SONET/SDH interfaces

Configuring SONET/SDH Defect Triggers

(unframed | no-unframed)

E3 IQ interfaces

Configuring E3 IQ and IQE Unframed Mode

unidirectional

10-Gigabit Ethernet interfaces on:

Enabling Unidirectional Traffic Flow on

Physical Interfaces on page 142

percent number)

milliseconds;

vbr peak rate sustained rate burst

MX960 4Port 10Gigabit Ethernet

DPC

T Series 10Gigabit Ethernet IQ2 PIC

T Series 10Gigabit Ethernet IQ2E PIC

ATM interfaces

Defining the ATM Traffic-Shaping Profile

vc-cos-mode (alternate | strict)

ATM2 interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

vlan-tagging

Fast Ethernet, Tri-Rate Ethernet copper,

and Gigabit Ethernet interfaces

802.1Q VLANs Overview

vlan-vci-tagging

Fast Ethernet, Tri-Rate Ethernet copper,

Gigabit Ethernet, 10-Gigabit Ethernet, and
aggregated Ethernet interfaces

Configuring ATM-to-Ethernet
Interworking on page 262

length

Copyright 2014, Juniper Networks, Inc.

81

Interfaces Fundamentals for Routing Devices

Table 28: Statements for Physical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

vpi vpi-identifier

ATM interfaces

Configuring ATM Cell-Relay Promiscuous

Mode and Configuring the Maximum
Number of ATM1 VCs on a VP

vtmapping

Channelized STM1 interfaces

Configuring Channelized STM1 Interfaces

warningwarning-name

10-Gigabit Ethernet interfaces

Configuring 10-Gigabit Ethernet Link Down

Notification for Optics Options Alarm or
Warning

wavelength nm

Gigabit Ethernet dense

wavelength-division multiplexing (DWDM)
interfaces

Ethernet DWDM Interface Wavelength

Overview

working-circuit group-name

SONET/SDH interfaces

Configuring Switching Between the Working

and Protect Circuits

yellow-differential-delay

Link services and voice services interfaces

Junos OS Services Interfaces Library for

Routing Devices

SONET/SDH interfaces

Configuring an Incrementing STM ID to

Interoperate with Older Equipment in SDH
Mode

(syslog | link-down)

milliseconds
(z0-increment | no-z0-increment)

Related
Documentation

Junos OS Services Interfaces Library for Routing Devices

Interface Ranges

NOTE: This task uses Junos OS for EX Series switches that does not support
the Enhanced Layer 2 Software (ELS) configuration style. If your switch runs
software that supports ELS, see Interface Ranges. For ELS details, see Getting
Started with Enhanced Layer 2 Software.

The Junos OS allows you to group a range of identical interfaces into an interface range.
You first specify the group of identical interfaces in the interface range. Then you can
apply a common configuration to the specified interface range, reducing the number of
configuration statements required and saving time while producing a compact
configuration.

82

Configuring Interface Ranges on page 83

Expanding Interface Range Member and Member Range Statements on page 86

Configuration Inheritance for Member Interfaces on page 88

Member Interfaces Inheriting Configuration from Configuration Groups on page 89

Interfaces Inheriting Common Configuration on page 90

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Configuring Inheritance Range Priorities on page 90

Configuration Expansion Where Interface Range Is Used on page 91

Configuring Interface Ranges

To configure an interface range, include the interface-range statement at the [edit
interfaces] hierarchy level.
The interface-range statement accepts only physical networking interface names in its
definition. The following interface types are supported and example CLI descriptors are
shown:

ATMat-fpc/pic/port

Channelized(coc | cstm)n-fpc/pic/port

DPCxe-fpc/pic/port

E1/E3(e1 | e3)-fpc/pic/port

Ethernet(xe | ge | fe)-fpc/pic/port

ISDNisdn-fpc/pic/port

Serialse-fpc/pic/port

SONET/SDHso-fpc/pic/port

T1/T3(t1 | t3)-fpc/pic/port

Interfaces can be grouped either as a range of interfaces or using a number range under
the interface-range statement definition.
Interfaces in an interface-range definition can be added as part of a member range or as
individual members or multiple members using a number range.
To specify a member range, use the member-range statement at the [edit interfaces
interface-range name] hierarchy level.
To specify interfaces in lexical order, use the member-range start-range to end-range
statement.
A range for a member statement should contain the following:

*All, specifies sequential interfaces from 0 through 47.

CAUTION: The wildcard * in a member statement does not take into

account the interface numbers supported by a specific interface type.
Irrespective of the interface type, * includes interface numbers ranging
from 0 through 47 to the interface group. Therefore, use * in a member
statement with caution.

numNumber, specifies one specific interface by its number.

Copyright 2014, Juniper Networks, Inc.

83

Interfaces Fundamentals for Routing Devices

[low-high]Numbers between low to high, specifies a range of sequential interfaces.

[num1, num2, num3]Numbers num1, num2, and num3 specify multiple specific

interfaces.
Example: Specifying an
Interface Range
Member Range

member-range ge-0/0/0 to ge-4/0/40;

To specify one or multiple members, use the member statement at the [edit interfaces
interface-range name] hierarchy level.
To specify the list of interface range members individually or for multiple interfaces using
regex, use the member list of interface names statement.
Example: Specifying an
Interface Range
Member

member ge-0/0/0;
member ge-0/*/*
member ge-0/[1-10]/0;
member ge-0/[1,2,3]/3;

Regex or wildcards are not supported for interface-type prefixes. For example, prefixes
ge, fe, and xe must be mentioned explicitly.
An interface-range definition can contain both member and member-range statements
within it. There is no maximum limit on the number of member or member-range
statements within an interface-range. However, at least one member or member-range
statement must exist within an interface-range definition.
Example: Interface
Range Common
Configuration

Configuration common to an interface range can be added as a part of the interface-range

definition, as follows:
[edit]
interfaces {
+ interface-range foo {
+ member-range ge-1/0/0 to ge-4/0/40;
+ member ge-0/1/1;
+ member ge-5/[1-10]/*;
/*Common configuration is added as part of interface-range definition*/
mtu 256;
hold-time up 10;
ether-options {
flow-control;
speed {
100m;
}
802.3ad primary;
}
}
}

An interface-range definition having just member or member-range statements and no

common configurations statements is valid.
These defined interface ranges can be used in other configuration hierarchies, in places
where an interface node exists.

84

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Example:
Interface-Range foo
Used Under the
Protocols Hierarchy

protocols {
dot1x {
authenticator {
interface foo{
retries 1;
}
}
}
}
foo should be an interface-range defined at the [interfaces] hierarchy level. In the above

example, the interface node can accept both individual interfaces and interface ranges.

TIP: To view an interface range in expanded configuration, use the (show |

display inheritance) command. For more information, see the CLI User Guide.

By default, interface-range is not available to configure in the CLI where the interface
statement is available. The following locations are supported; however, some of the
hierarchies shown in this list are product specific:

protocols dot1x authentication interface

protocols dvmrp interface

protocols oam ethernet lmi interface

protocols esis interface

protocols igmp interface

protocols igmp-host client num interface

protocols mld-host client num interface

protocols router-advertisement interface

protocols isis interface

protocols ldp interface

protocols oam ethernet link-fault-management interface

protocols lldp interface

protocols link-management peer lmp-control-channel interface

protocols link-management peer control-channel

protocols link-management te-link name interface

protocols mld interface

protocols ospf area id interface

protocols pim interface

protocols router-discovery interface

protocols rip group name neighbour

Copyright 2014, Juniper Networks, Inc.

85

Interfaces Fundamentals for Routing Devices

protocols ripng group name neighbour

protocols rsvp interface

protocols snmp interface

protocols layer2-control bpdu-block interface

protocols layer2-control mac-rewrite interface

protocols mpls interface

protocols stp interface

protocols rstp interface

protocols mstp interface

protocols vstp interface

protocols mstp msti id interface

protocols mstp msti vlan id interface

protocols vstp vlan name interface

protocols gvrp interface

protocols igmp-snooping vlan name interface

protocols lldp interface

protocols lldp-med interface

protocols sflow interfaces

ethernet-switching-options analyzer name input [egress | ingress ] interface

ethernet-switching-options analyzer name output interface

ethernet-switching-options secure-access-port interface

ethernet-switching-options interfaces ethernet-switching-options voip interface

ethernet-switching-options redundant-trunk-group group g1 interface

ethernet-switching-options redundant-trunk-group group g1 interface

ethernet-switching-options bpdu-block interface

poe interface vlans pro-bng-mc1-bsd1 interface

Expanding Interface Range Member and Member Range Statements

All member and member-range statements in an interface range definition are expanded
to generate the final list of interface names for the specified interface range.
Example: Expanding
Interface Range
Member and Member
Range Statements

86

[edit]
interfaces {
interface-range range-1 {
member-range ge-0/0/0 to ge-4/0/20;
member ge-10/1/1;
member ge-5/[0-5]/*;

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

/*Common configuration is added part of the interface-range definition*/

mtu 256;
hold-time up 10;
ether-options {
flow-control;
speed {
100m;
}
802.3ad primary;
}
}
}

For the member-range statement, all possible interfaces between start-range and
end-range are considered in expanding the members. For example, the following
member-range statement:
member-range ge-0/0/0 to ge-4/0/20

expands to:
[ge-0/0/0, ge-0/0/1 ... ge-0/0/max_ports
ge-0/1/0 ge-0/1/1 ... ge-0/1/max_ports
ge-0/2/0 ge-0/2/1 ... ge-0/2/max_ports
.
.
ge-0/MAX_PICS/0 ... ge-0/max_pics/max_ports
ge-1/0/0 ge-1/0/1 ... ge-1/0/max_ports
.
ge-1/MAX_PICS/0 ... ge-1/max_pics/max_ports
.
.
ge-4/0/0 ge-4/0/1 ... ge-4/0/max_ports]

The following member statement:

ge-5/[0-5]/*

expands to:
ge-5/0/0 ... ge-5/0/max_ports
ge-5/1/0 ... ge-5/0/max_ports
.
.
ge-5/5/0 ... ge-5/5/max_ports

The following member statement:

ge-5/1/[2,3,6,10]

expands to:
ge-5/1/2
ge-5/1/3
ge-5/1/6
ge-5/1/10

Copyright 2014, Juniper Networks, Inc.

87

Interfaces Fundamentals for Routing Devices

Configuration Inheritance for Member Interfaces

When the Junos OS expands the member and member-range statements present in an
interface-range, it creates interface objects if they are not explicitly defined in the
configuration. The common configuration is copied to all its member interfaces in the
interface-range.
Example:
Configuration Priorities

Foreground interface configuration takes priority compared to configuration inherited by

the interface through the interface-range.
interfaces {
interface-range range-1 {
member-range ge-1/0/0/ to ge-10/0/47;
mtu 256;
}
ge-1/0/1 {
mtu 1024;
}
}

In the preceding example, interface ge-1/0/1 will have an MTU value of 1024.
This can be verified with output of the show interfaces | display inheritance command,
as follows:
user@host: # show interfaces | display inheritance
## 'ge-1/0/0' was expanded from interface-range 'range-1'
##
ge-1/0/0 {
##
## '256' was expanded from interface-range 'range-1'
##
mtu 256;
}
ge-1/0/1 {
mtu 1024;
}
##
## 'ge-1/0/2' was expanded from interface-range 'range-1'
##
ge-1/0/2 {
##
## '256' was expanded from interface-range 'range-1'
##
mtu 256;
}
.........
.........
##
## 'ge-10/0/47' was expanded from interface-range 'range-1'
##
ge-10/0/47 {
##
## '256' was expanded from interface-range 'range-1'
##
mtu 256;
}

88

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Member Interfaces Inheriting Configuration from Configuration Groups

Interface range member interfaces inherit the config-groups configuration like any other
foreground configuration. interface-range is similar to any other foreground configuration
statement. The only difference is that the interface-range goes through a member
interfaces expansion before Junos OS reads this configuration.
groups {
global {
interfaces {
<*> {
hold-time up 10;
}
}
}
apply-groups [global];
interfaces {
interface-range range-1 {
member-range ge-1/0/0 to ge-10/0/47;
mtu 256;
}
}
}

The hold-time configuration is applied to all members of interface-range range-1.

This can be verified with show interfaces | display inheritance as follows:
user@host# show interfaces | display inheritance
ge-1/0/0 {
##
## '256' was expanded from interface-range 'range-1'
##
mtu 256;
##
## 'hold-time' was inherited from group 'global'
## '10' was inherited from group 'global'
##
hold-time up 10;
}
ge-1/0/1 {
##
## '256' was expanded from interface-range 'range-1'
##
mtu 256;
##
## 'hold-time' was inherited from group 'global'
## '10' was inherited from group 'global'
##
hold-time up 10;
}
ge-10/0/47 {
##
## '256' was expanded from interface-range 'range-1'
##
mtu 256;
##
## 'hold-time' was inherited from group 'global'
## '10' was inherited from group 'global'

Copyright 2014, Juniper Networks, Inc.

89

Interfaces Fundamentals for Routing Devices

##
hold-time up 10;
}

Interfaces Inheriting Common Configuration

If an interface is a member of several interface ranges, that interface will inherit the
common configuration from all of those interface ranges.
[edit]
interfaces {
interface-range range-1 {
member-range ge-1/0/0 to ge-10/0/47;
mtu 256;
}
}
interfaces {
interface-range range-1 {
member-range ge-10/0/0 to ge-10/0/47;
hold-time up 10;
}
}

In this example, interfaces ge-10/0/0 through ge-10/0/47 will have both hold-time and
mtu.

Configuring Inheritance Range Priorities

The interface ranges are defined in the order of inheritance priority, with the first interface
range configuration data taking priority over subsequent interface ranges.
[edit]
interfaces {
interface-range int-grp-one {
member-range ge-0/0/0 to ge-4/0/40;
member ge-1/1/1;
/*Common config is added part of the interface-range definition*/
mtu 256;
hold-time up 10;
}
}
interfaces {
interface-range int-grp-two {
member-range ge-5/0/0 to ge-10/0/40;
member ge-1/1/1;
mtu 1024;
}
}

Interface ge-1/1/1 exists in both interface-range int-grp-one and interface-range int-grp-two.

This interface inherits mtu 256 from interface-range int-grp-one because it was defined
first.

90

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Configuration Expansion Where Interface Range Is Used

In this example, interface-range range-1 is used under the protocols hierarchy:
[edit]
interfaces {
interface-range range-1 {
member ge-10/1/1;
member ge-5/5/1;
mtu 256;
hold-time up 10;
ether-options {
flow-control;
speed {
100m;
}
802.3ad primary;
}
}
protocols {
dot1x {
authenticator {
interface range-1 {
retries 1;
}
}
}
}
}

The interface node present under authenticator is expanded into member interfaces of
the interface-range range-1 as follows:
protocols {
dot1x {
authenticator {
interface ge-10/1/1 {
retries 1;
}
interface ge-5/5/1 {
retries 1;
}
}
}
}

The interface range-1 statement is expanded into two interfaces, ge-10/1/1 and ge-5/5/1,
and configuration retries 1 is copied under those two interfaces.
This configuration can be verified using the show protocols dot1x | display inheritance
command.
Related
Documentation

Physical Interfaces

Copyright 2014, Juniper Networks, Inc.

91

Interfaces Fundamentals for Routing Devices

Specifying an Aggregated Interface

The M Series, MX Series, and T Series routers support aggregated interfaces. To specify
an aggregated interface assign a number with the aggregated interface name. For
example, configure aex at the [edit interfaces] hierarchy level, where x is an integer ranging
0 through 127 for M Series and T Series routers and 0 through 479 on MX Series routers.
For aggregated SONET/SDH interfaces, configure asx at the [edit interfaces] hierarchy
level.

NOTE: SONET/SDH aggregation is proprietary to the Junos OS and might

not work with other software.

If you are configuring VLANs for aggregated Ethernet interfaces, you must include the
vlan-tagging statement at the [edit interfaces aex] hierarchy level to complete the
association.
Related
Documentation

Aggregated Ethernet Interfaces Overview

Configuring Aggregated SONET/SDH Interfaces

Configuring Interface Description

You can include a text description of each physical interface in the configuration file. Any
descriptive text you include is displayed in the output of the show interfaces commands,
and is also exposed in the ifAlias Management Information Base (MIB) object. It has no
impact on the interfaces configuration.
Before you add a text description of a physical interface in the configuration file, you must
first configure the interface at the [edit interfaces] hierarchy level. To add a text
description, include the description statement at the [edit interfaces interface-name]
hierarchy level:
[edit]
user@host# edit interfaces interface-name
description text

For example:
[edit interfaces fe-0/0/1]
description "Backbone connection to PHL01"

The description can be a single line of text. If the text contains spaces, enclose it in
quotation marks.

92

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

NOTE: You can configure the extended DHCP relay to include the interface
description in the option 82 Agent Circuit ID suboption. See Using DHCP Relay
Agent Option 82 Information in the Junos OS Broadband Subscriber
Management and Services Library.

For information about describing logical units, see Adding a Logical Unit Description to
the Configuration on page 171.
To display the description from the router or switch CLI, use the show interfaces command:
user@host>
show interfaces fe-0/0/1
Physical interface: fe-0/0/1, Enabled, Physical link is Up
Interface index: 129, SNMP ifIndex: 23
Description: Backbone connection to PHL01
...

To display the interface description from the interfaces MIB, use the snmpwalk command
from a server. To isolate information for a specific interface, search for the interface index
shown in the SNMP ifIndex field of the show interfaces command output. The ifAlias
object is in ifXTable.
user-server>snmpwalk host-fxp0.mylab public ifXTable | grep -e '\.23'
snmpwalk host-fxp0.mylab public ifXTable | grep -e '\.23'
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifName.23 = fe-0/0/1
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifInMulticastPkts.23 = Counter32: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifInBroadcastPkts.23 = Counter32: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifOutMulticastPkts.23 = Counter32: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifOutBroadcastPkts.23 = Counter32: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCInOctets.23 = Counter64: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCInUcastPkts.23 = Counter64: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCInMulticastPkts.23 = Counter64: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCInBroadcastPkts.23 = Counter64: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCOutOctets.23 = Counter64: 42
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCOutUcastPkts.23 = Counter64: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCOutMulticastPkts.23 = Counter64: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHCOutBroadcastPkts.23 = Counter64: 0
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifLinkUpDownTrapEnable.23 = enabled(1)
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifHighSpeed.23 = Gauge32: 100
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifPromiscuousMode.23 = false(2)
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifConnectorPresent.23 = true(1)
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifAlias.23 = Backbone connection to PHL01
ifMIB.ifMIBObjects.ifXTable.ifXEntry.ifCounterDiscontinuityTime.23 = Timeticks:
(0) 0:00:00.00

Related
Documentation

Using DHCP Relay Agent Option 82 Information

Adding a Logical Unit Description to the Configuration on page 171

Configuring the Media MTU

The media maximum transmission unit (MTU) is the largest data unit that can be
forwarded without fragmentation.

Copyright 2014, Juniper Networks, Inc.

93

Interfaces Fundamentals for Routing Devices

This topic contains the following sections:

Media MTU Overview on page 94

How to Configure the Media MTU on page 95

Encapsulation Overhead by Encapsulation Type on page 96

Media MTU Sizes by Interface Type for M5 and M7i Routers with CFEB, M10 and M10i
Routers with CFEB, and M20 and M40 Routers on page 97

Media MTU Sizes by Interface Type for M40e Routers on page 97

Media MTU Sizes by Interface Type for M160 Routers on page 99

Media MTU Sizes by Interface Type for M7i Routers with CFEB-E, M10i Routers with
CFEB-E, and M320 and M120 Routers on page 99

Media MTU Sizes by Interface Type for MX Series Routers on page 100

Media MTU Sizes by Interface Type for T320 Routers on page 101

Media MTU Sizes by Interface Type for T640 Platforms on page 101

Media MTU Sizes by Interface Type for J2300 Platforms on page 102

Media MTU Sizes by Interface Type for J4300 and J6300 Platforms on page 102

Media MTU Sizes by Interface Type for J4350 and J6350 Platforms on page 103

Media MTU Sizes by Interface Type for EX Series Switches and ACX Series
Routers on page 105

Media MTU Sizes by Interface Type for PTX Series Packet Transport Routers on page 105

Media MTU Overview

The default media MTU size used on a physical interface depends on the encapsulation
used on that interface. In some cases, the default IP Protocol MTU depends on whether
the protocol used is IP version 4 (IPv4) or International Organization for Standardization
(ISO).
The default media MTU is calculated as follows:
Default media MTU = Default IP MTU + encapsulation overhead

When you are configuring point-to-point connections, the MTU sizes on both sides of the
connections must be the same. Also, when you are configuring point-to-multipoint
connections, all interfaces in the subnet must use the same MTU size. For details about
encapsulation overhead, see Encapsulation Overhead by Encapsulation Type on page 96.

94

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

NOTE: The actual frames transmitted also contain cyclic redundancy check
(CRC) bits, which are not part of the media MTU. For example, the media
MTU for a Gigabit Ethernet Version 2 interface is specified as 1514 bytes, but
the largest possible frame size is actually 1518 bytes; you need to consider
the extra bits in calculations of MTUs for interoperability.
The physical MTU for Ethernet interfaces does not include the 4-byte frame
check sequence (FCS) field of the Ethernet frame.
A SONET/SDH interface operating in concatenated mode has a c added
to the rate descriptor. For example, a concatenated OC48 interface is referred
to as OC48c.
If you do not configure an MPLS MTU, the Junos OS derives the MPLS MTU
from the physical interface MTU. From this value, the software subtracts the
encapsulation-specific overhead and space for the maximum number of
labels that might be pushed in the Packet Forwarding Engine. Currently, the
software provides for three labels of four bytes each, for a total of 12 bytes.
In other words, the formula used to determine the MPLS MTU is the following:
MPLS MTU = physical interface MTU encapsulation overhead 12

If you configure an MTU value by including the mtu statement at the [edit
interfaces interface-name unit logical-unit-number family mpls] hierarchy level,
the configured value is used.

How to Configure the Media MTU

To modify the default media MTU size for a physical interface, include the mtu statement
at the [edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
mtu bytes;

If you change the size of the media MTU, you must ensure that the size is equal to or
greater than the sum of the protocol MTU and the encapsulation overhead.

NOTE: Changing the media MTU or protocol MTU causes an interface to be

deleted and added again.

You configure the protocol MTU by including the mtu statement at the following hierarchy
levels:

[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]

Copyright 2014, Juniper Networks, Inc.

95

Interfaces Fundamentals for Routing Devices

Because tunnel services interfaces are considered logical interfaces, you cannot configure
the MTU setting for the physical interface. This means you cannot include the mtu
statement at the [edit interfaces interface-name] hierarchy level for the following interface
types: generic routing encapsulation (gr-), IP-IP (ip-), loopback (lo-), link services (ls-),
multilink services (ml-), and multicast (pe-, pd-). You can, however, configure the protocol
MTU on tunnel interfaces, as described in Setting the Protocol MTU on page 208.

Encapsulation Overhead by Encapsulation Type

Table 29: Encapsulation Overhead by Encapsulation Type

96

Interface Encapsulation

Encapsulation Overhead (Bytes)

802.1Q/Ethernet 802.3

21

802.1Q/Ethernet Subnetwork Access Protocol (SNAP)

26

802.1Q/Ethernet version 2

18

ATM Cell Relay

ATM permanent virtual connection (PVC)

12

Cisco HDLC

Ethernet 802.3

17

Ethernet circuit cross-connect (CCC) and virtual private

LAN service (VPLS)

Ethernet over ATM

32

Ethernet SNAP

22

Ethernet translational cross-connect (TCC)

18

Ethernet version 2

14

Extended virtual local area network (VLAN) CCC and

VPLS

Extended VLAN TCC

22

Frame Relay

PPP

VLAN CCC

VLAN VPLS

VLAN TCC

22

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Media MTU Sizes by Interface Type for M5 and M7i Routers with CFEB, M10 and M10i Routers
with CFEB, and M20 and M40 Routers
Table 30: Media MTU Sizes by Interface Type for M5 and M7i Routers with
CFEB, M10 and M10i Routers with CFEB, and M20 and M40 Routers
Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

Adaptive Services
(MTU size not
configurable)

9192

N/A

N/A

ATM

4482

9192

4470

E1/T1

1504

9192

1500

E3/T3

4474

9192

4470

Fast Ethernet

1514

1533 (4-port)

1500 (IPv4),
1497 (ISO)

Interface Type

1532 (8-port)
1532 (12-port)
NOTE: The maximum
MTU for two
100Base-TX Fast
Ethernet port FIC is
9192 bytes.
Gigabit Ethernet

1514

9192

1500 (IPv4),
1497 (ISO)

NOTE: The maximum

MTU for one Gigabit
Ethernet port FIC is
9192 bytes.
Serial

1504

9192

1500 (IPv4),
1497 (ISO)

SONET/SDH

4474

9192

4470

Media MTU Sizes by Interface Type for M40e Routers

Table 31: Media MTU Sizes by Interface Type for M40e Routers
Default Media
MTU (Bytes)

Maximum MTU (Bytes)

Default IP Protocol
MTU (Bytes)

Adaptive Services
(MTU size not
configurable)

9192

N/A

N/A

ATM

4482

9192

4470

Interface Type

Copyright 2014, Juniper Networks, Inc.

97

Interfaces Fundamentals for Routing Devices

Table 31: Media MTU Sizes by Interface Type for M40e Routers (continued)
Interface Type

Default Media
MTU (Bytes)

Maximum MTU (Bytes)

Default IP Protocol
MTU (Bytes)

E1/T1

1504

4500

1500

E3/T3

4474

4500

4470

9192 (4-port)
E3/DS3 IQ

4474

9192

4470

Fast Ethernet

1514

1533

1500 (IPv4),
1497 (ISO)

Gigabit Ethernet

1514

9192 (1- or 2-port)

1500 (IPv4),
1497 (ISO)

9192 (4-port)
Serial

1504

9192

1500 (IPv4),
1497 (ISO)

SONET/SDH

4474

4500 (1-port
nonconcatenated)

4470

9192 (4-port OC3)

9192 (4-port OC3c)
4500 (1-port OC12)
4500 (4-port OC12)
4500 (4-port OC12c)
4500 (1-port OC48)
9192 (2-port OC3)
9192 (2-port OC3c)
9192 (1-port OC12c)
9192 (1-port OC48c)
4500 (1-port OC192)
9192 (1-port OC192c)

98

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Media MTU Sizes by Interface Type for M160 Routers

Table 32: Media MTU Sizes by Interface Type for M160 Routers
Default Media
MTU (Bytes)

Maximum MTU (Bytes)

Default IP Protocol
MTU (Bytes)

Adaptive Services
(MTU size not
configurable)

9192

N/A

N/A

ATM

4482

9192

4470

E1/T1

1504

4500

1500

E3/T3

4474

4500

4470

E3/DS3 IQ

4474

9192

4470

Fast Ethernet

1514

1533

1500 (IPv4),
1497 (ISO)

Gigabit Ethernet

1514

9192 (1- or 2-port)

1500 (IPv4),
1497 (ISO)

Interface Type

4500 (4-port)
Serial

1504

9192

1500 (IPv4),
1497 (ISO)

SONET/SDH

4474

4500 (1-port
nonconcatenated)

4470

9192 (1- or 2-port)

4500 (4-port)

Media MTU Sizes by Interface Type for M7i Routers with CFEB-E, M10i Routers with CFEB-E,
and M320 and M120 Routers
Table 33: Media MTU Sizes by Interface Type for M7i Routers with CFEB-E,
M10i Routers with CFEB-E, and M320 and M120 Routers
Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

ATM2 IQ

4482

9192

4470

Channelized DS3 IQ

4471

4500

4470

Channelized E1 IQ

1504

4500

1500

Channelized OC12 IQ

4474

9192

4470

Copyright 2014, Juniper Networks, Inc.

99

Interfaces Fundamentals for Routing Devices

Table 33: Media MTU Sizes by Interface Type for M7i Routers with CFEB-E,
M10i Routers with CFEB-E, and M320 and M120 Routers (continued)
Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

Channelized STM1 IQ

4474

9192

4470

DS3

4471

4500

4470

E1

1504

4500

1500

E3 IQ

4471

4500

4470

Fast Ethernet

1514

1533 (4-port)

1500 (IPv4),
1497 (ISO)

1532 (8-, 12- and

48-port)
Gigabit Ethernet

1514

9192

1500 (IPv4),
1497 (ISO)

SONET/SDH

4474

9192

4470

T1

1504

4500

1500

CT3 IQ

4474

9192

4470

(excluding M120)

Media MTU Sizes by Interface Type for MX Series Routers

Table 34: Media MTU Sizes by Interface Type for MX Series Routers

100

Interface Type

Default Media
MTU (Bytes)

Maximum MTU (Bytes)

Default IP Protocol
MTU (Bytes)

Gigabit Ethernet

1514

9192

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

10-Gigabit Ethernet

1514

9192

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

Multi-Rate Ethernet

1514

9192

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

Tri-Rate Ethernet

1514

9192

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 34: Media MTU Sizes by Interface Type for MX Series

Routers (continued)
Channelized
SONET/SDH
OC3/STM1
(Multi-Rate)

1514

9192

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

DS3/E3 (Multi-Rate)

1514

9192

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

Media MTU Sizes by Interface Type for T320 Routers

Table 35: Media MTU Sizes by Interface Type for T320 Routers
Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

ATM

4482

9192

4470

ATM2 IQ

4482

9192

4470

Channelized OC12 IQ

4474

9192

4470

Channelized STM1 IQ

4474

9192

4470

DS3

4471

4500

4470

Fast Ethernet

1514

1533 (4-port)

1500 (IPv4),
1497 (ISO)

1532 (12- and 48-port)

Gigabit Ethernet

1514

9192

1500 (IPv4),
1497 (ISO)

SONET/SDH

4474

9192

4470

CT3 IQ

4474

9192

4470

Media MTU Sizes by Interface Type for T640 Platforms

Table 36: Media MTU Sizes by Interface Type for T640 Platforms
Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

ATM2 IQ

4482

9192

4470

48-port Fast Ethernet

1514

1532

1500 (IPv4),
1497 (ISO)

Copyright 2014, Juniper Networks, Inc.

101

Interfaces Fundamentals for Routing Devices

Table 36: Media MTU Sizes by Interface Type for T640

Platforms (continued)
Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

Gigabit Ethernet

1514

9192

1500 (IPv4),
1497 (ISO)

SONET/SDH

4474

9192

4470

CT3 IQ

4474

9192

4470

Media MTU Sizes by Interface Type for J2300 Platforms

Table 37: Media MTU Sizes by Interface Type for J2300 Platforms
Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

Fast Ethernet
(10/100)

1514

9192

1500

G.SHDSL

4482

9150

4470

ISDN BRI

1504

4092

1500

Serial

1504

9150

1500

T1 or E1

1504

9150

1500

Interface Type

Media MTU Sizes by Interface Type for J4300 and J6300 Platforms
Table 38: Media MTU Sizes by Interface Type for J4300 and J6300
Platforms

102

Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

ADSL2+ PIM

4482

9150

4470

Dual-port Fast
Ethernet (10/100) PIM

1514

9192

1500

Dual-port Serial PIM

1504

9150

1500

Dual-port T1 or E1 PIM

1504

9150

1500

Dual-port
Channelized T1/E1 PIM
(channelized to
DS0s)

1504

4500

1500

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 38: Media MTU Sizes by Interface Type for J4300 and J6300
Platforms (continued)
Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

Dual-port
Channelized T1/E1 PIM
(clear channel T1 or
E1)

1504

9150

1500

Fast Ethernet
(10/100) built-in
interface

1514

9192

1500

G.SHDSL PIM

4482

9150

4470

4-port ISDN BRI PIM

1504

4092

1500

T3 (DS3) or E3 PIM

4474

9192

4470

Interface Type

Media MTU Sizes by Interface Type for J4350 and J6350 Platforms
Table 39: Media MTU Sizes by Interface Type for J4350 and J6350
Platforms
Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

4-port ISDN BRI PIM

1504

4092

1500

ADSL2+ PIM

4482

9150

4470

Dual-port Fast
Ethernet (10/100) PIM

1514

9192

1500

Dual-port Serial PIM

1504

9150

1500

Dual-port T1 or E1 PIM

1504

9150

1500

Dual-port
Channelized T1/E1 PIM
(channelized to
DS0s)

1504

4500

1500

Dual-port
Channelized T1/E1 PIM
(clear channel T1 or
E1)

1504

9150

1500

4-port Fast Ethernet

(10/100) ePIM

1518

1518

1500

Copyright 2014, Juniper Networks, Inc.

103

Interfaces Fundamentals for Routing Devices

Table 39: Media MTU Sizes by Interface Type for J4350 and J6350
Platforms (continued)
Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

Gigabit Ethernet
(10/100/1000)
built-in interface

1514

9018

1500

Gigabit Ethernet
(10/100/1000)
Enhanced Physical
Interface Module
(ePIM)

1514

9018

1500

Gigabit Ethernet
(10/100/1000) SFP
ePIM

1514

9018

1500

G.SHDSL PIM

4482

9150

4470

T3 (DS3) or E3 PIM

4474

9192

4470

Interface Type

NOTE: On Gigabit Ethernet ePIMs in J4350 and J6350 Services Routers, you
can configure a maximum transmission unit (MTU) size of only 9018 bytes
even though the CLI indicates that you can configure an MTU of up to 9192
bytes. If you configure an MTU greater than 9018 bytes, the router does not
accept the configuration and generates a system log error message similar
to the following:
/kernel: ge-0/0/0: Illegal media change. MTU invalid: 9192. Max MTU
supported on this PIC: 9018

On 4-port Fast Ethernet ePIMs in J4350 and J6350 Services Routers, you can
configure a maximum transmission unit (MTU) size of only 1518 bytes even
though the CLI indicates that you can configure an MTU of up to 9192 bytes.
If you configure an MTU greater than 1518 bytes, the router does not accept
the configuration and generates a system log error message similar to the
following:
/kernel: fe-3/0/1: Illegal media change. MTU invalid: 9192. Max MTU
supported on this PIC: 1518

104

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Media MTU Sizes by Interface Type for EX Series Switches and ACX Series Routers
Table 40: Media MTU Sizes by Interface Type for EX Series Switches and
ACX Series Routers
Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

Gigabit Ethernet

1514

9192

1500 (IPv4),
1497 (ISO)

10-Gigabit Ethernet

1514

9192

1500 (IPv4),
1497 (ISO)

NOTE: On ACX Series routers, you can configure the protocol MTU by including
the mtu statement at the [edit interfaces interface-name unit logical-unit-number
family inet] or [edit interfaces interface-name unit logical-unit-number family
inet6] hierarchy level.

If you configure the protocol MTU at any of these hierarchy levels, the
configured value is applied to all families that are configured on the logical
interface.

If you are configuring the protocol MTU for both inet and inet6 families on
the same logical interface, you must configure the same value for both the
families. It is not recommended to configure different MTU size values for
inet and inet6 families that are configured on the same logical interface.

Media MTU Sizes by Interface Type for PTX Series Packet Transport Routers
Table 41: Media MTU Sizes by Interface Type for PTX Series Packet
Transport Routers

Related
Documentation

Interface Type

Default Media
MTU (Bytes)

Maximum MTU
(Bytes)

Default IP Protocol
MTU (Bytes)

10-Gigabit Ethernet

1514

9500

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

40-Gigabit Ethernet

1514

9500

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

100-Gigabit Ethernet

1514

9500

1500 (IPv4),
1488 (MPLS),
1497 (ISO)

Configuring Interface Encapsulation on Physical Interfaces on page 117

Copyright 2014, Juniper Networks, Inc.

105

Interfaces Fundamentals for Routing Devices

Setting the Protocol MTU on page 208

Configuring the Interface Speed

You can configure the interface speed on the following interfaces:

Configuring the Speed of Management Ethernet Interfaces on M Series and T Series

Routers on page 106

Configuring the Speed of Gigabit Ethernet Interfaces on J Series Routers on page 106

Configuring the Speed of Fast Ethernet Interfaces on page 107

Configuring the Speed of Tri-Rate Ethernet Copper Interfaces on page 107

Configuring the Speed of SONET/SDH Interfaces on page 108

Configuring the Speed of Management Ethernet Interfaces on M Series and T Series Routers
M Series routers, MX Series routers, T Series routers, and TX Series routers use one of
two management Ethernet interface types, either em or fxp, dependent on the installed
Routing Engine model. For information about management Ethernet interfaces and to
determine the management Ethernet interface type for your router, see Understanding
Management Ethernet Interfaces on page 10 and Supported Routing Engines by Router
on page 14.
By default, the M Series and T Series routers management Ethernet interface
autonegotiates whether to operate at 10 megabits per second (Mbps) or 100 Mbps. All
other interfaces automatically choose the correct speed based on the PIC type and
whether the PIC is configured to operate in multiplexed mode (using the no-concatenate
statement in the [edit chassis] configuration hierarchy, as described in the Junos OS
Administration Library for Routing Devices).
To configure the management Ethernet interface to operate at 10 Mbps or 100 Mbps,
include the speed statement at the [edit interfaces fxp0] or [edit interfaces em0] hierarchy
level:
[edit interfaces (fxp0 | em0)]
(10m | 100m);

For information about configuring the link mode, see Configuring the Link Characteristics
on Ethernet Interfaces.

Configuring the Speed of Gigabit Ethernet Interfaces on J Series Routers

By default, Gigabit Ethernet interfaces (both built-in and PIMs) for J Series routers
autonegotiate whether to operate at 10 megabits per second (Mbps), 100 Mbps, or 1000
Mbps.
To configure a J Series Gigabit Ethernet interface to operate at 10 Mbps, 100 Mbps, or
1000 Mbps, include the speed statement at the [edit interfaces ge-pim/0/port] hierarchy
level:
[edit interfaces ge-pim/0/port]

106

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

speed (10m | 100m | 1g);

For information about configuring the link mode, see Configuring the Link Characteristics
on Ethernet Interfaces.

Configuring the Speed of Fast Ethernet Interfaces

By default, both of the built-in Fast Ethernet ports on the M7i router FIC autonegotiate
whether to operate at 10 Mbps or 100 Mbps. All other interfaces automatically choose
the correct speed based on the PIC type and whether the PIC is configured to operate in
multiplexed mode (using the no-concatenate statement at the [edit chassis] hierarchy
level, as described in the Junos OS Administration Library for Routing Devices).
If the link partner does not support autonegotiation, configure either Fast Ethernet port
manually to match its link partner's speed and link mode. When the link mode is
configured, autonegotiation is disabled.

NOTE: When you manually configure Fast Ethernet interfaces on the M Series
and T Series routers, link mode and speed must both be configured. If both
these values are not configured, the router uses autonegotiation for the link
and ignores the user-configured settings.

To configure a Fast Ethernet port on the FIC to operate at 10 Mbps or 100 Mbps, include
the speed statement at the [edit interfaces fe-fpc/pic/port] hierarchy level:
[edit interfaces fe-fpc/pic/port]
speed (10m | 100m);

For information about configuring the link mode, see Configuring the Link Characteristics
on Ethernet Interfaces.

Configuring the Speed of Tri-Rate Ethernet Copper Interfaces

By default, the Tri-Rate Ethernet copper interfaces on MX Series routers operate at 1
Gbps. Tri-Rate Ethernet copper interfaces can also be configured to operate at 10 Mbps,
100 Mbps, or 1 Gbps.

NOTE: When you configure the Tri-Rate Ethernet copper interface to operate
at 1 Gbps, autonegotiation must be enabled.

NOTE: Half-duplex mode is not supported on Tri-Rate Ethernet copper

interfaces. When you include the speed statement, you must include the
link-mode full-duplex statement at the same hierarchy level.

To configure a Tri-Rate Ethernet copper interface to operate at 10 Mbps, 100 Mbps, or 1

Gbps, include the speed statement at the [edit interfaces ge-fpc/pic/port] hierarchy level:
[edit interfaces ge-fpc/pic/port]

Copyright 2014, Juniper Networks, Inc.

107

Interfaces Fundamentals for Routing Devices

speed (10m | 100m | 1g);

For information about configuring the link mode, see Configuring the Link Characteristics
on Ethernet Interfaces.

Configuring the Speed of SONET/SDH Interfaces

You can configure the speed of SONET/SDH interfaces on next-generation SONET/SDH
Type 1 and Type 2 PICs with SFP. The speed you select is dependent upon whether the
PIC is in concatenated or nonconcatenated mode. In concatenated mode, the bandwidth
of the interface is in a single channel. In nonconcatenated mode, the PIC operates in
channelized (multiplexed) mode.
Table 42 on page 108 shows the mode combinations for the next-generation SONET/SDH
Type 1 PICs with SFP.

Table 42: Type 1 PIC Mode Combinations

PIC

Mode

2-port OC3

2xOC3 concatenated

fpc/pic/0 speed oc3

concatenated

4-port OC3

1xOC12 concatenated

fpc/pic/0 speed oc12

1xOC12 nonconcatenated

fpc/pic/0:0 speed oc3

nonconcatenated

4xOC3 concatenated

fpc/pic/port speed oc3

concatenated

1xOC12 concatenated

fpc/pic/0 speed oc12

concatenated

1xOC12 nonconcatenated

fpc/pic/0:0 speed oc3

nonconcatenated

1xOC3 concatenated

fpc/pic/0 speed oc3

1-port OC12

Speed Configuration

Default Mode

Table 43 on page 108 shows the mode combinations for the next-generation SONET/SDH
Type 2 PICs with SFP.

Table 43: Type 2 PIC Mode Combinations

PIC

Mode

1-port OC48, IQ
and IQE

1xOC48 concatenated

fpc/pic/0 speed oc48

concatenated

1xOC48 nonconcatenated

fpc/pic/0:0 speed oc12

nonconcatenated

1xOC12 concatenated

fpc/pic/0 speed oc12

1xOC12 nonconcatenated

fpc/pic/0 0 speed oc3

1xOC3 concatenated

fpc/pic/0 speed oc3

108

Speed Configuration

Default Mode

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 43: Type 2 PIC Mode Combinations (continued)

PIC

Mode

4-port OC12, IQ
and IQE

1xOC48 concatenated

fpc/pic/0 speed oc48

1xOC48 nonconcatenated

fpc/pic/0:0 speed oc12

nonconcatenated

1xOC12 nonconcatenated

fpc/pic/0 speed oc3

4xOC12 concatenated

fpc/pic/port speed oc3|oc12

concatenated

1xOC12 concatenated

fpc/pic/0 speed oc12

1xOC12 nonconcatenated

fpc/pic/0:0 speed oc3

nonconcatenated

4xOC3 concatenated

fpc/pic/port speed oc3

concatenated

4-port OC3, IQ
and IQE

Speed Configuration

Default Mode

By default, SONET/SDH PICs operate in concatenated mode. To specify interface speed

in concatenated mode, include the speed statement with options at the [edit interfaces
so-fpc/pic/port] hierarchy level:
[edit interfaces so-fpc/pic/port]
speed (oc3 | oc12 | oc48);

For example, each port of the 4-port OC12 PIC can be configured to be in OC3 or OC12
speed independently when this PIC is in 4xOC12 concatenated mode.
To specify interface speed in nonconcatenated mode, include the speed statement at
the [edit interfaces so-fpc/pic/port.channel] hierarchy level:
[edit interfaces so-fpc/pic/port.channel]
speed (oc3 | oc12);

To configure the PIC to operate in channelized (multiplexed) mode, include the

no-concatenate statement at the [edit chassis fpc slot-number pic pic-number] hierarchy
level.
For more information about using the no-concatenate statement, see the Junos OS
Administration Library for Routing Devices.

Configuring the Link Characteristics

By default, the routers management Ethernet interface, fxp0 or em0, autonegotiates
whether to operate in full-duplex or half-duplex mode. Fast Ethernet and J Series router
Gigabit Ethernet interfaces can operate in either full-duplex or half-duplex mode, and
all other interfaces can operate only in full-duplex mode. For Gigabit Ethernet, the link
partner must also be set to full duplex.

NOTE: When you configure the Tri-Rate Ethernet copper interface to operate
at 1 Gbps, autonegotiation must be enabled.

Copyright 2014, Juniper Networks, Inc.

109

Interfaces Fundamentals for Routing Devices

NOTE: When you manually configure Fast Ethernet interfaces on the M Series
and T Series routers, link mode and speed must both be configured. If both
these values are not configured, the router uses autonegotiation for the link
and ignores the user-configured settings.

NOTE: When the Fast Ethernet interface on Juniper Networks routers with
autonegotiation enabled interoperates with a device configured to operate
in half-duplex mode (autonegotiation disabled), the interface defaults to
half-duplex mode after the PIC is taken offline and brought back online. This
results in packet loss and cyclic redundancy check (CRC) errors.

To explicitly configure an Ethernet interface to operate in either full-duplex or half-duplex

mode, include the link-mode statement at the [edit interfaces interface-name] hierarchy
level:
[edit interfaces interface-name]
link-mode (full-duplex | half-duplex);

Interface Alias Names Overview

You can configure a textual description of a logical unit on a physical interface to be the
alias of an interface name. Interface aliasing is supported only at the unit level. If you
configure an alias name, the alias name is displayed instead of the interface name in the
output of all show, show interfaces, and other operational mode commands. In Junos OS
Release 13.3R3 and later, display of the alias can be suppressed in favor of the actual
interface name by using the display no-interface-alias parameter along with the show
command. Configuring an alias for a logical unit of an interface has no effect on how the
interface on the router or switch operates.
When you configure the alias name of an interface, the CLI saves the alias name as the
value of the interface-name variable in the configuration database. To enable backward
compatibility with Junos OS releases in which the support for interface aliases is not
available, when the Junos OS processes query the configuration database for the
interface-name variable, the actual, exact value of the interface-name variable is returned
instead of the alias name for system operations and computations.
This capability to define interface alias names for physical and logical interfaces is useful
in a Junos Node Unifier (JNU) environment that contains a Juniper Networks MX Series
3D Universal Edge Router as a controller and EX Series Ethernet switches, QFX Series
devices, and ACX Series Universal Access Routers as satellite devices. The following are
the benefits of configuring an alias name, which enables a meaningful, single, and easily
identifiable name to be allocated to an interface:

110

You can group physical interfaces as one aggregated interface (link aggregation group
or LAG bundle) and name that bundle as a satellite connection interface (for example,
sat1).

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

You can select a logical interface as a member of the LAG bundle or the entire LAG,
and name that interface to represent a satellite device port or a service instance (for
example, ge-0/0/1).

You can combine the satellite name and the interface name aliases to wholly represent
the satellite port name (for example, sat1:ge-0/0/1 or ge-sat1/0/0/1 or ge-1/0/0/1) in
the most easily distinguishable format that denotes a combination of port and satellite
parts of the name.

To specify an interface alias, you can use the alias statement at the [edit interfaces
interface-name unit logical-unit-number] and [edit logical-systems logical-system-name
interfaces interface-name unit logical-unit-number] hierarchy levels.

NOTE: In Juniper Networks M Series Multiservice Edge Routers, if the same

alias name is configured on more than one logical interface, the router displays
an error message and commit fails.

Related
Documentation

Example: Adding an Interface Alias Name on page 111

alias on page 422

Example: Adding an Interface Alias Name

This example shows how to add an alias to the logical unit of an interface. Using an alias
to identify interfaces as they appear in the output for operational commands can allow
for more meaningful naming conventions and easier identification.

Requirements on page 111

Overview on page 111

Configuration on page 112

Verification on page 114

Requirements
This example uses the following hardware and software components:

One MX Series router that acts as a controller

One EX4200 switch that acts as a satellite device

Junos OS Release 13.3R1 or later

Overview
You can create an alias for each logical unit on a physical interface. The descriptive text
you define for the alias is displayed in the output of the show interfaces commands. In
Junos OS Release 13.3R3 and later, display of the alias can be suppressed in favor of the
actual interface name by using the display no-interface-alias parameter along with the

Copyright 2014, Juniper Networks, Inc.

111

Interfaces Fundamentals for Routing Devices

show command. The alias configured for a logical unit of an interface has no effect on
how the interface on the router or switch operates it is only a cosmetic label.

Configuration
Consider a scenario in which alias names are configured on the interfaces of a JNU
controller that are connected to a satellite, sat1, in the downlink direction in the JNU
management network by using two links. The alias names enable effective, streamlined
identification of these interfaces in the operational mode commands that are run on the
controller and satellites.

CLI Quick
Configuration

Configuring Alias Names for the Controller Interfaces on page 112

Results on page 113

To quickly configure this example, copy the following commands, paste them in 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:
set interfaces ae0 unit 0 alias "controller-sat1-downlink1"
set interfaces ae0.0 family inet address 10.0.0.1/24
set interfaces ae1 unit 0 alias "controller-sat1-downlink1"
set interfaces ae0.0 family inet address 192.0.2.128/25
set interfaces ge-0/0/0 vlan-tagging
set interfaces ge-0/0/0 unit 0 alias "ge-to-corp-gw1"
set interfaces ge-0/0/0.0 vlan-id 101
set interfaces ge-0/0/0.0 family inet address 1.1.1.1/23
set interfaces ge-0/1/0 gigether-options 802.3ad ae0
set interfaces ge-0/1/1 gigether-options 802.3ad ae0
set protocols rip group corporate-firewall neighbor ge-to-corp-gw1

Configuring Alias Names for the Controller Interfaces

Step-by-Step
Procedure

The following example requires you to navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To add an alias name to the controller interfaces that are used to connect to the satellite
devices in the downlink direction:
1.

Configure an alias name for the logical unit of an aggregated Ethernet interface that
is used to connect to a satellite, sat1, in the downlink direction. Configure inet family
and address for the interface.
[edit]
user@host# set interfaces ae0 unit 0 alias "controller-sat1-downlink1"
user@host# set interfaces ae0.0 family inet address 10.0.0.1/24

2.

Configure an alias name for the logical unit of another aggregated Ethernet interface
that is used to connect to the same satellite, sat1, in downlink direction. Configure
INET family and address for the interface.
[edit]
user@host# set interfaces ae0 unit 1 alias "controller-sat1-downlink2"
user@host# set interfaces ae0.0 family inet address 10.0.0.3/24

112

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

3.

Configure an alias name for the Gigabit Ethernet interface on the controller and
configure its parameters.
[edit]
user@host# set interfaces ge-0/0/0 vlan-tagging
user@host# set interfaces ge-0/0/0 unit 0 alias "ge-to-corp-gw1"
user@host# set interfaces ge-0/0/0.0 vlan-id 101
user@host# set interfaces ge-0/0/0.0 family inet address 1.1.1.1/23

4.

Configure Gigabit Ethernet interfaces to be member links of an ae- logical interface.

[edit]
user@host# set interfaces ge-0/1/0 gigether-options 802.3ad ae0
user@host# set interfaces ge-0/1/1 gigether-options 802.3ad ae0

5.

Configure RIP in the network between the controller and the firewall gateway.
[edit]
user@host# set protocols rip group corporate-firewall neighbor ge-to-corp-gw1

Results
In configuration mode, confirm your configuration by entering the show command. If the
output does not display the intended configuration, repeat the configuration instructions
in this example to correct it.
[edit]
interfaces {
ae0 {
unit 0 {
alias "controller-sat1-downlink1";
family inet {
address 10.0.0.1/24;
}
}
unit 1 {
alias "controller-sat1-downlink2";
family inet {
address 10.0.0.3/24;
}
}
}
ge-0/0/0 {
vlan-tagging;
unit 0 {
alias "ge-to-corp-gw1";
vlan-id 101;
family inet {
address 1.1.1.1/23;
}
}
}
ge-0/1/0 {
gigether-options {
802.3ad ae0;
}
}
ge-0/1/1 {
gigether-options {
802.3ad ae0;

Copyright 2014, Juniper Networks, Inc.

113

Interfaces Fundamentals for Routing Devices

}
}
}
protocols rip {
group corporate-firewall {
neighbor ge-to-corp-gw1;
}
}

After you have confirmed that the interfaces are configured, enter the commit command
in configuration mode.

NOTE: In Juniper Networks M Series Multiservice Edge Routers, if the same

alias name is configured on more than one logical interface, the router displays
an error message and commit fails.

Verification
To verify that the alias name is displayed instead of the interface name, perform these
steps:

Verifying the Configuration of the Alias Name for the Controller Interfaces on page 114

Verifying the Configuration of the Alias Name for the Controller Interfaces
Purpose

Action

Verify that the alias name is displayed instead of the interface name.

Display information about all RIP neighbors.

user@router> show rip neighbor
Local Source
Neighbor
State Address
ge-to-corp-gw1
DN (null)

Meaning

Related
Documentation

114

Destination
Send
Address
Mode
255.255.255.255 mcast

Receive
Mode
both

In
Met
1

The output displays the details of the benchmarking test that was performed. For more
information about the show rip neighbor operational command, see show rip neighbor in
the CLI Explorer.

Interface Alias Names Overview on page 110

alias on page 422

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Clock Source Overview

For both the router and interfaces, the clock source can be an external clock that is
received on the interface or the routers internal Stratum 3 clock.
For example, interface A can transmit on interface As received clock (external, loop
timing) or the Stratum 3 clock (internal, line timing, or normal timing). Interface A cannot
use a clock from any other source. For interfaces such as SONET/SDH that can use
different clock sources, you can configure the source of the transmit clock on each
interface.
The clock source resides on the System Control Board (SCB) for M40 routers, the System
and Switch Board (SSB) for M20 routers, the Control Board (CB) for M120 routers, and
the Miscellaneous Control Subsystem (MCS) for M40e and M160 routers. M7i and M10i
routers have a clock source on the Compact Forwarding Engine Board (CFEB) and
Enhanced Compact Forwarding Engine Board (CFEB-E).
For T Series and MX Series, the clock source internal Stratum 3 clock resides on the
SONET Clock Generator and Switch Control Board (SCB) respectively. By default, the
19.44-MHz Stratum 3 reference clock generates the clock signal for all serial PICs
(SONET/SDH) and Plesiochronous Digital Hierarchy (PDH) PICs. PDH PICs include DS3,
E3, T1, and E1 PICs.

NOTE: M7i and M10i routers do not support external clocking of SONET
interfaces.

For information about clocking on channelized interfaces, see Channelized IQ and IQE
Interfaces Properties. Also see Configuring the Clock Source on SONET/SDH Interfaces
and Configuring the Channelized T3 Loop Timing.
For information about configuring an external synchronization interface that can be used
to synchronize the internal Stratum 3 clock to an external source on the M40e, M120,
M320, routers and T Series routers, see Junos OS Administration Library for Routing Devices,
Configuring the Junos OS to Support an External Clock Synchronization Interface for M
Series and T Series Routers.
For information about configuring Synchronous Ethernet on MX 80, MX240, MX480, and
MX960 3D Universal Edge Routers, see Junos OS Administration Library for Routing Devices,
Synchronous Ethernet Overview and Configuring Clock Synchronization Interface on MX
Series Routers.
Related
Documentation

Configuring an External Synchronization Interface

Configuring the Clock Source on page 116

Configuring the Junos OS to Support an External Clock Synchronization Interface for M

Series and T Series Routers

Synchronous Ethernet Overview

Copyright 2014, Juniper Networks, Inc.

115

Interfaces Fundamentals for Routing Devices

Configuring Clock Synchronization Interface on MX Series Routers

Configuring the Clock Source

For both the router and interfaces, the clock source can be an external clock that is
received on the interface or the routers internal Stratum 3 clock.
To set the clock source as external or internal:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level:

[edit]
user@host# edit interfaces interface-name

2. Configure the clocking option as external or internal.

[edit interfaces interface-name]

user@host# set clocking (external | internal)

NOTE: M7i and M10i routers do not support external clocking of SONET
interfaces.

NOTE: On Channelized SONET/SDH PICs, if you set the parent (or the master)
controller clock to external, then you must set the child controller clocks to
the default valuethat is, internal.
For example, on the Channelized STM1 PIC, if the clock on the Channelized
STM1 interface (which is the master controller) is set to external, then you
must not configure the CE1 interface (which is the child controller) clock to
external. Instead you must configure the CE1 interface clock to internal.

For information about clocking on channelized interfaces, see Channelized IQ and IQE
Interfaces Properties. Also see Configuring the Clock Source on SONET/SDH Interfaces
and Configuring the Channelized T3 Loop Timing.
For information about configuring an external synchronization interface that can be used
to synchronize the internal Stratum 3 clock to an external source on the M40e, M120,
and M320 routers and on the T Series routers, see Junos OS Administration Library for
Routing Devices, Configuring the Junos OS to Support an External Clock Synchronization
Interface for M Series and T Series Routers.
For information about configuring Synchronous Ethernet on MX80, MX240, MX480, and
MX960 3D Universal Edge Routers, see Junos OS Administration Library for Routing Devices,
Synchronous Ethernet Overview and Configuring Clock Synchronization Interface on MX
Series Routers.
Related
Documentation

116

Configuring an External Synchronization Interface

clocking on page 469

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Clock Source Overview on page 115

Configuring the Junos OS to Support an External Clock Synchronization Interface for M

Series and T Series Routers

Synchronous Ethernet Overview

Configuring Clock Synchronization Interface on MX Series Routers

Configuring Interface Encapsulation on Physical Interfaces

Point-to-Point Protocol (PPP) encapsulation is the default encapsulation type for physical
interfaces. You need not configure encapsulation for any physical interfaces that support
PPP encapsulation. If you do not configure encapsulation, PPP is used by default. For
physical interfaces that do not support PPP encapsulation, you must configure an
encapsulation to use for packets transmitted on the interface.
You can optionally configure an encapsulation on a logical interface, which is the
encapsulation used within certain packet types. For more information about logical
interface encapsulation, see Configuring the Encapsulation on a Logical Interface on
page 173.
For information about encapsulation overhead, see Table 29 on page 96.
This section contains the following topics:

Configuring the Encapsulation on a Physical Interface on page 117

Encapsulation Capabilities on page 121

Configuring the Encapsulation on a Physical Interface

By default, PPP is the encapsulation type for physical interfaces. To configure the
encapsulation on a physical interface, include the encapsulation statement at the [edit
interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
encapsulation (atm-ccc-cell-relay | atm-pvc | cisco-hdlc | cisco-hdlc-ccc | cisco-hdlc-tcc
| ethernet-ccc | ethernet-over-atm | ethernet-tcc | ethernet-vpls |
extended-frame-relay-ccc | extended-frame-relay-ether-type-tcc |
extended-frame-relay-tcc | extended-vlan-ccc | extended-vlan-tcc | extended-vlan-vpls
| flexible-ethernet-services | flexible-frame-relay | frame-relay | frame-relay-ccc |
frame-relay-ether-type | frame-relay-ether-type-tcc | frame-relay-port-ccc |
frame-relay-tcc | multilink-frame-relay-uni-nni | ppp | ppp-ccc | ppp-tcc | vlan-ccc |
vlan-vpls);

The physical interface encapsulation can be one of the following:

ATM CCC cell relayConnects two remote virtual circuits or ATM physical interfaces
with a label-switched path (LSP). Traffic on the circuit is ATM cells.
You can configure an ATM1 Physical Interface Card (PIC) to use cell-relay accumulation
mode (CAM). In this mode, the incoming cells (1 to 8 cells) are packaged into a single

Copyright 2014, Juniper Networks, Inc.

117

Interfaces Fundamentals for Routing Devices

packet and forwarded to the LSP. Cell-relay accumulation mode is not supported on
ATM2 PICs. You configure CAM as shown in the following example:
[edit chassis]
fpc 1 {
pic 0 {
atm-cell-relay-accumulation;
}
}

For more information, see the Junos OS Administration Library for Routing Devices.

ATM PVCDefined in RFC 2684, Multiprotocol Encapsulation over ATM Adaptation

Layer 5. When you configure physical ATM interfaces with ATM PVC encapsulation, an
RFC 2684-compliant ATM Adaptation Layer 5 (AAL5) tunnel is set up to route the
ATM cells over a Multiprotocol Label Switching (MPLS) path that is typically established
between two MPLS-capable routers using the Label Distribution Protocol (LDP).

Cisco HDLCE1, E3, SONET/SDH, T1, and T3 interfaces can use Cisco HDLC
encapsulation. Two related versions are supported:

CCC version (cisco-hdlc-ccc)The logical interface does not require an encapsulation

statement. When you use this encapsulation type, you can configure the ccc family
only.

TCC version (cisco-hdlc-tcc)Similar to CCC and has the same configuration

restrictions, but used for circuits with different media on either side of the connection.

Ethernet over ATMAs defined in RFC 1483, Multiprotocol Encapsulation over ATM
Adaptation Layer 5, this encapsulation type allows ATM interfaces to connect to devices
that support only bridged-mode protocol data units (BPDUs). The Junos OS does not
completely support bridging, but accepts BPDU packets as a default gateway. If you
use the router as an edge device, then the router acts as a default gateway. It accepts
Ethernet logical link control (LLC)/SNAP frames with IP or Address Resolution Protocol
(ARP) in the payload, and drops the rest. For packets destined to the Ethernet local
area network (LAN), a route lookup is done using the destination IP address. If the
route lookup yields a full address match, the packet is encapsulated with an LLC/SNAP
and media access control (MAC) header, and the packet is forwarded to the ATM
interface.

Ethernet cross-connectEthernet interfaces without VLAN tagging can use

Ethernet CCC encapsulation. Two related versions are supported:

CCC version (ethernet-ccc)Ethernet interfaces with standard Tag Protocol ID

(TPID) tagging can use Ethernet CCC encapsulation. When you use this encapsulation
type, you can configure the ccc family only.

TCC version (ethernet-tcc)Similar to CCC, but used for circuits with different media
on either side of the connection.
For 8-port, 12-port, and 48-port Fast Ethernet PICs, TCC is not supported.

118

VLAN CCC (vlan-ccc)Ethernet interfaces with VLAN tagging enabled can use VLAN
CCC encapsulation. VLAN CCC encapsulation supports TPID 0x8100 only. When you
use this encapsulation type, you can configure the ccc family only.

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Extended VLAN cross-connectGigabit Ethernet interfaces with VLAN 802.1Q tagging

enabled can use extended VLAN cross-connect encapsulation. (Ethernet interfaces
with standard TPID tagging can use VLAN CCC encapsulation.) Two related versions
of extended VLAN cross-connect are supported:

CCC version (extended-vlan-ccc)Extended VLAN CCC encapsulation supports

TPIDs 0x8100, 0x9100, and 0x9901. When you use this encapsulation type, you can
configure the ccc family only.

TCC version (extended-vlan-tcc)Similar to CCC, but used for circuits with different
media on either side of the connection.
For 8-port, 12-port, and 48-port Fast Ethernet PICs, extended VLAN CCC is not
supported. For 4-port Gigabit Ethernet PICs, extended VLAN CCC and extended
VLAN TCC are not supported.

Ethernet VPLS (ethernet-vpls)Ethernet interfaces with VPLS enabled can use

Ethernet VPLS encapsulation. For more information about VPLS, see the Junos OS
VPNs Library for Routing Devices and the Junos OS, Release 14.2.

Ethernet VLAN VPLS (vlan-vpls)Ethernet interfaces with VLAN tagging and VPLS
enabled can use Ethernet VLAN VPLS encapsulation. For more information about
VPLS, see the Junos OS VPNs Library for Routing Devices and the Junos OS, Release
14.2.

NOTE: When vlan-vpls encapsulation is set at the physical interface level,

commit check will validate that there should not be any inet family
configured within it.

Extended VLAN VPLS (extended-vlan-vpls)Ethernet interfaces with VLAN 802.1Q

tagging and VPLS enabled can use Ethernet Extended VLAN VPLS encapsulation.
(Ethernet interfaces with standard TPID tagging can use Ethernet VLAN VPLS
encapsulation.) Extended Ethernet VLAN VPLS encapsulation supports TPIDs 0x8100,
0x9100, and 0x9901. For more information about VPLS, see the Junos OS VPNs Library
for Routing Devices and the Junos OS, Release 14.2.

Flexible Ethernet services (flexible-ethernet-services)Gigabit Ethernet and Gigabit

Ethernet IQ and IQE PICs with SFPs (except the 10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i router) can use flexible Ethernet services
encapsulation. Aggregated Ethernet bundles can use this encapsulation type. You use
this encapsulation type when you want to configure multiple per-unit Ethernet
encapsulations. This encapsulation type allows you to configure any combination of
route, TCC, CCC, Layer 2 virtual private networks (VPNs), and VPLS encapsulations
on a single physical port. If you configure flexible Ethernet services encapsulation on
the physical interface, VLAN IDs from 1 through 511 are no longer reserved for normal
VLANs.

Flexible Frame Relay (flexible-frame-relay)IQ and IQE interfaces can use flexible
Frame Relay encapsulation. You use flexible Frame Relay encapsulation when you
want to configure multiple per-unit Frame Relay encapsulations. This encapsulation
type allows you to configure any combination of TCC, CCC, and standard Frame Relay

Copyright 2014, Juniper Networks, Inc.

119

Interfaces Fundamentals for Routing Devices

encapsulations on a single physical port. Also, each logical interface can have any
data-link connection identifier (DLCI) value from 1 through 1022.

120

Frame Relay (frame-relay)Defined in RFC 1490, Multiprotocol Interconnect over Frame

Relay. E1, E3, link services, SONET/SDH, T1, T3, and voice services interfaces can use
Frame Relay encapsulation. Five related versions are supported:

CCC version (frame-relay-ccc)The same as standard Frame Relay for DLCIs

0 through 511. DLCIs 512 through 1022 are dedicated to CCC. The logical interface
must also have frame-relay-ccc encapsulation. When you use this encapsulation
type, you can configure the ccc family only.

TCC version (frame-relay-tcc)Similar to Frame Relay CCC and has the same
configuration restrictions, but used for circuits with different media on either side of
the connection.

Extended CCC version (extended-frame-relay-ccc)This encapsulation type allows

you to dedicate DLCIs 1 through 1022 to CCC. The logical interface must have
frame-relay-ccc encapsulation. When you use this encapsulation type, you can
configure the ccc family only.

Extended TCC version (extended-frame-relay-tcc)Similar to extended Frame Relay

CCC, this encapsulation type allows you to dedicate DLCIs 1 through 1022 to TCC,
which is used for circuits with different media on either side of the connection.

Port CCC version (frame-relay-port-ccc)Defined in the IETF document Frame Relay

Encapsulation over Pseudo-Wires (expired December 2002). This encapsulation type
allows you to transparently carry all the DLCIs between two customer edge (CE)
routers without explicitly configuring each DLCI on the two provider edge (PE) routers
with Frame Relay transport. The connection between the two CE routers can be
either user-to-network interface (UNI) or network-to-network interface (NNI); this
is completely transparent to the PE routers. The logical interface does not require
an encapsulation statement. When you use this encapsulation type, you can configure
the ccc family only.

Frame Relay Ether Type (frame-relay-ether-type)Physical interfaces can use Frame

Relay ether type encapsulation for compatibility with Cisco Frame Relay. IETF frame
relay encapsulation identifies the payload format using NLPID and SNAP formats.
Cisco-compatible Frame Relay encapsulation uses the Ethernet type to identify the
type of payload. Two related versions are supported:

TCC version (frame-relay-ether-type-tcc)Cisco-compatible Frame Relay for DLCIs

0 through 511. DLCIs 512 through 1022 are dedicated to TCC. This encapsulation is
used for circuits with different media on either side of the connection.

Extended TCC version (extended-frame-relay-ether-type-tcc)This encapsulation

allows you to dedicate Cisco-compatible Frame Relay TCC for DLCIs 1 through 1022.
This encapsulation is used for circuits with different media on either side of the
connection.

Multilink Frame Relay (MLFR) UNI and NNI (multilink-frame-relay-uni-nni)Link services

and voice services interfaces functioning as FRF.16 bundles can use multilink Frame

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Relay UNI NNI encapsulation. This encapsulation is also used on link services and voice
services interfaces constituent T1, E1, or NxDS0 interfaces.

PPPDefined in RFC 1661, The Point-to-Point Protocol (PPP) for the Transmission of
Multiprotocol Datagrams over Point-to-Point Links. PPP is the default encapsulation
type for physical interfaces. E1, E3, SONET/SDH, T1, and T3 interfaces can use PPP
encapsulation. Two related versions are supported:

Circuit cross-connect (CCC) version (ppp-ccc)The logical interface does not require
an encapsulation statement. When you use this encapsulation type, you can configure
the ccc family only.

Translational cross-connect (TCC) version (ppp-tcc)Similar to CCC and has the

same configuration restrictions, but used for circuits with different media on either
side of the connection.

NOTE: When the encapsulation type is set to Cisco-compatible Frame Relay

encapsulation, ensure that the LMI type is set to ANSI or Q933-A.

Encapsulation Capabilities
When you configure a point-to-point encapsulation (such as PPP or Cisco HDLC) on a
physical interface, the physical interface can have only one logical interface (that is, only
one unit statement) associated with it. When you configure a multipoint encapsulation
(such as Frame Relay), the physical interface can have multiple logical units, and the
units can be either point-to-point or multipoint.
Ethernet CCC encapsulation for Ethernet interfaces with standard TPID tagging requires
that the physical interface have only a single logical interface. Ethernet interfaces in VLAN
mode can have multiple logical interfaces.
For Ethernet interfaces in VLAN mode, VLAN IDs are applicable as follows:

VLAN ID 0 is reserved for tagging the priority of frames.

For encapsulation type vlan-ccc, VLAN IDs 1 through 511 are reserved for normal VLANs.
VLAN IDs 512 and above are reserved for VLAN CCCs.

For encapsulation type vlan-vpls, VLAN IDs 1 through 511 are reserved for normal VLANs,
and VLAN IDs 512 through 4094 are reserved for VPLS VLANs. For 4-port Fast Ethernet
interfaces, you can use VLAN IDs 512 through 1024 for VPLS VLANs.

For Gigabit Ethernet interfaces and Gigabit Ethernet IQ and IQE PICs with SFPs (except
the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router),
you can configure flexible Ethernet services encapsulation on the physical interface.
For interfaces with flexible-ethernet-services encapsulation, all VLAN IDs are valid.
VLAN IDs from 1 through 511 are not reserved.

For encapsulation types extended-vlan-ccc and extended-vlan-vpls, all VLAN IDs are
valid.

The upper limits for configurable VLAN IDs vary by interface type.

Copyright 2014, Juniper Networks, Inc.

121

Interfaces Fundamentals for Routing Devices

When you configure a TCC encapsulation, some modifications are needed to handle
VPN connections over unlike Layer 2 and Layer 2.5 links and terminate the Layer 2 and
Layer 2.5 protocol locally.
The router performs the following media-specific changes:

PPP TCCBoth Link Control Protocol (LCP) and Network Control Protocol (NCP) are
terminated on the router. Internet Protocol Control Protocol (IPCP) IP address
negotiation is not supported. The Junos OS strips all PPP encapsulation data from
incoming frames before forwarding them. For output, the next hop is changed to PPP
encapsulation.

Cisco HDLC TCCKeepalive processing is terminated on the router. The Junos OS

strips all Cisco HDLC encapsulation data from incoming frames before forwarding
them. For output, the next hop is changed to Cisco HDLC encapsulation.

Frame Relay TCCAll Local Management Interface (LMI) processing is terminated on

the router. The Junos OS strips all Frame Relay encapsulation data from incoming
frames before forwarding them. For output, the next hop is changed to Frame Relay
encapsulation.

ATMOperation, Administration, and Maintenance (OAM) and Interim Local

Management Interface (ILMI) processing is terminated at the router. Cell relay is not
supported. The Junos OS strips all ATM encapsulation data from incoming frames
before forwarding them. For output, the next hop is changed to ATM encapsulation.

Example: Configuring the Encapsulation on a Physical Interface

Configure PPP encapsulation on a SONET/SDH interface. The second and third family
statements allow Intermediate System-to-Intermediate System (IS-IS) and MPLS to
run on the interface.
[edit interfaces]
so-7/0/0 {
encapsulation ppp;
unit 0 {
point-to-point;
family inet {
address 192.168.1.113/32 {
destination 192.168.1.114;
}
}
family iso;
family mpls;
}
}

Related
Documentation

122

Configuring the Encapsulation on a Logical Interface on page 173

Configuring the Media MTU on page 93

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Configuring Interface Encapsulation on PTX Series Packet Transport Routers

This topic describes how to configure interface encapsulation on PTX Series Packet
Transport Routers. Use the flexible-ethernet-services configuration statement to configure
different encapsulation for different logical interfaces under a physical interface. With
flexible Ethernet services encapsulation, you can configure each logical interface
encapsulation without range restrictions for VLAN IDs.
Supported encapsulations for physical interfaces include:

flexible-ethernet-services

ethernet-ccc

ethernet-tcc

Supported encapsulations for logical interfaces include:

ethernet

vlan-ccc

vlan-tcc

NOTE: PTX Series Packet Transport Routers do not support extended-vlan-cc

and extended-vlan-tcc encapsulation on logical interfaces. Instead, you can
configure a tag protocol ID (TPID) value of 0x9100 to achieve the same
results.

To configure flexible Ethernet services encapsulation, include the encapsulation

flexible-ethernet-services statement at the [edit interfaces et-fpc/pic/port ] hierarchy
level. For example:
interfaces {
et-fpc/pic/port {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
vlan-id 1000;
family inet {
address 11.0.0.20/24;
}
}
unit 1 {
encapsulation vlan-ccc;
vlan-id 1010;
}
unit 2 {
encapsulation vlan-tcc;
vlan-id 1020;
family tcc {
proxy {

Copyright 2014, Juniper Networks, Inc.

123

Interfaces Fundamentals for Routing Devices

inet-address 11.0.2.160;
}
remote {
inet-address 11.0.2.10;
}
}
}
}
}

Related
Documentation

Configuring Interface Encapsulation on Physical Interfaces on page 117

Configuring Keepalives
By default, physical interfaces configured with Cisco HDLC or PPP encapsulation send
keepalive packets at 10-second intervals. The Frame Relay term for keepalives is LMI
packets; the Junos OS supports both ANSI T1.617 Annex D LMIs and ITU Q933 Annex A
LMIs. On ATM networks, OAM cells perform the same function. You configure OAM cells
at the logical interface level; for more information, see Defining the ATM OAM F5 Loopback
Cell Period.
To disable the sending of keepalives:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level.

[edit ]
user@host# edit interfaces interface-name

2. Include the no-keepalives statement at the [edit interfaces interface-name] hierarchy

level.
[edit interfaces interface-name]
no-keepalives;

To disable the sending of keepalives on a physical interface configured with Cisco HDLC
encapsulation for a translational cross-connection:
1.

In configuration mode, go to the [edit interfacesinterface-name] hierarchy level.

[edit ]
user@host# edit interfaces interface-name

2. Include the no-keepalives statement with the encapsulation cisco-hdlc-tcc statement

at the [edit interfaces interface-name] hierarchy level.

[edit interfaces interface-name]
encapsulation cisco-hdlc-tcc;
no-keepalives;

To disable the sending of keepalives on a physical interface configured with PPP

encapsulation for a translational cross-connection:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level.

[edit ]
user@host# edit interfaces interface-name

124

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

2. Include the no-keepalives statement with the encapsulation ppp-tcc statement at the

[edit interfaces interface-name] hierarchy level.

[edit interfaces interface-name]
encapsulation ppp-tcc;
no-keepalives;

For more information about translation cross-connections, see Circuit and Translational
Cross-Connects Overview.
When you configure PPP over ATM or Multilink PPP over ATM encapsulation, you can
enable or disable keepalives on the logical interface. For more information, see Configuring
PPP over ATM2 Encapsulation.
To explicitly enable the sending of keepalives:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level.

[edit ]
user@host# edit interfaces interface-name

2. Include the keepalives statement at the [edit interfaces interface-name] hierarchy

level.
[edit interfacesinterface-name]
keepalives;

To change one or more of the default keepalive values:

1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level.

[edit ]
user@host# edit interfaces interface-name

2. Include the keepalives statement with the appropriate option as intervalseconds,

down-countnumber, and the up-countnumber..

[edit interfaces interface-name]
keepalives;
keepalives <interval seconds> <down-count number> <up-count number>;

On interfaces configured with Cisco HDLC or PPP encapsulation, you can include the
following three keepalive statements; note that Frame Relay encapsulation is not affected
by these statements:

interval secondsThe time in seconds between successive keepalive requests. The

range is from 1 second through 32767 seconds, with a default of 10 seconds.

down-count numberThe number of keepalive packets a destination must fail to receive

before the network takes a link down. The range is from 1 through 255, with a default
of 3.

up-count numberThe number of keepalive packets a destination must receive to

change a links status from down to up. The range is from 1 through 255, with a default
of 1.

Copyright 2014, Juniper Networks, Inc.

125

Interfaces Fundamentals for Routing Devices

CAUTION: If interface keepalives are configured on an interface that does

not support the keepalives configuration statement (for example, 10-Gigabit
Ethernet), the link layer may go down when the PIC is restarted. Avoid
configuring the keepalives on interfaces that do not support the keepalives
configuration statement.

For information about Frame Relay keepalive settings, see Configuring Frame Relay
Keepalives.
On MX Series routers with Modular Port Concentrators/Modular Interface Cards
(MPCs/MICs), the Packet Forwarding Engine on an MPC/MIC processes and responds
to Link Control Protocol (LCP) Echo-Request keepalive packets that the PPP subscriber
(client) initiates and sends to the router. The mechanism by which LCP Echo-Request
packets are processed by the Packet Forwarding Engine instead of by the Routing Engine
is referred to as PPP fast keepalive For more information about how PPP fast keepalive
works on an MX Series router with MPCs/MICs, see the Junos OS Subscriber Access
Configuration Guide.
Related
Documentation

Defining the ATM OAM F5 Loopback Cell Period

Disabling the Sending of PPPoE Keepalive Messages

Understanding How the Router Processes Subscriber-Initiated PPP Fast Keepalive

Requests

keepalives on page 652

no-keepalives on page 744

Configuring Frame Relay Keepalives

Circuit and Translational Cross-Connects Overview on page 255

Configuring PPP over ATM2 Encapsulation

Configuring the PPP Challenge Handshake Authentication Protocol

For interfaces with PPP encapsulation, you can configure interfaces to support the PPP
Challenge Handshake Authentication Protocol (CHAP), as defined in RFC 1994,
PPP Challenge Handshake Authentication Protocol (CHAP). When you enable CHAP on
an interface, the interface can authenticate its peer and can be authenticated by its peer.
By default, PPP CHAP is disabled. If CHAP is not explicitly enabled, the interface makes
no CHAP challenges and denies all incoming CHAP challenges. To enable CHAP, you
must create an access profile, and you must configure the interfaces to use CHAP.
To configure a CHAP access profile, include the profile statement and specify a profile
name at the [edit access] hierarchy level:
[edit access]
profile profile-name {
client name chap-secret data;

126

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

For more information about configuring access profiles, see the Junos OS Administration
Library for Routing Devices.
When you configure an interface to use CHAP, you must assign an access profile to the
interface. When an interface receives CHAP challenges and responses, the access profile
in the packet is used to look up the shared secret, as defined in RFC 1994.
If no matching access profile is found for the CHAP challenge that was received by the
interface, the optionally configured default CHAP secret is used. The default CHAP secret
is useful if the CHAP name of the peer is unknown, or if the CHAP name changes during
PPP link negotiation.
To configure PPP CHAP on an interface with PPP encapsulation, include the chap
statement at the [edit interfaces interface-name ppp-options] hierarchy level:
[edit interfaces interface-name ppp-options]
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}

On each interface with PPP encapsulation, you can configure the following PPP CHAP
properties:

Assigning an Access Profile to an Interface on page 127

Configuring a Default CHAP Secret on page 128

Configuring the Local Name on page 128

Configuring Passive Mode on page 128

Example: Configuring the PPP Challenge Handshake Authentication Protocol on page 128

When you configure PPP over ATM or Multilink PPP over ATM encapsulation, you can
enable CHAP on the logical interface. For more information, see Configuring PPP over
ATM2 Encapsulation.

Assigning an Access Profile to an Interface

To assign an access profile to an interface, include the access-profile statement at the
[edit interfaces interface-name ppp-options chap] hierarchy level:
[edit interfaces interface-name ppp-options chap]
access-profile name;

You must include the access-profile statement when you configure the CHAP
authentication method. If an interface receives a CHAP challenge or response from a
peer that is not in the applied access profile, the link is immediately dropped unless a
default CHAP secret has been configured. For information about configuring the default
CHAP secret, see Configuring a Default CHAP Secret on page 128.

Copyright 2014, Juniper Networks, Inc.

127

Interfaces Fundamentals for Routing Devices

Configuring a Default CHAP Secret

To configure a default CHAP secret for an interface, include the default-chap-secret
statement at the [edit interfaces interface-name ppp-options chap] hierarchy level:
[edit interfaces interface-name ppp-options chap]
default-chap-secret name;

The default CHAP secret is used when no matching CHAP access profile exists, or if the
CHAP name changes during PPP link negotiation.

Configuring the Local Name

By default, when CHAP is enabled on an interface, the interface uses the routers system
hostname as the name sent in CHAP challenge and response packets.
To configure the name the interface uses in CHAP challenge and response packets,
include the local-name statement at the [edit interfaces interface-name ppp-options
chap] hierarchy level:
[edit interfaces interface-name ppp-options chap]
local-name name;

The local name is any string from 1 to 250 characters in length, starting with an
alphanumeric or underscore character, and including only the following characters:
a-z A-Z 0-9 % @ # / \ . _ -

Configuring Passive Mode

By default, when CHAP is enabled on an interface, the interface always challenges its
peer and responds to challenges from its peer.
You can configure the interface not to challenge its peer, and only respond when
challenged. To configure the interface not to challenge its peer, include the passive
statement at the [edit interfaces interface-name ppp-options chap] hierarchy level:
[edit interfaces interface-name ppp-options chap]
passive;

Example: Configuring the PPP Challenge Handshake Authentication Protocol

Configure CHAP:
[edit access]
profile pe-A-ppp-clients;
client cpe-1 chap-secret "$1$dQYsZ$B5ojUeUjDsUo.yKwcCZ0";
# SECRET-DATA
client cpe-2 chap-secret "$1$kdAsfaDAfkdjDsASxfafdKdFKJ";
# SECRET-DATA
[edit interfaces so-1/2/0]
encapsulation ppp;
ppp-options {
chap {
access-profile pe-A-ppp-clients;

128

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

default-chap-secret "$9$mPafafhdsaiufhyrv1Rxd";
local-name "pe-A-so-1/1/1";
}
}
[edit interfaces so-1/1/2]
encapsulation ppp;
ppp-options {
chap {
access-profile pe-A-ppp-clients;
default-chap-secret "$9$mPafafhdsaiufhyrv1Rxd";
local-name pe-A-so-1/1/2";
}
}

Configuring the PPP Password Authentication Protocol

For interfaces with PPP encapsulation, you can configure interfaces to support the
Password Authentication Protocol (PAP), as defined in RFC 1334, PAP Authentication
Protocols. If authentication is configured, the PPP link negotiates using CHAP or PAP
protocol for authentication during the Link Control Protocol (LCP) negotiation phase.
PAP is only performed after the link establishment phase (LCP up) portion of the
authentication phase.
During authentication, the PPP link sends a PAP authentication-request packet to the
peer with an ID and password. The authentication-request packet is sent every 2 seconds,
similar to the CHAP challenge, until a response is received (acknowledgment packet,
nonacknowledgment packet). If an acknowledgment packet is received, the PPP link
transitions to the next state, the network phase. If a nonacknowledgment packet is
received, an LCP terminate request is sent, and the PPP link goes back to the link
establishment phase. If no response is received, and an optional retry counter is set to
true, a new request acknowledgment packet is resent. If the retry counter expires, the
PPP link transitions to the LCP negotiate phrase.
You can configure the PPP link with PAP in passive mode. By default, when PAP is enabled
on an interface, the interface expects authenticate-request packets from the peer.
However, the interface can be configured to send authentication request packets to the
peer by configuring PAP to operate in passive mode. In PAP passive mode, the interface
sends the authenticate-request packets to the peer only if the interface receives the PAP
option from the peer during LCP negotiationin passive mode, the interface does not
authenticate the peer.
When both CHAP and PAP authentication are configured on a PPP interface, only CHAP
protocol is used for authentication. If CHAP authentication fails, LCP is restarted and the
PPP link uses the CHAP protocol again for authentication. Therefore, each time CHAP
authentication fails, LCP is restarted.
To enable PAP, you must create an access profile, and you must configure the interfaces
to use PAP.
To configure a PAP access profile, include the profile statement and specify a profile
name at the [edit access] hierarchy level:

Copyright 2014, Juniper Networks, Inc.

129

Interfaces Fundamentals for Routing Devices

[edit access]
profile profile-name {
client name;
pap-password password;
}

For more information about configuring access profiles, see the Junos OS Administration
Library for Routing Devices.
When you configure an interface to use PAP, you must assign an access profile to the
interface. When an interface receives PAP authentication requests, the access profile in
the packet is used to look up the password.
If no matching access profile is found for the PAP authentication request that was received
by the interface, the optionally configured default PAP password is used. For information
about configuring the default PAP password, see Configuring PPP PAP Authentication
on page 178.
To configure PPP PAP on a physical interface with PPP encapsulation, include the pap
statement at the [edit interfaces interface-name ppp-options] hierarchy level:
[edit interfaces interface-name ppp-options]
pap {
access-profile name;
local-name name;
local-password password;
passive;
}

To configure PPP PAP on a logical interface with PPP encapsulation, include the pap
statement with options:
pap {
default-pap-password password;
local-name name;
local-password password;
passive;
}

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

For more information about configuring PAP for logical interfaces, see Configuring PPP
PAP Authentication on page 178. For information about configuring tracing operations
for PPP, see Tracing Operations of the pppd Process on page 137.
On each physical interface with PPP encapsulation, you can perform one of the following
tasks:

130

Configuring the Local Name on page 131

Configuring the Local Password on page 131

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Configuring Passive Mode on page 131

Example: Configuring PAP Authentication Protocol on page 131

Configuring the Local Name

By default, when PAP is enabled on an interface, the interface uses the routers system
hostname as the name sent in PAP request and response packets.
To configure the name the interface uses in PAP request and response packets, include
the local-name statement at the [edit interfaces interface-name ppp-options pap] hierarchy
level:
[edit interfaces interface-name ppp-options pap]
local-name name;

Configuring the Local Password

You need to configure the password to be used for authentication. To configure the host
password for sending PAP requests, include the local-password statement at the [edit
interfaces interface-name ppp-options pap] hierarchy level:
[edit interfaces interface-name ppp-options pap]
local-password password;

Configuring Passive Mode

By default, when PAP is enabled on an interface, the interface expects
authenticate-request packets from the peer. However, the interface can be configured
to send authentication request packets to the peer by configuring PAP to operate in
passive mode. In PAP passive mode, the interface sends the authenticate-request packets
to the peer only if the interface receives the PAP option from the peer during LCP
negotiationin passive mode, the interface does not authenticate the peer.
To configure the interface to authenticate with PAP in passive mode, include the passive
statement at the [edit interfaces interface-name ppp-options pap] hierarchy level:
[edit interfaces interface-name ppp-options pap]
passive;

Example: Configuring PAP Authentication Protocol

Configure a PAP access profile, the physical and logical interfaces, and tracing operations
for PPP.
For PAP authentication, a username and password for the peer is configured in the access
profile, along with a PAP password. Each user can have either a PAP password or a CHAP
secret.
[edit access]
profile userlist1;
client {
papuser {
pap-password "#%@^***"; # SECRET-DATA;
}

Copyright 2014, Juniper Networks, Inc.

131

Interfaces Fundamentals for Routing Devices

chapuser {
chap-secret "#%@^***"; # SECRET-DATA;
}
}

To configure the same name for the PAP password and the CHAP secret, configure the
client with two different access profiles:
[edit access]
profile chap-profile;
client {
sjcrouter {
chap-secret "#%@^***"; # SECRET-DATA;
}
boston {
chap-secret "#%@^***"; # SECRET-DATA;
}
}
profile pap-profile;
client {
sjcrouter {
pap-password "#%@^***"; # SECRET-DATA;
}
boston {
pap-password "#%@^***"; # SECRET-DATA;
}
}

Configure the physical interface, including the access profile name to be used for PPP
authentication:
[edit interfaces so-0/0/0]
ppp-options {
pap {
access-profile pap-profile;
local-name "rtrnum1";
local-password "XXXXXXX"; #SECRET-DATA
passive;
}
}

Configure the logical interface, including the default PAP password to be used, should
the access profile not be located during authentication:
[edit interfaces so-0/0/0]
encapsulation frame-relay;
unit 0 {
dlci 100;
encapsulation frame-relay-ppp;
ppp-options {
pap {
local-name "rtrnum1";
local-password "XXXXXXX"; #SECRET-DATA
default-pap-password "XXXXX"; #SECRET-DATA
passive;
}
}

132

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Include the pap statement to trace PPP protocol operations:

[edit protocols]
ppp {
traceoptions {
flag {
pap;
}
}
}

Configuring PPP Address and Control Field Compression

For interfaces with PPP, PPP CCC, or PPP TCC encapsulation, you can configure
compression of the Data Link Layer address and control fields, as defined in RFC 1661,
The Point-to-Point Protocol (PPP). By default, the address and control fields are not
compressed. This means PPP-encapsulated packets are transmitted with two 1-byte
fields (0xff and 0x03). If you configure address and control field compression (ACFC)
and ACFC is successfully negotiated with the local router's peer, the local router transmits
packets without these 2 bytes. ACFC allows you to conserve bandwidth by transmitting
less data.
On M320, M120, and T Series routers, ACFC is not supported for any ISO family protocols.
Do not include the acfc statement at the [edit interfaces interface-name ppp-options
compression] hierarchy level when you include the family iso statement at the [edit
interfaces interface-name unit logical-unit-number] hierarchy level.

NOTE: The address and control fields cannot be compressed in Link Control
Protocol (LCP) packets.
The PPP session restarts when you configure or modify compression options.

To configure ACFC:
1.

In configuration mode, go to the [edit interfaces interface-name ppp-options] hierarchy

level.
[edit ]
user@host# edit interfaces interface-name ppp-options

2. Include the compression statement at the [edit interfaces interface-name ppp-options]

hierarchy level, and specify acfc.

[edit interfaces interface-name ppp-options]
compression acfc;

To monitor the configuration, issue the show interfaces interface-name command.

Configured options are displayed in the link flags field for the physical interface.
Successfully negotiated options are displayed in the flags field for the logical interface.

Copyright 2014, Juniper Networks, Inc.

133

Interfaces Fundamentals for Routing Devices

In this example, both ACFC and PFC are configured, but neither compression feature has
been successfully negotiated.
user@router# run show interfaces so-0/1/1
Physical interface: so-0/1/1, Enabled, Physical link is Up
Interface index: 133, SNMP ifIndex: 27
Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC3,
Loopback: None, FCS: 16
Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps 16384
Link flags
: No-Keepalives ACFC PFC
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Not-configured
CoS queues
: 4 supported
Last flapped
: 2004-12-29 10:49:32 PST (00:18:35 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SONET alarms
: None
SONET defects : None
Logical interface so-0/1/1.0 (Index 68) (SNMP ifIndex 169)
Flags: Point-To-Point SNMP-Traps ACFC Encapsulation: PPP
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 3.3.3/24, Local: 3.3.3.2, Broadcast: 3.3.3.255

This configuration causes the local router to try to negotiate ACFC with its peer. If ACFC
is successfully negotiated, the local router sends packets with compressed address and
control fields. When you include the compression acfc statement in the configuration,
the PPP session restarts, and the local router sends the ACFC option in the LCP
Configure-Request packet. The ACFC option informs the local router's peer that the local
router can receive packets with compression. If the peer indicates that it, too, can receive
packets with compression, then ACFC is negotiated. If ACFC is successfully negotiated,
the local router can receive packets with or without the address and control bytes included.
Related
Documentation

ppp-options on page 812

compression on page 475
acfc on page 404

134

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Configuring the PPP Protocol Field Compression

For interfaces with PPP, PPP CCC, or PPP TCC encapsulation, you can configure protocol
field compression. By default, the protocol field is not compressed. This means
PPP-encapsulated packets are transmitted with a two-byte protocol field. For example,
IPv4 packets are transmitted with the protocol field set to 0x0021, and MPLS packets
are transmitted with the protocol field set to 0x0281.
For all protocols with identifiers in the range 0x0000 through 0x00ff, you can configure
the router to compress the protocol field to one byte, as defined in RFC 1661, The
Point-to-Point Protocol (PPP). Protocol field compression (PFC) allows you to conserve
bandwidth by transmitting less data.

NOTE: The protocol field cannot be compressed in Link Control Protocol

(LCP) packets.
The PPP session restarts when you configure or modify compression options.

To configure PFC:
1.

In configuration mode, go to the [edit interfaces interface-name ppp-options] hierarchy

level.
[edit ]
user@host# edit interfaces interface-name ppp-options

2. Include the compression statement at the [edit interfaces interface-name ppp-options]

hierarchy level, and specify pfc.

[edit interfaces interface-name ppp-options]
compression pfc;

To monitor the configuration, issue the show interfaces interface-name command.

Configured options are displayed in the link flags field for the physical interface.
Successfully negotiated options are displayed in the flags field for the logical interface.
In this example, both ACFC and PFC are configured, but neither compression feature has
been successfully negotiated.
user@router# run show interfaces so-0/1/1
Physical interface: so-0/1/1, Enabled, Physical link is Up
Interface index: 133, SNMP ifIndex: 27
Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC3,
Loopback: None, FCS: 16,
Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps 16384
Link flags
: No-Keepalives ACFC PFC
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Not-configured
CoS queues
: 4 supported
Last flapped
: 2004-12-29 10:49:32 PST (00:18:35 ago)

Copyright 2014, Juniper Networks, Inc.

135

Interfaces Fundamentals for Routing Devices

Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SONET alarms
: None
SONET defects : None
Logical interface so-0/1/1.0 (Index 68) (SNMP ifIndex 169)
Flags: Point-To-Point SNMP-Traps ACFC Encapsulation: PPP
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 3.3.3/24, Local: 3.3.3.2, Broadcast: 3.3.3.255

This configuration causes the local router to try to negotiate PFC with its peer. If PFC is
successfully negotiated, the local router sends packets with compressed protocol fields.
When you include the compression pfc statement in the configuration, the PPP session
restarts, and the local router sends the PFC option in the LCP Configure-Request packet.
The PFC option informs the local router's peer that the local router can receive packets
with compression. If the peer indicates that it, too, can receive packets with compression,
then PFC is negotiated. If PFC is successfully negotiated, the local router can receive
packets with either 2-byte (uncompressed) or 1-byte (compressed) protocol fields.
Related
Documentation

ppp-options on page 812

compression on page 475
pfc on page 792

Monitoring a PPP Session

You can monitor PPP packet exchanges. When monitoring is enabled, packets exchanged
during a session are logged by default to /var/log/pppd, or to the file specified in the
traceoptions statement.
To monitor a PPP session:
1.

In configuration mode, go to the [edit protocols ppp] hierarchy level.

[edit ]
user@host# edit protocols ppp

2. Include the monitor-session statement.

[edit protocols ppp]

user@host# monitor-session (interface-name | all);

When monitoring is configured, the operational mode commands show ppp summary
and show ppp interface display a Monitored flag in the Session flags column or line.
Related
Documentation

136

monitor-session on page 712

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Tracing Operations of the pppd Process

You can trace the operations of the routers pppd process.
To trace the routers pppd process:
In configuration mode, go to the [edit protocols ppp] hierarchy level.

1.

[edit ]
user@host# edit protocols ppp
2. Include the traceoptions statement.

[edit protocols ppp]

traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
flag flag;
level severity-level;
no-remote-trace;
}

To specify more than one tracing operation, include multiple flag statements.
You can specify the following flags in the traceoptions statement:

accessTrace access code

address-poolTrace address pool code

allTrace all areas of code

authTrace authentication code

chapTrace challenge handshake authentication protocol code

ciTrace CI code

configTrace configuration code

ifdbTrace interface database code

lcpTrace LCP state machine code

memoryTrace memory management code

messageTrace message processing code

mlpppTrace multilink point-to-point protocol code

ncpTrace NCP state machine code

papTrace password authentication protocol code

pppTrace PPP protocol processing code

radiusTrace RADIUS processing code

redundancyTrace redundancy code

rtsockTrace routing socket code

Copyright 2014, Juniper Networks, Inc.

137

Interfaces Fundamentals for Routing Devices

Related
Documentation

sessionTrace session management code

signalTrace signal handling code

timerTrace timer code

uiTrace user interface code

traceoptions on page 928

Configuring the Router as a DCE with Frame Relay Encapsulation

By default, when you configure an interface with Frame Relay encapsulation, the routing
platform is assumed to be data terminal equipment (DTE). That is, the routing platform
is assumed to be at a terminal point on the network.
When you configure the router to be a data circuit-terminating equipment (DCE),
keepalives are disabled by default.
To configure the router to be DCE:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level:

[edit]
user@host# edit interfaces interface-name

2. Configure the dce option to respond to Frame Relay status enquiry messages.

[edit interfaces interface-name]

user@host# set dce

Perform one of the following tasks for back-to-back Frame Relay connections:

Related
Documentation

Disable sending of keepalives on both sides of the connection.

Configure one side of the connection as a DTE (the default Junos configuration) by
removing the dce statement from the configuration and the other as a DCE.

dce on page 496

Receive and Transmit Leaky Bucket Properties Overview

Congestion control is particularly difficult in high-speed networks with high volumes of
traffic. When congestion occurs in such a network, it is usually too late to react. You can
avoid congestion by regulating the flow of packets into your network. Smoother flows
prevent bursts of packets from arriving at (or being transmitted from) the same interface
and causing congestion.
For all interface types except ATM, Fast Ethernet, Gigabit Ethernet, and channelized IQ
and IQE, you can configure leaky bucket properties, which allow you to limit the amount
of traffic received on and transmitted by a particular interface. You effectively specify
what percentage of the interfaces total capacity can be used to receive or transmit

138

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

packets. You might want to set leaky bucket properties to limit the traffic flow from a
link that is known to transmit high volumes of traffic.

NOTE: Instead of configuring leaky bucket properties, you can limit traffic
flow by configuring policers. Policers work on all interfaces. For more
information, see the Routing Policies, Firewall Filters, and Traffic Policers
Feature Guide for Routing Devices.

The leaky bucket is used at the host-network interface to allow packets into the network
at a constant rate. Packets might be generated in a bursty manner, but after they pass
through the leaky bucket, they enter the network evenly spaced. In some cases, you might
want to allow short bursts of packets to enter the network without smoothing them out.
By controlling the number of packets that can accumulate in the bucket, the threshold
property controls burstiness. The maximum number of packets entering the network int
time units is threshold + rate * t.
By default, leaky buckets are disabled and the interface can receive and transmit packets
at the maximum line rate.
For each DS3 channel on a channelized OC12 interface, you can configure unique receive
and transmit buckets.

NOTE: HDLC payload scrambling conflicts with traffic shaping configured

using leaky bucket properties. If you configure leaky bucket properties, you
must disable payload scrambling, because the Junos OS rejects configurations
that have both features enabled. For more information, see Configuring
SONET/SDH HDLC Payload Scrambling for Link Stability.

Related
Documentation

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

SONET/SDH Interfaces Overview

receive-bucket on page 838

transmit-bucket on page 935

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion
You can configure leaky bucket properties which allow you to limit the amount of traffic
received on and transmitted by a particular interface. You can specify what percentage
of the interfaces total capacity can be used to receive or transmit packets. You might
want to set leaky bucket properties to limit the traffic flow from a link that is known to
transmit high volumes of traffic.

Copyright 2014, Juniper Networks, Inc.

139

Interfaces Fundamentals for Routing Devices

To configure leaky bucket properties:

1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level.

[edit]
user@host# edit interfaces interface-name

2. Configure the receive-bucket statement.

[edit interfaces interface-name]

user@host# set receive-bucket
3. Configure the overflow option, the threshold option, and the rate option for the receive

leaky bucket, which specifies what percentage of the interfaces total capacity can
be used to receive packets.
[edit interfaces interface-name receive-bucket]
user@host# set overflow (discard | tag)
user@host# set threshold bytes
user@host# set rate percentage
4. Configure the transmit-bucket statement.

[edit interfaces interface-name]

user@host# set transmit-bucket
5. Configure the overflow option, the threshold option, and the rate option for the transmit

leaky bucket, which specifies what percentage of the interfaces total capacity can
be used to transmit packets.
[edit interfaces interface-name transmit-bucket]
user@host# set overflow (discard | tag)
user@host# set threshold bytes
user@host# set rate percentage

Related
Documentation

140

Receive and Transmit Leaky Bucket Properties Overview on page 138

SONET/SDH Interfaces Overview

receive-bucket on page 838

transmit-bucket on page 935

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Understanding Unidirectional Traffic Flow on Physical Interfaces

By default, physical interfaces are bidirectional; that is, they both transmit and receive
traffic. You can configure unidirectional link mode on a 10-Gigabit Ethernet interface that
creates two new physical interfaces that are unidirectional. The new transmit-only and
receive-only interfaces operate independently, but both are subordinate to the original
parent interface.
The unidirectional interfaces enable the configuration of a unidirectional link topology.
Unidirectional links are useful for applications such as broadband video services where
almost all traffic flow is in one direction, from the provider to the user. Unidirectional link
mode conserves bandwidth by enabling it to be differentially dedicated to transmit and
receive interfaces. In addition, unidirectional link mode conserves ports for such
applications because the transmit-only and receive-only interfaces act independently.
Each can be connected to different routers, for example, reducing the total number of
ports required.

NOTE: Unidirectional link mode is currently supported on only the following

hardware:

4port 10Gigabit Ethernet DPC on the MX960 router

10Gigabit Ethernet IQ2 PIC and 10Gigabit Ethernet IQ2E PIC on the T
Series router

The transmit-only interface is always operationally up. The operational status of the
receive-only interface depends only on local faults; it is independent of remote faults
and of the status of the transmit-only interface.
On the parent interface, you can configure attributes common to both interfaces, such
as clocking, framing, gigether-options, and sonet-options. On each of the unidirectional
interfaces, you can configure encapsulation, MAC address, MTU size, and logical interfaces.
Unidirectional interfaces support IP and IPv6. Packet forwarding takes place by means
of static routes and static ARP entries. which you can configure independently on both
unidirectional interfaces.
Only transmit statistics are reported on the transmit-only interface (and shown as zero
on the receive-only interface). Only receive statistics are reported on the receive-only
interface (and shown as zero on the transmit-only interface). Both transmit and receive
statistics are reported on the parent interface.
Related
Documentation

unidirectional on page 944

Enabling Unidirectional Traffic Flow on Physical Interfaces on page 142

Copyright 2014, Juniper Networks, Inc.

141

Interfaces Fundamentals for Routing Devices

Enabling Unidirectional Traffic Flow on Physical Interfaces

By default, physical interfaces are bidirectional; that is, they both transmit and receive
traffic. You can configure unidirectional link mode on a 10-Gigabit Ethernet interface that
creates two new physical interfaces that are unidirectional. The new transmit-only and
receive-only interfaces operate independently, but both are subordinate to the original
parent interface.
To enable unidirectional link mode on a physical interface, perform the following steps:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level:

[edit]
user@host# edit interfaces interface-name

2. Configure the unidirectional option to create two new, unidirectional (transmit-only

and receive-only) physical interfaces subordinate to the original parent interface.

[edit interfaces interface-name]
user@host# set unidirectional

NOTE: Unidirectional link mode is currently supported on only the following

hardware:

Related
Documentation

142

4port 10Gigabit Ethernet DPC on the MX960 router

10Gigabit Ethernet IQ2 PIC and 10Gigabit Ethernet IQ2E PIC on the T
Series router

unidirectional on page 944

Understanding Unidirectional Traffic Flow on Physical Interfaces on page 141

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Physical Interface Damping Overview

Physical interface damping limits the advertisement of the up and down transitions
(flapping) on an interface. Each time a transition occurs, the interface state is changed,
which generates an advertisement to the upper-level routing protocols. Damping helps
reduce the number of these advertisements.
From the viewpoint of network deployment, physical interface flaps fall into the following
categories:

Nearly instantaneous multiple flaps of short duration (milliseconds).

Periodic flaps of long duration (seconds).

Figure 6 on page 143 is used to describe these types of interface flaps and the damping
configuration that you can use in each case.

Figure 6: Two Router Interfaces Connected Through Transport Equipment

NOTE: We recommend that you use similar damping configurations on both

ends of the physical interface. Configuring damping on one end and not having
interface damping on the other end can result in undesired behavior.

The following sections describe the types of interface damping depending upon the
transition time length.

Damping Overview for Shorter Physical Interface Transitions on page 143

Damping Overview for Longer Physical Interface Transitions on page 144

Damping Overview for Shorter Physical Interface Transitions

Figure 6 on page 143 shows two routers with two transport devices between them. If a
redundant link between the two transport devices fails, link switching is performed. Link
switching takes a number of milliseconds. As shown in Figure 7 on page 144, during
switching, both router interfaces might encounter multiple flaps with an up-and-down
duration of several milliseconds. These multiple flaps, if advertised to the upper-level
routing protocols, might result in undesired route updates. This is why you might want
to damp these interface flaps.

NOTE: Damping is suitable only with routing protocols.

Copyright 2014, Juniper Networks, Inc.

143

Interfaces Fundamentals for Routing Devices

For shorter physical interface transitions, you configure interface damping with the
hold-time statement on the interface. The hold timer enables interface damping by not
advertising interface transitions until the hold timer duration has passed. When a
hold-down timer is configured and the interface goes from up to down, the interface is
not advertised to the rest of the system as being down until it has remained down for
the hold-down timer period. Similarly, when a hold-up timer is configured and an interface
goes from down to up, it is not advertised as being up until it has remained up for the
hold-up timer period.

Figure 7: Multiple Flaps of Short Duration (Milliseconds)

Damping Overview for Longer Physical Interface Transitions

When the link between a router interface and the transport devices is not stable, this can
lead to periodic flapping, as shown in Figure 8 on page 145. Flaps occur in the order of
seconds or more, with an up-and-down flap duration in the order of a second or more.
In this case, using the hold timer feature might not produce optimal results as it cannot
suppress the relatively longer and repeated interface flaps. Increasing the hold time
duration to seconds still allows the system to send route updates on the flapping interface,
so fails to suppress periodically flapping interfaces on the system.

144

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Figure 8: Periodic Flaps of Long Duration (Seconds)

For longer periodic interface flaps, you configure interface damping with the damping
statement on the interface. This damping method uses an exponential back-off algorithm
to suppress interface up-and-down event reporting to the upper-level protocols. Every
time an interface goes down, a penalty is added to the interface penalty counter. If at
some point the accumulated penalty exceeds the suppress level, the interface is placed
in the suppress state, and further interface link up and down events are not reported to
the upper-level protocols.

NOTE:

Only PTX Series routers, T Series routers, MX960 routers, MX480 routers,
MX240 routers, MX80 routers, and M10i routers support interface damping
for longer periodic interface flaps.

The system does not indicate whether an interface is down because of

suppression or that is the actual state of the physical interface. Because
of this, SNMP link traps and Operation, Administration, and Maintenance
(OAM) protocols cannot differentiate the damped version of the link state
from the real version. Therefore, the traps and protocols might not work
as expected.

You can verify suppression by viewing the information in the Damping field
of the show interface extensive command output.

At all times, the interface penalty counter follows an exponential decay process.
Figure 9 on page 147 and Figure 10 on page 148 show the decay process as it applies to
recovery when the physical level link is down or up. As soon as the accumulated penalty
reaches the lower boundary of the reuse level, the interface is marked as unsuppressed,
and further changes in the interface link state are again reported to the upper-level

Copyright 2014, Juniper Networks, Inc.

145

Interfaces Fundamentals for Routing Devices

protocols. You use the max-suppress option to configure the maximum time for restricting
the accumulation of the penalty beyond the value of the maximum penalty. The value
of the maximum penalty is calculated by the software. The maximum penalty corresponds
to the time it would take max-suppress to decay and reach the reuse level. The penalty
continues to decay after crossing the reuse level.
Figure 9 on page 147 and Figure 10 on page 148 show the accumulated penalty, and the
decay over time as a curve. Whenever the penalty is below the reuse level and the physical
level link changes state, state changes are advertised to the system and cause SNMP
state changes.
Figure 9 on page 147 shows the penalty dropping below the reuse level when the physical
link is down. The system is notified of a state change only after the physical level link
transitions to up.

146

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Figure 9: Physical-Level Link Is Down When the Penalty Falls Below the
Reuse Level

Figure 10 on page 148 shows the penalty dropping below the reuse level when the physical
link is up. The system is notified of a state change immediately.

Copyright 2014, Juniper Networks, Inc.

147

Interfaces Fundamentals for Routing Devices

Figure 10: Physical-Level Link Is Up When the Penalty Falls Below the
Reuse Level

Related
Documentation

148

Damping Shorter Physical Interface Transitions on page 149

Damping Longer Physical Interface Transitions on page 150

Understanding BGP Route Flap Damping Parameters

damping on page 490

hold-time on page 599

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Damping Shorter Physical Interface Transitions

By default, when an interface changes from being up to being down, or from down to up,
this transition is advertised immediately to the hardware and Junos OS. In some
situationsfor example, when an interface is connected to an add/drop multiplexer
(ADM) or wavelength-division multiplexer (WDM), or to protect against SONET/SDH
framer holesyou might want to damp interface transitions. This means not advertising
the interfaces transition until a certain period of time has passed, called the hold-time.
When you have damped interface transitions and the interface goes from up to down,
the interface is not advertised to the rest of the system as being down until it has remained
down for the hold-time period. Similarly, when an interface goes from down to up, it is
not advertised as being up until it has remained up for the hold-time period. For
information about physical interface damping, see Physical Interface Damping Overview
on page 143.
This task applies to damping shorter physical interface transitions in milliseconds. To
damp longer physical interface transitions in seconds, see Damping Longer Physical
Interface Transitions on page 150.
To configure damping of shorter physical interface transitions:
1.

Select the interface to damp, where the interface name is interface-type-fpc/pic/port:

[edit]
user@host# edit interfaces interface-name

2. Configure the hold-time for link up and link down.

[edit interfaces interface-name]

user@host# set hold-time up milliseconds down milliseconds

The hold time can be a value from 0 through 4,294,967,295 milliseconds. The default
value is 0, which means that interface transitions are not damped. Junos OS advertises
the transition within 100 milliseconds of the time value you specify.
For most Ethernet interfaces, hold timers are implemented using a one-second polling
algorithm. For 1-port, 2-port, and 4-port Gigabit Ethernet interfaces with small form-factor
pluggable transceivers (SFPs), hold timers are interrupt-driven.

NOTE: The hold-time option is not available for controller interfaces.

Related
Documentation

Physical Interface Damping Overview on page 143

Damping Longer Physical Interface Transitions on page 150

SONET/SDH Defect Hold Times for Damping Interface Transitions Overview

Configuring SONET/SDH Defect Triggers

hold-time on page 599

Copyright 2014, Juniper Networks, Inc.

149

Interfaces Fundamentals for Routing Devices

Damping Longer Physical Interface Transitions

Physical interface damping limits the advertisement of the up and down transitions
(flapping) on an interface. An unstable link between a router Interface and the transport
devices can lead to periodic flapping. Longer flaps occur with a period of about five
seconds or more, with an up-and-down duration of one second. For these longer periodic
interface flaps, you configure interface damping with the damping statement on the
interface. This damping method uses an exponential back-off algorithm to suppress
interface up and down event reporting to the upper-level protocols. Every time an interface
goes down, a penalty is added to the interface penalty counter. If at some point the
accumulated penalty exceeds the suppress level max-suppress, the interface is placed
in the suppress state, and further interface state up and down transitions are not reported
to the upper-level protocols.

NOTE:

Only PTX Series routers, T Series routers, MX960 routers, MX480 routers,
MX240 routers, MX80 routers, and M10i routers support interface damping
for longer periodic interface flaps.

The system does not indicate whether an interface is down because of

suppression or that is the actual state of the physical interface. Because
of this, SNMP link traps and Operation, Administration, and Maintenance
(OAM) protocols cannot differentiate the damped version of the link state
from the real version. Therefore, the traps and protocols might not work
as expected.

You can verify suppression by viewing the information in the Damping field
of the show interface extensive command output.

You can view the damping parameters with the show interfaces extensive command.
To configure damping of longer physical interface transitions:
1.

Select the interface to damp, where the interface name is interface-type-fpc/pic/port

or an interface range:
[edit]
user@host# edit interfaces interface-name

2. Enable longer interface transition damping on a physical interface:

[edit interfaces interface-name damping]

user@host# set enable
3. (Optional) Set the maximum time in seconds that an interface can be suppressed no

matter how unstable the interface has been.

NOTE: Configure max-suppress to a value that is greater than the value

of half-life; otherwise, the configuration is rejected.

150

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

[edit interfaces interface-name damping]

user@host# set max-suppress maximum-seconds
4. (Optional) Set the decay half-life in seconds, which is the interval after which the

accumulated interface penalty counter is reduced by half if the interface remains

stable.

NOTE: Configure max-suppress to a value that is greater than the value

of half-life; otherwise, the configuration is rejected.

[edit interfaces interface-name damping]

user@host# set half-life seconds
5. (Optional) Set the reuse threshold (no units). When the accumulated interface penalty

counter falls below this value, the interface is no longer suppressed.

[edit interfaces interface-name damping]
user@host# set reuse number
6. (Optional) Set the suppression threshold (no units). When the accumulated interface

penalty counter exceeds this value, the interface is suppressed.

[edit interfaces interface-name damping]
user@host# set suppress number

Related
Documentation

Physical Interface Damping Overview on page 143

show interfaces extensive on page 1372

Damping Shorter Physical Interface Transitions on page 149

damping on page 490

Example: Configuring Physical Interface Damping

This example shows how to configure damping for a physical interface on a PTX Series
Packet Transport Router.

Requirements on page 151

Overview on page 152

Configuration on page 152

Verification on page 153

Requirements
This example uses the following hardware and software components:

One PTX Series Packet Transport Router

One or more routers that provide input packets and receive output packets

Junos OS Release 14.1 or later

Copyright 2014, Juniper Networks, Inc.

151

Interfaces Fundamentals for Routing Devices

Overview
Physical interface damping provides a smoothing of the up and down transitions (flapping)
on an interface. Each time a transition occurs, the interface state is changed, which
generates an advertisement to the upper-level routing protocols. Damping helps reduce
the number of these advertisements.
From the viewpoint of network deployment, physical interface flaps fall into these
categories:

Nearly instantaneous multiple flaps of short duration (milliseconds). For shorter physical
interface transitions, you configure interface damping with the hold-time statement
on the interface. The hold timer enables interface damping by not advertising interface
transitions until the hold timer duration has passed. When a hold-down timer is
configured and the interface goes from up to down, the interface is not advertised to
the rest of the system as being down until it has remained down for the hold-down
timer period. Similarly, when a hold-up timer is configured and an interface goes from
down to up, it is not advertised as being up until it has remained up for the hold-up
timer period.

Periodic flaps of long duration (seconds). For longer periodic interface flaps, you
configure interface damping with the damping statement on the interface. This damping
method uses an exponential back-off algorithm to suppress interface up and down
event reporting to the upper-level protocols. Every time an interface goes down, a
penalty is added to the interface penalty counter. If at some point the accumulated
penalty exceeds the suppress level, the interface is placed in the suppress state, and
further interface state up transitions are not reported to the upper-level protocols.

Configuration
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.
set interfaces xe-6/0/0 damping half-life 11 max-suppress 2222 reuse 3333 suppress
4444

Step-by-Step
Procedure

To configure damping on the PTX Series Packet Transport Router:

1.

Enable damping on the interface, set the half-life interval, maximum suppression,
reuse, and suppress values:
[edit interface]
user@router# set xe-6/0/0 damping half-life 11 max-suppress 2222 reuse 3333
suppress 4444

2.

Commit configuration:
[edit]
user@router# commit

152

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Results
From configuration mode, confirm your configuration by entering the show interfaces
command. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.
user@router# show interfaces
xe-6 {
damping {
half-life 11;
max-suppress 2222;
reuse 3333;
suppress 4444;
}

Verification
To confirm that the configuration is working properly, perform this task:

Verifying Interface Damping on xe6 on page 153

Verifying Interface Damping on xe6

Purpose

Action

Verify that damping is enabled on the interface and that the damping parameter values
are correctly set.

From operational mode, run the show interfaces extensive command.

user@router# run show interfaces xe-6/0/0 extensive
Physical interface: xe-6/0/0, Enabled, Physical link is Up
Interface index: 158, SNMP ifIndex: 535, Generation: 161
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, BPDU Error:
None, Loopback: None,
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Damping
: half-life: 11 sec, max-suppress: 2222 sec, reuse: 3333,
suppress: 4444, state: unsuppressed

Meaning

Related
Documentation

Damping is enabled and configured successfully on the xe-6 interface.

Physical Interface Damping Overview on page 143

damping on page 490

Configuring Multiservice Physical Interface Properties

The adaptive services (AS), collector, monitoring services, and monitoring services II
interfaces are multiservice interfaces specifically designed to enable IP services. To

Copyright 2014, Juniper Networks, Inc.

153

Interfaces Fundamentals for Routing Devices

configure multiservice physical interface properties on the collector, monitoring services,

and AS interfaces, include the multiservice-options statement:
multiservice-options {
(core-dump | no-core-dump);
(syslog | no-syslog);
flow-control-options {
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
}
}

You can include these statements at the following hierarchy levels:

[edit interfaces cp-fpc/pic/port]

[edit interfaces mo-fpc/pic/port]

[edit interfaces sp-fpc/pic/port]

For more information about the services interfaces, see the Junos OS Services Interfaces
Library for Routing Devices.

Enabling or Disabling SNMP Notifications on Physical Interfaces

By default, Simple Network Management Protocol (SNMP) notifications are sent when
the state of an interface or a connection changes. You can enable or disable these
notification based on you requirements.
To explicitly enable sending SNMP notifications on the physical interface, perform the
following steps:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level:

[edit]
user@host# edit interfaces interface-name

2. Configure the traps option to enable sending of Simple Network Management Protocol

(SNMP) notifications when the state of the connection changes.

[edit interfaces interface-name]
user@host# set traps

To disable sending SNMP notifications on the physical interface, perform the following
steps:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level:

[edit]
user@host# edit interfaces interface-name

2. Configure the no-traps option to disable sending of Simple Network Management

Protocol (SNMP) notifications when the state of the connection changes.

[edit interfaces interface-name]
user@host# set no-traps

154

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

NOTE: Gigabit Ethernet interfaces on J Series routers do not support SNMP.

Related
Documentation

traps on page 938

Configuring Accounting for the Physical Interface

Juniper Networks routers and switches can collect various kinds of data about traffic
passing through the router and switch. You can set up one or more accounting profiles
that specify some common characteristics of this data, including the following:

The fields used in the accounting records

The number of files that the router or switch retains before discarding, and the number
of bytes per file

The polling period that the system uses to record the data

You configure the profiles and define a unique name for each profile using statements
at the [edit accounting-options] hierarchy level. There are two types of accounting profiles:
interface profiles and filter profiles. You configure interface profiles by including the
interface-profile statement at the [edit accounting-options] hierarchy level. You configure
filter profiles by including the filter-profile statement at the [edit accounting-options]
hierarchy level. For more information, see the Network Management Administration Guide
for Routing Devices.
You apply filter profiles by including the accounting-profile statement at the [edit firewall
filter filter-name] and [edit firewall family family filter filter-name] hierarchy levels. For
more information, see the Routing Policies, Firewall Filters, and Traffic Policers Feature
Guide for Routing Devices.

Applying an Accounting Profile to the Physical Interface

To enable accounting on an interface, include the accounting-profile statement at the
[edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
accounting-profile name;

You can also reference profiles by logical unit; for more information, see Configuring
Accounting for the Logical Interface on page 182.

Example: Applying an Accounting Profile to the Physical Interface

Configure an accounting profile for an interface and apply it to a physical interface:
[edit]
accounting-options {
file if_stats {
size 4m files 10 transfer-interval 15;
archive-sites {
"ftp://login:password@host/path";

Copyright 2014, Juniper Networks, Inc.

155

Interfaces Fundamentals for Routing Devices

}
}
interface-profile if_profile {
interval 15;
file if_stats {
fields {
input-bytes;
output-bytes;
input-packets;
output-packets;
input-errors;
output-errors;
}
}
}
}
[edit interfaces ge-1/0/1]
accounting-profile if_profile;

Disabling a Physical Interface

You can disable a physical interface, marking it as being down, without removing the
interface configuration statements from the configuration. To do this, include the disable
statement at the [edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
disable;

CAUTION: Dynamic subscribers and logical interfaces use physical interfaces

for connection to the network. The Junos OS allows you to set the interface
to disable and commit the change while dynamic subscribers and logical
interfaces are still active. This action results in the loss of all subscriber
connections on the interface. Use care when disabling interfaces.

NOTE: On the router, when you use the disable statement at the edit interfaces
hierarchy level, depending on the PIC type, the interface might or might not
turn off the laser. Older PIC transceivers do not support turning off the laser,
but newer Gigabit Ethernet PICs with SFP and XFP transceivers do support
it and the laser will be turned off when the interface is disabled.

Table 44: Effect of set interfaces disable <interface_name> on T series PICs

Type of
PIC

Behaviour

10-Gigabit Ethernet LAN/WAN PIC with SFP+

(T4000 Router)

Tx laser disabled

10-Gigabit Ethernet LAN/WAN PIC with

Oversubscription and SFP+ (T4000 Router)

Tx laser disabled

PIC Model Number

PIC Description

PF-12XGE-SFPP

PF-24XGE-SFPP

156

Copyright 2014, Juniper Networks, Inc.

Chapter 2: Configuring Physical Interface Properties

Table 44: Effect of set interfaces disable <interface_name> on T series PICs (continued)
Type of
PIC

Behaviour

100-Gigabit Ethernet PIC with CFP (T4000

Router)

Tx laser disabled

PD-4XGE-XFP

10-Gigabit Ethernet, 4-port LAN/WAN XFP

Tx laser disabled

PD-5-10XGE-SFPP

10-Gigabit LAN/WAN with SFP+

Tx laser disabled

PD-1XLE-CFP

40-Gigabit with CFP

Tx laser disabled

PD-1CE-CFP-FPC4

100-Gigabit with CFP

Tx laser disabled

PD-TUNNEL

40-Gigabit Tunnel Services

NA

PD-4OC192-SON-XFP

OC192/STM64, 4-port XFP

Tx laser not disabled

PD-1OC768-SON-SR

OC768c/STM256, 1-port

Tx laser not disabled

PIC Model Number

PIC Description

PF-1CGE-CFP

WARNING: Do not stare into the laser beam or view it directly with optical
instruments even if the interface has been disabled.

Example: Disabling a Physical Interface

Sample interface configuration:
[edit interfaces]
user@host# show
ge-0/3/2 {
unit 0 {
description CE2-to-PE1;
family inet {
address 20.1.1.6/24;
}
}
}

Disabling the interface:

[edit interfaces]
user@host# set ge-0/3/2 disable

Verifying the interface configuration:

[edit interfaces]
user@host# show
ge-0/3/2 {
disable; # Interface is marked as disabled.
unit 0 {

Copyright 2014, Juniper Networks, Inc.

157

Interfaces Fundamentals for Routing Devices

description CE2-to-PE1;
family inet {
address 20.1.1.6/24;
}
}
}

158

Copyright 2014, Juniper Networks, Inc.

CHAPTER 3

Configuring Logical Interface Properties

Logical Interfaces Configuration Properties Overview on page 159

Logical Interfaces Configuration Statements on page 160

Logical Interfaces Statements List on page 163

Specifying the Logical Interface Number on page 171

Adding a Logical Unit Description to the Configuration on page 171

Configuring the Interface Bandwidth on page 172

Configuring Interface Encapsulation on Logical Interfaces on page 172

Configuring Interface Encapsulation on PTX Series Packet Transport Routers on page 174

Configuring a Point-to-Point Connection on page 175

Configuring a Multipoint Connection on page 176

Configuring the PPP Restart Timers on page 176

Configuring the PPP Clear Loop Detected Timer on page 177

Configuring the LCP Configure-Request Maximum Sent on page 177

Configuring the NCP Configure-Request Maximum Sent on page 177

Configuring Dynamic Profiles for PPP on page 178

Configuring PPP CHAP Authentication on page 178

Configuring PPP PAP Authentication on page 178

Configuring Dynamic Call Admission Control on page 181

Configuring Accounting for the Logical Interface on page 182

Enabling or Disabling SNMP Notifications on Logical Interfaces on page 183

Disabling a Logical Interface on page 184

Configuring Logical System Interface Properties on page 184

Logical Interfaces Configuration Properties Overview

For a physical interface device to function, you must configure at least one logical interface
on that device. For each logical interface, you must specify the protocol family that the
interface supports. You can also configure other logical interface properties. These vary
by Physical Interface Card (PIC) and encapsulation type, but include the IP address of
the interface, and whether the interface supports multicast traffic, data-link connection

Copyright 2014, Juniper Networks, Inc.

159

Interfaces Fundamentals for Routing Devices

identifiers (DLCIs), virtual channel identifiers (VCIs) and virtual path identifiers (VPIs),
and traffic shaping.
Related
Documentation

Logical Part of an Interface Name on page 32

Logical Interfaces Configuration Statements

To configure logical interface properties, include the following statements:
unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
accounting-profile name;
allow-any-vci;
atm-scheduler-map (map-name | default);
backup-options {
interface interface-name;
}
bandwidth rate;
cell-bundle-size cells;
clear-dont-fragment-bit;
compression {
rtp {
f-max-period number;
queues [ queue-numbers ];
port {
minimum port-number;
maximum port-number;
}
}
}
compression-device interface-name;
copy-tos-to-outer-ip-header;
demux-destination family;
demux-source family;
demux-options {
underlying-interface interface-name;
}
description text;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
callback;
callback-wait-period time;
deactivation-delay seconds;

160

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

dial-string [ dial-string-numbers ];
idle-timeout seconds;
incoming-map {
caller (caller-id| accept-all);
initial-route-check seconds;
load-interval seconds;
load-threshold number;
pool pool-name;
redial-delay time;
watch-list {
[ routes ];
}
}
}
disable;
disable-mlppp-inner-ppp-pfc;
dlci dlci-identifier;
drop-timeout milliseconds;
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
encapsulation type;
epd-threshold plp1 cells;
filter filter-name;
fragment-threshold bytes;
inner-vlan-id-range start start-id end end-id;
input-vlan-map {
inner-tag-protocol-id;
inner-vlan-id;
(pop | pop-pop | pop-swap | push | push-push | swap |swap-push | swap-swap);
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
link-layer-overhead percent;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
output-vlan-map {
inner-tag-protocol-id;

Copyright 2014, Juniper Networks, Inc.

161

Interfaces Fundamentals for Routing Devices

inner-vlan-id;
(pop | pop-pop | pop-swap | push | push-push | swap |swap-push | swap-swap);
tag-protocol-id tpid;
vlan-id number;
}
passive-monitor-mode;
peer-unit unit-number;
plp-to-clp;
point-to-point;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
dynamic-profile profile-name;
lcp-restart-timer milliseconds;
loopback-clear-timer seconds;
ncp-restart-timer milliseconds;
pap {
default-pap-password password;
local-name name;
local-password password;
passive;
}
pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
short-sequence;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}

162

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
vci-range start start-vci end end-vci;
vpi vpi-identifier;
vlan-id number;
vlan-id-range number-number;
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
family family {
[ family-statements ];
}
}

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name]

[edit logical-systems logical-system-name interfaces interface-name]

For information about interface-specific logical properties, see Table 45 on page 163.

Logical Interfaces Statements List

Table 45 on page 163 lists statements that you can use to configure logical interfaces.

Table 45: Statements for Logical Interface Properties

Statement

Interface Types

Usage Guidelines

access-profile name

ATM2 IQ interfaces

Configuring PPP PAP Authentication on

page 178

accept-source-mac

Gigabit Ethernet intelligent queuing (IQ)

interfaces

Configuring Gigabit Ethernet Policers

accounting-profile name

All

Configuring Accounting for the Logical

Interface on page 182

activation-delay seconds

ISDN interfaces

ISDN Interfaces Overview

activation-priority priority

Fast Ethernet and Gigabit Ethernet

interfaces, ISDN BRI interfaces, and serial
interfaces with PPP or Frame Relay
encapsulation on J4350 and J6350
Services Routers supporting voice over IP
with the TGM550 media gateway module

Configuring Dynamic Call Admission

Control on page 181

adaptive-shapers
adaptive-shaper-name

Frame Relay interfaces on J Series routers

Class of Service Feature Guide for Routing

Devices

allow-any-vci

Asynchronous Transfer Mode (ATM)

interfaces

Configuring ATM Interface Encapsulation

Copyright 2014, Juniper Networks, Inc.

163

Interfaces Fundamentals for Routing Devices

Table 45: Statements for Logical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

ATM2 IQ interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

backup-destination address

Encryption interfaces

Class of Service Feature Guide for Routing

Devices

backup-options

J Series routers ISDN interfaces

Configuring ISDN Logical Interface

Properties

bandwidth rate

All interfaces, except multilink and

aggregated

Configuring the Interface Bandwidth on

page 172

bearer-bandwidth-limit

Fast Ethernet and Gigabit Ethernet

interfaces, ISDN BRI interfaces, and serial
interfaces with PPP or Frame Relay
encapsulation on J4350 and J6350
Services Routers supporting voice over IP
with the TGM550 media gateway module

Configuring Dynamic Call Admission

Control on page 181

cbr rate

ATM interfaces

Defining the ATM Traffic-Shaping Profile

cell-bundle-size cells

ATM2 IQ interfaces

Configuring the Layer 2 Circuit Cell-Relay

Cell Maximum

clear-dont-fragment-bit

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

compression

AS PIC or MultiServices PIC link services

IQ interfaces (lsq) and voice services
interfaces

Junos OS Services Interfaces Library for

Routing Devices

compression-device
interface-name

J Series routers E1 and T1 interfaces.

Junos OS Services Interfaces Library for

Routing Devices

copy-tos-to-outer-ip-header

GRE tunnel interfaces

Class of Service Feature Guide for Routing

Devices

deactivation-delay seconds

ISDN interfaces

ISDN Interfaces Overview

demux-destination family

IP demux interfaces

Configuring an IP Demultiplexing
Interface on page 284

demux-options family

IP demux interfaces

Configuring an IP Demultiplexing
Interface on page 284

demux-source family

IP demux interfaces

Configuring an IP Demultiplexing
Interface on page 284

description text

All

Adding a Logical Unit Description to the

Configuration on page 171

atm-scheduler-map (map-name |

default)

kilobits-per-second

164

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

Table 45: Statements for Logical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

Encryption generic routing encapsulation

(GRE) tunnel, and IP tunnel interfaces

Junos OS Services Interfaces Library for

Routing Devices

dialer-options

J Series routers ISDN interfaces

Configuring ISDN Physical Interface

Properties

disable

All

Disabling a Logical Interface on page 184

disable-mlppp-inner-ppp-pfc

MLPPP interfaces

Junos OS Services Interfaces Library for

Routing Devices

dlci dlci-identifier

Point-to-point interfaces with Frame Relay

encapsulation

Configuring Frame Relay DLCIs

drop-timeout milliseconds

Multilink interfaces

Junos OS Services Interfaces Library for

Routing Devices

dynamic-call-admission-control

Fast Ethernet and Gigabit Ethernet

interfaces, ISDN BRI interfaces, and serial
interfaces with PPP or Frame Relay
encapsulation on J4350 and J6350
Services Routers supporting voice over IP
with the TGM550 media gateway module

Configuring Dynamic Call Admission

Control on page 181

dynamic-profile profile-name

1-Gigabit Ethernet and 10-Gigabit Ethernet

interfaces configured with PPP over
Ethernet on M120 and M320 routers

Junos Subscriber Access Configuration

Guide

encapsulation type

All interfaces, except aggregated

SONET/SDH and loopback

Configuring the Encapsulation on a

Logical Interface on page 173

epd-threshold cells

ATM2 IQ interfaces

Configuring the ATM2 IQ EPD Threshold

f-max-period number

AS PIC or MultiServices link services IQ

interfaces (lsq-) and voice services
interfaces

Junos OS Services Interfaces Library for

Routing Devices

family

All

Configuring the Protocol Family on

page 190

fragment-threshold bytes

Multilink interfaces

Junos OS Services Interfaces Library for

Routing Devices

frame-relay map-name | default)

Frame Relay Interfaces on J Series routers

Junos OS Services Interfaces Library for

Routing Devices and Class of Service
Feature Guide for Routing Devices

idle-timeout

ISDN interfaces

Configuring ISDN Logical Interface

Properties

destination (address |

routing-instance-name)

Copyright 2014, Juniper Networks, Inc.

165

Interfaces Fundamentals for Routing Devices

Table 45: Statements for Logical Interface Properties (continued)

Statement

166

Interface Types

Usage Guidelines

initial-route-check seconds

ISDN interfaces

Configuring ISDN Logical Interface

Properties

inner-tag-protocol-id

Gigabit Ethernet IQ interfaces

802.1Q VLANs Overview

inner-vlan-id

Gigabit Ethernet IQ interfaces

802.1Q VLANs Overview

inner-vlan-id-range

Gigabit Ethernet, 10-Gigabit Ethernet, and

aggregated Ethernet IQ interfaces

Configuring ATM-to-Ethernet
Interworking on page 262

input

AS PIC or MultiServices link services

Junos OS Services Interfaces Library for

Routing Devices

input-policer policer-name

For 1-Gigabit Ethernet and 10-Gigabit

Ethernet IQ2 and IQ2-E interfaces on M
Series and T Series routers

Junos OS Services Interfaces Library for

Routing Devices and Configuring Gigabit
Ethernet Two-Color and Tricolor Policers

input-three-color policer-name

For 1-Gigabit Ethernet and 10-Gigabit

Ethernet IQ2 and IQ2-E interfaces on M
Series and T Series routers

Class of Service Feature Guide for Routing

Devices and Configuring Gigabit Ethernet
Two-Color and Tricolor Policers

input-vlan-map

Gigabit Ethernet IQ interfaces

Stacking and Rewriting Gigabit Ethernet

VLAN Tags Overview

interleave-fragments

Link services interfaces

Junos OS Services Interfaces Library for

Routing Devices

inverse-arp

Interfaces with ATM and Frame Relay

encapsulation

Configuring Inverse ATM1 or ATM2 ARP and

Configuring Inverse Frame Relay ARP

key number

GRE tunnel interfaces on Adaptive Services

PICs

Junos OS Services Interfaces Library for

Routing Devices

layer2-policer

1-Gigabit Ethernet and 10-Gigabit Ethernet

IQ2 and IQ2-E interfaces

Configuring Gigabit Ethernet Two-Color and

Tricolor Policers

lcp-restart-timer

Interfaces with PPP encapsulation

Configuring the PPP Restart Timers on

page 176

l2tp-interface-id name

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

link-layer-overhead percent

AS PIC or MultiServices link services IQ

interfaces (lsq)

Junos OS Services Interfaces Library for

Routing Devices

load-threshold number

ISDN interfaces

Configuring ISDN Logical Interface

Properties

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

Table 45: Statements for Logical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

local-name name

ATM2 IQ interfaces

Configuring PPP CHAP Authentication

on page 178 and Configuring PPP PAP
Authentication on page 178

loss-priority-maps

Frame Relay interfaces on J Series routers

Junos OS Services Interfaces Library for

Routing Devices and Class of Service
Feature Guide for Routing Devices

mac-address mac-address

Gigabit Ethernet interfaces and Gigabit

Ethernet IQ and IQE interfaces with small
form-factor pluggable transceivers (SFPs)
(except the 10-port Gigabit Ethernet PIC
and the built-in Gigabit Ethernet port on
the M7i router)

Configuring Gigabit Ethernet Policers

minimum-links number

Multilink interfaces

Junos OS Services Interfaces Library for

Routing Devices

mrru bytes

Multilink interfaces

Junos OS Services Interfaces Library for

Routing Devices

multicast-dlci dlci-identifier

Point-to-multipoint Frame Relay

interfaces

Configuring Frame Relay DLCIs

multicast-vci

Point-to-multipoint ATM1 and ATM2 IQ

interfaces

Configuring the ATM OAM F5 Loopback Cell

Threshold

multilink-max-classes number

AS PIC or MultiServices link services IQ

interfaces (lsq-)

Junos OS Services Interfaces Library for

Routing Devices

multipoint

All

Configuring a Multipoint Connection on

page 176

ncp-restart-timer

Interfaces with PPP encapsulation

Configuring the PPP Restart Timers on

page 176

oam-liveness

ATM1 and ATM2 IQ interfaces

Configuring the ATM OAM F5 Loopback Cell

Threshold

oam-period (disable | seconds)

ATM1 and ATM2 IQ interfaces

Defining the ATM OAM F5 Loopback Cell

Period

output

All

Junos OS Services Interfaces Library for

Routing Devices

output-policer policer-name

For 1-Gigabit Ethernet and 10-Gigabit

Ethernet IQ2 and IQ2-E interfaces on M
Series and T Series routers

Class of Service Feature Guide for Routing

Devices and Configuring Gigabit Ethernet
Two-Color and Tricolor Policers

vpi-identifiervci-identifier

Copyright 2014, Juniper Networks, Inc.

167

Interfaces Fundamentals for Routing Devices

Table 45: Statements for Logical Interface Properties (continued)

Statement

168

Interface Types

Usage Guidelines

output-three-color policer-name

For 1-Gigabit Ethernet and 10-Gigabit

Ethernet IQ2 and IQ2-E interfaces on M
Series and T Series routers

Class of Service Feature Guide for Routing

Devices and Configuring Gigabit Ethernet
Two-Color and Tricolor Policers

output-vlan-map

Gigabit Ethernet IQ interfaces

Stacking and Rewriting Gigabit Ethernet

VLAN Tags Overview

passive (CHAP)

ATM2 IQ interfaces

Configuring PPP CHAP Authentication

on page 178

passive (PAP)

ATM2 IQ interfaces

Configuring PPP PAP Authentication on

page 178

passive-monitor-mode

SONET/SDH interfaces

Enabling Packet Flow Monitoring on

SONET/SDH Interfaces

peer-unit unit-number

Logical tunnel interfaces

Junos OS Services Interfaces Library for

Routing Devices

pfc

Interfaces with PPP, PPP CCC, or PPP TCC

encapsulation

Configuring the PPP Protocol Field

Compression on page 135

plp1 cells

ATM2 IQ interfaces

Configuring the ATM2 IQ EPD Threshold

plp-to-clp

ATM2 IQ interfaces

Configuring ATM2 IQ VC Tunnel CoS

Components

point-to-point

All

Configuring a Point-to-Point Connection

on page 175

policer

Gigabit Ethernet and Gigabit Ethernet IQ

and IQE PICs with SFPs (except the
10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i
router)

Configuring Gigabit Ethernet Policers

pop

Gigabit Ethernet IQ interfaces

Removing a VLAN Tag

pop-pop

Gigabit Ethernet IQ interfaces

Removing the Outer and Inner VLAN Tags

pop-swap

Gigabit Ethernet IQ interfaces

Removing the Outer VLAN Tag and

Rewriting the Inner VLAN Tag

port

AS PIC or MultiServices or MultiServices

link services IQ interfaces (lsq) and voice
services interfaces

Junos OS Services Interfaces Library for

Routing Devices

ppp-options

Interfaces with PPP, PPP CCC, or PPP TCC

encapsulation

Configuring PPP CHAP Authentication

on page 178 and Configuring PPP PAP
Authentication on page 178

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

Table 45: Statements for Logical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

proxy-arp

Ethernet interfaces

Configuring Restricted and Unrestricted

Proxy ARP

push

Gigabit Ethernet IQ interfaces

Stacking a VLAN Tag

push-push

Gigabit Ethernet IQ interfaces

Stacking Two VLAN Tags

queue-length number

ATM1 interfaces

Configuring the ATM1 Queue Length

queues [ queue-numbers ]

AS PIC or MultiServices link services IQ

interfaces (lsq) and voice services
interfaces

Junos OS Services Interfaces Library for

Routing Devices

routing-instance

GRE tunnel and IP tunnel interfaces

Junos OS Services Interfaces Library for

Routing Devices

rtp

AS PIC or MultiServices link services IQ

interfaces (lsq) and voice services
interfaces

Junos OS Services Interfaces Library for

Routing Devices

rtvbr peak rate sustained rate burst

ATM2 interfaces

Defining the ATM Traffic-Shaping Profile

service-domain (inside | outside)

Adaptive services interfaces

Junos OS Services Interfaces Library for

Routing Devices

shaping

ATM1 and ATM2 IQ interfaces

Defining the ATM Traffic-Shaping Profile

short-sequence

Multilink interfaces

Junos OS Services Interfaces Library for

Routing Devices

source source-address

Encryption, GRE tunnel, and IP tunnel

interfaces

Junos OS Services Interfaces Library for

Routing Devices

swap

Gigabit Ethernet IQ interfaces

Configuring Frames with Particular TPIDs

to Be Processed as Tagged Frames

swap-push

Gigabit Ethernet IQ interfaces

Rewriting a VLAN Tag and Adding a New

Tag

swap-swap

Gigabit Ethernet IQ interfaces

Rewriting the Inner and Outer VLAN Tags

tag-protocol-id tpid

Gigabit Ethernet and Gigabit Ethernet IQ

and IQE PICs with SFPs (except the
10-port Gigabit Ethernet PIC, Aggregated
Ethernet with Gigabit Ethernet IQ
interfaces, and the built-in Gigabit Ethernet
port on the M7i router)

Rewriting the VLAN Tag on Tagged Frames

length

Copyright 2014, Juniper Networks, Inc.

169

Interfaces Fundamentals for Routing Devices

Table 45: Statements for Logical Interface Properties (continued)

Statement

Interface Types

Usage Guidelines

transmit-weight number

ATM2 IQ interfaces

Configuring the ATM2 IQ Transmission

Weight

(traps | no-traps)

All

Enabling or Disabling SNMP Notifications

on Logical Interfaces on page 183

trunk-bandwidth rate

ATM2 IQ interfaces

Configuring Layer 2 Circuit Trunk Mode

Scheduling

trunk-id number

ATM2 IQ interfaces

Configuring Layer 2 Circuit Transport Mode

on ATM2 IQ Interfaces

ttl number

GRE tunnel and IP tunnel interfaces

Junos OS Services Interfaces Library for

Routing Devices

tunnel

Encryption, GRE tunnel, and IP tunnel

interfaces

Junos OS Services Interfaces Library for

Routing Devices

underlying-interface

IP demux interfaces

Configuring an IP Demultiplexing
Interface on page 284

vbr peak rate sustained rate burst

ATM interfaces

Defining the ATM Traffic-Shaping Profile

vci vpi-identifiervci-identifier

ATM1 and ATM2 IQ point-to-point

interfaces

Configuring a Point-to-Point ATM1 or ATM2

IQ Connection

vci-range

ATM2 IQ interfaces

Configuring ATM-to-Ethernet
Interworking on page 262

vpi vpi-identifier

ATM1 and ATM2 IQ point-to-point

interfaces

Configuring a Point-to-Point ATM1 or ATM2

IQ Connection

vlan-id number

Fast Ethernet, Gigabit Ethernet, and

Gigabit Ethernet IQ interfaces and
aggregated Ethernet using Gigabit
Ethernet IQ interfaces

Binding VLAN IDs to Logical Interfaces and

Rewriting the VLAN Tag on Tagged Frames

vlan-tags inner tpidvlan-id

Gigabit Ethernet IQ interfaces

Configuring Dual VLAN Tags

ISDN interfaces

Configuring ISDN Logical Interface

Properties

length

outer tpidvlan-id
watch-list

Related
Documentation

170

Logical Interfaces Feature Guide for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

Specifying the Logical Interface Number

Each logical interface must have a logical unit number. The logical unit number
corresponds to the logical unit part of the interface name. For more information, see
Interface Naming Overview on page 26.
Point-to-Point Protocol (PPP), Cisco High-level Data Link Control (HDLC), and Ethernet
circuit cross-connect (CCC) encapsulations support only a single logical interface, whose
logical unit number must be 0. Frame Relay and ATM encapsulations support multiple
logical interfaces, so you can configure one or more logical unit numbers.
You specify the logical unit number by including the unit statement:
unit logical-unit-number {
...
}

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name]

[edit logical-systems logical-system-name interfaces interface-name]

The logical unit number can be in the range 0 through 65,535 for demux and PPPoE static
interfaces only. The logical unit number can be in the range 0 through 16,385 for all other
static interface types.

Adding a Logical Unit Description to the Configuration

You can include a text description of each logical unit in the configuration file. Any
descriptive text you include is displayed in the output of the show interfaces commands,
and is also exposed in the ifAlias Management Information Base (MIB) object. It has no
impact on the interfaces configuration. To add a text description, include the description
statement:
description text;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

The description can be a single line of text. If the text contains spaces, enclose it in
quotation marks.

NOTE: You can configure the extended DHCP relay to include the interface
description in the option 82 Agent Circuit ID suboption. See Using DHCP
Relay Agent Option 82 Information in the Junos OS Broadband Subscriber
Management and Services Library.

Copyright 2014, Juniper Networks, Inc.

171

Interfaces Fundamentals for Routing Devices

For information about describing physical interfaces, see Configuring Interface

Description on page 92.

Configuring the Interface Bandwidth

By default, the Junos OS uses the physical interfaces speed for the MIB-II object, ifSpeed.
You can configure the logical unit to populate the ifSpeed variable by configuring a
bandwidth value for the logical interface. The bandwidth statement sets an
informational-only parameter; you cannot adjust the actual bandwidth of an interface
with this statement.

NOTE: We recommend that you be careful when setting this value. Any
interface bandwidth value that you configure using the bandwidth statement
affects how the interface cost is calculated for a dynamic routing protocol,
such as OSPF. By default, the interface cost for a dynamic routing protocol
is calculated using the following formula:
cost = reference-bandwidth/bandwidth,

where bandwidth is the physical interface speed. However, if you specify a

value for bandwidth using the bandwidth statement, that value is used to
calculate the interface cost, rather than the actual physical interface
bandwidth.

To configure the bandwidth value for a logical interface, include the bandwidth statement:
bandwidth rate;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

rate is the peak rate, in bps or 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 using the formula 1 cps = 384 bps. The value
can be any positive integer. The bandwidth statement is valid for all logical interfaces,
except multilink interfaces.

Configuring Interface Encapsulation on Logical Interfaces

PPP encapsulation is the default encapsulation type for physical interfaces. You need
not configure encapsulation for any physical interfaces that support PPP encapsulation.
If you do not configure encapsulation, PPP is used by default. For physical interfaces that
do not support PPP encapsulation, you must configure an encapsulation to use for

172

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

packets transmitted on the interface. For more information about physical interface
encapsulation, see Configuring the Encapsulation on a Physical Interface on page 117.
You can optionally configure an encapsulation on a logical interface, which is the
encapsulation used within certain packet types.

Configuring the Encapsulation on a Logical Interface

Generally, you configure an interfaces encapsulation at the [edit interfaces interface-name]
hierarchy level. However, for some encapsulation types, such as Frame Relay, ATM, and
Ethernet virtual local area network (VLAN) encapsulations, you can also configure the
encapsulation type that is used inside the Frame Relay, ATM, or VLAN circuit itself. To
do this, include the encapsulation statement:
encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-tcc-vc-mux | atm-cisco-nlpid
| 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 | ethernet |
frame-relay-ether-type | frame-relay-ether-type-tcc | frame-relay-ccc | frame-relay-tcc
| multilink-frame-relay-end-to-end | multilink-ppp | vlan-ccc | vlan-tcc | vlan-vpls);

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

Some of the ATM encapsulations are defined in RFC 2684, Multiprotocol Encapsulation
over ATM Adaptation Layer 5.
The following restrictions apply to logical interface encapsulation:

With the atm-nlpid, atm-cisco-nlpid, and atm-vc-mux encapsulations, you can configure
the inet family only.

With the CCC circuit encapsulations, you cannot configure a family on the logical
interface.

A logical interface cannot have frame-relay-ccc encapsulation unless the physical

device also has frame-relay-ccc encapsulation.

A logical interface cannot have frame-relay-tcc encapsulation unless the physical

device also has frame-relay-tcc encapsulation. In addition, you must assign this logical
interface a DLCI from 512 through 1022 and configure it as point-to-point.

A logical interface cannot have frame-relay-ether-type or frame-relay-ether-type-tcc

encapsulation unless the physical interface has flexible-frame-relay encapsulation
and is on an IQ or IQE PIC.

For frame-relay-ether-type-tcc encapsulation, you must assign this logical interface

a DLCI from 512 through 1022.

For interfaces that carry IP version 6 (IPv6) traffic, you cannot configure
ether-over-atm-llc encapsulation.

Copyright 2014, Juniper Networks, Inc.

173

Interfaces Fundamentals for Routing Devices

When you use ether-over-atm-llc encapsulation, you cannot configure multipoint

interfaces.

A logical interface cannot have vlan-ccc or vlan-vpls encapsulation unless the physical
device also has vlan-ccc or vlan-vpls encapsulation, respectively. In addition, you must
assign this logical interface a VLAN ID from 512 through 1023; if the VLAN ID is 511 or
lower, it is subject to the normal destination filter lookups in addition to source address
filtering. For more information, see Configuring VLAN Encapsulation.

You can create an ATM cell-relay circuit by configuring an entire ATM physical device
or an individual virtual circuit (VC). When you configure an entire device, only cell-relay
encapsulation is allowed on the logical interfaces. For more information, see Configuring
an ATM1 Cell-Relay Circuit.

For more information about ATM encapsulations, see Configuring ATM Interface
Encapsulation.
For more information about Frame Relay encapsulations, see Configuring Frame Relay
Interface Encapsulation.
For more information about multilink encapsulations, see the Junos OS Services Interfaces
Library for Routing Devices.

Configuring Interface Encapsulation on PTX Series Packet Transport Routers

This topic describes how to configure interface encapsulation on PTX Series Packet
Transport Routers. Use the flexible-ethernet-services configuration statement to configure
different encapsulation for different logical interfaces under a physical interface. With
flexible Ethernet services encapsulation, you can configure each logical interface
encapsulation without range restrictions for VLAN IDs.
Supported encapsulations for physical interfaces include:

flexible-ethernet-services

ethernet-ccc

ethernet-tcc

Supported encapsulations for logical interfaces include:

ethernet

vlan-ccc

vlan-tcc

NOTE: PTX Series Packet Transport Routers do not support extended-vlan-cc

and extended-vlan-tcc encapsulation on logical interfaces. Instead, you can
configure a tag protocol ID (TPID) value of 0x9100 to achieve the same
results.

174

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

To configure flexible Ethernet services encapsulation, include the encapsulation

flexible-ethernet-services statement at the [edit interfaces et-fpc/pic/port ] hierarchy
level. For example:
interfaces {
et-fpc/pic/port {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
vlan-id 1000;
family inet {
address 11.0.0.20/24;
}
}
unit 1 {
encapsulation vlan-ccc;
vlan-id 1010;
}
unit 2 {
encapsulation vlan-tcc;
vlan-id 1020;
family tcc {
proxy {
inet-address 11.0.2.160;
}
remote {
inet-address 11.0.2.10;
}
}
}
}
}

Related
Documentation

Configuring Interface Encapsulation on Physical Interfaces on page 117

Configuring a Point-to-Point Connection

By default, all interfaces are assumed to be point-to-point connections. You must ensure
that the maximum transmission unit (MTU) sizes on both sides of the connection are
the same.
For all interfaces except aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet, you
can explicitly configure an interface to be a point-to-point connection by including the
point-to-point statement:
point-to-point;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

Copyright 2014, Juniper Networks, Inc.

175

Interfaces Fundamentals for Routing Devices

Configuring a Multipoint Connection

By default, all interfaces are assumed to be point-to-point connections. To configure an
interface to be a multipoint connection, include the multipoint statement:
multipoint;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

Configuring the PPP Restart Timers

You can configure a restart timer for the Link Control Protocol (LCP) and Network Control
Protocol (NCP) components of a PPP session. You can configure the LCP restart timer
on interfaces with PPP, PPP TCC, PPP over Ethernet, PPP over ATM, and PPP over Frame
Relay encapsulations. You can configure the NCP restart timer on interfaces with PPP
and PPP TCC encapsulations and on multilink PPP bundle interfaces.
To configure the restart timer for the NCP component of a PPP session, include the
ncp-restart-timer statement, and specify the number of milliseconds.
To configure the restart timer for the LCP component of a PPP session, include the
lcp-restart-timer statement, and specify the number of milliseconds:
lcp-restart-timer milliseconds;
ncp-restart-timer milliseconds;

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number ppp-options]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number ppp-options]

To monitor the configuration, issue the show interfaces interface-name command.

Configured options are displayed in the PPP parameters field for the physical interface.
user@host> run show interfaces t1-0/0/0:1:1.0 detail
Logical interface t1-0/0/0:1:1.0 (Index 67) (SNMP ifIndex 40)
(Generation 156)
Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps 0x4000
Encapsulation: PPP
PPP parameters:
LCP restart timer: 2000 msec
NCP restart timer: 2000 msec
Protocol inet, MTU: 1500, Generation: 163, Route table: 0
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.2, Broadcast: 1.1.1.255,

176

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

Configuring the PPP Clear Loop Detected Timer

When a Point-to-Point Protocol (PPP) session detects a loop, the loop detected flag is
set. If the flag is not cleared by the protocol after the loopback is cleared, the clear loop
detected timer clears the flag after the specified time has elapsed.
To configure the clear loop detected timer for the LCP component of a PPP session,
include the loopback-clear-timer statement, and specify the number of seconds.
loopback-clear-timer seconds;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number ppp-options]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number ppp-options]

To monitor the configuration, issue the show interfaces interface-name extensive command.

Configuring the LCP Configure-Request Maximum Sent

Link Control Protocol (LCP) Configure-Request is used to establish a link. You can
configure the maximum number of LCP Configure-Requests to send. The router stops
sending LCP Configure-Requests after the specified maximum number is sent. To
configure the LCP Configure-Request maximum, use the lcp-max-conf-req statement
at the [edit interfaces interface-name unit number ppp-options] hierarchy level. The number
range is from 0 to 65,535; where 0 specifies no limit and the LCP Configure-Request is
sent indefinitely. The default is 254.
Related
Documentation

lcp-max-conf-req on page 658

Configuring the NCP Configure-Request Maximum Sent

Network Control Protocol (NCP) Configure-Request is used to establish a link. You can
configure the maximum number of NCP Configure-Requests to send. The router stops
sending NCP Configure-Requests after the specified maximum number is sent. To
configure the NCP Configure-Request maximum, use the ncp-max-conf-req statement
at the [edit interfaces interface-name unit number ppp-options] hierarchy level. The number
range is from 0 to 65,535; where 0 specifies no limit and NCP Configure-Request is sent
indefinitely. The default is 254.
Related
Documentation

ppp-options on page 812

Copyright 2014, Juniper Networks, Inc.

177

Interfaces Fundamentals for Routing Devices

Configuring Dynamic Profiles for PPP

A dynamic profile acts as a template that enables you to create, update, or remove a
configuration that includes attributes for client access (for example, interface or protocol)
or service (for example, IGMP). Using these profiles you can consolidate all of the common
attributes of a client (and eventually a group of clients) and apply the attributes
simultaneously.
After they are created, the profiles reside in a profile library on the router. You can then
use the dynamic-profile statement to attach profiles to interfaces. To assign a dynamic
profile to a PPP interface, you can include the dynamic-profile statement at the [edit
interfaces interface-name unit logical-unit-number ppp-options] hierarchy level:
[edit interfaces interface-name unit logical-unit-number ppp-options]
dynamic-profile profile-name;

To monitor the configuration, issue the show interfaces interface-name command.

For information about dynamic profiles, see Dynamic Profiles Overview in the Junos
Subscriber Access Configuration Guide.
For information about creating dynamic profiles, see Configuring a Basic Dynamic Profile
in the Junos Subscriber Access Configuration Guide.
For information about assigning a dynamic profile to a PPP interface, see Attaching
Dynamic Profiles to Static PPP Subscriber Interfaces in the Junos Subscriber Access
Configuration Guide.

NOTE: Dynamic profiles for PPP subscribers are supported only on PPPoE
interfaces for this release.

Related
Documentation

Configuring Dynamic Authentication for PPP Subscribers

Configuring PPP CHAP Authentication

For interfaces with PPP encapsulation, you can configure interfaces to support the PPP
Challenge Handshake Authentication Protocol (CHAP), as defined in RFC 1994,
PPP Challenge Handshake Authentication Protocol (CHAP). When you enable CHAP on
an interface, the interface can authenticate its peer and can be authenticated by its peer.
For information about configuring CHAP, see Configuring the PPP Challenge Handshake
Authentication Protocol on page 126.

Configuring PPP PAP Authentication

The Password Authentication Protocol (PAP) provides a simple method for the peer to
establish its identity using a two-way handshake. This is done only upon initial link
establishment.

178

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

After the link is established, an ID and password pair is repeatedly sent by the peer to the
authenticator until authentication is acknowledged or the connection is terminated.
To configure PAP, you must create an access profile, configure tracing operations, and
configure the logical and physical interfaces.
To configure PAP on a logical interface with PPP encapsulation, include the pap statement
with options:
pap {
default-pap-password password;
local-name name;
local-password password;
passive;
}

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

For more information about configuring PAP for physical interfaces, see Configuring the
PPP Password Authentication Protocol on page 129. For information about configuring
tracing operations for the PPP protocol, see Tracing Operations of the pppd Process
on page 137.
On each logical interface with PPP encapsulation, you can perform the following tasks:

Configuring a Default PAP Password on page 179

Configuring the Local Name on page 180

Configuring the Local Password on page 180

Configuring Passive Mode on page 180

Configuring a Default PAP Password

The default PAP password is used when no matching PAP access profile exists, or if the
PAP access profile name changes during PPP link negotiation.
To configure a default PAP password for an interface, include the default-pap-password
statement:
default-pap-password password;

You can include the statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number ppp-options pap]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number ppp-options pap]

Copyright 2014, Juniper Networks, Inc.

179

Interfaces Fundamentals for Routing Devices

Configuring the Local Name

By default, when PAP is enabled on an interface, the interface uses the routers system
hostname as the name sent in PAP request and response packets.
To configure the name the interface uses in PAP request and response packets, include
the local-name statement:
local-name name;

You can include the statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number ppp-options pap]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number ppp-options pap]

Configuring the Local Password

You need to configure the password to be used for authentication.
To configure the host password for sending PAP requests, include the local-password
statement:
local-password password;

You can include the statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number ppp-options pap]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number ppp-options pap]

Configuring Passive Mode

By default, when PAP is enabled on an interface, the interface expects
authenticate-request packets from the peer. However, the interface can be configured
to send authentication request packets to the peer by configuring PAP to operate in
passive mode. In PAP passive mode, the interface sends the authenticate-request packets
to the peer only if the interface receives the PAP option from the peer during LCP
negotiationin passive mode, the interface does not authenticate the peer.
To configure the interface to authenticate with PAP in passive mode, include the passive
statement:
passive;

You can include the statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number ppp-options pap]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number ppp-options pap]

180

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

Configuring Dynamic Call Admission Control

Dynamic call admission control (CAC) provides enhanced control over WAN bandwidth.
You can configure dynamic CAC on J4350 and J6350 Services Routers supporting voice
over IP through the TGM550 media gateway module. It can be used with the following
interfaces:

Fast Ethernet and Gigabit Ethernet interfaces

ISDN BRI interfaces

Serial interfaces with PPP or Frame Relay encapsulation

When dynamic CAC is configured on an interface responsible for providing call bandwidth,
the TGM550 informs the Media Gateway Controller (MGC) of the bandwidth limit
available for voice packets on the interface and requests the MGC to block new calls
when the bandwidth is exhausted.
Dynamic CAC is useful when a primary link becomes unavailable and a backup link with
less bandwidth takes its place. Without dynamic CAC, the MGC cannot detect the
switchover to the backup link or the resulting changes in network topology and available
bandwidth. The MGC would continue to admit calls at the bandwidth of the primary link,
causing network congestion and possible jitter, delay, and loss of calls.
To configure dynamic CAC for a logical interface, include the
dynamic-call-admission-control statement, with options:
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

bearer-bandwidth-limit kilobits-per-second is the dynamic CAC bearer bandwidth limit

(BBL)the maximum bandwidth available for voice traffic on the interface. The TGM550
reports the BBL to the MGC. When the call bandwidth exceeds the BBL, the MGC blocks
new calls and alerts the user with a busy tone. The BBL range is from 0 through 9999.
The default BBL is -1, which indicates that dynamic CAC is not configured on an interface.
activation-priority priority specifies the order in which interfaces are used for providing

call bandwidth. The interface with the highest activation priority value is used as the
primary link for providing call bandwidth. If the primary link becomes unavailable, the
TGM550 switches to the next active interface with the highest activation priority value,
and so on. The activation priority value range is from 0 through 255. The default is 50.

Copyright 2014, Juniper Networks, Inc.

181

Interfaces Fundamentals for Routing Devices

NOTE: Dynamic CAC works in conjunction with the Avaya Communication

Manager (CM) Call Admission Control: Bandwidth Limitation (CAC-BL)
feature. If you configure dynamic CAC on WAN interfaces, you must also
configure CAC-BL on Avaya CM. For more information about configuring
CAC-BL, see the Administrator Guide for Avaya Communication Manager.

Example: Configuring Dynamic CAC

Configure dynamic CAC on a logical interface:
[edit]
interfaces {
t1-4/0/0 {
unit 0 {
dynamic-call-admission-control {
bearer-bandwidth-limit 900 kbps;
activation-priority 75;
}
}
}
}

Configuring Accounting for the Logical Interface

Juniper Networks routers or switches can collect various kinds of data about traffic passing
through the router or switch . You can set up one or more accounting profiles that specify
some common characteristics of this data, including the following:

The fields used in the accounting records

The number of files that the router or switch retains before discarding, and the number
of bytes per file

The period that the system uses to record the data

You configure the profiles and define a unique name for each profile using statements
at the [edit accounting-options] hierarchy level. There are two types of accounting profiles:
interface profiles and filter profiles. You configure interface profiles by including the
interface-profile statement at the [edit accounting-options] hierarchy level. You configure
filter profiles by including the filter-profile statement at the [edit accounting-options]
hierarchy level. For more information, see the Network Management Administration Guide
for Routing Devices.
You apply filter profiles by including the accounting-profile statement at the [edit firewall
filter filter-name] and [edit firewall family family filter filter-name] hierarchy levels. For
more information, see the Routing Policies, Firewall Filters, and Traffic Policers Feature
Guide for Routing Devices.

Applying an Accounting Profile to the Logical Interface

To enable accounting on a logical interface, include the accounting-profile statement:

182

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

accounting-profile name;

You can include this statement at the following hierarchy level:

[edit interfaces interface-name unit logical-unit-number]

You can also reference profiles for the physical interface; for more information, see
Configuring Accounting for the Physical Interface on page 155.

Example: Applying an Accounting Profile to the Logical Interface

Configure an accounting profile for an interface and apply it to a logical interface:
[edit]
accounting-options {
file if_stats {
size 4m files 10 transfer-interval 15;
archive-sites {
"ftp://login:password@host/path";
}
}
interface-profile if_profile {
interval 15;
file if_stats {
fields {
input-bytes;
output-bytes;
input-packets;
output-packets;
input-errors;
output-errors;
}
}
}
}
[edit interfaces ge-1/0/1 unit 1]
accounting-profile if_profile;

To reference profiles by physical interface, see Applying an Accounting Profile to the

Physical Interface on page 155. For information about configuring a firewall filter
accounting profile, see the Routing Policies, Firewall Filters, and Traffic Policers Feature
Guide for Routing Devices.

Enabling or Disabling SNMP Notifications on Logical Interfaces

By default, Simple Network Management Protocol (SNMP) notifications are sent when
the state of an interface or a connection changes. To explicitly enable these notifications
on the logical interface, include the traps statement; to disable these notifications on
the logical interface, include the no-traps statement:
(traps | no-traps);

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

Copyright 2014, Juniper Networks, Inc.

183

Interfaces Fundamentals for Routing Devices

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

NOTE: Gigabit Ethernet interfaces on J Series routers do not support SNMP.

Disabling a Logical Interface

You can unconfigure a logical interface, effectively disabling that interface, without
removing the logical interface configuration statements from the configuration. To do
this, include the disable statement:
disable;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

When an interface is disabled, a route (pointing to the reserved target REJECT) with
the IP address of the interface and a 32bit subnet mask is installed in the routing table.
See Routing Protocols.

Configuring Logical System Interface Properties

With Junos OS, you can partition a single physical router into multiple logical devices that
perform independent routing tasks. Because logical systems perform a subset of the
tasks once handled by the physical router, logical systems offer an effective way to
maximize the use of a single router.
You can include the following logical system statements:
[edit logical-systems logical-system-name]
interfaces interface-name {
unit logical-unit-number {
logical-interface-statements;
}
}
policy-options {
policy-options-statements;
}
protocols {
protocols-statements;
}
routing-instances {
routing-instances-statements;
}
routing-options {
routing-options-statements;
}

184

Copyright 2014, Juniper Networks, Inc.

Chapter 3: Configuring Logical Interface Properties

For an overview of logical systems, see the Junos OS, Release 14.2. For detailed information
about logical system configuration, see the Junos OS Routing Protocols Library for Routing
Devices. For information about configuring peer relationships between logical systems,
see Junos OS Services Interfaces Library for Routing Devices.
To configure interface properties of a logical system, you must include the following
statements at the [edit logical-systems logical-system-name] hierarchy level:
[edit logical-systems logical-system-name]
interfaces interface-name {
unit logical-unit-number {
logical-interface-statements;
}
}

Example: Configuring Logical System Interface Properties

Configure a logical systems interface properties:
[edit interfaces t3-0/0/1]
description Physical interface to be partitioned into multiple logical systems;
[edit logical-systems 1-on-t3-0/0/1]
interfaces t3-0/0/1 {
unit 1 {
family inet {
address 10.0.0.1/32 {
destination 10.0.0.2;
}
}
}
}

Related
Documentation

[edit logical-systems] Hierarchy Level

Copyright 2014, Juniper Networks, Inc.

185

Interfaces Fundamentals for Routing Devices

186

Copyright 2014, Juniper Networks, Inc.

CHAPTER 4

Configuring Protocol Family and Interface

Address Properties

Protocol Family Configuration and Interface Address Statements on page 187

Configuring the Protocol Family on page 190

Configuring the Interface Address on page 192

Configuring Default, Primary, and Preferred Addresses and Interfaces on page 197

Configuring ICCP for MC-LAG on page 199

Configuring IPCP Options on page 200

Configuring an Unnumbered Interface on page 203

Setting the Protocol MTU on page 208

Disabling the Removal of Address and Control Bytes on page 209

Disabling the Transmission of Redirect Messages on an Interface on page 210

Applying Policers on page 210

Applying a Filter to an Interface on page 219

Configuring Unicast RPF on page 224

Example: Configuring Unicast Reverse-Path-Forwarding Check on page 234

Enabling Source Class and Destination Class Usage on page 242

Understanding Targeted Broadcast on page 250

Configuring Targeted Broadcast on page 251

Protocol Family Configuration and Interface Address Statements

For each logical interface, you must configure one or more protocol families. You can
also configure interface address properties. To do this, include the following statements:
family family {
accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
address address {

Copyright 2014, Juniper Networks, Inc.

187

Interfaces Fundamentals for Routing Devices

destination address;
}
bundle interface-name;
filter {
dialer filter-name;
input filter-name;
output filter-name;
group filter-group-number;
}
interface-mode (access | trunk);
ipsec-sa sa-name;
keep-address-and-control;
mtu bytes;
multicast-only;
negotiate-address;
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>;
sampling {
direction;
}
service {
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
targeted-broadcast {
forward-and-send-to-re;
forward-only;
}
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
translate-plp-control-word-de;
vlan-id number;
vlan-id-list [number number-number];
unnumbered-address interface-name destination address destination-profile
profile-name;
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;

188

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

eui-64;
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 peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
primary;
preferred;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertise-interval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority-number number;
track {
priority-cost seconds;
priority-hold-time interface-name {
interface priority;
bandwidth-threshold bits-per-second {
priority;
}
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
virtual-address [ addresses ];
}
}
}

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

For information about interface-specific protocol and address properties, see Configuring
T1 and NxDS0 Interfaces.
Related
Documentation

Configuring T1 and NxDS0 Interfaces

Copyright 2014, Juniper Networks, Inc.

189

Interfaces Fundamentals for Routing Devices

Configuring the Protocol Family

For each logical interface, you can configure one or more of the following protocols that
run on the interface:

anyProtocol-independent family used for Layer 2 packet filtering. This option is not

supported on J Series routers and 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.

cccCircuit cross-connect (CCC). 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.

inetIP. 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).

inet6IP version 6 (IPv6). 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). For more information about IPv6, see
IPv6 Overview on page 191.

isoInternational Organization for Standardization (ISO). You must configure this

protocol family for the logical interface to support IS-IS traffic.

mlfr-uni-nniMultilink Frame Relay (MLFR) FRF.16 user-to-network network-to-network

(UNI NNI). You must configure this protocol or mlfr-end-to-end for the logical interface
to support link services and voice services bundling.

mlfr-end-to-endMultilink Frame Relay end-to-end. You must configure this protocol

or multilink Point-to-Point Protocol (MLPPP) for the logical interface to support

multilink bundling.

mlpppMLPPP. You must configure this protocol (or mlfr-end-to-end) for the logical

interface to support multilink bundling.

mplsMultiprotocol Label Switching (MPLS). You must configure this protocol family

for the logical interface to participate in an MPLS path.

tccTranslational cross-connect (TCC). You can configure this protocol family for the

logical interface of TCC physical interfaces.

tnpTrivial Network Protocol. This protocol is used to communicate between the

Routing Engine and the routers packet forwarding components. The Junos OS

190

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

automatically configures this protocol family on the routers internal interfaces only,
as discussed in Understanding Internal Ethernet Interfaces on page 12.

vplsM Series and T Series routers support Virtual Private LAN service (VPLS). 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
and the Junos OS, Release 14.2.
To configure the logical interfaces protocol family, include the family statement,
specifying the selected family. To configure more than one protocol family on a logical
interface, include multiple family statements. Following is the minimum configuration:
family family {
mtu size;
multicast-only;
no-redirects;
primary;
address address {
destination address;
broadcast address;
preferred;
primary;
}
}

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

IPv6 Overview
IP version 4 (IPv4) has been widely deployed and used to network the Internet today.
With the rapid growth of the Internet, enhancements to IPv4 are needed to support the
influx of new subscribers, Internet-enabled devices, and applications. IPv6 is designed
to enable the global expansion of the Internet.
IPv6 builds upon the functionality of IPv4, providing improvements to addressing,
configuration and maintenance, and security.
IPv6 is defined in the following documents:

RFC 2373, IP Version 6 Addressing Architecture

RFC 2460, Internet Protocol, Version 6 (IPv6)

Copyright 2014, Juniper Networks, Inc.

191

Interfaces Fundamentals for Routing Devices

IPv4-to-IPv6 Transition
Implementing IPv6 requires a transition mechanism to allow interoperability between
IPv6 nodes (both routers and hosts) and IPv4 nodes. The transition mechanism is the
key factor in the successful deployment of IPv6. Because millions of IPv4 nodes already
exist, upgrading every node to IPv6 at the same time is not feasible.
As a result, transition from IPv4 to IPv6 happens gradually, allowing nodes to be upgraded
independently and without disruption to other nodes. While a gradual upgrade occurs,
compatibility between IPv6 and IPv4 nodes becomes a requirement. Otherwise, an IPv6
node would not be able to communicate with an IPv4 node.
Transition mechanisms allow IPv6 and IPv4 nodes to coexist together in the same
network, and make gradual upgrading possible. The transition mechanism supported by
the Junos OS is tunneling. Tunnels allow IPv6 packets to be encapsulated into IPv4
headers and sent across an IPv4 infrastructure. For more information about configuring
tunnels to support IPv4-to-IPv6 transition, see the Junos OS Services Interfaces Library
for Routing Devices.

VRRP Properties
The Virtual Router Redundancy Protocol (VRRP) provides a much faster switchover to
a backup router when the default router fails. Using VRRP, a backup router can take over
a failed default router within a few seconds. This is done with minimum amount of VRRP
traffic and without any interactions with the hosts.
For more information on VRRP properties, see the Junos OS High Availability Library for
Routing Devices.
Related
Documentation

Understanding Internal Ethernet Interfaces on page 12

Configuring the Interface Address

You assign an address to an interface by specifying the address when configuring the
protocol family. For the inet or inet6 family, configure the interface IP address. For the
iso family, configure one or more addresses for the loopback interface. For the ccc,
ethernet-switching, tcc, mpls, tnp, and vpls families, you never configure an address.

NOTE: The point-to-point (PPP) address is taken from the loopback interface
address that has the primary attribute. When the loopback interface is
configured as an unnumbered interface, it takes the primary address from
the donor interface.

To assign an address to an interface, include the address statement:

address address {
broadcast address;
destination address;
destination-profile name;

192

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

eui-64;
preferred;
primary;
}

You can include these statements at the following hierarchy levels:

[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]

In the address statement, specify the network address of the interface.

For each address, you can optionally configure one or more of the following:

Broadcast address for the interface subnetSpecify this in the broadcast statement;
this applies only to Ethernet interfaces, such as the management interface fxp0, em0,
or me0 the Fast Ethernet interface, and the Gigabit Ethernet interface.

Address of the remote side of the connection (for point-to-point interfaces

only)Specify this in the destination statement.

PPP properties to the remote endSpecify this in the destination-profile statement.

You define the profile at the [edit access group-profile name ppp] hierarchy level (for
point-to-point interfaces only).

Whether the router or switch automatically generates the host number portion of
interface addressesThe eui-64 statement applies only to interfaces that carry IPv6
traffic, in which the prefix length of the address is 64 bits or less, and the low-order 64
bits of the address are zero. This option does not apply to the loopback interface (lo0)
because IPv6 addresses configured on the loopback interface must have a 128-bit
prefix length.

Whether this address is the preferred addressEach subnet on an interface has a

preferred local address. If you configure more than one address on the same subnet,
the preferred local address is chosen by default as the source address when you
originate packets to destinations on the subnet.
By default, the preferred address is the lowest-numbered address on the subnet. To
override the default and explicitly configure the preferred address, include the preferred
statement when configuring the address.

Whether this address is the primary addressEach interface has a primary local address.
If an interface has more than one address, the primary local address is used by default
as the source address when you send packets from an interface where the destination
provides no information about the subnet (for example, some ping commands).

By default, the primary address on an interface is the lowest-numbered non-127 (in other
words, non-loopback) preferred address on the interface. To override the default and
explicitly configure the preferred address, include the primary statement when configuring
the address.

Copyright 2014, Juniper Networks, Inc.

193

Interfaces Fundamentals for Routing Devices

NOTE: If you configure a duplicate IP address on an interface, even when the

earlier interface with that IP address is disabled, a Warning message is added
to the syslog and not displayed on the screen. Do not configure the same IP
address of a disabled interface on another interface.

Configuring Interface IPv4 Addresses on page 194

Configuring Interface IPv6 Addresses on page 196

Configuring Interface IPv4 Addresses

You can configure router or switch interfaces with a 32-bit IP version 4 (IPv4) address
and optionally with a destination prefix, sometimes called a subnet mask. An IPv4 address
utilizes a 4-octet dotted decimal address syntax (for example, 192.16.1.1). An IPv4 address
with destination prefix utilizes a 4-octet dotted decimal address syntax with a destination
prefix appended (for example, 192.16.1.1/30).
To configure an IPv4 address on routers and switches running Junos OS, use the edit
interface interface-name unit number family inet address a.b.c.d/nn statement at the [edit
interfaces] hierarchy level.

NOTE: Juniper Networks routers and switches support /31 destination prefixes
when used in point-to-point Ethernet configurations; however, they are not
supported by many other devices, such as hosts, hubs, routers, or switches.
You must determine if the peer system also supports /31 destination prefixes
before configuration.

Operational Behavior of Interfaces when the Same IPv4 Address is Assigned to

Them
You can configure the same IPv4 address on multiple physical interfaces. When you
assign the same IPv4 address to multiple physical interfaces, the operational behavior
of those interfaces differs, depending on whether they are implicitly or explicitly
point-to-point .

NOTE: By default, all interfaces are assumed to be point-to-point (PPP)

interfaces. For all interfaces except aggregated Ethernet, Fast Ethernet, and
Gigabit Ethernet, you can explicitly configure an interface to be a
point-to-point connection.

The following examples show the sample configuration of assigning the same IPv4
address to implicitly and explicilty point-to-point interfaces, and their corresponding
show interfaces terse command outputs to see their operational status.
Configuring same IPv4 address on implicitly PPP interfaces:
[edit]

194

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

user@host# show
ge-0/1/0 {
unit 0 {
family inet {
address 200.1.1.1/24;
}
}
}
ge-3/0/1 {
unit 0 {
family inet {
address 200.1.1.1/24;
}
}
}

The sample output shown below for the above configuration reveals that only
ge-0/1/0.0 was assigned the same IPv4 address 200.1.1.1/24 and its link state was up,
while ge-3/0/1.0 was not assigned the IPv4 address, though its link state was up,
which means that it will be operational only when it gets a unique IPv4 address other
than 200.1.1.1/24.
user@host> show interfaces terse ge*
Interface
Admin Link Proto
Local
ge-0/1/0
up
up
ge-0/1/0.0
up
up
inet
multiservice
ge-0/1/1
up
down
ge-3/0/0
up
down
ge-3/0/1
up
up
ge-3/0/1.0
up
up
inet
multiservice

Remote
200.1.1.1/24

Configuring same IPv4 address on explicitly PPP interfaces:

[edit]
user@host# show
so-0/0/0 {
unit 0 {
family inet {
address 200.1.1.1/24;
}
}
}
so-0/0/3 {
unit 0 {
family inet {
address 200.1.1.1/24;
}
}
}

The sample output shown below for the above configuration reveals that both
so-0/0/0.0 and so-0/0/3.0 were assigned the same IPv4 address 200.1.1.1/24 and
that their link states were down, which means that to make them operational atleast
one of them will have be configured with a unique IPv4 address other than 200.1.1.1/24.

Copyright 2014, Juniper Networks, Inc.

195

Interfaces Fundamentals for Routing Devices

user@host> show interfaces terse so*

Interface
Admin Link Proto
so-0/0/0
up
up
so-0/0/0.0
up
down inet
so-0/0/1
up
up
so-0/0/2
up
down
so-0/0/3
up
up
so-0/0/3.0
up
down inet
so-1/1/0
up
down
so-1/1/1
up
down
so-1/1/2
up
up
so-1/1/3
up
up
so-2/0/0
up
up
so-2/0/1
up
up
so-2/0/2
up
up
so-2/0/3
up
down

Local

Remote

200.1.1.1/24

200.1.1.1/24

Configuring Interface IPv6 Addresses

NOTE: IPv6 is not currently supported for the QFX Series.

You represent IP version 6 (IPv6) addresses in hexadecimal notation using a

colon-separated list of 16-bit values.
You assign a 128-bit IPv6 address to an interface by including the address statement:
address aaaa:bbbb:...:zzzz/nn;

NOTE: You cannot configure a subnet zero IPv6 address because RFC 2461
reserves the subnet-zero address for anycast addresses, and Junos OS
complies with the RFC.

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family inet6]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family inet6]

The double colon (::) represents all bits set to 0, as shown in the following example:
interfaces fe-0/0/1 {
unit 0 {
family inet6 {
address fec0:1:1:1::2/64;
}
}
}

196

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

NOTE: You must manually configure the router or switch advertisement and
advertise the default prefix for autoconfiguration to work on a specific
interface.

Related
Documentation

Configuring IPCP Options on page 200

Configuring Default, Primary, and Preferred Addresses and Interfaces on page 197

Configuring Default, Primary, and Preferred Addresses and Interfaces

The router has a default address and a primary interface, and interfaces have primary
and preferred addresses.
The default address of the router is used as the source address on unnumbered interfaces.
The routing protocol process tries to pick the default address as the router ID, which is
used by protocols, including OSPF and internal BGP (IBGP).
The primary interface for the router is the interface that packets go out when no interface
name is specified and when the destination address does not imply a particular outgoing
interface.
An interfaces primary address is used by default as the local address for broadcast and
multicast packets sourced locally and sent out the interface. An interfaces preferred
address is the default local address used for packets sourced by the local router to
destinations on the subnet.
The default address of the router is chosen using the following sequence:
1.

The primary address on the loopback interface lo0 that is not 127.0.0.1 is used.

2. The primary address on the primary interface is used.

To configure these addresses and interfaces, you can do the following:

Configuring the Primary Interface for the Router on page 197

Configuring the Primary Address for an Interface on page 198

Configuring the Preferred Address for an Interface on page 198

Configuring the Primary Interface for the Router

The primary interface for the router has the following characteristics:

It is the interface that packets go out when you type a command such as ping
255.255.255.255that is, a command that does not include an interface name (there
is no interface type-0/0/0.0 qualifier) and where the destination address does not
imply any particular outgoing interface.

It is the interface on which multicast applications running locally on the router, such
as Session Announcement Protocol (SAP), do group joins by default.

Copyright 2014, Juniper Networks, Inc.

197

Interfaces Fundamentals for Routing Devices

It is the interface from which the default local address is derived for packets sourced
out an unnumbered interface if there are no non-127 addresses configured on the
loopback interface, lo0.

By default, the multicast-capable interface with the lowest-index address is chosen as

the primary interface. If there is no such interface, the point-to-point interface with the
lowest index address is chosen. Otherwise, any interface with an address could be picked.
In practice, this means that, on the router, the fxp0 or em0 interface is picked by default.
To configure a different interface to be the primary interface, include the primary
statement:
primary;

You can include this statement at the following hierarchy levels:

[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]

Configuring the Primary Address for an Interface

The primary address on an interface is the address that is used by default as the local
address for broadcast and multicast packets sourced locally and sent out the interface.
For example, the local address in the packets sent by a ping interface so-0/0/0.0
255.255.255.255 command is the primary address on interface so-0/0/0.0. The primary
address flag also can be useful for selecting the local address used for packets sent out
unnumbered interfaces when multiple non-127 addresses are configured on the loopback
interface, lo0. By default, the primary address on an interface is selected as the numerically
lowest local address configured on the interface.
To set a different primary address, include the primary statement:
primary;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family family address address]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family family address address]

Configuring the Preferred Address for an Interface

The preferred address on an interface is the default local address used for packets sourced
by the local router to destinations on the subnet. By default, the numerically lowest local
address is chosen. For example, if the addresses 172.16.1.1/12, 172.16.1.2/12, and 172.16.1.3/12
are configured on the same interface, the preferred address on the subnet (by default,
172.16.1.1) would be used as a local address when you issue a ping 172.16.1.5 command.
To set a different preferred address for the subnet, include the preferred statement:
preferred;

198

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family family address address]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family family address address]

Related
Documentation

Configuring the Interface Address on page 192

Junos OS Administration Library for Routing Devices

Configuring ICCP for MC-LAG

For multichassis link aggregation (MC-LAG), you must configure Inter-Control Center
Communications Protocol (ICCP) to exchange information between two MC-LAG peers.
To enable ICCP, include the iccp statement at the [edit protocols] hierarchy level:
[edit protocols]
iccp {
authentication-key string;
local-ip-addr ipv4-address;
peer ip-address{
authentication-key string;
liveness-detection {
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}
local-ip-addr ipv4-address;
redundancy-group-id-list [ redundancy-groups ];
session-establishment-hold-time value;
}
session-establishment-hold-time value;
traceoptions;
}

The local-ip-address statement sets the source address. This could be a specified address
or interface address. The session-establishment-hold-time statement determines whether
a chassis takes over as the master at the ICCP session.
The authentication-key statement is provided by TCP Message Digest 5 (md5) option
for an ICCP TCP session. The redundancy-group-id-list statement specifies the redundancy
groups between ICCP peers and the liveness-detection hierarchy configures Bidirectional
Forwarding Detection (BFD) protocol options.

Copyright 2014, Juniper Networks, Inc.

199

Interfaces Fundamentals for Routing Devices

NOTE: ICCP is based on TCP and it uses IP routes to reach the MC-LAG peer.
To ensure that the ICCP session is as resilient as possible, we recommend
that you configure alternative routes between the ICCP end-point IP
addresses. Alternatively, configure a LAG interface that has two or more
interfaces between the MC-LAG pairs to prevent session failure when there
are no alternative routes.

For Inter-Control Center Communications Protocol (ICCP) in a multichassis link

aggregation group (MC-LAG) configured in an active-active bridge domain, you must
ensure that you configure the same peer IP address hosting the MC-LAG by including the
peer ip-address statement at the [edit protocols iccp] hierarchy level and the
multi-chassis-protection peer ip-address statement at the [edit interfaces interface-name]
hierarchy level. Multichassis protection reduces the configuration at the logical interface
level for MX Series routers with multichassis aggregated Ethernet (MC-AE) interfaces.
If the ICCP is UP and the interchassis data link (ICL) comes UP, the router configured as
standby will bring up the MC-AE interfaces shared with the peer active-active node
specified by the peer statement.
For example, the following statements illustrate how the same peer IP address can be
configured for both the ICCP peer and multichassis protection link:
set interfaces ae1 unit 0 multi-chassis-protection 10.255.34.112 interface ae0.0
set protocols iccp peer 10.255.34.112 redundancy-group-id-list 1

Although you can commit an MC-LAG configuration with various parameters defined for
it, you can configure multichassis protection between two peers without configuring the
ICCP peer address. You can also configure multiple ICCP peers and commit such a
configuration.
Related
Documentation

[edit protocols] Hierarchy Level

Configuring IPCP Options

For interfaces with PPP encapsulation, you can configure IPCP to negotiate IP address
assignments and to pass network-related information such as Windows Name Service
(WINS) and Domain Name System (DNS) servers, as defined in RFC 1877, PPP Internet
Protocol Control Protocol Extensions for Name Server Addresses.

NOTE: The Junos OS does not request name servers from the remote end;
the software does, however, send name servers to the remote end if
requested.

On the logical interface, the following PPP encapsulation types are supported:

200

atm-mlppp-llc

atm-ppp-llc

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

atm-ppp-vc-mux

multilink-ppp

When you enable a PPP interface, you can configure an IP address, enable the interface
to negotiate an IP address assignment from the remote end, or allow the interface to be
unnumbered. You can also assign a destination profile to the remote end. The destination
profile includes PPP properties, such as primary and secondary DNS and NetBIOS Name
Servers (NBNSs). These options are described in the following sections:

Configuring an IP Address for an Interface on page 201

Negotiating an IP Address Assignment from the Remote End on page 201

Configuring an Interface to Be Unnumbered on page 202

Assigning a Destination Profile to the Remote End on page 202

Configuring an IP Address for an Interface

You can configure an IP address for the interface by including the address statement in
the configuration. For more information, see Configuring the Interface Address on
page 192.
If you include the address statement in the configuration, you cannot include the
negotiate-address or unnumbered-address statement in the configuration.
When you include the address statement in the interface configuration, you can assign
PPP properties to the remote end, as shown in Assigning a Destination Profile to the
Remote End on page 202.

NOTE: The option to negotiate an IP address is not allowed in MLFR and MFR
encapsulations.

Negotiating an IP Address Assignment from the Remote End

To enable the interface to obtain an IP address from the remote end, include the
negotiate-address statement:
negotiate-address;

You can include this statement at the following hierarchy levels:

[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]

If you include the negotiate-address statement in the configuration, you cannot include
the address or unnumbered-address statement in the configuration.

Copyright 2014, Juniper Networks, Inc.

201

Interfaces Fundamentals for Routing Devices

Configuring an Interface to Be Unnumbered

To configure an interface to be unnumbered, include the unnumbered-address and
destination statements in the configuration:
unnumbered-address interface-name destination address;

The unnumbered-address statement enables the local address to be derived from the
specified interface. The interface name must include a logical unit number and must
have a configured address (see Configuring the Interface Address on page 192). Specify
the IP address of the remote interface with the destination statement.
You can include these statements at the following hierarchy levels:

[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]

If you include the unnumbered-address statement in the configuration, you cannot include
the address or negotiate-address statement in the interface configuration.
When you include the unnumbered-address statement in the interface configuration, you
can assign PPP properties to the remote end, as shown in Assigning a Destination Profile
to the Remote End on page 202.

Assigning a Destination Profile to the Remote End

When you include the address or unnumbered-address statement in the interface
configuration, you can assign PPP properties to the remote end. To do this, include the
destination-profile statement:
destination-profile name;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family inet address address]

[edit interfaces interface-name unit logical-unit-number family inet unnumbered-address

interface-name]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family inet address address]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family inet unnumbered-address interface-name]

The profile name is a PPP group profile. You define the profile by including the following
statements at the [edit access group-profile name ppp] hierarchy level:
[edit access group-profile name ppp]
framed-pool pool-id;
interface-id interface-id;
primary-dns primary-dns;
primary-wins primary-win-server;

202

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

secondary-dns secondary-dns;
secondary-wins secondary-wins;

For more information about PPP group profiles, see the Junos OS Administration Library
for Routing Devices.
Related
Documentation

Configuring the Interface Address on page 192

Junos OS Administration Library for Routing Devices

Configuring an Unnumbered Interface

When you need to conserve IP addresses, you can configure unnumbered interfaces.
Setting up an unnumbered interface enables IP processing on the interface without
assigning an explicit IP address to the interface. For IPv6, in which conserving addresses
is not a major concern, you can configure unnumbered interfaces to share the same
subnet across multiple interfaces. IPv6 unnumbered interfaces are only supported on
Ethernet interfaces. The statements you use to configure an unnumbered interface
depend on the type of interface you are configuring: a point-to-point interface or an
Ethernet interface:

Configuring an Unnumbered Point-to-Point Interface on page 203

Configuring an Unnumbered Ethernet or Demux Interface on page 204

Configuring an Unnumbered Point-to-Point Interface

To configure an unnumbered point-to-point interface, configure the protocol family, but
do not include the address statement:
family family;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

NOTE: For interfaces with PPP encapsulation, you can configure an

unnumbered interface by including the unnumbered-interface statement in
the configuration. For more information, see Configuring IPCP Options on
page 200.

When configuring unnumbered interfaces, you must ensure that a source address is
configured on some interface in the router. This address is the default address. We
recommend that you do this by assigning an address to the loopback interface (lo0), as
described in Configuring the Loopback Interface on page 295. If you configure an address
(other than a martian) on the lo0 interface, that address is always the default address,
which is preferable because the loopback interface is independent of any physical
interfaces and therefore is always accessible.

Copyright 2014, Juniper Networks, Inc.

203

Interfaces Fundamentals for Routing Devices

Example: Configuring an Unnumbered Point-to-Point Interface

Configure an unnumbered point-to-point interface:
[edit]
interfaces {
so-6/1/0 {
unit 0 {
family inet;
family iso;
}
}
}

Configuring an Unnumbered Ethernet or Demux Interface

To configure an unnumbered Ethernet or demultiplexing interface, include the
unnumbered-address statement in the configuration:
unnumbered-address interface-name;

You can include this statement at the following hierarchy levels:

[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]

For dynamic profiles, include the unnumbered-address statement at the following hierarchy
levels:

[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]

The unnumbered-address statement currently supports configuration of unnumbered

demux interfaces only for the IPv4 address family. You can configure unnumbered Ethernet
interfaces for both IPv4 and IPv6 address families.
The interface that you configure to be unnumbered borrows an assigned IP address from
another interface, and is referred to as the borrower interface. The interface from which
the IP address is borrowed is referred to as the donor interface. In the unnumbered-address
statement, interface-name specifies the donor interface. For an unnumbered Ethernet
interface, the donor interface can be an Ethernet, ATM, SONET, or loopback interface
that has a logical unit number and configured IP address and is not itself an unnumbered
interface. For an unnumbered IP demultiplexing interface, the donor interface can be an
Ethernet or loopback interface that has a logical unit number and configured IP address
and is not itself an unnumbered interface. In addition, for either Ethernet or demux, the
donor interface and the borrower interface must be members of the same routing instance
and the same logical system.

204

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

When you configure an unnumbered Ethernet or demux interface, the IP address of the
donor interface becomes the source address in packets generated by the unnumbered
interface.
You can configure a host route that points to an unnumbered Ethernet or demux interface.
For information about host routes, see the Junos OS MPLS Applications Library for Routing
Devices.
For more information, see the following sections:

Configuring a Preferred Source Address for Unnumbered Ethernet or Demux

Interfaces on page 205

Configuring Static Routes on Unnumbered Ethernet Interfaces on page 206

Restrictions for Configuring Unnumbered Ethernet Interfaces on page 206

Example: Configuring an Unnumbered Ethernet Interface on page 207

Example: Configuring the Preferred Source Address for an Unnumbered Ethernet

Interface on page 207

Example: Configuring an Unnumbered Ethernet Interface as the Next Hop for a Static
Route on page 208

For additional information about dynamic-profiles, see Dynamic Profiles Overview.

Configuring a Preferred Source Address for Unnumbered Ethernet or Demux

Interfaces
When a loopback interface with multiple secondary IP addresses is configured as the
donor interface for an unnumbered Ethernet or demux interface, you can optionally
specify any one of the loopback interfaces secondary addresses as the preferred source
address for the unnumbered Ethernet or demux interface. This feature enables you to
use an IP address other than the primary IP address on some of the unnumbered Ethernet
or demux interfaces in your network.
To configure a secondary address on a loopback donor interface as the preferred source
address for an unnumbered Ethernet or demux interface, include the
preferred-source-address option in the unnumbered-address statement:
unnumbered-address interface-name <preferred-source-address address>;

You can include this statement at the following hierarchy levels:

[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]

[edit dynamic-profiles profile-nameinterfaces interface-name unit logical-unit-number

family family]

[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family

family]

Copyright 2014, Juniper Networks, Inc.

205

Interfaces Fundamentals for Routing Devices

The following considerations apply when you configure a preferred source address on
an unnumbered Ethernet or demux interface:

The unnumbered-address statement currently supports the configuration of a preferred

source address only for the IPv4 address family for demux interfaces, and for IPv4 and
IPv6 address families for Ethernet interfaces.

If you do not specify the preferred source address, the router uses the default primary
IP address of the donor interface.

You cannot delete an address on a donor loopback interface while it is being used as
the preferred source address for an unnumbered Ethernet or demux interface.

For a configuration example that illustrates this feature, see Example: Configuring the
Preferred Source Address for an Unnumbered Ethernet Interface on page 207.
To display the preferred source address for an unnumbered Ethernet or demux interface,
use the show interfaces operational mode command. For information about using this
command, see the CLI Explorer.

Configuring Static Routes on Unnumbered Ethernet Interfaces

You can configure static routes on an unnumbered Ethernet interface. To do so, you use
the qualified-next-hop statement to specify the unnumbered Ethernet interface as the
next-hop interface for a configured static route. This feature enables you to specify
independent preferences and metrics for static routes on a next-hop basis.
For a configuration example that illustrates this feature, see Example: Configuring an
Unnumbered Ethernet Interface as the Next Hop for a Static Route on page 208.
For information about how to specify an independent preference for a static route, see
the Junos OS Routing Protocols Library for Routing Devices.

Restrictions for Configuring Unnumbered Ethernet Interfaces

The following restrictions apply when you configure unnumbered Ethernet interfaces:

206

The unnumbered-address statement currently supports the configuration of

unnumbered Ethernet interfaces for IPv4 and IPv6 address families.

You cannot assign an IP address to an Ethernet interface that is already configured as

an unnumbered interface.

The donor interface for an unnumbered Ethernet interface must have one or more
configured IP addresses.

The donor interface for an unnumbered Ethernet interfaced cannot be configured as

unnumbered.

An unnumbered Ethernet interface does not support configuration of the following

address statement options: arp, broadcast, primary, preferred, and vrrp-group. For
information about these options, see Configuring the Interface Address on page 192.

Running IGMP and PIM are supported only on unnumbered Ethernet interfaces that
directly face the host and have no downstream PIM neighbors. IGMP and PIM are not

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

supported on unnumbered Ethernet interfaces that act as upstream interfaces in a

PIM topology.

Running OSPF and IS-IS on unnumbered Ethernet interfaces is not supported. However,
you can run OSPF over unnumbered Ethernet interfaces configured as a Point-to-Point
connection.

Example: Configuring an Unnumbered Ethernet Interface

In this example, ge-1/0/0 is the unnumbered interface and ge-0/0/0 is the donor interface
from which ge-1/0/0 borrows an IP address.
interfaces {
ge-0/0/0 {
unit 0 {
family inet {
address 4.4.4.1/24;
}
}
}
ge-1/0/0 {
unit 0 {
family inet {
unnumbered-address ge-0/0/0.0;
}
}
}
}

The sample configuration that is described works correctly on M and T Series routers.
For unnumbered interfaces on MX Series routers, you must additionally configure static
routes on an unnumbered Ethernet interface by including the qualified-next-hop statement
at the [edit routing-options static route destination-prefix] hierarchy level to specify the
unnumbered Ethernet interface as the next-hop interface for a configured static route.

Example: Configuring the Preferred Source Address for an Unnumbered Ethernet

Interface
In this example, loopback interface lo0 is the donor interface from which unnumbered
Ethernet interface ge-4/0/0 borrows an IP address. The example also configures one
of the loopback interfaces secondary addresses, 3.3.3.1, as the preferred source address
for the unnumbered Ethernet interface.
interfaces {
lo0 {
unit 0 {
family inet {
address 2.2.2.1/32;
address 3.3.3.1/32;
}
}
}
}
interfaces {
ge-4/0/0 {

Copyright 2014, Juniper Networks, Inc.

207

Interfaces Fundamentals for Routing Devices

unit 0 {
family inet {
unnumbered-address lo0.0 preferred-source-address 3.3.3.1;
}
}
}
}

Example: Configuring an Unnumbered Ethernet Interface as the Next Hop for a

Static Route
In this example, ge-0/0/0 is the unnumbered interface and a loopback interface, lo0, is
the donor interface from which ge-0/0/0 borrows an IP address. The example also
configures a static route to 7.7.7.1/32 with a next hop through unnumbered interface
ge-0/0/0.0.
interfaces {
lo0 {
unit 0 {
family inet {
address 5.5.5.1/32;
address 6.6.6.1/32;
}
}
}
}
interfaces
ge-0/0/0 {
unit 0 {
family inet {
unnumbered-address lo0.0;
}
}
}
}
routing-options {
static {
route 7.7.7.1/32 {
qualified next-hop ge-0/0/0.0;
}
}
}

Related
Documentation

Configuring the Interface Address on page 192

Junos OS Administration Library for Routing Devices

Setting the Protocol MTU

When you initially configure an interface, the protocol maximum transmission unit (MTU)
is calculated automatically. If you subsequently change the media MTU, the protocol
MTU on existing address families automatically changes.
For a list of default protocol MTU values, see Configuring the Media MTU on page 93.

208

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

To modify the MTU for a particular protocol family, include the mtu statement:
mtu bytes;

You can include this statement at the following hierarchy levels:

[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]

If you increase the size of the protocol MTU, you must ensure that the size of the media
MTU is equal to or greater than the sum of the protocol MTU and the encapsulation
overhead. For a list of encapsulation overhead values, see Table 29 on page 96. If you
reduce the media MTU size, but there are already one or more address families configured
and active on the interface, you must also reduce the protocol MTU size. (You configure
the media MTU by including the mtu statement at the [edit interfaces interface-name]
hierarchy level, as discussed in Configuring the Media MTU on page 93.)

NOTE: Changing the media MTU or protocol MTU causes an interface to be

deleted and added again.

The maximum number of data-link connection identifiers (DLCIs) is determined by the

MTU on the interface. If you have keepalives enabled, the maximum number of DLCIs is
1000, with the MTU set to 5012.
The actual frames transmitted also contain cyclic redundancy check (CRC) bits, which
are not part of the MTU. For example, the default protocol MTU for a Gigabit Ethernet
interface is 1500 bytes, but the largest possible frame size is actually 1504 bytes; you
need to consider the extra bits in calculations of MTUs for interoperability.
Related
Documentation

Configuring the Media MTU on page 93

Disabling the Removal of Address and Control Bytes

For Point-to-Point Protocol (PPP) CCC-encapsulated interfaces, the address and control
bytes are removed by default before the packet is encapsulated into a tunnel.
You can disable the removal of address and control bytes. To do this, include the
keep-address-and-control statement:
keep-address-and-control;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family ccc]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family ccc]

Copyright 2014, Juniper Networks, Inc.

209

Interfaces Fundamentals for Routing Devices

Related
Documentation

keep-address-and-control on page 651

Disabling the Transmission of Redirect Messages on an Interface

By default, the interface sends protocol redirect messages. To disable the sending of
these messages on an interface, include the no-redirects statement:
no-redirects;

You can include this statement at the following hierarchy levels:

[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]

To disable the sending of protocol redirect messages for the entire router or switch,
include the no-redirects statement at the [edit system] hierarchy level.
Related
Documentation

no-redirects on page 752

Applying Policers
Policers allow you to perform simple traffic policing on specific interfaces or Layer 2
virtual private networks (VPNs) without configuring a firewall filter. To apply policers,
include the policer statement:
policer {
arp policer-template-name;
disable-arp-policer
input policer-template-name;
output policer-template-name;
}

You can include these statements at the following hierarchy levels:

[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]

In the family statement, the protocol family can be ccc, inet, inet6, mpls, tcc, or vpls.
In the arp statement, list the name of one policer template to be evaluated when Address
Resolution Protocol (ARP) packets are received on the interface. By default, an ARP
policer is installed that is shared among all the Ethernet interfaces on which you have
configured the family inet statement. If you want more stringent or lenient policing of
ARP packets, you can configure an interface-specific policer and apply it to the interface.
You configure an ARP policer just as you would configure any other policer, at the [edit
firewall policer] hierarchy level. If you apply this policer to an interface, the default ARP

210

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

packet policer is overridden. If you delete this policer, the default policer takes effect
again.
Starting with Junos OS Release 14.1, you can configure the router to disable the processing
of the specified ARP policers on the received ARP packets. Disabling ARP policers can
cause denial-of-service (DoS) attacks on the system. Due to this possibility, we
recommend that you exercise caution while disabling ARP policers. To prevent the
processing of ARP policers on the arriving ARP packets, include the disable-arp-policer
statement at the [edit interfaces interface-name unit logical-unit-number family inet policer]
or the [edit logical-systems logical-system-name interfaces interface-name unit
logical-unit-number family inet policer] hierarchy level. You can configure this statement
only for interfaces with inet address families and on MX Series routers with MPCs. When
you disable ARP policers per interface, the packets are continued to be policed by the
distributed DoS (DDoS) ARP policer. The maximum rate of is 10000 pps per FPC.
In the input statement, list the name of one policer template to be evaluated when
packets are received on the interface.
In the output statement, list the name of one policer template to be evaluated when
packets are transmitted on the interface.

NOTE: To use policing on a CCC or TCC interface, you must configure the
CCC or TCC protocol family.

You can configure a different policer on each protocol family on an interface, with one
input policer and one output policer for each family. When you apply policers, you can
configure the family ccc, inet, inet6, mpls, tcc, or vpls only, and one ARP policer for the
family inet protocol only. Each time a policer is referenced, a separate copy of the policer
is installed on the packet forwarding components for that interface.
If you apply both policers and firewall filters to an interface, input policers are evaluated
before input firewall filters, and output policers are evaluated after output firewall filters.
If you apply the policer to the interface lo0, it is applied to packets received or transmitted
by the Routing Engine.
On T Series, M120, and M320 platforms, if the interfaces are on the same FPC, the filters
or policers do not act on the sum of traffic entering and exiting the interfaces.
For more information about policers, see the Routing Policies, Firewall Filters, and Traffic
Policers Feature Guide for Routing Devices.
This section includes the following topics:

Applying Aggregate Policers on page 212

Applying Hierarchical Policers on Enhanced Intelligent Queuing PICs on page 214

Copyright 2014, Juniper Networks, Inc.

211

Interfaces Fundamentals for Routing Devices

Applying Aggregate Policers

By default, if you apply a policer to multiple protocol families on the same logical interface,
the policer restricts traffic for each protocol family individually. For example, a policer
with a 50 Mbps bandwidth limit applied to both IPv4 and IPv6 traffic would allow the
interface to accept 50 Mbps of IPv4 traffic and 50 Mbps of IPv6 traffic. If you apply an
aggregate policer, the policer would allow the interface to receive only 50 Mbps of IPv4
and IPv6 traffic combined.
To configure an aggregate policer, include the logical-interface-policer statement at the
[edit firewall policer policer-template-name] hierarchy level:
[edit firewall policer policer-template-name]
logical-interface-policer;

For the policer to be treated as an aggregate, you must apply it to multiple protocol
families on a single logical interface by including the policer statement:
policer {
arp policer-template-name;
disable-arp-policer
input policer-template-name;
output policer-template-name;
}

You can include these statements at the following hierarchy levels:

[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]

In the family statement, the protocol family can be ccc, inet, inet6, mpls, tcc, or vpls.
The protocol families on which you do not apply the policer are not affected by the policer.
For example, if you configure a single logical interface to accept MPLS, IPv4, and IPv6
traffic and you apply the logical interface policer policer1 to only the IPv4 and IPv6 protocol
families, MPLS traffic is not subject to the constraints of policer1.
If you apply policer1 to a different logical interface, there are two instances of the policer.
This means the Junos OS polices traffic on separate logical interfaces separately, not as
an aggregate, even if the same logical-interface policer is applied to multiple logical
interfaces on the same physical interface port.

Example: Applying Aggregate Policers

Configure two logical interface policers: aggregate_police1 and aggregate_police2. Apply
aggregate_police1 to IPv4 and IPv6 traffic received on logical interface fe-0/0/0.0. Apply
aggregate_police2 to CCC and MPLS traffic received on logical interface fe-0/0/0.0. This
configuration causes the software to create only one instance of aggregate_police1 and
one instance of aggregate_police2.

212

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Apply aggregate_police1 to IPv4 and IPv6 traffic received on another logical interface
fe-0/0/0.1. This configuration causes the software to create a new instance of
aggregate_police1, one that applies to unit 0 and another that applies to unit 1.
[edit firewall]
policer aggregate_police1 {
logical-interface-policer;
if-exceeding {
bandwidth-limit 100m;
burst-size-limit 500k;
}
then {
discard;
}
}
policer aggregate_police2 {
logical-interface-policer;
if-exceeding {
bandwidth-limit 10m;
burst-size-limit 200k;
}
then {
discard;
}
}
[edit interfaces fe-0/0/0]
unit 0 {
family inet {
policer {
input aggregate_police1;
}
}
family inet6 {
policer {
input aggregate_police1;
}
}
family ccc {
policer {
input aggregate_police2;
}
}
family mpls {
policer {
input aggregate_police2;
}
}
}
unit 1 {
family inet {
policer {
input aggregate_police1;
}
}
family inet6 {

Copyright 2014, Juniper Networks, Inc.

213

Interfaces Fundamentals for Routing Devices

policer {
input aggregate_police1;
}
}
}

Applying Hierarchical Policers on Enhanced Intelligent Queuing PICs

M40e, M120, and M320 edge routers and T Series core routers with Enhanced Intelligent
Queuing (IQE) PICs support hierarchical policers in the ingress direction and allow you
to apply a hierarchical policer for the premium and aggregate (premium plus normal)
traffic levels to an interface. Hierarchical policers provide cross-functionality between
the configured physical interface and the Packet Forwarding Engine.
Before you begin, there are some general restrictions that apply to hierarchical policers:

Only one type of policer can be configured for a logical or physical interface. For
example, a hierarchical policer and a regular policer in the same direction for the same
logical interface is not allowed.

The chaining of the policersthat is, applying policers to both a port and the logical
interfaces of that portis not allowed.

There is a limit of 64 policers per interface in case there is no BA classification, providing

a single policer per DLCI.

Only one kind of policer can be applied on a physical or logical interface.

The policer should be independent of BA classification. Without BA classification, all

traffic on an interface will be treated either as EF or non-EF, based on the configuration.
With BA classification, an interface can support up to 64 policers. Again, the interface
here may be a physical interface or logical interface (for example, DLCI).

With BA classification, the miscellaneous traffic (the traffic not matching with any of
the BA classification DSCP/EXP bits) will be policed as non-EF traffic. No separate
policers will be installed for this traffic.

Hierarchical Policer Overview

Hierarchical policing uses two token buckets, one for aggregate (non-EF) traffic and one
for premium (EF) traffic. Which traffic is EF and which is non-EF is determined by the
class-of-service configuration. Logically, hierarchical policing is achieved by chaining two
policers.

Figure 11: Hierarchical Policer

non-EF Traffic

Premium Policer

Aggregate Policer

g017301

EF Traffic

In the example in Figure 11 on page 214, EF traffic is policed by Premium Policer and non
EF traffic is policed by Aggregate Policer. What that means is, for EF traffic the out-of-spec

214

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

action will be the one that is configured for Premium Policer, but the in-spec EF traffic
will still consume the tokens from the Aggregate Policer.
But EF traffic will never be submitted to the out-of-spec action of the Aggregate Policer.
Also, if the out-of-spec action of the Premium Policer is not set to Discard, those
out-of-spec packets will not consume the tokens from the Aggregate Policer. Aggregate
Policer only polices the non-EF traffic. As you can see, the Aggregate Policer token bucket
can go negative, if all the tokens are consumed by the non-EF traffic and then you get
bursts of EF traffic. But that will be for a very short time, and over a period of time it will
average out. For example:

Premium Policer: Bandwidth 2 Mbps, OOS Action: Discard

Aggregate Policer: Bandwidth 10 Mbps, OOS Action: Discard

In the above case, EF traffic is guaranteed 2 Mbps and the non-EF traffic will get from 8
Mbps to 10 Mbps, depending on the input rate of the EF traffic.

Hierarchical Policing Characteristics

Hierarchical token bucket features include:

Ingress traffic is first classified into EF and non-EF traffic prior to applying a policer:

Channel number selects a shared token bucket policer:

Classification is performed by Q-tree lookup

Dual token bucket policer is divided into two single bucket policers:

Policer1EF traffic

Policer2non-EF traffic

Shared token bucket is used to police the traffic as follows:

Policer1 is set to EF rate (for example, 2 Mbps)

Policer2 is set to aggregate interface policed rate (for example, 10 Mbps).

EF traffic gets applied to Policer1.

If traffic is in-spec it is allowed to pass and decrement from both Policer1 and
Policer2.

If traffic is out-of-spec it can be discarded or marked with a new FC or loss priority.

Policer2 will not do anything with out-of-spec EF traffic.

Non-EF traffic gets applied only to Policer2.

If traffic is in-spec it is allowed to pass through and decremented Policer2.

If traffic is out-of-spec it is discarded or marked with a new FC or set with a new

drop priority.

Rate-limit the port speed to a desired rate at Layer 2

Rate-limit the EF traffic

Copyright 2014, Juniper Networks, Inc.

215

Interfaces Fundamentals for Routing Devices

Rate-limit the non-EF traffic

Policing drops counted per color

Configuring Hierarchical Policers

To configure a hierarchical policer, apply the policing-priority statement to the proper
forwarding class and configure a hierarchical policer for the aggregate and premium
level. For more information about class of service, see the Class of Service Feature Guide
for Routing Devices.

NOTE: Hierarchical policers can only be configured on SONET physical

interfaces hosted on an IQE PIC. Only aggregate and premium levels are
supported.

CoS Configuration of
Forwarding Classes for
Hierarchical Policers

[edit class-of-service forwarding-classes]

class fc1 queue-num 0 priority high policing-priority premium;
class fc2 queue-num 1 priority low policing-priority normal;
class fc3 queue-num 2 priority low policing-priority normal;
class fc4 queue-num 3 priority low policing-priority normal;

For detailed information on class-of-service configuration and statements, see the Class
of Service Feature Guide for Routing Devices.
Firewall Configuration
for Hierarchical
Policers

[edit firewall hierarchical-policer foo]

aggregate {
if-exceeding {
bandwidth-limit 70m;
burst-size-limit 1500;
}
then {
discard;
}
premium {
if-exceeding {
bandwidth-limit 50m;
burst-size-limit 1500;
}
then {
discard;
}
}

You can apply the hierarchical policer as follows:

[edit interfaces so-0/1/0 unit 0 layer-2-policer]
input-hierarchical-policer foo;

You also have the option to apply the policer at the physical port level as follows:
[edit interfaces so-0/1/0 layer-2-policer]
input-hierarchical-policer foo;

216

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Configuring a Single-Rate Two-Color Policer

You can configure a single-rate two-color policer as follows:
[edit firewall policer foo]
if-exceeding {
bandwidth-limit 50m;
burst-size-limit 1500;
}
then {
discard;
}

You can apply the policer as follows:

[edit interfaces so-0/1/0 unit 0 layer-2-policer]
input-policer foo;

You also have the option to apply the policer at the physical port level as follows:
[edit interfaces so-0/1/0 layer-2-policer]
input-policer foo;

Configuring a Single-Rate Tricolor Policer

This section describes single-rate color blind and color aware policers.
Configuring a Single-Rate Color-Blind Policer
You can configure a single-rate color blind policer as follows:
[edit firewall three-color-policer foo]
single-rate {
color-blind;
committed-information-rate 50m;
committed-burst-size 1500;
excess-burst-size 1500;
}

You can apply the single-rate color blind policer as follows:

[edit interfaces so-0/1/0 unit 0 layer-2-policer]
input-three-color foo;

You also have the option to apply the policer at the physical port level as follows:
[edit interfaces so-0/1/0 layer-2-policer]
input-three-color foo;

Configuring a Single-Rate Color-Aware Policer

You can configure a single-rate color-aware policer as follows:
[edit firewall three-color-policer bar]
single-rate {
color-aware;
committed-information-rate 50m;
committed-burst-size 1500;
excess-burst-size 1500;

Copyright 2014, Juniper Networks, Inc.

217

Interfaces Fundamentals for Routing Devices

You can apply the single-rate color-aware policer as follows:

[edit interfaces so-0/1/0 unit 0 layer-2-policer]
input-three-color foo;

You also have the option to apply the policer at the physical port level as follows:
[edit interfaces so-0/1/0 layer-2-policer]
input-three-color bar;

Configuring a Two-Rate Tricolor Marker Policer

Ingress policing is implemented using a two-rate tricolor marker (trTCM). This is done
with a dual token bucket (DTB) that maintains two rates, committed, and a peak. Egress
static policing also uses a token bucket.
The token buckets perform the following ingress policing functions:

(1K) trTCM - Dual token bucket (red, yellow, and green marking)

Policing is based on Layer 2 packet size:

Marking is color aware and color blind:

218

After +/- byte adjust offset

Color aware needs to have the color set by q-tree lookup based on:

ToS

EXP

Programmable marking actions:

Color (red, yellow, green)

Drop based on color and congestion profile

Policer is selected based on the arriving channel number:

Channel number LUT produces policer index and queue index

Multiple channels can share the same policer (LUT produces same policer index)

Support ingress policing and trTCM at the following levels:

Queue

Logical interface (ifl/DLCI)

Physical interface (ifd)

Physical port (controller ifd)

Any combinations of logical interface, physical interface, and port

Support percentage of interface speed and bits per second

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Rate limits may be applied to selected queues on ingress and on predefined queues at
egress. The token bucket operates in color aware and color blind modes (specified by
RFC 2698).
Configuring a
Color-Blind trTCM

[edit firewall three-color-policer foo]

two-rate {
color-blind;
committed-information-rate 50m;
committed-burst-size 1500;
peak-information-rate 100m;
peak-burst-size 3k;
}

You can apply the three-color two-rate color-blind policer as follows:

[edit interfaces so-0/1/0 unit 0 layer-2-policer]
input-three-color foo;

You also have the option to apply the policer at the physical port level as follows:
[edit interfaces so-0/1/0 layer-2-policer]
input-three-color foo;

Configuring a
Color-Aware trTCM

[edit firewall three-color-policer bar]

two-rate {
color-aware;
committed-information-rate 50m;
committed-burst-size 1500;
peak-information-rate 100m;
peak-burst-size 3k;
}

You can apply the three-color two-rate color-aware policer as follows:

[edit interfaces so-0/1/0 unit 0 layer-2-policer]
input-three-color bar;

You also have the option to apply the policer at the physical port level as follows:
[edit interfaces so-0/1/0 layer-2-policer]
input-three-color bar;

Related
Documentation

Class of Service Feature Guide for Routing Devices

Applying a Filter to an Interface

To apply firewall filters to an interface, include the filter statement:
filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
}

Copyright 2014, Juniper Networks, Inc.

219

Interfaces Fundamentals for Routing Devices

To apply a single filter, include the input statement:

filter {
input filter-name;
}

To apply a list of filters to evaluate packets received on an interface, include the input-list
statement.
filter {
input-list [ filter-names ];
}

Up to 16 filter names can be included in an input list.

To apply a list of filters to evaluate packets transmitted on an interface, include the
output-list statement.
filter {
output-list [ filter-names ];
}

When you apply filters using the input-list statement or the output-list statement, a new
filter is created with the name <interface-name>.<unit-direction>. This filter is exclusively
interface-specific.
You can include these statements at the following hierarchy levels:

[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]

In the family statement, the protocol family can be ccc, inet, inet6, mpls, or vpls.
In the group statement, specify the interface group number to associate with the filter.
In the input statement, list the name of one firewall filter to be evaluated when packets
are received on the interface.
In the input-list statement, list the names of filters to evaluate when packets are received
on the interface. You can include up to 16 filter names.
In the output statement, list the name of one firewall filter to be evaluated when packets
are transmitted on the interface.

NOTE: Output filters do not work for broadcast and multicast traffic, including
VPLS traffic (except in MX Series routers with MPC/MIC interfaces), as shown
in Example: Applying a Filter to an Interface on page 222.

220

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

NOTE: On an MX Series router, you cannot apply as an output filter, a firewall

filter configured at the [edit firewall filter family ccc] hierarchy level. Firewall
filters configured for the family ccc statement can be applied only as input
filters.

In the output-list statement, list the names of filters to evaluate when packets are
transmitted on the interface. You can include up to 16 filter names.
You can use the same filter one or more times. On M Series routers (except the M320
and M120 routers), if you apply a firewall filter or policer to multiple interfaces, the filter
or policer acts on the sum of traffic entering or exiting those interfaces.
On T Series, M120, and M320 routers, interfaces are distributed among multiple packet
forwarding components. Therefore, on these routers, if you apply a firewall filter or policer
to multiple interfaces, the filter or policer acts on the traffic stream entering or exiting
each interface, regardless of the sum of traffic on the multiple interfaces.
For more information on Understanding Ethernet Frame Statistics, see the MX Series
Layer 2 Configuration Guide.
If you apply the filter to the interface lo0, it is applied to packets received or transmitted
by the Routing Engine. You cannot apply MPLS filters to the management interface (fxp0
or em0) or the loopback interface (lo0).
Filters applied at the [set interfaces lo0 unit 0 family any filter input] hierarchy level are
not installed on T4000 Type 5 FPCs.
For more information about firewall filters, see the Routing Policies, Firewall Filters, and
Traffic Policers Feature Guide for Routing Devices. For more information about MPLS
filters, see the Junos OS MPLS Applications Library for Routing Devices.
See also the following sections:

Defining Interface Groups in Firewall Filters on page 221

Filter-Based Forwarding on the Output Interface on page 222

Example: Applying a Filter to an Interface on page 222

Defining Interface Groups in Firewall Filters

When applying a firewall filter, you can define an interface to be part of an interface group.
Packets received on that interface are tagged as being part of the group. You can then
match these packets using the interface-group match statement, as described in the
Routing Policies, Firewall Filters, and Traffic Policers Feature Guide for Routing Devices.
To define the interface to be part of an interface group, include the group statement:
group filter-group-number;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family family filter]

Copyright 2014, Juniper Networks, Inc.

221

Interfaces Fundamentals for Routing Devices

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family family filter]

NOTE: The number 0 is not a valid interface group number.

Filter-Based Forwarding on the Output Interface

If port-mirrored packets are to be distributed to multiple monitoring or collection
interfaces, based on patterns in packet headers, it is helpful to configure a filter-based
forwarding (FBF) filter on the port-mirroring egress interface.
When an FBF filter is installed as an output filter, a packet that is forwarded to the filter
has already undergone at least one route lookup. After the packet is classified at the
egress interface by the FBF filter, it is redirected to another routing table for additional
route lookup. To avoid packet looping inside the Packet Forwarding Engine, the route
lookup in the latter routing table (designated by an FBF routing instance) must result in
a different next hop from any next hop specified in a table that has already been applied
to the packet.
If an input interface is configured for FBF, the source lookup is disabled for those packets
headings to a different routing instance, since the routing table is not set up to handle
the source lookup.
For more information about FBF configuration, see the Junos OS Routing Protocols Library
for Routing Devices. For more information about port mirroring, see the Junos OS Services
Interfaces Library for Routing Devices.

Example: Applying a Filter to an Interface

Input Filter for VPLS
Traffic

For M Series and T Series routers only, apply an input filter to VPLS traffic. Output filters
do not work for broadcast and multicast traffic, including VPLS traffic. Note that on MX
Series routers with MPC/MIC interfaces, the VPLS filters on the egress is applicable to
broadcast, multicast, and unknown unicast traffic.

NOTE:
[edit interfaces]
fe-2/2/3 {
vlan-tagging;
encapsulation vlan-vpls;
unit 601 {
encapsulation vlan-vpls;
vlan-id 601;
family vpls {
filter {
input filter1; # Works for multicast destination MAC address
output filter1; # Does not work for multicast destination MAC address
}
}
}

222

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

}
[edit firewall]
family vpls {
filter filter1 {
term 1 {
from {
destination-mac-address {
01:00:0c:cc:cc:cd/48;
}
}
then {
discard;
}
}
term 2 {
then {
accept;
}
}
}
}

Filter-Based
Forwarding at the
Output Interface

The following example illustrates the configuration of filter-based forwarding at the

output interface. In this example, the packet flow follows this path:

1.

A packet arrives at interface fe-1/2/0.0 with source and destination addresses

10.50.200.1 and 10.50.100.1 respectively.

2. The route lookup in routing table inet.0 points to the egress interface so-0/0/3.0.
3. The output filter installed at so-0/0/3.0 redirects the packet to routing table fbf.inet.0.
4. The packet matches the entry 10.50.100.0/25 in the fbf.inet.0 table, and finally leaves

the router from interface so-2/0/0.0.

[edit interfaces]
so-0/0/3 {
unit 0 {
family inet {
filter {
output fbf;
}
address 10.50.10.2/25;
}
}
}
fe-1/2/0 {
unit 0 {
family inet {
address 10.50.50.2/25;
}
}
}
so-2/0/0 {
unit 0 {
family inet {

Copyright 2014, Juniper Networks, Inc.

223

Interfaces Fundamentals for Routing Devices

address 10.50.20.2/25;
}
}
}
[edit firewall]
filter fbf {
term 0 {
from {
source-address {
10.50.200.0/25;
}
}
then routing-instance fbf;
}
term d {
then count d;
}
}
[edit routing-instances]
fbf {
instance-type forwarding;
routing-options {
static {
route 10.50.100.0/25 next-hop so-2/0/0.0;
}
}
}
[edit routing-options]
interface-routes {
rib-group inet fbf-group;
}
static {
route 10.50.100.0/25 next-hop 10.50.10.1;
}
rib-groups {
fbf-group {
import-rib [inet.0 fbf.inet.0];
}
}

Related
Documentation

Routing Policies, Firewall Filters, and Traffic Policers Feature Guide for Routing Devices

Configuring Unicast RPF

For interfaces that carry IPv4 or IPv6 traffic, you can reduce the impact of denial of service
(DoS) attacks by configuring unicast reverse path forwarding (RPF). Unicast RPF helps
determine the source of attacks and rejects packets from unexpected source addresses
on interfaces where unicast RPF is enabled.

224

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

NOTE: If you want to configure unicast RPF, your router must be equipped
with the Internet Processor II application-specific integrated circuit (ASIC).
If you enable unicast RPF on live traffic, some packets are dropped while the
packet forwarding components are updating.
For transit packets exiting the router through the tunnel, forwarding path
features, such as RPF, forwarding table filtering, source class usage, and
destination class usage are not supported on the interfaces you configure as
the output interface for tunnel traffic. For firewall filtering, you must allow
the output tunnel packets through the firewall filter applied to input traffic
on the interface that is the next-hop interface towards the tunnel destination.

The following sections describe unicast RPF in detail:

Unicast RPF and Default Routes on page 225

Unicast RPF with Routing Asymmetry on page 227

Configuring Unicast RPF Strict Mode on page 227

Configuring Unicast RPF Loose Mode on page 229

Configuring Unicast RPF Loose Mode with Ability to Discard Packets on page 230

Configuring Unicast RPF on a VPN on page 232

Example: Configuring Unicast RPF on page 233

Unicast RPF and Default Routes

When the active route cannot be chosen from the routes in a routing table, the router
chooses a default route. A default route is equivalent to an IP address of 0.0.0.0/0. If
you configure a default route, and you configure unicast RPF on an interface that the
default route uses, unicast RPF behaves differently than it does otherwise. For information
about configuring default routes, see the Junos OS Routing Protocols Library for Routing
Devices.
To determine whether the default route uses an interface, enter the show route command:
user@host> show route address
address is the next-hop address of the configured default route. The default route uses

the interfaces shown in the output of the show route command.

The following sections describe how unicast RPF behaves when a default route uses an
interface and when a default route does not use an interface:

Unicast RPF Behavior with a Default Route on page 226

Unicast RPF Behavior Without a Default Route on page 226

Copyright 2014, Juniper Networks, Inc.

225

Interfaces Fundamentals for Routing Devices

Unicast RPF Behavior with a Default Route

On all routers except those with MPCs and the MX80 router, unicast RPF behaves as
follows if you configure a default route that uses an interface configured with unicast
RPF:

Loose modeAll packets are automatically accepted. For this reason, we recommend
that you not configure unicast RPF loose mode on interfaces that the default route
uses.

Strict modeThe packet is accepted when the source address of the packet matches
any of the routes (either default or learned) that can be originated from the interface.
Note that routes can have multiple destinations associated with them; therefore, if
one of the destinations matches the incoming interface of the packet, the packet is
accepted.

On all routers with MPCs and the MX80 router, unicast RPF behaves as follows if you
configure a default route that uses an interface configured with unicast RPF:

Loose modeAll packets except the packets whose source is learned from the default
route are accepted. All packets whose source is learned from the default route are
dropped at the Packet Forwarding Engine. The default route is treated as if the route
does not exist.

Strict modeThe packet is accepted when the source address of the packet matches
any of the routes (either default or learned) that can be originated from the interface.
Note that routes can have multiple destinations associated with them; therefore, if
one of the destinations matches the incoming interface of the packet, the packet is
accepted.

On all routers, the packet is not accepted when either of the following is true:

The source address of the packet does not match a prefix in the routing table.

The interface does not expect to receive a packet with this source address prefix.

Unicast RPF Behavior Without a Default Route

If you do not configure a default route, or if the default route does not use an interface
configured with unicast RPF, unicast RPF behaves as described in Configuring Unicast
RPF Strict Mode on page 227 and Configuring Unicast RPF Loose Mode on page 229. To
summarize, unicast RPF without a default route behaves as follows:

226

Strict modeThe packet is not accepted when either of the following is true:

The packet has a source address that does not match a prefix in the routing table.

The interface does not expect to receive a packet with this source address prefix.

Loose modeThe packet is not accepted when the packet has a source address that
does not match a prefix in the routing table.

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Unicast RPF with Routing Asymmetry

In general, we recommend that you not enable unicast RPF on interfaces that are internal
to the network because internal interfaces are likely to have routing asymmetry. Routing
asymmetry means that a packets outgoing and return paths are different. Routers in the
core of the network are more likely to have asymmetric reverse paths than routers at the
customer or provider edge. Figure 12 on page 227 shows unicast RPF in an environment
with routing asymmetry.

Figure 12: Unicast RPF with Routing Asymmetry

In Figure 12 on page 227, if you enable unicast RPF on interface so-0/0/0, traffic destined
for Router A is not rejected. If you enable unicast RPF on interface so-1/0/1, traffic from
Router A is rejected.
If you need to enable unicast RPF in an asymmetric routing environment, you can use fail
filters to allow the router to accept incoming packets that are known to be arriving by
specific paths. For an example of a fail filter that accepts packets with a specific source
and destination address, see Example: Configuring Unicast RPF on page 233.

Configuring Unicast RPF Strict Mode

In strict mode, unicast RPF checks whether the incoming packet has a source address
that matches a prefix in the routing table, and whether the interface expects to receive
a packet with this source address prefix.
If the incoming packet fails the unicast RPF check, the packet is not accepted on the
interface. When a packet is not accepted on an interface, unicast RPF counts the packet
and sends it to an optional fail filter. If the fail filter is not configured, the default action
is to silently discard the packet.
The optional fail filter allows you to apply a filter to packets that fail the unicast RPF
check. You can define the fail filter to perform any filter operation, including accepting,
rejecting, logging, sampling, or policing.
When unicast RPF is enabled on an interface, Bootstrap Protocol (BOOTP) packets and
Dynamic Host Configuration Protocol (DHCP) packets are not accepted on the interface.
To allow the interface to accept BOOTP packets and DHCP packets, you must apply a
fail filter that accepts all packets with a source address of 0.0.0.0 and a destination
address of 255.255.255.255. For a configuration example, see Example: Configuring
Unicast RPF on page 233.
For more information about unicast RPF, see the Junos OS Routing Protocols Library for
Routing Devices. For more information about defining fail filters, see the Routing Policies,
Firewall Filters, and Traffic Policers Feature Guide for Routing Devices.

Copyright 2014, Juniper Networks, Inc.

227

Interfaces Fundamentals for Routing Devices

To configure unicast RPF, include the rpf-check statement:

rpf-check <fail-filter filter-name>;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family (inet | inet6)]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family (inet | inet6)]

Using unicast RPF can have several consequences when implemented with traffic filters:

RPF fail filters are evaluated after input filters and before output filters.

If you configure a filter counter for packets dropped by an input filter, and you want to
know the total number of packets dropped, you must also configure a filter counter
for packets dropped by the RPF check.

To count packets that fail the RPF check and are accepted by the RPF fail filter, you
must configure a filter counter.

If an input filter forwards packets anywhere other than the inet.0 or inet6.0 routing
tables, the unicast RPF check is not performed.

If an input filter forwards packets anywhere other than the routing instance the input
interface is configured for, the unicast RPF check is not performed.

Example: Configuring Unicast RPF Strict Mode

Configure unicast RPF strict mode, and apply a fail filter that allows the interface to
accept BOOTP packets and DHCP packets. The filter accepts all packets with a source
address of 0.0.0.0 and a destination address of 255.255.255.255.
To configure unicast RPF in strict mode:
1.

Configure the fail filter:

[edit firewall]
filter rpf-special-case-dhcp-bootp {
term allow-dhcp-bootp {
from {
source-address {
0.0.0.0/32;
}
address {
255.255.255.255/32;
}
}
then {
count rpf-dhcp-bootp-traffic;
accept;
}
}
term default {
then {
log;

228

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

reject;
}
}
}
2. Configure unicast RPF on interfaces:

[edit]
interfaces {
so-0/0/0 {
unit 0 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp-bootp;
}
}
}
}
3. Commit the configuration.

[edit]
commit;

Configuring Unicast RPF Loose Mode

By default, unicast RPF uses strict mode. Unicast RPF loose mode is similar to unicast
RPF strict mode and has the same configuration restrictions. The only check in loose
mode is whether the packet has a source address with a corresponding prefix in the
routing table; loose mode does not check whether the interface expects to receive a
packet with a specific source address prefix. If a corresponding prefix is not found, unicast
RPF loose mode does not accept the packet. As in strict mode, loose mode counts the
failed packet and optionally forwards it to a fail filter, which either accepts, rejects, logs,
samples, or polices the packet.
To configure unicast RPF loose mode, include the mode:
mode loose;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family (inet | inet6) rpf-check

<fail-filter filter-name>]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family (inet | inet6) rpf-check <fail-filter filter-name>]

Example: Configuring Unicast RPF Loose Mode

In this example, no special configuration beyond device initialization is required.
Configure unicast RPF loose mode, and apply a fail filter that allows the interface to
accept BOOTP packets and DHCP packets. The filter accepts all packets with a source
address of 0.0.0.0 and a destination address of 255.255.255.255.

Copyright 2014, Juniper Networks, Inc.

229

Interfaces Fundamentals for Routing Devices

To configure unicast RPF in strict mode:

1.

Configure the fail filter:

[edit firewall]
filter rpf-special-case-dhcp-bootp {
term allow-dhcp-bootp {
from {
source-address {
0.0.0.0/32;
}
address {
255.255.255.255/32;
}
}
then {
count rpf-dhcp-bootp-traffic;
accept;
}
}
term default {
then {
log;
reject;
}
}
}

2. Configure unicast RPF on interfaces:

[edit]
interfaces {
so-0/0/0 {
unit 0 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp-bootp;
mode loose;
}
}
}
}
3. Commit the configuration.

[edit]
commit;

Configuring Unicast RPF Loose Mode with Ability to Discard Packets

Starting with Junos OS Release 12.1, unicast RPF loose mode has the ability to discard
packets with the source address pointing to the discard interface. This feature is supported
on MX Series routers and on T Series routers with Type 1 FPCs, Type 2 FPCs, and Type 3
FPCs. Using unicast RPF loose mode, along with Remote Triggered Black Hole (RTBH)
filtering, provides an efficient way to discard packets coming from known attack sources.
BGP policies in edge routers ensure that packets with untrusted source addresses have
their next hop set to a discard route. When a packet arrives at the router with an untrusted

230

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

source address, unicast RPF performs a route lookup of the source address. Because the
source address route points to a discard next hop, the packet is dropped and a counter
is incremented. This feature is supported on both IPv4 (inet) and IPv6 (inet6) address
families.
To configure unicast RPF loose mode with the ability to discard packets, include the
rpf-loose-mode-discard family inet statement at the [edit forwarding-options] hierarchy
level:
rpf-loose-mode-discard {
family {
inet;
}
}

Example: Configuring Unicast RPF Loose Mode with Ability to Discard Packets
In this example, no special configuration beyond device initialization is required.
Configure unicast RPF loose mode, and apply a fail filter that allows the interface to
accept BOOTP packets and DHCP packets. The filter accepts all packets with a source
address of 0.0.0.0 and a destination address of 255.255.255.255.
To configure unicast RPF loose mode with the ability to discard packets:
1.

Configure the fail filter:

[edit firewall]
filter rpf-special-case-dhcp-bootp {
term allow-dhcp-bootp {
from {
source-address {
0.0.0.0/32;
}
address {
255.255.255.255/32;
}
}
then {
count rpf-dhcp-bootp-traffic;
accept;
}
}
term default {
then {
log;
reject;
}
}
}

2. Configure unicast RPF on interfaces:

[edit]
interfaces {
so-0/0/0 {

Copyright 2014, Juniper Networks, Inc.

231

Interfaces Fundamentals for Routing Devices

unit 0 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp-bootp;
mode loose;
}
}
}
}
3. Configure the ability to discard packets.

[edit]
forwarding-options{
rpf-loose-mode-discard {
family {
inet;
}
}
}
4. Commit the configuration.

[edit]
commit;

Configuring Unicast RPF on a VPN

You can configure unicast RPF on a VPN interface by enabling unicast RPF on the interface
and including the interface statement at the [edit routing-instances routing-instance-name]
hierarchy level.
You can configure unicast RPF only on the interfaces you specify in the routing instance.
This means the following:

For Layer 3 VPNs, unicast RPF is supported on the CE router interface.

Unicast RPF is not supported on core-facing interfaces.

For virtual-router routing instances, unicast RPF is supported on all interfaces you
specify in the routing instance.

If an input filter forwards packets anywhere other than the routing instance the input
interface is configured for, the unicast RPF check is not performed.

For more information about VPNs and virtual-router routing instances, see the Junos OS
VPNs Library for Routing Devices. For more information about FBF, see the Junos OS
Routing Protocols Library for Routing Devices.

Example: Configuring Unicast RPF on a VPN

Configure unicast RPF on a Layer 3 VPN interface:
[edit interfaces]
so-0/0/0 {
unit 0 {
family inet {
rpf-check;

232

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

}
}
}
[edit routing-instance]
VPN-A {
interface so-0/0/0.0;
}

Example: Configuring Unicast RPF

Configure unicast RPF strict mode, and apply a fail filter that allows the interface to
accept BOOTP packets and DHCP packets. The filter accepts all packets with a source
address of 0.0.0.0 and a destination address of 255.255.255.255.
[edit firewall]
filter rpf-special-case-dhcp-bootp {
term allow-dhcp-bootp {
from {
source-address {
0.0.0.0/32;
}
address {
255.255.255.255/32;
}
}
then {
count rpf-dhcp-bootp-traffic;
accept;
}
}
term default {
then {
log;
reject;
}
}
}
[edit]
interfaces {
so-0/0/0 {
unit 0 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp-bootp;
}
}
}
}

Related
Documentation

unicast-reverse-path

Example: Configuring Unicast Reverse-Path-Forwarding Check on page 234

Copyright 2014, Juniper Networks, Inc.

233

Interfaces Fundamentals for Routing Devices

Example: Configuring Unicast Reverse-Path-Forwarding Check

Understanding Unicast Reverse Path Forwarding on page 234

Example: Configuring Unicast Reverse-Path-Forwarding Check on page 234

Understanding Unicast Reverse Path Forwarding

IP spoofing can occur during a denial-of-service (DoS) attack. IP spoofing allows an
intruder to pass IP packets to a destination as genuine traffic, when in fact the packets
are not actually meant for the destination. This type of spoofing is harmful because it
consumes the destinations resources.
A unicast reverse-path-forwarding (RPF) check is a tool to reduce forwarding of IP packets
that might be spoofing an address. A unicast RPF check performs a route table lookup
on an IP packets source address, and checks the incoming interface. The router or switch
determines whether the packet is arriving from a path that the sender would use to reach
the destination. If the packet is from a valid path, the router or switch forwards the packet
to the destination address. If it is not from a valid path, the router or switch discards the
packet. Unicast RPF is supported for the IPv4 and IPv6 protocol families, as well as for
the virtual private network (VPN) address family.

NOTE: Reverse path forwarding is not supported on the interfaces you

configure as tunnel sources. This affects only the transit packets exiting the
tunnel.

Example: Configuring Unicast Reverse-Path-Forwarding Check

Unicast reverse path forwarding (RPF) helps protect against DoS and DDoS attacks by
verifying the unicast source address of each packet that arrives on an ingress interface
where unicast RPF is enabled.
This example shows how to help defend ingress interfaces against denial-of-service
(DoS) and distributed denial-of-service (DDoS) attacks by configuring unicast RPF to
filter incoming traffic.

Requirements on page 234

Overview on page 234

Configuration on page 235

Verification on page 241

Requirements
In this example, no special configuration beyond device initialization is required.

Overview
Large amounts of unauthorized traffic such as attempts to flood a network with fake
(bogus) service requests in a DoS attack can consume network resources and deny

234

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

service to legitimate users. One way to help prevent DoS and DDoS attacks is to verify
that incoming traffic originates from legitimate network sources.
Unicast RPF helps ensure that a traffic source is legitimate (authorized) by comparing
the source address of each packet that arrives on an interface to the forwarding table
entry for its source address. If the device uses the same interface that the packet arrived
on to reply to the packet's source, this verifies that the packet originated from an
authorized source, and the device forwards the packet. If the device does not use the
same interface that the packet arrived on to reply to the packet's source, the packet
might have originated from an unauthorized source, and the device discards the packet.
In this example, Device B has unicast RPF configured. Device A is using OSPF to advertise
a prefix for the link that connects to Device D. OSPF is enabled on the links between
Device B and Device C and the links between Device A and Device C, but not on the links
between Device A and Device B. Therefore, Device B learns about the route to Device D
through Device C.
If ingress filtering is used in an environment where DHCP or BOOTP is used, it should be
ensured that the packets with a source address of 0.0.0.0 and a destination address of
255.255.255.255 are allowed to reach the relay agent in routers when appropriate.
This example also includes a fail filter. When a packet fails the unicast RPF check, the
fail filter is evaluated to determine if the packet should be accepted anyway. The fail
filter in this example allows Device Bs interfaces to accept Dynamic Host Configuration
Protocol (DHCP) packets. The filter accepts all packets with a source address of 0.0.0.0
and a destination address of 255.255.255.255.
Figure 13 on page 235 shows the sample network.

Figure 13: Unicast RPF Sample Topoolgy

D

E
10.0.0.22

10.0.0.18
10.0.0.17

10.0.0.21
10.0.0.1

10.0.0.2

10.0.0.5

10.0.0.6

10.0.0.10

10.0.0.13

10.0.0.14

A
10.0.0.25

C
10.0.0.26

10.0.0.30
g041186

10.0.0.29

10.0.0.9

Configuration
CLI Quick
Configuration

Device A

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.
set interfaces fe-1/2/0 unit 1 family inet address 10.0.0.1/30
set interfaces fe-0/0/2 unit 5 family inet address 10.0.0.5/30
set interfaces fe-0/0/1 unit 17 family inet address 10.0.0.17/30

Copyright 2014, Juniper Networks, Inc.

235

Interfaces Fundamentals for Routing Devices

set interfaces fe-0/1/1 unit 25 family inet address 10.0.0.25/30

set interfaces fe-1/1/1 unit 29 family inet address 10.0.0.29/30
set protocols ospf export send-direct
set protocols ospf area 0.0.0.0 interface fe-0/1/1.25
set protocols ospf area 0.0.0.0 interface fe-1/1/1.29
set policy-options policy-statement send-direct from protocol direct
set policy-options policy-statement send-direct from route-filter 10.0.0.16/30 exact
set policy-options policy-statement send-direct then accept

Device B

set interfaces fe-1/2/0 unit 2 family inet rpf-check fail-filter rpf-special-case-dhcp

set interfaces fe-1/2/0 unit 2 family inet address 10.0.0.2/30
set interfaces fe-1/1/1 unit 6 family inet rpf-check fail-filter rpf-special-case-dhcp
set interfaces fe-1/1/1 unit 6 family inet address 10.0.0.6/30
set interfaces fe-0/1/1 unit 9 family inet rpf-check fail-filter rpf-special-case-dhcp
set interfaces fe-0/1/1 unit 9 family inet address 10.0.0.9/30
set interfaces fe-0/1/0 unit 13 family inet rpf-check fail-filter rpf-special-case-dhcp
set interfaces fe-0/1/0 unit 13 family inet address 10.0.0.13/30
set protocols ospf area 0.0.0.0 interface fe-0/1/1.9
set protocols ospf area 0.0.0.0 interface fe-0/1/0.13
set routing-options forwarding-table unicast-reverse-path active-paths
set firewall filter rpf-special-case-dhcp term allow-dhcp from source-address 0.0.0.0/32
set firewall filter rpf-special-case-dhcp term allow-dhcp from destination-address
255.255.255.255/32
set firewall filter rpf-special-case-dhcp term allow-dhcp then count rpf-dhcp-traffic
set firewall filter rpf-special-case-dhcp term allow-dhcp then accept
set firewall filter rpf-special-case-dhcp term default then log
set firewall filter rpf-special-case-dhcp term default then reject

Device C

set interfaces fe-1/2/0 unit 10 family inet address 10.0.0.10/30

set interfaces fe-0/0/2 unit 14 family inet address 10.0.0.14/30
set interfaces fe-1/0/2 unit 21 family inet address 10.0.0.21/30
set interfaces fe-1/2/2 unit 26 family inet address 10.0.0.26/30
set interfaces fe-1/2/1 unit 30 family inet address 10.0.0.30/30
set protocols ospf area 0.0.0.0 interface fe-1/2/0.10
set protocols ospf area 0.0.0.0 interface fe-0/0/2.14
set protocols ospf area 0.0.0.0 interface fe-1/2/2.26
set protocols ospf area 0.0.0.0 interface fe-1/2/1.30

Device D

set interfaces fe-1/2/0 unit 18 family inet address 10.0.0.18/30

Device E

set interfaces fe-1/2/0 unit 22 family inet address 10.0.0.22/30

Configuring Device A
Step-by-Step
Procedure

The following example requires you to navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure Device A:
1.

Configure the interfaces.

[edit interfaces]
user@A# set fe-1/2/0 unit 1 family inet address 10.0.0.1/30

236

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

user@A# set fe-0/0/2 unit 5 family inet address 10.0.0.5/30

user@A# set fe-0/0/1 unit 17 family inet address 10.0.0.17/30
user@A# set fe-0/1/1 unit 25 family inet address 10.0.0.25/30
user@A# set fe-1/1/1 unit 29 family inet address 10.0.0.29/30
2.

Configure OSPF.
[edit protocols ospf]
user@A# set export send-direct
user@A# set area 0.0.0.0 interface fe-0/1/1.25
user@A# set area 0.0.0.0 interface fe-1/1/1.29

3.

Configure the routing policy.

[edit policy-options policy-statement send-direct]
user@A# set from protocol direct
user@A# set from route-filter 10.0.0.16/30 exact
user@A# set then accept

4.

If you are done configuring Device A, commit the configuration.

[edit]
user@A# commit

Configuring Device B
Step-by-Step
Procedure

The following example requires you to navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure Device B:
1.

Configure the interfaces.

[edit interfaces]
user@B# set fe-1/2/0 unit 2 family inet address 10.0.0.2/30
user@B# set fe-1/1/1 unit 6 family inet address 10.0.0.6/30
user@B# set fe-0/1/1 unit 9 family inet address 10.0.0.9/30
user@B# set fe-0/1/0 unit 13 family inet address 10.0.0.13/30

2.

Configure OSPF.
[edit protocols ospf area 0.0.0.0]
user@B# set interface fe-0/1/1.9
user@B# set interface fe-0/1/0.13

3.

Configure unicast RPF, and apply the optional fail filter.

[edit interfaces]
user@B# set fe-1/2/0 unit 2 family inet rpf-check fail-filter rpf-special-case-dhcp

Copyright 2014, Juniper Networks, Inc.

237

Interfaces Fundamentals for Routing Devices

user@B# set fe-1/1/1 unit 6 family inet rpf-check fail-filter rpf-special-case-dhcp

user@B# set fe-0/1/1 unit 9 family inet rpf-check fail-filter rpf-special-case-dhcp
user@B# set fe-0/1/0 unit 13 family inet rpf-check fail-filter rpf-special-case-dhcp
4.

(Optional) Configure the fail filter that gets evaluated if a packet fails the RPF check.
[edit firewall filter rpf-special-case-dhcp]
user@B# set term allow-dhcp from source-address 0.0.0.0/32
user@B# set term allow-dhcp from destination-address 255.255.255.255/32
user@B# set term allow-dhcp then count rpf-dhcp-traffic
user@B# set term allow-dhcp then accept
user@B# set term default then log
user@B# set term default then reject

5.

(Optional) Configure only active paths to be considered in the RPF check.

This is the default behavior.
[edit routing-options forwarding-table]
user@B# set unicast-reverse-path active-paths

6.

If you are done configuring Device B, commit the configuration.

[edit]
user@B# commit

Results
Confirm your configuration by issuing the show firewall, show interfaces, show protocols,
show routing-options, and show policy-options commands. If the output does not display
the intended configuration, repeat the instructions in this example to correct the
configuration.
Device A

238

user@A# show interfaces

fe-1/2/0 {
unit 1 {
family inet {
address 10.0.0.1/30;
}
}
}
fe-0/0/2 {
unit 5 {
family inet {
address 10.0.0.5/30;
}
}
}
fe-0/0/1 {
unit 17 {
family inet {
address 10.0.0.17/30;
}
}
}

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

fe-0/1/1 {
unit 25 {
family inet {
address 10.0.0.25/30;
}
}
}
fe-1/1/1 {
unit 29 {
family inet {
address 10.0.0.29/30;
}
}
}
user@A# show protocols
ospf {
export send-direct;
area 0.0.0.0 {
interface fe-0/1/1.25;
interface fe-1/1/1.29;
}
}
user@A# show policy-options
policy-statement send-direct {
from {
protocol direct;
route-filter 10.0.0.16/30 exact;
}
then accept;
}

Device B

user@B# show firewall

filter rpf-special-case-dhcp {
term allow-dhcp {
from {
source-address {
0.0.0.0/32;
}
destination-address {
255.255.255.255/32;
}
destination-address {
255.255.255.255/32;
}
}
then {
count rpf-dhcp-traffic;
accept;
}
}
term default {
then {
log;
reject;

Copyright 2014, Juniper Networks, Inc.

239

Interfaces Fundamentals for Routing Devices

}
}
}
user@B# show interfaces
fe-1/2/0 {
unit 2 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp;
address 10.0.0.2/30;
}
}
}
fe-1/1/1 {
unit 6 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp;
address 10.0.0.6/30;
}
}
}
fe-0/1/1 {
unit 9 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp;
address 10.0.0.9/30;
}
}
}
fe-0/1/0 {
unit 13 {
family inet {
rpf-check fail-filter rpf-special-case-dhcp;
address 10.0.0.13/30;
}
}
}
user@B# show protocols
ospf {
area 0.0.0.0 {
interface fe-0/1/1.9;
interface fe-0/1/0.13;
}
}
user@B# show routing-options
forwarding-table {
unicast-reverse-path active-paths;
}

Enter the configurations on Device C, Device D, and Device E, as shown in CLI Quick
Configuration on page 235.

240

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Verification
Confirm that the configuration is working properly.

Confirm That Unicast RPF Is Enabled on page 241

Confirm That the Source Addresses Are Blocked on page 241

Confirm That the Source Addresses Are Unblocked on page 242

Confirm That Unicast RPF Is Enabled

Purpose

Action

Meaning

Make sure that the interfaces on Device B have unicast RPF enabled.

user@B> show interfaces fe-0/1/0.13 extensive

Logical interface fe-0/1/0.13 (Index 73) (SNMP ifIndex 553) (Generation 208)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Traffic statistics:
Input bytes :
999390
Output bytes :
1230122
Input packets:
12563
Output packets:
12613
Local statistics:
Input bytes :
998994
Output bytes :
1230122
Input packets:
12563
Output packets:
12613
Transit statistics:
Input bytes :
396
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 1500, Generation: 289, Route table: 22
Flags: Sendbcast-pkt-to-re, uRPF
RPF Failures: Packets: 0, Bytes: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.0.12/30, Local: 10.0.0.13, Broadcast: 10.0.0.15,
Generation: 241

The uRPF flag confirms that unicast RPF is enabled on this interface.
Confirm That the Source Addresses Are Blocked

Purpose

Action

Use the ping command to make sure that Device B blocks traffic from unexpected source
addresses.

From Device A, ping Device Bs interfaces, using 10.0.0.17 as the source address.
user@A> ping 10.0.0.6 source 10.0.0.17
PING 10.0.0.6 (10.0.0.6): 56 data bytes
^C
--- 10.0.0.6 ping statistics --3 packets transmitted, 0 packets received, 100% packet loss

Meaning

As expected, the ping operation fails.

Copyright 2014, Juniper Networks, Inc.

241

Interfaces Fundamentals for Routing Devices

Confirm That the Source Addresses Are Unblocked

Purpose

Action

Use the ping command to make sure that Device B does not block traffic when the RPF
check is deactivated.
1.

Deactivate the RPF check on one of the interfaces.

2. Rerun the ping operation.

user@B> deactivate interfaces fe-1/1/1.6 family inet rpf-check
user@A> ping 10.0.0.6 source 10.0.0.17
PING 10.0.0.2 (10.0.0.2): 56 data bytes
64 bytes from 10.0.0.2: icmp_seq=0 ttl=63 time=1.316 ms
64 bytes from 10.0.0.2: icmp_seq=1 ttl=63 time=1.263 ms
^C
--- 10.0.0.2 ping statistics --2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.263/1.289/1.316/0.027 ms

Meaning

Related
Documentation

As expected, the ping operation succeeds.

Example: Enabling Indirect Next Hops on the Packet Forwarding Engine

Enabling Source Class and Destination Class Usage

For interfaces that carry IPv4, IPv6, MPLS, or peer AS billing traffic, you can maintain
packet counts based on the entry and exit points for traffic passing through your network.
Entry and exit points are identified by source and destination prefixes grouped into disjoint
sets defined as source classes and destination classes. You can define classes based on
a variety of parameters, such as routing neighbors, autonomous systems, and route filters.
Source class usage (SCU) counts packets sent to customers by performing lookup on
the IP source address. SCU makes it possible to track traffic originating from specific
prefixes on the provider core and destined for specific prefixes on the customer edge.
You must enable SCU accounting on both the inbound and outbound physical interfaces,
and the route for the source of the packet must be in located in the forwarding table.

NOTE: SCU and DCU accounting do not work with directly connected interface
routes. Source class usage does not count packets coming from sources with
direct routes in the forwarding table because of software architecture
limitations.

Destination class usage (DCU) counts packets from customers by performing lookup of
the IP destination address. DCU makes it possible to track traffic originating from the
customer edge and destined for specific prefixes on the provider core router.

242

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

NOTE: SCU and DCU accounting are supported on the J Series router only
for IPv4 and IPv6 traffic.

NOTE: We recommend that you stop the network traffic on an interface

before you modify the DCU or SCU configuration for that interface. Modifying
the DCU or SCU configuration without stopping the traffic might corrupt the
DCU or SCU statistics. Before you restart the traffic after modifying the
configuration, enter the clear interfaces statistics command.

Figure 14 on page 243 illustrates an Internet service provider (ISP) network. In this topology,
you can use DCU to count packets customers send to specific prefixes. For example, you
can have three counters, one per customer, that count the packets destined for prefix
210.210/16 and 220.220/16.
You can use SCU to count packets the provider sends from specific prefixes. For example,
you can count the packets sent from prefix 210.210/16 and 215.215/16 and transmitted
on a specific output interface.

Figure 14: Prefix Accounting with Source and Destination Classes

You can configure up to 126 source classes and 126 destination classes. For each interface
on which you enable destination class usage and source class usage, the Junos OS
maintains an interface-specific counter for each corresponding class up to the 126 class
limit.

NOTE: For transit packets exiting the router through the tunnel, forwarding
path features, such as RPF, forwarding table filtering, source class usage,
and destination class usage are not supported on the interfaces you configure
as the output interface for tunnel traffic. For firewall filtering, you must allow
the output tunnel packets through the firewall filter applied to input traffic
on the interface that is the next-hop interface towards the tunnel destination.

Copyright 2014, Juniper Networks, Inc.

243

Interfaces Fundamentals for Routing Devices

NOTE:
Performing DCU accounting when an output service is enabled produces
inconsistent behavior in the following configuration:

Both SCU input and DCU are configured on the packet input interface.

SCU output is configured on the packet output interface.

Interface services is enabled on the output interface.

For an incoming packet with source and destination prefixes matching the
SCU and DCU classes respectively configured in the router, both SCU and
DCU counters will be incremented. This behavior is not harmful or negative.
However, it is inconsistent with non-serviced packets, in that only the SCU
count will be incremented (because the SCU class ID will override the DCU
class ID in this case).

To enable packet counting on an interface, include the accounting statement:

accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
direction can be one of the following:

inputConfigure at least one expected ingress point.

outputConfigure at least one expected egress point.

input outputOn a single interface, configure at least one expected ingress point and

one expected egress point.

You can include these statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number family (inet | inet6 | mpls)]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number family (inet | inet6 | mpls)]

For SCU to work, you must configure at least one input interface and at least one output
interface.
The ability to count a single packet for both SCU and DCU accounting depends on the
underlying physical interface.

244

For traffic over MPC/MIC interfaces , a single incoming packet is counted for both SCU
and DCU accounting if both SCU and DCU are configured. To ensure the outgoing
packet is counted, include the source-class-usage output statements in the configuration
of the outgoing interface.

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

For traffic over DPC interfaces, an incoming packet is counted only once, and SCU
takes priority over DCU. This means that when a packet arrives on an interface on which
you include the source-class-usage input and destination-class-usage statements in
the configuration, and when the source and destination both match accounting prefixes,
the Junos OS associates the packet with the source class only.

For traffic over MPC interfaces , SCU and DCU accounting is performed after output filters
are evaluated. If a packet matches a firewall filter match condition, the packet is included
in SCU or DCU accounting except in the case where the action of the matched term is
discard.
On T Series, M120, and M320 routers, the source class and destination classes are not
carried across the router fabric. The implications of this are as follows:

On T Series, M120, and M320 routers, SCU and DCU accounting is performed before
the packet enters the fabric.

On M7i, M10i, M120, and M320 routers, on MX Series routers with non-MPC, and on T
Series routers, SCU and DCU accounting is performed before output filters are
evaluated. Consequently, if a packet matches a firewall filter match condition, the
packet is included in SCU or DCU accounting; the packet is counted for any term action
(including the discard action).

On M120, M320, and T Series routers, the destination-class and source-class statements
are supported at the [edit firewall family family-name filter filter-name term term-name
from] hierarchy level only for the filter applied to the forwarding table. On M7i, M10i,
and MX Series routers, these statements are supported.

Once you enable accounting on an interface, the Junos OS maintains packet counters
for that interface, with separate counters for inet, inet6, and mpls protocol families. You
must then configure the source class and destination class attributes in policy action
statements, which must be included in forwarding-table export policies.

NOTE: When configuring policy action statements, you can configure only
one source class for each matching route. In other words, more than one
source class cannot be applied to the same route.

In Junos OS Release 9.3 and later, you can configure SCU accounting for Layer 3 VPNs
configured with the vrf-table-label statement. Include the source-class-usage statement
at the [edit routing-instances routing-instance-name vrf-table-label] hierarchy level. The
source-class-usage statement at this hierarchy level is supported only for the virtual
routing and forwarding (VRF) instance type.

NOTE: DCU counters cannot be enabled on the label-switched interface

(LSI) that is created dynamically when the vrf-table-label statement is
configured within a VRF. For more information, see the Junos OS VPNs Library
for Routing Devices.

Copyright 2014, Juniper Networks, Inc.

245

Interfaces Fundamentals for Routing Devices

For a complete discussion about source and destination class accounting profiles, see
the Network Management Administration Guide for Routing Devices. For more information
about MPLS, see the Junos OS MPLS Applications Library for Routing Devices.

Examples: Enabling Source Class and Destination Class Usage

Configure DCU and SCU output on one interface:
[edit]
interfaces {
so-6/1/0 {
unit 0 {
family inet {
accounting {
destination-class-usage;
source-class-usage {
output;
}
}
}
}
}
}

Complete SCU
Configuration

Source routers A and B use loopback addresses as the prefixes to be monitored. Most
of the configuration tasks and actual monitoring occur on transit Router SCU.
The loopback address on Router A contains the origin of the prefix that is to be assigned
to source class A on Router SCU. However, no SCU processing happens on this router.
Therefore, configure Router A for basic OSPF routing and include your loopback interface
and interface so-0/0/2 in the OSPF process.

Router A

246

[edit]
interfaces {
so-0/0/2 {
unit 0 {
family inet {
address 10.255.50.2/24;
}
}
}
lo0 {
unit 0 {
family inet {
address 10.255.192.10/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface so-0/0/2.0;
interface lo0.0;
}
}

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Router SCU

Last, apply the policy to the forwarding table.

Router SCU handles the bulk of the activity in this example. On Router SCU, enable source
class usage on the inbound and outbound interfaces at the [edit interfaces interface-name
unit unit-number family inet accounting] hierarchy level. Make sure you specify the expected
traffic: input, output, or, in this case, both.
Next, configure a route filter policy statement that matches the prefixes of the loopback
addresses from routers A and B. Include statements in the policy that classify packets
from Router A in one group named scu-class-a and packets from Router B in a second
class named scu-class-b. Notice the efficient use of a single policy containing multiple
terms.
[edit]
interfaces {
so-0/0/1 {
unit 0 {
family inet {
accounting {
source-class-usage {
input;
output;
}
}
address 10.255.50.1/24;
}
}
}
so-0/0/3 {
unit 0 {
family inet {
accounting {
source-class-usage {
input;
output;
}
}
address 10.255.10.3/24;
}
}
}
lo0 {
unit 0 {
family inet {
address 10.255.6.111/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface so-0/0/1.0;
interface so-0/0/3.0;

Copyright 2014, Juniper Networks, Inc.

247

Interfaces Fundamentals for Routing Devices

}
}
}
routing-options {
forwarding-table {
export scu-policy;
}
}
policy-options {
policy-statement scu-policy {
term 0 {
from {
route-filter 10.255.192.0/24 orlonger;
}
then source-class scu-class-a;
}
term 1 {
from {
route-filter 10.255.165.0/24 orlonger;
}
then source-class scu-class-b;
}
}
}

Router B

Just as Router A provides a source prefix, Router B's loopback address matches the prefix
assigned to scu-class-b on Router SCU. Again, no SCU processing happens on this router,
so configure Router B for basic OSPF routing and include your loopback interface and
interface so-0/0/4 in the OSPF process.
interfaces {
so-0/0/4 {
unit 0 {
family inet {
address 10.255.10.4/24;
}
}
}
lo0 {
unit 0 {
family inet {
address 10.255.165.226/32;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface so-0/0/4.0;
interface lo0.0;
}
}
}

248

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Enabling Packet
Counting for Layer 3
VPNs

You can use SCU and DCU to count packets on Layer 3 VPNs. To enable packet counting
for Layer 3 VPN implementations at the egress point of the MPLS tunnel, you must
configure a virtual loopback tunnel interface (vt) on the PE router, map the virtual routing
and forwarding (VRF) instance type to the virtual loopback tunnel interface, and send
the traffic received from the VPN out the source class output interface, as shown in the
following example:
Configure a virtual loopback tunnel interface on a provider edge router equipped with a
tunnel PIC:
[edit interfaces]
vt-0/3/0 {
unit 0 {
family inet {
accounting {
source-class-usage {
input;
}
}
}
}
}

Map the VRF instance type to the virtual loopback tunnel interface.
In Junos OS Release 9.3 and later, you can configure SCU accounting for Layer 3 VPNs
configured with the vrf-table-label statement. Include the source-class-usage statement
at the [edit routing-instances routing-instance-name vrf-table-label] hierarchy level. The
source-class-usage statement at this hierarchy level is supported only for the virtual
routing and forwarding (VRF) instance type. DCU is not supported when the vrf-table-label
statement is configured. For more information, see the Junos OS VPNs Library for Routing
Devices.
[edit routing-instances]
VPN-A {
instance-type vrf;
interface at-2/1/1.0;
interface vt-0/3/0.0;
route-distinguisher 10.255.14.225:100;
vrf-import import-policy-A;
vrf-export export-policy-A;
protocols {
bgp {
group to-r4 {
local-address 10.27.253.1;
peer-as 400;
neighbor 10.27.253.2;
}
}
}
}

Send traffic received from the VPN out the source class output interface:
[edit interfaces]
at-2/1/0 {
unit 0 {

Copyright 2014, Juniper Networks, Inc.

249

Interfaces Fundamentals for Routing Devices

family inet {
accounting {
source-class-usage {
output;
}
}
}
}
}

For more information about VPNs, see the Junos OS VPNs Library for Routing Devices. For
more information about virtual loopback tunnel interfaces, see the Junos OS Services
Interfaces Library for Routing Devices.
Related
Documentation

accounting on page 403

destination-classes

family on page 568

forward-and-send-to-re on page 580

source-classes

targeted-broadcast on page 916

unit on page 948

Understanding Targeted Broadcast

Targeted broadcast is a process of flooding a target subnet with Layer 3 broadcast IP
packets originating from a different subnet. The intent of targeted broadcast is to flood
the target subnet with the broadcast packets on a LAN interface without broadcasting
to the entire network. Targeted broadcast is configured with various options on the egress
interface of the router or switch and the IP packets are broadcast only on the LAN (egress)
interface. Targeted broadcast helps you implement remote administration tasks such
as backups and wake-on LAN (WOL) on a LAN interface, and supports virtual routing
and forwarding (VRF) instances.
Regular Layer 3 broadcast IP packets originating from a subnet are broadcast within the
same subnet. When these IP packets reach a different subnet, they are forwarded to the
Routing Engine (to be forwarded to other applications). Because of this, remote
administration tasks such as backups cannot be performed on a particular subnet through
another subnet. As a workaround you can enable targeted broadcast, to forward broadcast
packets that originate from a different subnet.
Layer 3 broadcast IP packets have a destination IP address that is a valid broadcast
address for the target subnet. These IP packets traverse the network in the same way
as unicast IP packets until they reach the destination subnet. In the destination subnet,
if the receiving router has targeted broadcast enabled on the egress interface, the IP
packets are forwarded to an egress interface and the Routing Engine or to an egress
interface only. The IP packets are then translated into broadcast IP packets which flood
the target subnet only through the LAN interface (if there is no LAN interface, the packets
are discarded), and all hosts on the target subnet receive the IP packets. If targeted

250

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

broadcast is not enabled on the receiving router, the IP packets are treated as regular
Layer 3 broadcast IP packets and are forwarded to the Routing Engine. If targeted
broadcast is enabled without any options, the IP packets are discarded.
Targeted broadcast can be configured to forward the IP packets only to an egress
interface, which is helpful when the router is flooded with packets to process, or to both
an egress interface and the Routing Engine.

NOTE: Targeted broadcast does not work when the targeted broadcast
option forward-and-send-to-re and the traffic sampling option sampling are
configured on the same egress interface of an M320 router, a T640 router,
or an MX960 router. To overcome this scenario, you must either disable one
of the these options or enable the sampling option with the targeted broadcast
option forward-only on the egress interface. For information about traffic
sampling, see Configuring Traffic Sampling.

NOTE: Any firewall filter that is configured on the Routing Engine loopback
interface (lo0) cannot be applied to IP packets that are forwarded to the
Routing Engine as a result of a targeted broadcast. This is because broadcast
packets are forwarded as flood next hop and not as local next hop traffic,
and you can only apply a firewall filter to local next hop routes for traffic
directed towards the Routing Engine.

Related
Documentation

Configuring Targeted Broadcast on page 251

targeted-broadcast on page 916

Configuring Targeted Broadcast

The following sections explain how to configure targeted broadcast on an egress interface
and its options:

Configuring Targeted Broadcast and Its Options on page 251

Display Targeted Broadcast Configuration Options on page 252

Configuring Targeted Broadcast and Its Options

You can configure targeted broadcast on an egress interface with different options. You
can either allow the IP packets destined for a Layer 3 broadcast address to be forwarded
on the egress interface and to send a copy of the IP packets to the Routing Engine or you
can allow the IP packets to be forwarded on the egress interface only. Note that the
packets are broadcast only if the egress interface is a LAN interface.
To configure targeted broadcast and its options:
1.

Configure the physical interface.

Copyright 2014, Juniper Networks, Inc.

251

Interfaces Fundamentals for Routing Devices

[edit]
user@host# set interfaces interface-name
2. Configure the logical unit number at the [edit interfaces interface-name hierarchy level.

[edit interfaces interface-name]

user@host# set unit logical-unit-number
3. Configure the protocol family as inet at the [edit interfaces interface-name unit

interface-unit-number hierarchy level.

[edit interfaces interface-name unit interface--unit-number]
user@host# set family inet
4. Configure targeted broadcast at the [edit interfaces interface-name unit

interface-unit-number family inet hierarchy level

[edit interfaces interface-name unit interface--unit-number family inet]
user@host# set targeted-broadcast
5. Specify one of the following options as per requirement:

To allow IP packets destined for a Layer 3 broadcast address to be forwarded on

the egress interface and to send a copy of the IP packets to the Routing Engine.
[edit interfaces interface-name unit interface-unit-number family inet
targeted-broadcast]
user@host# set forward-and-send-to-re

To allow IP packets to be forwarded on the egress interface only.

[edit interfaces interface-name unit interface-unit-number family inet
targeted-broadcast]
user@host# set forward-only

NOTE: Targeted broadcast does not work when the targeted broadcast
option forward-and-send-to-re and the traffic sampling option sampling are
configured on the same egress interface of an M320 router, a T640 router,
or an MX960 router. To overcome this scenario, you must either disable one
of the these options or enable the sampling option with the targeted broadcast
option forward-only on the egress interface. For information about traffic
sampling, see Configuring Traffic Sampling.

Display Targeted Broadcast Configuration Options

The following topics display targeted broadcast configuration with its various options:

Forward IP Packets On the Egress Interface and To the Routing Engine on page 252

Forward IP Packets On the Egress Interface Only on page 253

Forward IP Packets On the Egress Interface and To the Routing Engine

Purpose

252

Display the configuration when targeted broadcast is configured on the egress interface
to forward the IP packets on the egress interface and to send a copy of the IP packets
to the Routing Engine.

Copyright 2014, Juniper Networks, Inc.

Chapter 4: Configuring Protocol Family and Interface Address Properties

Action

To display the configuration run the show command at the [edit interfaces interface-name
unit interface-unit-number family inet] where the interface name is ge-2/0/0, the unit
value is set to 0, the protocol family is set to inet.
[edit interfaces interface-name unit interface-unit-number family inet]
user@host#show
targeted-broadcast {
forward-and-send-to-re;
}

Forward IP Packets On the Egress Interface Only

Purpose

Display the configuration when targeted broadcast is configured on the egress interface
to forward the IP packets on the egress interface only.

Action

To display the configuration run the show command at the [edit interfaces interface-name
unit interface-unit-number family inet] where the interface name is ge-2/0/0, the unit
value is set to 0, the protocol family is set to inet.
[edit interfaces interface-name unit interface-unit-number family inet]
user@host#show
targeted-broadcast {
forward-only;
}

Related
Documentation

targeted-broadcast on page 916

Understanding Targeted Broadcast on page 250

Copyright 2014, Juniper Networks, Inc.

253

Interfaces Fundamentals for Routing Devices

254

Copyright 2014, Juniper Networks, Inc.

CHAPTER 5

Configuring Circuit and Translational

Cross-Connects

Circuit and Translational Cross-Connects Overview on page 255

Defining the Encapsulation for Switching Cross-Connects on page 257

Defining the Connection for Switching Cross-Connects on page 261

Configuring MPLS for Switching Cross-Connects on page 261

Configuring IS-IS or MPLS Traffic for TCC Interfaces on page 261

Configuring ATM-to-Ethernet Interworking on page 262

Example: Configuring a CCC over Frame Relay Encapsulated Interface on page 266

Example: Configuring a TCC on page 267

Example: Configuring CCC over Aggregated Ethernet on page 268

Example: Configuring a Remote LSP CCC over Aggregated Ethernet on page 270

Example: Configuring ATM-to-Ethernet Interworking on page 272

Circuit and Translational Cross-Connects Overview

Circuit cross-connect (CCC) and translational cross-connect (TCC) allow you to configure
transparent connections between two circuits, where a circuit can be a Frame Relay
data-link connection identifier (DLCI), an Asynchronous Transfer Mode (ATM) virtual
circuit (VC), a Point-to-Point Protocol (PPP) interface, a Cisco High-level Data Link
Control (HDLC) interface, or a Multiprotocol Label Switching (MPLS) label-switched
path (LSP).
Using CCC or TCC, packets from the source circuit are delivered to the destination circuit
with, at most, the Layer 2 address being changed. No other processing, such as header
checksums, time-to-live (TTL) decrementing, or protocol processing, is done.
To connect interfaces of the same type, use CCC. To connect unlike interfaces, use TCC.

Copyright 2014, Juniper Networks, Inc.

255

Interfaces Fundamentals for Routing Devices

CCC and TCC circuits fall into three categories: logical interfaces, which include ATM VCs
and Frame Relay DLCIs; physical interfaces, which include PPP and Cisco HDLC; and
paths, which include LSPs. The three circuit categories provide three types of
cross-connect:

Layer 2 switching (interface-to-interface)Cross-connects between logical interfaces

provide what is essentially Layer 2 switching.

MPLS tunneling (interface-to-LSP)Cross-connects between interfaces and LSPs

allow you to connect two distant interface circuits by creating MPLS tunnels that use
LSPs as the conduit.

LSP stitching (LSP-to-LSP)Cross-connects between LSPs provide a way to stitch

together two label-switched paths, including paths that fall in two different traffic
engineering database (TED) areas.

The cross-connect is bidirectional, so packets received on the first interface are

transmitted out the second interface, and those received on the second interface are
transmitted out the first interface.
For most CCC connections that connect interfaces, the interfaces must be of the same
type; that is, ATM to ATM, Frame Relay to Frame Relay, PPP to PPP, or Cisco HDLC to
Cisco HDLC.
ATM-to-Ethernet interworking cross-connect circuits connect logical interfaces configured
on an ATM2 and Gigabit Ethernet IQ2 and IQ2-E or 10-Gigabit Ethernet IQ2 and IQ2-E
physical interfaces.
For all TCC connections that connect interfaces, the interfaces can be of unlike types.
Mainly, TCC is used for Layer 2.5 virtual private networks (VPNs), but it can also be used
as a simple unlike circuit switch.
Switching cross-connects join logical interfaces to form what is essentially Layer 2
switching.
Figure 15 on page 256 illustrates a Layer 2 switching circuit cross-connect. In this topology,
Router A and Router C have Frame Relay connections to Router B, which is a Juniper
Networks router. CCC allows you to configure Router B to act as a Frame Relay (Layer 2)
switch. To do this, configure a circuit from Router A to Router C that passes through
Router B, effectively configuring Router B as a Frame Relay switch with respect to these
routers. This configuration allows Router B to transparently switch packets (frames)
between Router A and Router C without regard to the packets contents or the Layer 3
protocols. The only processing that Router B performs is to translate DLCI 600 to 750.

Figure 15: Layer 2 Switching Circuit Cross-Connect

If the Router AtoRouter B and Router BtoRouter C circuits are PPP, for example,
the Link Control Protocol and Network Control Protocol exchanges occur between
Router A and Router C. These messages are handled transparently by Router B, allowing

256

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

Router A and Router C to use various PPP options (such as header or address compression
and authentication) that Router B might not support. Similarly, Router A and Router C
exchange keepalives, providing circuit-to-circuit connectivity status.
You can configure Layer 2 switching cross-connects on PPP, Cisco HDLC, Frame Relay,
Ethernet CCC, Ethernet VLAN, and ATM circuits. With CCC, only like interfaces can be
connected in a single cross-connect. With TCC, unlike interfaces can be connected in a
single cross-connect. In Layer 2 switching cross-connects, the exchanges take place
between point-to-point links.
This chapter discusses the Layer 2 switching cross-connect configuration tasks. For
information about MPLS tunneling and LSP stitching, see the Junos OS MPLS Applications
Library for Routing Devices.
For information about Layer 2 and Layer 2.5 VPNs, see the Junos OS VPNs Library for
Routing Devices.
Related
Documentation

Defining the Encapsulation for Switching Cross-Connects on page 257

Defining the Connection for Switching Cross-Connects on page 261

Configuring MPLS for Switching Cross-Connects on page 261

Configuring IS-IS or MPLS Traffic for TCC Interfaces on page 261

Configuring ATM-to-Ethernet Interworking on page 262

Example: Configuring a CCC over Frame Relay Encapsulated Interface on page 266

Example: Configuring a TCC on page 267

Example: Configuring CCC over Aggregated Ethernet on page 268

Example: Configuring a Remote LSP CCC over Aggregated Ethernet on page 270

Example: Configuring ATM-to-Ethernet Interworking on page 272

Defining the Encapsulation for Switching Cross-Connects

To configure Layer 2 or Layer 2.5 switching cross-connects, configure the CCC or TCC
encapsulation on the router that is acting as the switch (Router B in Figure 15 on page 256).

NOTE: When you use CCC encapsulation, you can configure the ccc family
only. Likewise, when you use TCC encapsulation, you can configure the tcc
family only.

This section contains the following topics:

Configuring PPP or Cisco HDLC Circuits on page 258

Configuring ATM Circuits on page 258

Configuring Frame Relay Circuits on page 258

Copyright 2014, Juniper Networks, Inc.

257

Interfaces Fundamentals for Routing Devices

Configuring Ethernet CCC Circuits on page 259

Configuring Ethernet VLAN Circuits on page 260

Configuring PPP or Cisco HDLC Circuits

For PPP or Cisco HDLC circuits, specify the encapsulation by including the encapsulation
statement at the [edit interfaces interface-name] hierarchy level. This statement configures
the entire physical device. For these circuits to work, you must configure a logical interface
unit 0.
[edit interfaces interface-name]
encapsulation (ppp-ccc | cisco-hdlc-ccc | ppp-tcc | cisco-hdlc-tcc);
unit 0;

Configuring ATM Circuits

For ATM circuits, include the vpi statement [edit interfaces interface-name atm-options]
hierarchy level:
[edit interfaces at-fpc/pic/port]
atm-options {
vpi vpi-identifier;
}

On the logical interface, include the following statements:

point-to-point;
encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-tcc-vc-mux | atm-tcc-snap);
vci vpi-identifier.vci-identifier;

You can include the logical interface statements at the following hierarchy levels:

[edit interfaces at-fpc/pic/port unit logical-unit-number]

[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit

logical-unit-number]

For each VC, configure whether it is a circuit or a regular logical interface. The default
interface type is point-to-point.

Configuring Frame Relay Circuits

For Frame Relay circuits, include the encapsulation statement at the [edit interfaces
interface-name] hierarchy level:
[edit interfaces interface-name]
encapsulation type;

On the logical interface, include the following statements:

point-to-point;
encapsulation type;
dlci dlci-identifier;

You can include the logical interface statements at the following hierarchy levels:

258

[edit interfaces interface-name unit logical-unit-number]

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

The encapsulation type can be one of the following:

Flexible Frame Relay (flexible-frame-relay)Intelligent queuing (IQ) interfaces can

use flexible Frame Relay encapsulation. You use flexible Frame Relay encapsulation
when you want to configure multiple per-unit Frame Relay encapsulations. This
encapsulation type allows you to configure any combination of TCC, CCC, and standard
Frame Relay encapsulations on a single physical port. Also, each logical interface can
have any DLCI value from 1 through 1022.

Frame Relay CCC version (frame-relay-ccc)For E1, E3, SONET/SDH, T1, and T3
interfaces, this encapsulation type is the same as standard Frame Relay for DLCIs
0 through 511. DLCIs 512 through 1022 are dedicated to CCC. The logical interface must
also have frame-relay-ccc encapsulation. When you use this encapsulation type, you
can configure the ccc family only.

Frame Relay TCC version (frame-relay-tcc)Similar to Frame Relay CCC and has the
same configuration restrictions, but used for circuits with different media on either side
of the connection.

Extended CCC version (extended-frame-relay-ccc)This encapsulation type allows

you to dedicate DLCIs 1 through 1022 to CCC. The logical interface must have
frame-relay-ccc encapsulation. When you use this encapsulation type, you can configure
the ccc family only.

Extended TCC version (extended-frame-relay-tcc)Similar to extended Frame Relay

CCC, this encapsulation type allows you to dedicate DLCIs 1 through 1022 to TCC, which
is used for circuits with different media on either side of the connection.

Port CCC version (frame-relay-port-ccc)Defined in the IETF document Frame Relay

Encapsulation over Pseudo-Wires (expired December 2002). This encapsulation type
allows you to transparently carry all the DLCIs between two customer edge (CE) routers
without explicitly configuring each DLCI on the two provider edge (PE) routers with
Frame Relay transport. The connection between the two CE routers can be either
user-to-network interface (UNI) or network-to-network interface (NNI); this is
completely transparent to the PE routers. The logical interface does not require an
encapsulation statement. When you use this encapsulation type, you can configure
the ccc family only.

For each DLCI, configure whether it is a circuit or a regular logical interface. The DLCI for
regular interfaces must be from 1 through 511. For CCC and TCC interfaces, it must be
from 512 through 1022. This restriction does not apply to IQ interfaces. The default
interface type is point to point.

Configuring Ethernet CCC Circuits

You can configure Ethernet CCC encapsulation on Fast Ethernet, Gigabit Ethernet, and
aggregated Ethernet interfaces.

Copyright 2014, Juniper Networks, Inc.

259

Interfaces Fundamentals for Routing Devices

NOTE: CCC over aggregated Ethernet requires an M Series Enhanced Flexible

PIC Concentrator (FPC).

For Ethernet CCC circuits, specify the encapsulation by including the encapsulation
statement at the [edit interfaces interface-name] hierarchy level. This statement configures
the entire physical device.
[edit interfaces interface-name]
encapsulation ethernet-ccc;
unit logical-unit-number {
...
}
[edit interfaces aex]
encapsulation ethernet-ccc;
unit logical-unit-number {
...
}

Configuring Ethernet VLAN Circuits

You can configure Ethernet virtual local area network (VLAN) circuits on Fast Ethernet,
Gigabit Ethernet, and aggregated Ethernet interfaces. For Ethernet VLAN circuits, specify
the encapsulation by including the encapsulation statement at the [edit interfaces
interface-name] hierarchy level. This statement configures the entire physical device. You
must also enable VLAN tagging. To do this, include the following statements:
[edit interfaces interface-name]
vlan-tagging;
encapsulation (extended-vlan-ccc | vlan-ccc);
[edit interfaces aex]
vlan-tagging;
encapsulation vlan-ccc;

On the logical interface, include the following statements:

encapsulation vlan-ccc;
vlan-id number;

You can include the logical interface statements at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number]

[edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number]

Ethernet interfaces in VLAN mode can have multiple logical interfaces. For encapsulation
type vlan-ccc, VLAN IDs 1 through 511 are reserved for normal VLANs, and VLAN IDs
512 through 1023 are reserved for CCC VLANs. For encapsulation type extended-vlan-ccc,
VLAN IDs 1 through 4094 are valid. VLAN ID 0 is reserved for tagging the priority of frames.

260

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

Defining the Connection for Switching Cross-Connects

To configure Layer 2 switching cross-connects, define the connection between the two
circuits. You configure this on the router that is acting as the switch (Router B in Figure
15 on page 256). The connection joins the interface that comes from the circuits source
to the interface that leads to the circuits destination. When you specify the interface
names, include the logical portion of the name, which corresponds to the logical unit
number. The cross-connect is bidirectional, so packets received on the first interface are
transmitted out the second interface, and those received on the second interface are
transmitted out the first interface.
[edit protocols]
connections {
remote-interface-switch connection-name {
interface interface-name.unit-number;
}
lsp-switch connection-name {
transmit-lsp lsp-number;
receive-lsp lsp-number;
}
}

Configuring MPLS for Switching Cross-Connects

For Layer 2 switching cross-connects to work, you must configure MPLS. The following
is a minimal MPLS configuration:
[edit protocols]
mpls {
interface (interface-name | all);
}

For more information, see the Junos OS MPLS Applications Library for Routing Devices.
Related
Documentation

Defining the Connection for Switching Cross-Connects on page 261

Configuring IS-IS or MPLS Traffic for TCC Interfaces

Layer 2.5 VPNs on T Series, M120, MX Series, and M320 routers support IPv4, IS-IS, and
MPLS traffic types. By default, IPv4 traffic runs on T Series, M120, MX Series, and M320
routers and over TCC interfaces. To configure IS-IS (ISO traffic) or MPLS traffic on Layer
2.5 VPNs, you must configure the same traffic type on both ends of the Layer 2.5 VPN.

NOTE: Some platform and FPC combinations can not pass TCC encapsulated
ISO traffic. See Platforms/FPCs That Cannot Forward TCC Encapsulated ISO
Traffic for details.

Copyright 2014, Juniper Networks, Inc.

261

Interfaces Fundamentals for Routing Devices

To specify which traffic can run over a TCC interface, include the protocols statement
with the appropriate value (inet, mpls, and iso) at the [edit interfaces interface-name unit
logical-unit-number family tcc] hierarchy level:
[edit interfaces interface-name unit logical-unit-number family tcc]
protocols [ inet iso mpls ];

NOTE: Layer 2.5 VPNs running on M Series Multiservice Edge Routers support
only IPv4 traffic. IPv6 is not supported on Layer 2.5 VPNs.

When enabling ISO over a Layer 2.5 VPN that is configured on a CE Ethernet interface,
you must also include the point-to-point statement at the [edit protocols isis interface
interface-name] hierarchy level:
[edit protocols isis interface interface-name]
point-to-point;

For more information about Layer 2.5 VPNs, see the Junos OS VPNs Library for Routing
Devices and the Translational Cross-Connect and Layer 2.5 VPNs Feature Guide.

Configuring ATM-to-Ethernet Interworking

The ATM-to-Ethernet interworking feature is useful where ATM2 interfaces are used to
terminate ATM DSLAM traffic. The ATM traffic can be forwarded with encapsulation
type ccc (circuit cross-connect) to a local or remote Gigabit Ethernet IQ2 and IQ2-E or
10-Gigabit Ethernet IQ2 and IQ2-E interface or label-switched path (LSP). The ATM VPI
and VCI are converted to stacked VLAN inner and outer VLAN tags.
These ATM-to-Ethernet interworking circuits can be mapped to individual logical
interfaces configured on an ATM2 IQ interface and Gigabit Ethernet IQ2 and IQ2-E or
10-Gigabit Ethernet IQ2 and IQ2-E physical interface.
The ATM-to-Ethernet interworking cross-connect essentially provides Layer 2 switching,
and statistics are reported at the logical interface level.
During conversion from ATM to Ethernet, the least significant 12 bits of the ATM cell VCI
are copied to the Ethernet frame inner VLAN tag. Cells received on an ATM logical interface
configured with encapsulation type vlan-vci-ccc and falling within the configured VCI
range are reassembled into packets and forwarded to a designated Ethernet logical
interface that is configured with encapsulation type vlan-vci-ccc.
During conversion from Ethernet to ATM, the Ethernet frame inner VLAN tags that fall
within the configured range, are copied to the least significant 12 bits of the ATM cell VCI.
The ATM logical interface uses its configured VPI when segmenting the Ethernet packets
into cells.
ATM-to-Ethernet interworking is supported on M120, M320, and T Series routers.
ATM-to-Ethernet interworking is supported on MX Series routers with aggregated Ethernet,
Gigabit Ethernet, and 10-Gigabit Ethernet interfaces. This feature is available on all
Enhanced Queuing (EQ) DPCs and Enhanced DPCS for MX Series routers.

262

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

NOTE: This feature is not supported on MX Series routers with ATM interfaces.

For more information on MX Series ATM-to-Ethernet interworking, see the MX Series

Solutions Guide.
The following sections discuss ATM-to-Ethernet interworking:

Enabling ATM-to-Ethernet Interworking on page 263

Configuring the Ethernet Interface on page 263

Configuring Ethernet Encapsulation on page 263

Configuring the Outer VLAN Identifier on page 264

Configuring the Inner VLAN Identifier Range on page 264

Configuring the Physical Interface VPI on page 264

Configuring the ATM Logical Interface on page 265

Configuring the Protocol Family on page 265

Configuring the Logical Interface VPI on page 265

Configuring the Logical Interface VCI on page 265

Enabling ATM-to-Ethernet Interworking

To enable the ATM-to-Ethernet interworking cross-connect function, include the
vlan-vci-tagging statement at the [edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
vlan-vci-tagging;

Configuring the Ethernet Interface

Configure the Ethernet or aggregated Ethernet physical interface by including the
encapsulation statement with the vlan-vci-ccc option at the [edit interfaces interface-name]
hierarchy level:
[edit interfaces interface-name]
encapsulation vlan-vci-ccc;

When the encapsulation type vlan-vci-ccc is configured on the physical interface, all
logical interfaces configured on the Ethernet interface must also have the encapsulation
type set to vlan-vci-ccc.

Configuring Ethernet Encapsulation

Configure the Ethernet logical interface by including the encapsulation statement with
the vlan-vci-ccc option at the [edit interfaces interface-name unit logical-unit-number]
hierarchy level:
[edit interfaces interface-name unit logical-unit-number]
encapsulation vlan-vci-ccc;

Copyright 2014, Juniper Networks, Inc.

263

Interfaces Fundamentals for Routing Devices

The chassis configuration cannot contain the atm-l2circuit-mode statement if any logical
interfaces are configured with the vlan-vci-ccc encapsulation option.

Configuring the Outer VLAN Identifier

Configure the Ethernet logical interface outer VLAN ID by including the vlan-id statement
specifying the outer VLAN ID at the [edit interfaces interface-name unit logical-unit-number]
hierarchy level:
[edit interfaces interface-name unit logical-unit-number]
vlan-id outer-vlan-identifier;

It is the administrators responsibility to ensure that the outer VLAN tag and VPI match
and the inner VLAN tags fall within the VCI range of the VPI.
The allowable VPI range is from 0 to 255. So the outer VLAN tags must not be configured
for values above 255.

Configuring the Inner VLAN Identifier Range

Configure the Ethernet logical interface inner VLAN ID range by including the
inner-vlan-id-range statement and specifying the starting VLAN ID and ending VLAN ID
at the [edit interfaces interface-name unit logical-unit-number] hierarchy level:
[edit interfaces interface-name unit logical-unit-number]
inner-vlan-id-range start start-id end end-id;

VLAN IDs 0 and 4095 are reserved by IEEE 801.1q and must not be used for the inner or
outer VLAN ID.
VCIs 0 through 31 are reserved for ATM management purposes by convention. Therefore
inner VLAN IDs 1 through 31 should not be used.
VLAN ID 1 might be used by Ethernet switches for certain bridge management services,
so using VLAN ID 1 for the inner or outer VLAN ID is discouraged.

Configuring the Physical Interface VPI

Configure the ATM physical interface VPI by including the vpi statement at the [edit
interfaces interface-name atm-options] hierarchy level:
[edit interfaces interface-name atm-options]
vpi virtual-path-identifier;

VPI 0 is reserved, and must not be used.

ATM F4/F5 OAM is not supported for VPIs used in ATM-to-Ethernet interworking
cross-connects. Any F4/F5 OAM cells received are discarded.
Only one logical interface may be declared per virtual path specified in the atm-options
statement hierarchy.
It is not necessary to dedicate all the VPIs of an ATM2 interface for ATM-to-Ethernet
interworking cross-connects.

264

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

Configuring the ATM Logical Interface

Configure the ATM logical interface by including the encapsulation statement and
specifying the encapsulation type vlan-vci-ccc at the [edit interfaces interface-name unit
logical-unit-number] hierarchy level:
[edit interfaces interface-name unit logical-unit-number]
encapsulation vlan-vci-ccc;

An ATM logical interface configured with the encapsulation type vlan-vci-ccc only supports
the epd-threshold, shaping, traps | no-traps, disable, and description statements. No other
configuration statements are supported. ATM interface CoS features are not supported
by logical interfaces configured with the encapsulation type vlan-vci-ccc.
The ATM2 OC48 PIC does not support the encapsulation type vlan-vci-ccc.
The encapsulation type vlan-vci-ccc only supports the ccc protocol family. Attempts to
configure any other interface protocol family are rejected.

Configuring the Protocol Family

Configure the ATM logical interface protocol family by including the family statement
and specifying the ccc option at the [edit interfaces interface-name unit logical-unit-number]
hierarchy level:
[edit interfaces interface-name unit logical-unit-number]
family ccc;

Configuring the Logical Interface VPI

Configure the ATM logical interface virtual path identifier by including the vpi statement
at the [edit interfaces interface-name unit logical-unit-number] hierarchy level:
[edit interfaces interface-name unit logical-unit-number]
vpi virtual-path-identifier;

VPI 0 is reserved, and must not be used.

It is the administrators responsibility to ensure the outer VLAN tag and VPI match and
the inner VLAN tags fall within the VCI range of the VPI.
Once a VPI is used in an ATM-to-Ethernet interworking cross-connect, it cannot be used
with any other logical interface, even if the vpi.vci value falls outside the VCI range for
the cross-connect.

Configuring the Logical Interface VCI

Configure the ATM logical interface virtual channel identifier range by including the
vci-range statement and specifying the starting VCI and ending VCI at the [edit interfaces
interface-name unit logical-unit-number] hierarchy level:
[edit interfaces interface-name unit logical-unit-number]
vci-range start start-vci end end-vci;

Copyright 2014, Juniper Networks, Inc.

265

Interfaces Fundamentals for Routing Devices

Do not use VCIs 0 through 31, which are reserved for ATM management purposes by
convention.
Related
Documentation

encapsulation on page 543

family on page 568

inner-vlan-id-range on page 621

vci-range on page 965

vlan-id on page 966

vlan-vci-tagging on page 980

vpi (ATM CCC Cell-Relay Promiscuous Mode) on page 981

vpi (Logical Interface and Interworking) on page 983

Example: Configuring a CCC over Frame Relay Encapsulated Interface

Configure a full-duplex Layer 2 switching circuit cross-connect between Router A and
Router C, using a Juniper Networks router, Router B, as the virtual switch. See the topology
in Figure 16 on page 266.

Figure 16: Example Topology of a Switching Circuit Cross-Connect with

Frame Relay CCC Encapsulation

[edit]
interfaces {
so-1/0/0 {
encapsulation frame-relay-ccc;
unit 1 {
point-to-point;
eui-64 frame-relay-ccc;
dlci 600;
}
}
so-2/0/0 {
encapsulation frame-relay-ccc;
unit 2 {
point-to-point;
encapsulation frame-relay-ccc;
dlci 750;
}
}
}
protocols {
connections {
interface-switch router-a-router-c {

266

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

interface so-1/0/0.1;
interface so-2/0/0.2;
}
}
mpls {
interface all;
}
}

Related
Documentation

Configuring Layer 2 Switching Cross-Connects Using CCC

Example: Configuring a TCC

Configure a full-duplex switching translational cross-connect with PPP TCC encapsulation
between Router A and Router C, using a Juniper Networks router, Router B, as the virtual
switch. See the topology in Figure 17 on page 267.
In this topology, Router B has a PPP connection to Router A and an ATM connection to
Router C.

Figure 17: Layer 2.5 Switching Translational Cross-Connect

On Router A

[edit]
interfaces {
so-0/1/0 {
description "to Router B so-1/0/0";
encapsulation ppp;
unit 0 {
family inet {
address 10.1.1.1/30;
}
}
}
}

On Router B

[edit]
interfaces {
so-1/0/0 {
description "to Router A so-0/1/0";
encapsulation ppp-tcc;
unit 0 {
}
}
at-1/1/0 {
description "to Router C at-0/3/0";
atm-options {
vpi 0 maximum-vcs 2000;
}
unit 32 {

Copyright 2014, Juniper Networks, Inc.

267

Interfaces Fundamentals for Routing Devices

vci 32;
encapsulation atm-tcc-vc-mux;
}
}
}
[edit]
protocols {
mpls {
interface so-1/0/0.0;
interface at-1/1/0.32;
}
connections {
interface-switch PPP-to-ATM {
interface so-1/0/0.0;
interface at-1/1/0.32;
}
}
}

On Router C

Related
Documentation

[edit]
interfaces {
at-0/3/0 {
description "to Router B at-1/1/0";
atm-options {
vpi 0 maximum-vcs 2000;
}
unit 32 {
vci 32;
encapsulation atm-vc-mux;
family inet {
address 10.1.1.2/30;
}
}
}
}

Circuit and Translational Cross-Connects Overview on page 255

Example: Configuring CCC over Aggregated Ethernet

See the topology in Figure 18 on page 269. In this topology, CE Routers A and C have
aggregated Ethernet connections to PE Router B. With CCC, you specify that the circuit
from Router A is connected to the circuit from Router C. Router B functions as a
cross-connect switch between the two circuits. For a back-to-back connection, all VLAN
IDs must be the same on Router A through Router C. You configure Router A and Router
C as standard aggregated Ethernet interfaces. For more information about aggregated
Ethernet, see Aggregated Ethernet Interfaces Overview.

268

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

Figure 18: Interface-to-Interface Circuit Cross-Connect over Aggregated

Ethernet Interfaces

On Router A

[edit interfaces]
ae0 {
vlan-tagging;
aggregated-ether-options {
minimum-links 1;
link-speed 1g;
}
unit 0 {
vlan-id 600;
family inet {
address 192.168.1.1/30;
}
}
}

On Router B

[edit interfaces]
ae0 {
encapsulation vlan-ccc;
vlan-tagging;
aggregated-ether-options {
minimum-links 1;
link-speed 1g;
}
unit 0 { # CCC switch
encapsulation vlan-ccc;
vlan-id 600;
family ccc;
}
ae1 {
encapsulation vlan-ccc;
vlan-tagging;
aggregated-ether-options {
minimum-links 1;
link-speed 100m;
}
unit 0 {
encapsulation vlan-ccc;
vlan-id 600;
family ccc;
}
}
[edit protocols]
mpls {
interface all;
}
connections {
interface-switch layer2-cross-connect {
interface ae0.0;

Copyright 2014, Juniper Networks, Inc.

269

Interfaces Fundamentals for Routing Devices

interface ae1.0;
}
}

On Router C

[edit interfaces]
ae1 {
vlan-tagging;
aggregated-ether-options {
minimum-links 1;
link-speed 1g;
}
unit 0 {
vlan-id 600;
family inet {
address 192.168.1.2/30;
}
}
}

Example: Configuring a Remote LSP CCC over Aggregated Ethernet

See the topology in Figure 19 on page 270. In this topology, CE Router G has an aggregated
Ethernet connection to PE Router F. CE Router D has an aggregated Ethernet connection
to PE Router E. Router E and Router F have an MPLS LSP between them. With remote
CCC, you specify that the circuit from Router D is connected to the circuit from Router G.
The circuit from Router D is connected to the LSP on Router E; the circuit from Router G
is connected to the LSP on Router F. In other words, ae0.0 and ae1.0 are connected using
lsp1-2 and lsp2-1. You configure Router D and Router G as standard aggregated Ethernet
interfaces. For more information about aggregated Ethernet, see Aggregated Ethernet
Interfaces Overview.

Figure 19: Remote Interface-LSP-Interface Circuit Cross-Connect over

Aggregated Ethernet Interfaces

On Router D

270

[edit interface]
ae0 {
aggregated-ether-options {
minimum-links 1;
link-speed 1g;
lacp {
active;
periodic fast;
}
}
unit 0 {
family inet {
address 192.168.2.1/30;
}

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

}
}

On Router E

[edit interfaces]
ae0 {
encapsulation ethernet-ccc;
aggregated-ether-options {
minimum-links 1;
link-speed 100m;
lacp {
active;
periodic fast;
}
}
unit 0 {
encapsulation vlan-ccc; # default
family ccc; # default
}
}
[edit protocols]
mpls {
interface all;
}
connections {
remote-interface-switch remote-sw-1 {
interface ae0.0;
receive-lsp lsp2_1;
transmit-lsp lsp1_2;
}
}

On Router F

[edit interfaces]
ae1 {
encapsulation ethernet-ccc;
aggregated-ether-options {
minimum-links 1;
link-speed 100m;
lacp {
active;
periodic fast;
}
}
unit 0 {
encapsulation vlan-ccc; # default
family ccc; # default
}
}
[edit protocols]
mpls {
interface all;
}
connections {
remote-interface-switch remote-sw-2 {
interface ae1.0;
receive-lsp lsp1_2;

Copyright 2014, Juniper Networks, Inc.

271

Interfaces Fundamentals for Routing Devices

transmit-lsp lsp2_1;
}
}

On Router G

[edit interface]
ae1 {
aggregated-ether-options {
minimum-links 1;
link-speed 1g;
lacp {
active;
periodic fast;
}
}
unit 0 {
family inet {
address 192.168.2.2/30;
}
}
}

Example: Configuring ATM-to-Ethernet Interworking

The following example shows the configuration of the ATM and Ethernet interfaces for
an ATM-to-Ethernet interworking cross connect. In the example ATM DSLAM traffic is
terminated on an ATM2 interface. The ATM traffic is forwarded using encapsulation type
vlan-vci-ccc to a local Ethernet IQ2 and IQ2-E interface. See the topology in
Figure 20 on page 272.

Figure 20: ATM-to-Ethernet Interworking

In this example, the ATM traffic comes from the DSLAM to the router on ATM interface
at-4/0/0 and is forwarded out on Ethernet interface ge-2/2/1.
[edit interfaces]
ge-2/2/1 {
vlan-vci-tagging;
encapsulation vlan-vci-ccc;
unit 0 {
encapsulation vlan-vci-ccc;
vlan-id 100;
inner-vlan-id-range start 100 end 500;
}
}
at-4/0/0 {
atm-options {
vpi 100;

272

Copyright 2014, Juniper Networks, Inc.

Chapter 5: Configuring Circuit and Translational Cross-Connects

}
unit 0 {
encapsulation vlan-vci-ccc;
family ccc;
vpi 100;
vci-range start 100 end 500;
}
}

Related
Documentation

Configuring ATM-to-Ethernet Interworking on page 262

Copyright 2014, Juniper Networks, Inc.

273

Interfaces Fundamentals for Routing Devices

274

Copyright 2014, Juniper Networks, Inc.

PART 2

Special Router Interfaces

Configuring Discard Interfaces on page 277

Configuring IP Demultiplexing Interfaces on page 281

Configuring the Loopback Interface on page 295

Copyright 2014, Juniper Networks, Inc.

275

Interfaces Fundamentals for Routing Devices

276

Copyright 2014, Juniper Networks, Inc.

CHAPTER 6

Configuring Discard Interfaces

Discard Interfaces Overview on page 277

Configuring Discard Interfaces on page 278

Discard Interfaces Overview

The discardinterface dsc is not a physical interface, but a virtual interface that discards
packets.
The following sections explain discard interfaces in detail:

Understanding Discard Interfaces on page 277

Guidelines to Follow When Configuring a Discard Interface on page 277

Understanding Discard Interfaces

The discard interface allows you to identify the ingress point of a denial-of-service (DoS)
attack. When your network is under attack, the target host IP address is identified, and
the local policy forwards attacking packets to the discard interface. When traffic is routed
out of the discard interface, the traffic is silently discarded.
The discard interface allows you to protect a network from DoS attacks by identifying
the target IP address that is being attacked and configuring a policy to forward all packets
to a discard interface. All packets forwarded to the discard interface are dropped. See
Example: Forwarding Packets to the Discard Interface.
You can configure the inet family protocol on the discard interface, which allows you to
apply an output filter to the interface. If you apply an output filter to the interface, the
action specified by the filter is executed before the traffic is discarded.
Once you configure a discard interface, you must then configure a local policy to forward
attacking traffic to the discard interface.

Guidelines to Follow When Configuring a Discard Interface

Keep the following guidelines in mind when configuring the discard interface:

Only the logical interface unit 0 is supported.

The filter and address statements are optional.

Copyright 2014, Juniper Networks, Inc.

277

Interfaces Fundamentals for Routing Devices

Related
Documentation

Although you can configure an input filter and a filter group, these configuration
statements have no effect because traffic is not transmitted from the discard interface.

The discard interface does not support class of service (CoS).

Configuring Discard Interfaces on page 278

Example: Forwarding Packets to the Discard Interface

Configuring Discard Interfaces

The discard (dsc) interface is not a physical interface, but a virtual interface that discards
packets. You can configure one discard interface. This interface allows you to identify
the ingress point of a denial-of-service (DoS) attack. When your network is under attack,
the target host IP address is identified, and the local policy forwards attacking packets
to the discard interface. Traffic routed out of the discard interface is silently discarded.
The following sections explain how to forward packets to a discard interface by configuring
a discard interface with an input filter and an output filter along with an input policy to
associate a community with the discard interface and an output policy to set up the
community on the routes injected into the network:

Configure a Discard Interface on page 278

Configure an Input Policy on page 279

Configure an Output Policy on page 279

Configure a Discard Interface

To configure a discard interface:
1.

In configuration mode, go to the [edit interfaces] hierarchy level.

[edit]
user@host# edit interfaces

2. Configure the discard interface.

[edit interfaces]
user@host# edit dsc
3. Configure the logical interface and the protocol family.

[edit interfaces dsc]

user@host# edit unit 0 family family
4. Configure an input filter to be applied to received packets.

[edit interfaces dsc unit 0 family family]

user@host# set filter input filter-name
5. Configure an output filter to be applied to transmitted packets.

[edit interfaces dsc unit 0 family family]

user@host# set filter output filter-name
6. Configure the interface IP address and the remote address of the connection.

278

Copyright 2014, Juniper Networks, Inc.

Chapter 6: Configuring Discard Interfaces

[edit interfaces dsc unit 0 family family]

user@host# set address ip-address destination ip-address
7. Commit the configuration and go to the top of the hierarchy level.

[edit interfaces dsc unit 0 family family]

user@host# commit
user@host# top

Configure an Input Policy

You must configure an input policy to associate a community with the discard interface.
To configure an input policy to associate a community with the discard interface:
1.

In configuration mode, go to the [edit policy-options] hierarchy level.

[edit]
user@host# edit policy-options

2. Configure the BGP community information option with a name and configure the

number of community members as needed.

[edit policy-options]
user@host# set community community-name members community-id
3. Configure a routing policy.

[edit policy-options]
user@host# edit policy-statement statement-name
4. Configure a policy term with a name.

[edit policy-options policy-statement statement-name]

user@host# edit term term-variable
5. Configure the conditions to match the source of a route with the from statement with

the BGP community members.

[edit policy-options policy-statement statement-name term term-variable]
user@host# set from community value
6. Configure the action that is to be taken when the if and to conditions match with the

then statement. In this case, configure the next-hop address of the remote end of the

point-to-point interface and accept the action.

[edit policy-options policy-statement statement-name term term-variable]
user@host# set then next-hop address
user@host# set then accept
7. Commit the configuration and go to the top of the hierarchy level.

[edit policy-options policy-statement statement-name term term-variable]

user@host# commit
user@host# top

Configure an Output Policy

You must configure an output policy to set up the community on the routes injected into
the network.

Copyright 2014, Juniper Networks, Inc.

279

Interfaces Fundamentals for Routing Devices

To configure an output policy.

1.

In configuration mode, go to the [edit policy-options] hierarchy level.

[edit]
user@host# edit policy-options

2. Configure a routing policy.

[edit policy-options]
user@host# edit policy-statement statement-name
3. Configure a policy term with a name.

[edit policy-options policy-statement statement-name]

user@host# edit term term-variable
4. Configure the list of prefix-lists of routes to match with a name.

[edit policy-options policy-statement statement-name term term-variable]

user@host# set from prefix-list name
5. Configure the action that is to be taken when the if and to conditions match with the

then statement. In this case, configure the BGP community properties (set, add, and

delete) associated with a route.

[edit policy-options policy-statement statement-name term term-variable]
user@host# set then community (set | add | delete) community-name
6. Commit the configuration and go to the top of the hierarchy level.

[edit interfaces dsc unit 0 family family]

user@host# commit
user@host# top

Related
Documentation

280

Discard Interfaces Overview on page 277

Copyright 2014, Juniper Networks, Inc.

CHAPTER 7

Configuring IP Demultiplexing Interfaces

Demultiplexing Interface Overview on page 281

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Demultiplexing Interface Overview

Demultiplexing (demux) interfaces are logical interfaces that share a common, underlying
interface. You can create logical subscriber interfaces using static or dynamic
demultiplexing interfaces. In addition, you can use IP demultiplexing interfaces or VLAN
demultiplexing interfaces when creating logical subscriber interfaces.
Demux interfaces are supported on M120 or MX Series routers only.
Demux interfaces support only Gigabit Ethernet, Fast Ethernet, 10-Gigabit Ethernet, or
aggregated Ethernet underlying interfaces.

NOTE: You can also configure demux interfaces dynamically. For information
about how to configure dynamic IP demux or dynamic VLAN demux interfaces,
see Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in
Dynamic Profiles or Configuring Dynamic Subscriber Interfaces Using VLAN
Demux Interfaces in Dynamic Profiles.

To configure static demux interfaces, see Configuring a VLAN Demultiplexing Interface

on page 288 and Configuring an IP Demultiplexing Interface on page 284.

IP Demux Interface Overview on page 281

VLAN Demux Interface Overview on page 282

Guidelines to Remember When Configuring A Demux Interface on page 282

MAC Address Validation on Static Demux Interfaces on page 283

IP Demux Interface Overview

IP demux interfaces use the IP source address or IP destination address to demultiplex
received packets when the subscriber is not uniquely identified by a Layer 2 circuit.

Copyright 2014, Juniper Networks, Inc.

281

Interfaces Fundamentals for Routing Devices

To determine which IP demux interface to use, the destination or source prefix is matched
against the destination or source address of packets that the underlying interface receives.
The underlying interface family type must match the demux interface prefix type.

VLAN Demux Interface Overview

VLAN demux interfaces use the VLAN ID to demultiplex received packets when the
subscriber is not uniquely identified. A VLAN demux interface uses an underlying logical
interface to receive packets.
To determine which VLAN demux interface to use, the VLAN ID is matched against that
which the underlying interface receives.

NOTE: VLAN demux subscriber interfaces over aggregated Ethernet physical

interfaces are supported only for MX Series routers that have only Trio MPCs
installed. If the router has other MPCs in addition to Trio MPCs, theCLI accepts
the configuration but errors are reported when the subscriber interfaces are
brought up.

Guidelines to Remember When Configuring A Demux Interface

Keep the following guidelines in mind when configuring the demux interface:

Demux interfaces are supported on M120 or MX Series routers only.

You can configure only one demux0 interface per chassis, but you can define logical
demux interfaces on top of it (for example, demux0.1, demux0.2, and so on).

If the address in a received packet does not match any demux prefix, the packet is
logically received on the underlying interface. For this reason, the underlying interface
is often referred to as the primary interface.

Points to Remember When Configuring an IP Demux Interface on page 282

Points to Remember When Configuring a VLAN Demux Interface on page 283

Points to Remember When Configuring an IP Demux Interface

In addition to the guidelines in Guidelines to Remember When Configuring A Demux
Interface on page 282, the following guidelines are to be noted when configuring an IP
demux interface:

You must associate demux interfaces with an underlying logical interface.

NOTE: IP demux interfaces currently support only Gigabit Ethernet, Fast

Ethernet, 10-Gigabit Ethernet, and aggregated Ethernet underlying
interfaces.

282

The demux underlying interface must reside on the same logical system as the demux
interfaces that you configure over it.

Copyright 2014, Juniper Networks, Inc.

Chapter 7: Configuring IP Demultiplexing Interfaces

IP demux interfaces currently supports the Internet Protocol version 4 (IPv4) suite inet
and Internet Protocol version 6 (IPv6) suite inet6 family types.

You can configure more than one demux prefix for a given demux unit. However, you
cannot configure the exact same demux prefix on two different demux units with the
same underlying interface.

You can configure overlapping demux prefixes on two different demux units with the
same underlying prefix. However, under this configuration, best match rules apply (in
other words, the most specific prefix wins).

Points to Remember When Configuring a VLAN Demux Interface

In addition to the guidelines in Guidelines to Remember When Configuring A Demux
Interface on page 282, the following guidelines are to be noted when configuring a VLAN
demux interface:

You must associate VLAN demux interfaces with an underlying logical interface.

NOTE: VLAN demux interfaces currently support only Gigabit Ethernet,

Fast Ethernet, 10-Gigabit Ethernet, and aggregated Ethernet underlying
interfaces.

The demux underlying interface must reside on the same logical system as the demux
interfaces that you configure over it.

VLAN demux interfaces currently supports the Internet Protocol version 4 (IPv4) suite
inet and Internet Protocol version 6 (IPv6) suite inet6 family types.

MAC Address Validation on Static Demux Interfaces

MAC address validation enables the router to validate that received packets contain a
trusted IP source and an Ethernet MAC source address.
MAC address validation is supported on static demux interfaces on MX Series routers
only.
There are two types of MAC address validation that you can configure:

Loose on page 283

Strict on page 284

Loose
Forwards packets when both the IP source address and the MAC source address match
one of the trusted address tuples.
Drops packets when the IP source address matches one of the trusted tuples, but the
MAC address does not support the MAC address of the tuple
Continues to forward packets when the source address of the incoming packet does not
match any of the trusted IP addresses.

Copyright 2014, Juniper Networks, Inc.

283

Interfaces Fundamentals for Routing Devices

Strict
Forwards packets when both the IP source address and the MAC source address match
one of the trusted address tuples.
Drops packets when the MAC address does not match the tuple's MAC source address,
or when IP source address of the incoming packet does not match any of the trusted IP
addresses.
Related
Documentation

Associating VLAN IDs to VLAN Demux Interfaces

Binding VLAN IDs to Logical Interfaces

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Subscriber Interfaces and Demultiplexing Overview

Configuring an IP Demultiplexing Interface

Demultiplexing (demux) interfaces are logical interfaces that share a common, underlying
interface. You can configure IP demultiplexing interfaces or VLAN demultiplexing
interfaces.
To configure an IP demux interface, you must configure the demux prefixes that are used
by the underlying interface and then configure the IP demultiplexing interface as explained
in the following tasks:
1.

Configuring an IP Demux Underlying Interface on page 284

2. Configuring the IP Demux Interface on page 285

3. Configuring MAC Address Validation on Static IP Demux Interfaces on page 287

Configuring an IP Demux Underlying Interface

An IP demux interface uses an underlying logical interface to receive packets. To determine
which IP demux interface to use, the destination or source prefix is matched against the
destination or source address of packets that the underlying interface receives. The
underlying interface family type must match the demux interface prefix type.

NOTE: IP demux interfaces currently support only Gigabit Ethernet, Fast

Ethernet, 10-Gigabit Ethernet, and aggregated Ethernet underlying interfaces.

To configure a logical interface as an IP demux underlying interface with demux source:

1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

284

Copyright 2014, Juniper Networks, Inc.

Chapter 7: Configuring IP Demultiplexing Interfaces

2. Configure the interface as fe-x/y/z and the logical interface with the unit statement.

Note that IP demux interfaces currently support only Gigabit Ethernet, Fast Ethernet,
10-Gigabit Ethernet, and aggregated Ethernet underlying interfaces.
[edit interfaces]
user@host# edit fe-x/y/z unit logical-unit-number unit logical-unit-number
3. Configure the logical demux source family type on the IP demux underlying interface

as inet or inet6.
[edit interfaces fe-x/y/z unit logical-unit-number]
user@host# set demux-source (inet | inet6)
4. Save the configuration and move to top of the hierarchy level.

[edit interfaces fe-x/y/z unit logial-unit-number]

user@host# commit
user@host# top

To configure a logical interface as an IP demux underlying interface with demux

destination:
1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the interface as fe-x/y/z and the logical interface with the unit statement.

Note that IP demux interfaces currently support only Gigabit Ethernet, Fast Ethernet,
10-Gigabit Ethernet, and aggregated Ethernet underlying interfaces.
[edit interfaces]
user@host# edit fe-x/y/z unit logical-unit-number unit logical-unit-number
3. Configure the logical demux destination family type on the IP demux underlying

interface as inet or inet6.

[edit interfaces fe-x/y/z unit logical-unit-number]
user@host# set demux-destination (inet | inet6)
4. Save the configuration and move to top of the hierarchy level.

[edit interfaces fe-x/y/z unit logial-unit-number]

user@host# commit
user@host# top

Configuring the IP Demux Interface

You can configure one or more logical demux source prefixes or destination prefixes after
specifying an underlying interface for the static demux interface to use. This underlying
interface must reside on the same logical system as the demux interface.
You configure demux prefixes for use by the underlying interface. The demux prefixes
can represent individual hosts or networks. For a given demux interface unit, you can
configure either demux source or demux destination prefixes but not both.
You can choose not to configure a demux source or demux destination prefix. This type
of configuration results in a transmit-only interface.

Copyright 2014, Juniper Networks, Inc.

285

Interfaces Fundamentals for Routing Devices

To configure the IP demux interface with source prefix:

1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the interface as a logical demux interface (for example, demux0 interface)

and configure the logical interface with the unit statement.

NOTE: You can configure only one demux0 interface per chassis, but you
can define logical demux interfaces on top of it (for example, demux0.1,
demux0.2, and so on).

[edit interfaces]
user@host# edit demux0 unit logical-unit-number
3. Configure the underlying interface on which the demux interface is running under the

demux-options statement.
[edit interfaces demux0 unit logical-unit-number]
user@host# set demux-options underlying-interface interface-name
4. Configure the protocol family.

[edit interfaces demux0 unit logical-unit-number]

user@host# edit family family
5. Configure one or more logical demux source prefixes (IP address). The prefixes are

matched against the source address of packets that the underlying interface receives.
When a match occurs, the packet is processed as if it was received on the demux
interface.
[edit interfaces demux0 unit logical-unit-number family family]
user@host# set demux-source source-prefix
6. Save the configuration and move to top of the hierarchy level.

[edit interfaces demux0 unit logical-unit-number family family]

user@host# commit
user@host# top

To configure the IP demux interface with destination prefix:

1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the interface as a logical demux interface (for example, demux0 interface)

and configure the logical interface with the unit statement.

NOTE: You can configure only one demux0 interface per chassis, but you
can define logical demux interfaces on top of it (for example, demux0.1,
demux0.2, and so on).

286

Copyright 2014, Juniper Networks, Inc.

Chapter 7: Configuring IP Demultiplexing Interfaces

[edit interfaces]
user@host# edit demux0 unit logical-unit-number
3. Configure the underlying interface on which the demux interface is running under the

demux-options statement.
[edit interfaces demux0 unit logical-unit-number]
user@host# set demux-options underlying-interface interface-name
4. Configure the protocol family.

[edit interfaces demux0 unit logical-unit-number]

user@host# edit family family
5. Configure one or more logical demux destination prefixes. The prefixes are matched

against the destination address of packets that the underlying interface receives.
When a match occurs, the packet is processed as if it was received on the demux
interface.
[edit interfaces demux0 unit logical-unit-number family family]
user@host# set demux-destination destination-prefix
6. Save the configuration and move to top of the hierarchy level.

[edit interfaces demux0 unit logical-unit-number family family]

user@host# commit
user@host# top

Configuring MAC Address Validation on Static IP Demux Interfaces

MAC address validation enables the router to validate that received packets contain a
trusted IP source and an Ethernet MAC source address.
To configure MAC address validation for an IP demux interface:
1.

In configuration mode, go to the [edit interfaces demux0 unit logical-unit-number]

hierarchy level:
[edit]
user@host# edit interfaces demux0 unit logical-unit-number

2. Configure the protocol family for the interface.

[edit interfaces demux0 unit logical-unit-number]

user@host# edit family family
3. Configure the mac-validate statement to validate source MAC address with loose or

strict options.
[edit interfaces demux0 unit logical-unit-number family family]
user@host# set mac-validate (loose | strict)
4. Save the configuration and move to top of the hierarchy level.

[edit interfaces demux0 unit logical-unit-number family family]

user@host# commit
user@host# top

Copyright 2014, Juniper Networks, Inc.

287

Interfaces Fundamentals for Routing Devices

Related
Documentation

Configuring a VLAN Demultiplexing Interface on page 288

Demultiplexing Interface Overview on page 281

Configuring a VLAN Demultiplexing Interface

Demultiplexing (demux) interfaces are logical interfaces that share a common, underlying
interface. You can configure IP demultiplexing interfaces or VLAN demultiplexing
interfaces.
To configure a VLAN demux interface, you must configure the demux prefixes that are
used by the underlying interface and then configure the VLAN demultiplexing interface
as explained by the following tasks:
1.

Configuring a VLAN Demux Underlying Interface on page 288

2. Configuring the VLAN Demux Interface on page 289

3. Configuring MAC Address Validation on Static VLAN Demux Interfaces on page 291
4. Verifying a Demux Interface Configuration on page 292

Configuring a VLAN Demux Underlying Interface

A VLAN demux interface uses an underlying logical interface to receive packets. To
determine which VLAN demux interface to use, the VLAN ID is matched against that
which the underlying interface receives.

NOTE: VLAN demux interfaces currently support only Gigabit Ethernet, Fast
Ethernet, 10-Gigabit Ethernet, and aggregated Ethernet underlying interfaces.
VLAN demux subscriber interfaces over aggregated Ethernet physical
interfaces are supported only for MX Series routers that have only Trio MPCs
installed. If the router has other MPCs in addition to Trio MPCs, the CLI accepts
the configuration but errors are reported when the subscriber interfaces are
brought up

To configure a logical interface as a VLAN demux underlying interface with demux source:
1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the interface as fe-x/y/z and the logical interface with the unit option.

[edit interfaces]
user@host# edit fe-x/y/z unit logical-unit-number unit logical-unit-number
3. Configure the VLAN ID. The VLAN ID is used to determine which VLAN demux interface

to use, that is the VLAN ID is matched against that which the underlying interface
receives.
[edit interfaces fe-x/y/z unit logical-unit-number]

288

Copyright 2014, Juniper Networks, Inc.

Chapter 7: Configuring IP Demultiplexing Interfaces

user@host# set vlan-id number

4. Configure the logical demux source family type on the VLAN demux underlying interface

as inet or inet6.
[edit interfaces fe-x/y/z unit logical-unit-number]
user@host# set demux-source (inet | inet6)
5. Save the configuration and move to top of the hierarchy level.

[edit interfaces fe-x/y/z unit logial-unit-number]

user@host# commit
user@host# top

To configure a logical interface as a VLAN demux underlying interface with demux

destination:
1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the interface as fe-x/y/z and the logical interface with the unit option.

[edit interfaces]
user@host# edit fe-x/y/z unit logical-unit-number unit logical-unit-number
3. Configure the VLAN ID. The VLAN ID is used to determine which VLAN demux interface

to use, that is the VLAN ID is matched against that which the underlying interface
receives.
[edit interfaces fe-x/y/z unit logical-unit-number]
user@host# set vlan-id number
4. Configure the logical demux destination family type on the VLAN demux underlying

interface as inet or inet6.

[edit interfaces fe-x/y/z unit logical-unit-number]
user@host# set demux-destination (inet | inet6)
5. Save the configuration and move to top of the hierarchy level.

[edit interfaces fe-x/y/z unit logial-unit-number]

user@host# commit
user@host# top

Configuring the VLAN Demux Interface

You can configure one or more logical demux source prefixes or destination prefixes after
specifying an underlying interface for the static demux interface to use. This underlying
interface must reside on the same logical system as the demux interface.
You configure demux prefixes for use by the underlying interface. The demux prefixes
can represent individual hosts or networks. For a given demux interface unit, you can
configure either demux source prefix or demux destination prefixes but not both.
You can choose not to configure a demux source prefix or a demux destination prefix.
This type of configuration results in a transmit-only interface

Copyright 2014, Juniper Networks, Inc.

289

Interfaces Fundamentals for Routing Devices

To configure VLAN demux interface with demux source prefix:

1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the interface as a logical demux interface (for example, demux0 interface)

and configure the logical interface with the unit statement.

NOTE: You can configure only one demux0 interface per chassis, but you
can define logical demux interfaces on top of it (for example, demux0.1,
demux0.2, and so on).

[edit interfaces]
user@host# edit demux0 unit logical-unit-number
3. Configure the underlying interface on which the demux interface is running under the

demux-options statement.
[edit interfaces demux0 unit logical-unit-number]
user@host# set demux-options underlying-interface interface-name
4. Configure the protocol family for the interface.

[edit interfaces demux0 unit logical-unit-number]

user@host# edit family family
5. Configure one or more logical demux source prefixes. The prefixes are matched against

the source address of packets that the underlying interface receives. When a match
occurs, the packet is processed as if it was received on the demux interface.
[edit interfaces demux0 unit logical-unit-number family family]
user@host# set demux-source source-prefix
6. Save the configuration and move to top of the hierarchy level.

[edit interfaces demux0 unit logical-unit-number]

user@host# commit
user@host# top

To configure VLAN demux interface with demux destination prefix:

1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the interface as a logical demux interface (for example, demux0 interface)

and configure the logical interface with the unit statement.

NOTE: You can configure only one demux0 interface per chassis, but you
can define logical demux interfaces on top of it (for example, demux0.1,
demux0.2, and so on).

[edit interfaces]

290

Copyright 2014, Juniper Networks, Inc.

Chapter 7: Configuring IP Demultiplexing Interfaces

user@host# edit demux0 unit logical-unit-number

3. Configure the underlying interface on which the demux interface is running under the

demux-options statement.
[edit interfaces demux0 unit logical-unit-number]
user@host# set demux-options underlying-interface interface-name
4. Configure the protocol family for the interface.

[edit interfaces demux0 unit logical-unit-number]

user@host# edit family family
5. Configure one or more logical demux destination prefixes. The prefixes are matched

against the destination address of packets that the underlying interface receives.
When a match occurs, the packet is processed as if it was received on the demux
interface.
[edit interfaces demux0 unit logical-unit-number family family]
user@host# set demux-destination destination-prefix
6. Save the configuration and move to top of the hierarchy level.

[edit interfaces demux0 unit logical-unit-number]

user@host# commit
user@host# top

Configuring MAC Address Validation on Static VLAN Demux Interfaces

MAC address validation enables the router to validate that received packets contain a
trusted IP source and an Ethernet MAC source address.
To configure MAC address validation for a VLAN demux interface:
1.

In configuration mode, go to the [edit interfaces demux0 unit logical-unit-number]

hierarchy level:
[edit]
user@host# edit interfaces demux0 unit logical-unit-number

2. Configure the protocol family for the interface.

[edit interfaces demux0 unit logical-unit-number]

user@host# edit family family
3. Configure the mac-validate statement to validate source MAC address with loose or

strict options.
[edit interfaces demux0 unit logical-unit-number family family]
user@host# set mac-validate (loose | strict)
4. Save the configuration and move to top of the hierarchy level.

[edit interfaces demux0 unit logical-unit-number family family]

user@host# commit
user@host# top

Copyright 2014, Juniper Networks, Inc.

291

Interfaces Fundamentals for Routing Devices

Verifying a Demux Interface Configuration

Purpose

Action

Check the configuration of a demux interface and its underlying interface when the
following are configured:

Two VLANs are configured, where each VLAN consists of two IP demux interfaces.

One VLAN demultiplexes based on the source address

The other VLAN demultiplexes based on the destination address.

From configuration mode on the MX Series router, run the show interfaces fe-0/0/0 and
show interfaces demux0 configuration mode commands.
user@host> show interfaces fe-0/0/0
vlan-tagging;
unit 100 {
vlan-id 100;
demux-source inet; # Enable demux of inet prefixes
family inet {
address 10.1.1.1/24;
filter {
input vlan1-primary-in-filter;
output vlan1-primary-out-filter;
}
mac-validate loose;
}
}
unit 200 {
vlan-id 200;
demux-destination inet; # Enable demux of inet using destination addresses
family inet {
address 20.1.1.1/24;
}
}
unit 300 {
vlan-id 300;
demux-source inet; # Enable demux of inet using source addresses
family inet {
address 20.1.2.1/24;
}
}
user@host> show interfaces demux0
unit 101 {
description vlan1-sub1;
demux-options {
underlying-interface fe-0/0/0.100;
}
family inet {
demux-source 10.1.1.0/24;
filter {
input vlan1-sub1-in-filter;
output vlan1-sub1-out-filter;
}
mac-validate loose;
}

292

Copyright 2014, Juniper Networks, Inc.

Chapter 7: Configuring IP Demultiplexing Interfaces

}
unit 102 {
description vlan1-sub2;
demux-options {
underlying-interface fe-0/0/0.100;
}
family inet {
demux-source {
10.1.0.0/16;
10.2.1.0/24;
}
filter {
input vlan1-sub2-in-filter;
output vlan1-sub2-out-filter;
}
mac-validate loose;
}
}
unit 202 {
description vlan2-sub2;
demux-options {
underlying-interface fe-0/0/0.200;
}
family inet {
demux-destination 100.1.2.0/24;
}
}
unit 302 {
description vlan2-sub2;
demux-options {
underlying-interface fe-0/0/0.300;
}
family inet {
demux-source 100.1.2.0/24;
}
}

Related
Documentation

Configuring an IP Demultiplexing Interface on page 284

Demultiplexing Interface Overview on page 281

Copyright 2014, Juniper Networks, Inc.

293

Interfaces Fundamentals for Routing Devices

294

Copyright 2014, Juniper Networks, Inc.

CHAPTER 8

Configuring the Loopback Interface

Configuring the Loopback Interface on page 295

Configuring the Loopback Interface

On the router, you can configure one physical loopback interface, lo0, and one or more
addresses on the interface.
To configure the physical loopback interface, include the following statements at the
[edit interfaces] hierarchy level:
[edit interfaces]
lo0 {
unit 0 {
family inet {
address loopback-address;
address <loopback-address2>;
...
}
family inet6 {
address loopback-address;
}
}
}

When specifying the loopback address, do not include a destination prefix. Also, in most
cases, do not specify a loopback address on any unit other than unit 0.

NOTE: For Layer 3 virtual private networks (VPNs), you can configure multiple
logical units for the loopback interface. This allows you to configure a logical
loopback interface for each virtual routing and forwarding (VRF) routing
instance. For more information, see the Junos OS VPNs Library for Routing
Devices.
For some applications, such as SSL for Junos XML protocol, the address for
the interface lo0.0 must be 127.0.0.1.

You can configure loopback interfaces using a subnetwork address for both inet and
inet6 address families. Many protocols require a subnetwork address as their source

Copyright 2014, Juniper Networks, Inc.

295

Interfaces Fundamentals for Routing Devices

address. Configuring a subnetwork loopback address as a donor interface enables these

protocols to run on unnumbered interfaces.
If you configure the loopback interface, it is automatically used for unnumbered interfaces.
If you do not configure the loopback interface, the router chooses the first interface to
come online as the default. If you configure more than one address on the loopback
interface, we recommend that you configure one to be the primary address to ensure
that it is selected for use with unnumbered interfaces. By default, the primary address is
used as the source address when packets originate from the interface.
For more information about unnumbered interfaces, see Configuring an Unnumbered
Interface on page 203. For more information about primary addresses, see Configuring
the Interface Address on page 192.

Example: Configuring the Loopback Interface

Configure two addresses on the loopback interface with host routes:
[edit]
user@host# edit interfaces lo0 unit 0 family inet
[edit interfaces lo0 unit 0 family inet]
user@host# set address 172.16.0.1
[edit interfaces lo0 unit 0 family inet]
user@host# set address 10.0.0.1
[edit interfaces lo0 unit 0 family inet]
user@host# top
[edit]
user@host# show
interfaces {
lo0 {
unit 0 {
family inet {
10.0.0.1;
127.0.0.1;
172.16.0.1;
}
}
}
}

Configure two addresses on the loopback interface with subnetwork routes:

[edit]
user@host# edit interfaces lo0 unit 0 family inet
[edit interfaces lo0 unit 0 family inet]
user@host# set address 192.16.0.1/24
[edit interfaces lo0 unit 0 family inet]
user@host# set address 10.2.0.1/16
[edit interfaces lo0 unit 0 family inet]
user@host# top
[edit]
user@host# show
interfaces {
lo0 {
unit 0 {

296

Copyright 2014, Juniper Networks, Inc.

Chapter 8: Configuring the Loopback Interface

family inet {
10.2.0.1/16;
127.0.0.1/32;
192.16.0.1/24;
}
}
}
}

Configure an IP and an IPv6 address on the loopback interface with subnetwork routes:
[edit]
user@host# edit interfaces lo0 unit 0 family inet
[edit interfaces lo0 unit 0 family inet]
user@host# set address 192.16.0.1/24
[edit interfaces lo0 unit 0 family inet]
user@host# up
[edit interfaces lo0 unit 0 family]
user@host# edit interfaces lo0 unit 0 family inet6
[edit interfaces lo0 unit 0 family inet6]
user@host# set address 3ffe::1:200:f8ff:fe75:50df/64
[edit interfaces lo0 unit 0 family inet6]
user@host# top
[edit]
user@host# show
interfaces {
lo0 {
unit 0 {
family inet {
127.0.0.1/32;
192.16.0.1/24;
}
family inet6 {
3ffe::1:200:f8ff:fe75:50df/64;
}
}
}
}

Copyright 2014, Juniper Networks, Inc.

297

Interfaces Fundamentals for Routing Devices

298

Copyright 2014, Juniper Networks, Inc.

PART 3

Serial Interfaces

Serial Interfaces Overview on page 301

Configuring Serial Interfaces on page 303

Copyright 2014, Juniper Networks, Inc.

299

Interfaces Fundamentals for Routing Devices

300

Copyright 2014, Juniper Networks, Inc.

CHAPTER 9

Serial Interfaces Overview

Serial Interfaces Overview on page 301

Serial Interfaces Overview

Devices that communicate over a serial interface are divided into two classes: data
terminal equipment (DTE) and data circuit-terminating equipment (DCE). Juniper
Networks Serial Physical Interface Cards (PICs) have two ports per PIC and support
full-duplex data transmission. These PICs support DTE mode only. On the Serial PIC, you
can configure three types of serial interfaces:

EIA-530An Electronics Industries Alliance (EIA) standard for the interconnection of

DTE and DCE using serial binary data interchange with control information exchanged
on separate control circuits.

V.35An ITU-T standard describing a synchronous, physical layer protocol used for
communications between a network access device and a packet network. V.35 is most
commonly used in the United States and in Europe.

X.21An ITU-T standard for serial communications over synchronous digital lines. The
X.21 protocol is used primarily in Europe and Japan.

The following standards apply to serial interfaces:

TIA/EIA Standard 530, High-Speed 25-Position Interface for Data Terminal Equipment
and Data Circuit-Terminating Equipment, defines the signals on the cable and specifies
the connector at the end of the cable.

TIA/EIA Standard 232, Interface between Data Terminal Equipment and Data
Circuit-Terminating Equipment Employing Serial Binary Data Interchange, describes the
physical interface and protocol for serial data communication.

ITU-T Recommendation V.35, Data Transmission at 48 kbit/s Using 60-108 kHz Group
Band Circuits. Note that the Juniper Networks Serial PIC supports V.35 interfaces with
speeds higher than 48 kilobits per second.

ITU-T Recommendation X.21, Interface Between Data Terminal Equipment and Data
Circuit-Terminating Equipment for Synchronous Operation on Public Data Networks.

There are no serial interface-specific logical properties. For information about general
logical properties that you can configure, see Configuring Logical Interface Properties. On

Copyright 2014, Juniper Networks, Inc.

301

Interfaces Fundamentals for Routing Devices

J Series routers, link fragmentation and interleaving (LFI) and Multilink Point-to-Point
Protocol (MLPPP) support has been extended to serial interfaces. This support on serial
interfaces is the same as the existing LFI and MLPPP support on T1 and E1 interfaces.
Related
Documentation

302

Example: Physical Interface Configuration Statements for Serial Interfaces on page 303

Configuring the Serial Line Protocol on page 304

Configuring the Serial Clocking Mode on page 307

Configuring the Serial Idle Cycle Flag on page 310

Configuring the Serial Signal Handling on page 310

Configuring the Serial DTR Circuit on page 313

Configuring Serial Signal Polarities on page 313

Configuring Serial Loopback Capability on page 314

Configuring Serial Line Encoding on page 315

Copyright 2014, Juniper Networks, Inc.

CHAPTER 10

Configuring Serial Interfaces

Example: Physical Interface Configuration Statements for Serial Interfaces on page 303

Configuring the Serial Line Protocol on page 304

Configuring the Serial Clocking Mode on page 307

Configuring the Serial Idle Cycle Flag on page 310

Configuring the Serial Signal Handling on page 310

Configuring the Serial DTR Circuit on page 313

Configuring Serial Signal Polarities on page 313

Configuring Serial Loopback Capability on page 314

Configuring Serial Line Encoding on page 315

Specifying a USB Modem Interface on J Series Routers on page 316

Example: Physical Interface Configuration Statements for Serial Interfaces

To configure serial physical interface properties, include the serial-options statement at
the [edit interfaces se-pim/0/port ] hierarchy level for J Series routers, or at the [edit
interfaces se- fpc/pic/port] hierarchy level for M Series and T Series routers:
[edit interfaces se-fpc/pic/port]
serial-options {
clock-rate rate;
clocking-mode (dce | internal | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {

Copyright 2014, Juniper Networks, Inc.

303

Interfaces Fundamentals for Routing Devices

control-signal (assert | de-assert | normal);

cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dtr-circuit (negative | positive);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
idle-cycle-flag flag;
indication-polarity (negative | positive);
line-protocol protocol;
loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}

Configuring the Serial Line Protocol

By default, serial interfaces use the EIA-530 line protocol. You can configure each port
on the PIC independently to use one of the following line protocols:

EIA-530

V.35

X.21

To configure the serial line protocol, include the line-protocol statement, specifying the
eia530, v.35, or x.21 option:
line-protocol protocol;

You can include these statements at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

For more information about serial interfaces, see the following sections:

Serial Interface Default Settings on page 304

Invalid Serial Interface Statements on page 306

Serial Interface Default Settings

304

EIA-530 Interface Default Settings on page 305

V.35 Interface Default Settings on page 305

X.21 Interface Default Settings on page 306

Copyright 2014, Juniper Networks, Inc.

Chapter 10: Configuring Serial Interfaces

EIA-530 Interface Default Settings

If you do not include the line-protocol statement or if you explicitly configure the default
EIA-530 line protocol, the default settings are as follows:
dce-options | dte-options {
cts normal;
dcd normal;
dsr normal;
dtr normal;
rts normal;
tm normal;
}
clock-rate 16.384mhz;
clocking-mode loop;
cts-polarity positive;
dcd-polarity positive;
dsr-polarity positive;
dtr-circuit balanced;
dtr-polarity positive;
encoding nrz;
rts-polarity positive;
tm-polarity positive;

NOTE: On M Series routers, you can set the DCE clocking mode for EIA-530
interfaces and commit. An error message is not displayed and the CLI is not
blocked.

You can include the line-protocol statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

V.35 Interface Default Settings

If you include the line-protocol v.35 statement, the default settings are as follows:
dce-options | dte-options {
cts normal;
dcd normal;
dsr normal;
dtr normal;
rts normal;
}
clock-rate 16.384mhz;
clocking-mode loop;
cts-polarity positive;
dcd-polarity positive;
dsr-polarity positive;
dtr-circuit balanced;
dtr-polarity positive;
encoding nrz;

Copyright 2014, Juniper Networks, Inc.

305

Interfaces Fundamentals for Routing Devices

rts-polarity positive;

You can include the line-protocol statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

X.21 Interface Default Settings

If you include the line-protocol x.21 statement, the default settings are as follows:
dce-options | dte-options {
control-signal normal;
indication normal;
}
clock-rate 16.384mhz;
clocking-mode loop;
control-polarity positive;
encoding nrz;
indication-polarity positive;

You can include the line-protocol statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

Invalid Serial Interface Statements

The following sections show the invalid configuration statements for each type of serial
interface. If you include the following statements in the configuration, an error message
indicates the location of the error and the configuration is not activated.

Invalid EIA-530 Interface Statements on page 306

Invalid V.35 interface Statements on page 307

Invalid X.21 Interface Statements on page 307

Invalid EIA-530 Interface Statements

If you do not include the line-protocol statement or if you explicitly configure the default
EIA-530 line protocol, the following statements are invalid:
dce-options | dte-options {
control-signal (assert | de-assert | normal);
indication (ignore | normal | require);
}
control-polarity (negative | positive);
indication-polarity (negative | positive);

You can include the line-protocol statement at the following hierarchy levels:

306

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

Copyright 2014, Juniper Networks, Inc.

Chapter 10: Configuring Serial Interfaces

Invalid V.35 interface Statements

If you include the line-protocol v.35 statement, the following statements are invalid:
dce-options | dte-options {
control-signal (assert | de-assert | normal);
indication (ignore | normal | require);
tm (ignore | normal | require);
}
control-polarity (negative | positive);
indication-polarity (negative | positive);
loopback (dce-local | dce-remote);
tm-polarity (negative | positive);

You can include the line-protocol statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

Invalid X.21 Interface Statements

If you include the line-protocol x.21 statement, the following statements are invalid:
dce-options | dte-options {
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr (assert | de-assert | normal);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
clocking-mode (dce | internal);
cts-polarity (negative | positive);
dce-polarity (negative | positive);
dsr-polarity (negative | positive);
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
loopback (dce-local | dce-remote);
rts-polarity (negative | positive);
tm-polarity (negative | positive);

You can include the line-protocol statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

Configuring the Serial Clocking Mode

By default, serial interfaces use loop clocking mode. For EIA-530 and V.35 interfaces,
you can configure each port on the PIC independently to use loop, DCE, or internal clocking
mode. For X.21 interfaces, only loop clocking mode is supported.
The three clocking modes work as follows:

Copyright 2014, Juniper Networks, Inc.

307

Interfaces Fundamentals for Routing Devices

Loop clocking modeUses the DCEs RX clock to clock data from the DCE to the DTE.

DCE clocking modeUses the TXC clock, which is generated by the DCE specifically
to be used by the DTE as the DTEs transmit clock.

Internal clocking modeAlso known as line timing, uses an internally generated clock.
You can configure the speed of this clock by including the clock-rate statement at the
[edit interfaces se-pim/0/port serial-options] or [edit interfaces se-fpc/pic/port
dte-options] hierarchy levels. For more information about the DTE clock rate, see
Configuring the DTE Clock Rate on page 309.

Note that DCE clocking mode and loop clocking mode use external clocks generated by
the DCE.
Figure 21 on page 308 shows the clock sources of loop, DCE, and internal clocking modes.

Figure 21: Serial Interface Clocking Mode

To configure the clocking mode of a serial interface, include the clocking-mode statement:
clocking-mode (dce | internal | loop);

You can include this statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

For more information about clocking on serial interfaces, see the following sections:

Inverting the Serial Interface Transmit Clock on page 308

Configuring the DTE Clock Rate on page 309

Inverting the Serial Interface Transmit Clock

When an externally timed clocking mode (DCE or loop) is used, long cables might
introduce a phase shift of the DTE-transmitted clock and data. At high speeds, this phase
shift might cause errors. Inverting the transmit clock corrects the phase shift, thereby
reducing error rates.

308

Copyright 2014, Juniper Networks, Inc.

Chapter 10: Configuring Serial Interfaces

By default, the transmit clock is not inverted. To invert the transmit clock, include the
transmit-clock invert statement:
transmit-clock invert;

You can include this statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

Configuring the DTE Clock Rate

By default, the serial interface has a clock rate of 16.384 MHz. For EIA-530 and V.35
interfaces with internal clocking mode configured, you can configure the clock rate. For
more information about internal clocking mode, see Configuring the Serial Clocking
Mode on page 307.
To configure the clock rate, include the clock-rate statement:
clock-rate rate;

You can include this statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

You can configure the following interface speeds:

2.048 MHz

2.341 MHz

2.731 MHz

3.277 MHz

4.096 MHz

5.461 MHz

8.192 MHz

16.384 MHz

Although the serial interface is intended for use at the default rate of 16.384 MHz, you
might need to use a slower rate if any of the following conditions prevail:

The interconnecting cable is too long for effective operation.

The interconnecting cable is exposed to an extraneous noise source that might cause
an unwanted voltage in excess of +1 volt measured differentially between the signal
conductor and circuit common at the load end of the cable, with a 50-ohm resistor
substituted for the generator.

You need to minimize interference with other signals.

You need to invert signals.

Copyright 2014, Juniper Networks, Inc.

309

Interfaces Fundamentals for Routing Devices

For detailed information about the relationship between signaling rate and interface
cable distance, see the following standards:

EIA-422-A, Electrical Characteristics of Balanced Voltage Digital Interface Circuits

EIA-423-A, Electrical Characteristics of Unbalanced Voltage Digital Interface Circuits

Configuring the Serial Idle Cycle Flag

By default, a serial interface on J Series routers transmits the value 0x7E in the idle cycles.
To have the interface transmit the value 0xFF (all ones) instead, include the idle-cycle-flag
statement at the [edit interfaces interface-name serial-options] hierarchy level, specifying
the ones option:
[edit interfaces interface-name serial-options]
idle-cycle-flag ones;

To explicitly configure the default value of 0x7E, include the idle-cycle-flag statement
with the flags option:
[edit interfaces interface-name serial-options]
idle-cycle-flag flags;

Configuring the Serial Signal Handling

By default, normal signal handling is enabled for all signals. For each signal, the normal
option applies to the normal signal handling for that signal, as defined by the following
standards:

TIA/EIA Standard 530

ITU-T Recommendation V.35

ITU-T Recommendation X.21

Table 46 on page 310 shows the serial interface modes that support each signal type.

Table 46: Signal Handling by Serial Interface Type

Signal

Serial Interfaces

From-DCE signals
Clear to send (CTS)

EIA-530 and V.35

Data carrier detect (DCD)

EIA-530 and V.35

Data set ready (DSR)

EIA-530 and V.35

Indication

X.21 only

Test mode (TM)

EIA-530 only

To-DCE signals

310

Copyright 2014, Juniper Networks, Inc.

Chapter 10: Configuring Serial Interfaces

Table 46: Signal Handling by Serial Interface Type (continued)

Signal

Serial Interfaces

Control signal

X.21 only

Data transfer ready (DTR)

EIA-530 and V.35

Request to send (RTS)

EIA-530 and V.35

You configure serial interface signal characteristics by including the dce-options or

dte-options statement:
dce-options |dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}

You can include these statements at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

For EIA-530 and V.35 interfaces, configure to-DCE signals by including the dtr and rts
statements, specifying the assert, de-assert, or normal option:
dtr (assert | de-assert | normal);
rts (assert | de-assert | normal);

For X.21 interfaces, configure to-DCE signals by including the control-signal statement,
specifying the assert, de-assert, or normal option:
control-signal (assert | de-assert | normal);

Assertion is when the positive side of a given signal is at potential high-level output voltage
(Voh), while the negative side of the same signal is at potential low-level output voltage
(Vol). Deassertion is when the positive side of a given signal is at potential Vol, while the
negative side of the same signal is at potential Voh.
For the DTR signal, you can configure normal signal handling using the signal for automatic
resynchronization by including the dtr statement, and specifying the auto-synchronize
option:
dtr {
auto-synchronize {
duration milliseconds;
interval seconds;

Copyright 2014, Juniper Networks, Inc.

311

Interfaces Fundamentals for Routing Devices

}
}

The pulse duration of resynchronization can be from 1 through 1000 milliseconds. The
offset interval for resynchronization can be from 1 through 31 seconds.
For EIA-530 and V.35 interfaces, configure from-DCE signals by including the cts, dcd,
and dsr statements, specifying the ignore, normal, or require option:
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);

For X.21 interfaces, configure from-DCE signals by including the indication statement,
specifying the ignore, normal, or require option:
indication (ignore | normal | require);

For EIA-530 interfaces only, you can configure from-DCE test-mode (TM) signaling by
including the tm statement, specifying the ignore, normal, or require option:
tm (ignore | normal | require);

To specify that the from-DCE signal must be asserted, include the require option in the
configuration. To specify that the from-DCE signal must be ignored, include the ignore
option in the configuration.

NOTE: For V.35 and X.21 interfaces, you cannot include the tm statement in
the configuration.
For X.21 interfaces, you cannot include the cts, dcd, dsr, dtr, and rts statements
in the configuration.
For EIA-530 and V.35 interfaces, you cannot include the control-signal and
indication statements in the configuration.
For a complete list of serial options statements that are not supported by
each serial interface mode, see Invalid Serial Interface Statements on
page 306.

To return to the default normal signal handling, delete the require, ignore, assert, de-assert,
or auto-synchronize statement from the configuration, as shown in the following example:
[edit]
user@host# delete interfaces se-fpc/pic/port dte-options control-leads cts require

To explicitly configure normal signal handling, include the control-signal statement with
the normal option:
control-signal normal;

You can configure the serial interface to ignore all control leads by including the ignore-all
statement:
ignore-all;

312

Copyright 2014, Juniper Networks, Inc.

Chapter 10: Configuring Serial Interfaces

You can include the ignore-all statement in the configuration only if you do not explicitly
enable other signal handling options at the [edit interfaces se-pim/0/port serial-options
dce-options] or [edit interfaces se-fpc/pic/port serial-options dte-options] hierarchy levels.
You can include the control-signal, cts, dcd, dsr, dtr, indication, rts, and tm statements at
the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options dte-options]

[edit interfaces se-fpc/pic/port serial-options dte-options]

Configuring the Serial DTR Circuit

A balanced circuit has two currents that are equal in magnitude and opposite in phase.
An unbalanced circuit has one current and a ground; if a pair of terminals is unbalanced,
one side is connected to electrical ground and the other carries the signal. By default, the
DTR circuit is balanced.
For EIA-530 and V.35 interfaces, configure the DTR circuit by including the dtr-circuit
statement:
dtr-circuit (balanced | unbalanced);

You can include this statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

Configuring Serial Signal Polarities

Serial interfaces use a differential protocol signaling technique. Of the two serial signals
associated with a circuit, the one referred to as the A signal is denoted with a plus sign,
and the one referred to as the B signal is denoted with a minus sign; for example, DTR+
and DTR. If DTR is low, then DTR+ is negative with respect to DTR. If DTR is high, then
DTR+ is positive with respect to DTR.
By default, all signal polarities are positive. You can reverse this polarity on a Juniper
Networks serial interface. You might need to do this if signals are miswired as a result of
reversed polarities.
For EIA-530 and V.35 interfaces, configure signal polarities by including the cts-polarity,
dcd-polarity, dsr-polarity, dtr-polarity, rts-polarity, and tm-polarity statements:
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dsr-polarity (negative | positive);
dtr-polarity (negative | positive);
rts-polarity (negative | positive);
tm-polarity (negative | positive);

You can include these statements at the following hierarchy levels:

Copyright 2014, Juniper Networks, Inc.

313

Interfaces Fundamentals for Routing Devices

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

For X.21 interfaces, configure signal polarities by including the control-polarity and
indication-polarity statements:
control-polarity (negative | positive);
indication-polarity (negative | positive);

You can include these statements at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

Configuring Serial Loopback Capability

From the router, remote line interface unit (LIU) loopback loops the TX (transmit) data
and TX clock back to the router as RX (receive) data and RX clock. From the line, LIU
loopback loops the RX data and RX clock back out the line as TX data and TX clock, as
shown in Figure 22 on page 314.

Figure 22: Serial Interface LIU Loopback

DCE local and DCE remote control the EIA-530 interface-specific signals for enabling
local and remote loopback on the link partner DCE. Local loopback is shown in
Figure 23 on page 314.

Figure 23: Serial Interface Local Loopback

For EIA-530 interfaces, you can configure DCE local, DCE remote, local, and remote (LIU)
loopback capability.

314

Copyright 2014, Juniper Networks, Inc.

Chapter 10: Configuring Serial Interfaces

For V.35, you can configure remote LIU and local loopback capability. DCE local and DCE
remote loopbacks are not supported on V.35 and X.21 interfaces. Local and remote
loopbacks are not supported on X.21 interfaces.
To configure the loopback capability on a serial interface, include the loopback statement,
specifying the dce-local, dce-remote, local, or remote option:
loopback mode;

You can include this statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

To disable the loopback capability, remove the loopback statement from the configuration:
[edit]
user@host# delete interfaces se-fpc/pic/port serial-options loopback

You can determine whether there is an internal or external problem by checking the error
counters in the output of the show interface se-fpc/pic/port extensive command:
user@host> show interfaces se-fpc/pic/port extensive

Example: Configuring Serial Loopback Capability

To determine the source of a problem, loop packets on the local router, the local DCE,
the remote DCE, and the remote line interface unit (LIU). To do this, include the
no-keepalives and encapsulation cisco-hdlc statements at the [edit interfaces
se-fpc/pic/port] hierarchy level, and the loopback local option at the [edit interfaces
se-pim/0/port serial-options] or [edit interfaces se-fpc/pic/port serial-options] hierarchy
level. With this configuration, the link stays up, so you can loop ping packets to a remote
router. The loopback local statement causes the interface to loop within the PIC just
before the data reaches the transceiver.
[edit interfaces]
se-1/0/0 {
no-keepalives;
encapsulation cisco-hdlc;
serial-options {
loopback local;
}
unit 0 {
family inet {
address 10.100.100.1/24;
}
}
}

Configuring Serial Line Encoding

By default, serial interfaces use non-return to zero (NRZ) line encoding. You can configure
non-return to zero inverted (NRZI) line encoding if necessary.

Copyright 2014, Juniper Networks, Inc.

315

Interfaces Fundamentals for Routing Devices

To have the interface use NRZI line encoding, include the encoding statement, specifying
the nrzi option:
encoding nrzi;

To explicitly configure the default NRZ line encoding, include the encoding statement,
specifying the nrz option:
encoding nrz;

You can include this statement at the following hierarchy levels:

[edit interfaces se-pim/0/port serial-options]

[edit interfaces se-fpc/pic/port serial-options]

When setting the line encoding parameter, you must set the same value for paired ports.
Ports 0 and 1 must share the same value.

Specifying a USB Modem Interface on J Series Routers

The J Series routers contain two USB ports controlled by a single USB controller. One
USB port can support USB devices, while the other one can act as a USB modem.
The USB modem provides a dial-in remote management interface, and supports dialer
interface features by sharing the same dial pool as a dialer interface. The dial pool allows
the logical dialer interface (dln) and the physical interface (umd0) to be bound together
dynamically on a per-call basis.
The following dialer interface features are supported by the USB modem interface:

Encapsulation PPP

CoS

NAT

Interface statistics

Packet capture

GRE tunnel

Stateful firewall

Traffic sampling

To configure a USB modem interface, include the following statements at the [edit
interfaces] hierarchy level:
[edit interfaces]
umd0 {
dialer-options {
pool pool-name <priority priority>;
}
modem-options {
dialin (console | routable);
init-command-string initialization-command-string;

316

Copyright 2014, Juniper Networks, Inc.

Chapter 10: Configuring Serial Interfaces

}
}

The pool name specified at the [edit interfaces umd0 dialer-options pool] hierarchy level
must be the same as the pool name specified at the [edit interfaces dln unit
logical-unit-number dialer-options pool] hierarchy level.
Configure the USB modem to operate as a dial-in WAN backup interface by including
the dialin statement and specifying the routable option. If the USB modem is to be used
as a dial-in console, specify the console option in the dialin statement.
When the Services Router applies the modem AT commands configured in the
init-command-string statement or the default sequence of initialization commands to
the modem, it compares them to the initialization commands already configured on the
modem and makes the following changes:

If the commands are the same, the router overrides the existing modem values that
do not match. For example, if the initialization commands on the modem include S0=0
and the routers init-command-string configuration includes S0=2, the Services Router
applies S0=2.

If the initialization commands on the modem do not include a command in the routers
init-command-string statement configuration, the router adds it. For example, if the
init-command-string statement includes the command L2, but the modem commands
do not include it, the router adds L2 to the initialization commands configured on the
modem.

Include the following statements at the [edit interfaces dln] hierarchy level to support a
minimum configuration for a dialer interface connected to a USB modem:
[edit interfaces dln]
encapsulation ppp;
unit logical-unit-number;
dialer-options {
dial-string dial-string-numbers;
pool pool-name <priority priority>;
}
ppp-options {
chap;
access-profile name;
local-name name;
passive;
}
family inet {
mtu bytes;
address address {
destination address;
}
}

For more information about configuring dial-in, see Configuring ISDN Logical Interface
Properties.

Copyright 2014, Juniper Networks, Inc.

317

Interfaces Fundamentals for Routing Devices

318

Copyright 2014, Juniper Networks, Inc.

PART 4

Monitoring and Troubleshooting Interfaces

Monitoring Interfaces on page 321

Troubleshooting Interfaces on page 327

Copyright 2014, Juniper Networks, Inc.

319

Interfaces Fundamentals for Routing Devices

320

Copyright 2014, Juniper Networks, Inc.

CHAPTER 11

Monitoring Interfaces

Tracing Interface Operations Overview on page 321

Tracing Operations of an Individual Router Interface on page 321

Tracing Operations of the Interface Process on page 322

Monitoring a PPP Session on page 323

Tracing Operations of the pppd Process on page 324

Tracing Interface Operations Overview

You can trace the operations of individual router interfaces and those of the interface
process (dcd). For a general discussion of tracing and of the precedence of multiple
tracing operations, see the Junos OS Administration Library for Routing Devices.
For information about the operations of Virtual Router Resolution Protocol
(VRRP)-enabled interfaces, see the Junos OS High Availability Library for Routing Devices.
Related
Documentation

Tracing Operations of an Individual Router Interface on page 321

Tracing Operations of the Interface Process on page 322

Tracing Operations of an Individual Router Interface

To trace the operations of individual router interfaces, perform the following steps:
1.

In configuration mode, go to the [edit interfaces interface-name] hierarchy level:

[edit]
user@host# edit interfaces interface-name

2. Configure the traceoptions option.

[edit interfaces interface-name]

user@host# edit traceoptions
3. Configure the tracing flag.

[edit interfaces interface-name traceoptions]

user@host# set flag flag-option

Copyright 2014, Juniper Networks, Inc.

321

Interfaces Fundamentals for Routing Devices

You can specify the following interface tracing flags:

allTrace all interface operations.

eventTrace all interface events.

ipcTrace all interface interprocess communication (IPC) messages.

mediaTrace all interface media changes.

The interfaces traceoptions statement does not support a trace file. The logging is done
by the kernel, so the tracing information is placed in the system syslog files.
For more information about trace operations, see Tracing Operations of the Interface
Process on page 322.
Related
Documentation

traceoptions on page 922

Tracing Operations of the Interface Process

To trace the operations of the router or switch interface process, dcd, perform the
following steps:
1.

In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces

2. Configure the traceoptions statement.

[edit interfaces]
user@host# edit traceoptions
3. Configure the no-remote-trace option to disable remote tracing.

[edit interfaces traceoptions]

user@host# set no-remote-trace
4. Configure the file filename option.

[edit interfaces traceoptions]

user@host# edit file
5. Configure the files number option, match regular-expression option, size size option,

and world-readable | no-world-readable option.

[edit interfaces traceoptions file]
user@host# set files number
user@host# set match regular-expression
user@host# set size size
user@host# set word-readable | no-world-readable
6. Configure the tracing flag.

[edit interfaces traceoptions]

user@host# set flag flag-option

322

Copyright 2014, Juniper Networks, Inc.

Chapter 11: Monitoring Interfaces

7. Configure the disable option in flag flag-option statement to disable the tracing

operation. You can use this option to disable a single operation when you have defined
a broad group of tracing operations, such as all.
[edit interfaces traceoptions]
user@host# set flag flag-option disable

You can specify the following flags in the interfaces traceoptions statement:

allEnable all configuration logging.

change-eventsLog changes that produce configuration events.

gres-eventsLog the events related to GRES.

resource-usageLog the resource usage for different states.

config-statesLog the configuration state machine changes.

kernelLog configuration IPC messages to kernel.

kernel-detailLog details of configuration messages to kernel.

select-eventsLog the events on select state machine.

By default, interface process operations are placed in the file named dcd and three 1-MB
files of tracing information are maintained.
For general information about tracing, see the tracing and logging information in the
Junos OS Administration Library for Routing Devices.
Related
Documentation

Tracing Interface Operations Overview on page 321

Tracing Operations of an Individual Router Interface on page 321

traceoptions on page 924

Monitoring a PPP Session

You can monitor PPP packet exchanges. When monitoring is enabled, packets exchanged
during a session are logged by default to /var/log/pppd, or to the file specified in the
traceoptions statement.
To monitor a PPP session:
1.

In configuration mode, go to the [edit protocols ppp] hierarchy level.

[edit ]
user@host# edit protocols ppp

2. Include the monitor-session statement.

[edit protocols ppp]

user@host# monitor-session (interface-name | all);

When monitoring is configured, the operational mode commands show ppp summary
and show ppp interface display a Monitored flag in the Session flags column or line.

Copyright 2014, Juniper Networks, Inc.

323

Interfaces Fundamentals for Routing Devices

Related
Documentation

monitor-session on page 712

Tracing Operations of the pppd Process

You can trace the operations of the routers pppd process.
To trace the routers pppd process:
In configuration mode, go to the [edit protocols ppp] hierarchy level.

1.

[edit ]
user@host# edit protocols ppp
2. Include the traceoptions statement.

[edit protocols ppp]

traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
flag flag;
level severity-level;
no-remote-trace;
}

To specify more than one tracing operation, include multiple flag statements.
You can specify the following flags in the traceoptions statement:

324

accessTrace access code

address-poolTrace address pool code

allTrace all areas of code

authTrace authentication code

chapTrace challenge handshake authentication protocol code

ciTrace CI code

configTrace configuration code

ifdbTrace interface database code

lcpTrace LCP state machine code

memoryTrace memory management code

messageTrace message processing code

mlpppTrace multilink point-to-point protocol code

ncpTrace NCP state machine code

papTrace password authentication protocol code

pppTrace PPP protocol processing code

radiusTrace RADIUS processing code

Copyright 2014, Juniper Networks, Inc.

Chapter 11: Monitoring Interfaces

Related
Documentation

redundancyTrace redundancy code

rtsockTrace routing socket code

sessionTrace session management code

signalTrace signal handling code

timerTrace timer code

uiTrace user interface code

traceoptions on page 928

Copyright 2014, Juniper Networks, Inc.

325

Interfaces Fundamentals for Routing Devices

326

Copyright 2014, Juniper Networks, Inc.

CHAPTER 12

Troubleshooting Interfaces

Interface Diagnostics on page 327

Troubleshooting: em0 Management Interface Link is Down on page 334

Troubleshooting: fxp0 Management Interface Link is Down on page 335

Troubleshooting: Faulty Ethernet Physical Interface on an M Series, an MX Series, or a

T Series Router on page 337

Interface Diagnostics
You can use two diagnostic tools to test the physical layer connections of interfaces:
loopback testing and bit error rate test (BERT) testing. Loopback testing enables you to
verify the connectivity of a circuit. BERT testing enables you to identify poor signal quality
on a circuit. This section contains the following topics:

Configuring Loopback Testing on page 327

Interface Diagnostics on page 329

Configuring Loopback Testing

Loopback testing allows you to verify the connectivity of a circuit. You can configure any
of the following interfaces to execute a loopback test: Aggregated Ethernet, Fast Ethernet,
Gigabit Ethernet, E1, E3, NxDS0, serial, SONET/SDH, T1, and T3.
The physical path of a network data circuit usually consists of segments interconnected
by devices that repeat and regenerate the transmission signal. The transmit path on one
device connects to the receive path on the next device. If a circuit fault occurs in the form
of a line break or a signal corruption, you can isolate the problem by using a loopback
test. Loopback tests allow you to isolate segments of the circuit and test them separately.
To do this, configure a line loopback on one of the routers. Instead of transmitting the
signal toward the far-end device, the line loopback sends the signal back to the originating
router. If the originating router receives back its own data link layer packets, you have
verified that the problem is beyond the originating router. Next, configure a line loopback
farther away from the local router. If this originating router does not receive its own data
link layer packets, you can assume the problem is on one of the segments between the
local router and the remote routers interface card. In this case, the next troubleshooting
step is to configure a line loopback closer to the local router to find the source of the
problem.

Copyright 2014, Juniper Networks, Inc.

327

Interfaces Fundamentals for Routing Devices

There are several types of loopback testing supported by the Junos OS, as follows:

DCE localLoops packets back on the local DCE.

DCE remoteLoops packets back on the remote DCE.

LocalUseful for troubleshooting physical PIC errors. Configuring local loopback on

an interface allows transmission of packets to the channel service unit (CSU) and then
to the circuit toward the far-end device. The interface receives its own transmission,
which includes data and timing information, on the local router's PIC. The data received
from the CSU is ignored. To test a local loopback, issue the show interfaces
interface-name command. If PPP keepalives transmitted on the interface are received
by the PIC, the Device Flags field contains the output Loop-Detected.

PayloadUseful for troubleshooting the physical circuit problems between the local
router and the remote router. A payload loopback loops data only (without clocking
information) on the remote routers PIC. With payload loopback, overhead is
recalculated.

RemoteUseful for troubleshooting the physical circuit problems between the local
router and the remote router. A remote loopback loops packets, including both data
and timing information, back on the remote routers interface card. A router at one end
of the circuit initiates a remote loopback toward its remote partner. When you configure
a remote loopback, the packets received from the physical circuit and CSU are received
by the interface. Those packets are then retransmitted by the PIC back toward the
CSU and the circuit. This loopback tests all the intermediate transmission segments.

Table 47 on page 328 shows the loopback modes supported on the various interface types.

Table 47: Loopback Modes by Interface Type

328

Interface

Loopback Modes

Usage Guidelines

Aggregated Ethernet,
Fast Ethernet, Gigabit
Ethernet

Local

Configuring Ethernet Loopback Capability

Circuit Emulation E1

Local and remote

Configuring E1 Loopback Capability

Circuit Emulation T1

Local and remote

Configuring T1 Loopback Capability

E1 and E3

Local and remote

Configuring E1 Loopback Capability and

Configuring E3 Loopback Capability

NxDS0

Payload

Configuring Channelized E1 IQ and IQE Interfaces,

Configuring T1 and NxDS0 Interfaces, Configuring
Channelized OC12/STM4 IQ and IQE Interfaces
(SONET Mode), Configuring Channelized STM1
IQ and IQE Interfaces, and Configuring
Channelized T3 IQ Interfaces

Serial (V.35 and X.21)

Local and remote

Configuring Serial Loopback Capability on

page 314

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

Table 47: Loopback Modes by Interface Type (continued)

Interface

Loopback Modes

Usage Guidelines

Serial (EIA-530)

DCE local, DCE

remote, local, and
remote

Configuring Serial Loopback Capability on

page 314

SONET/SDH

Local and remote

Configuring SONET/SDH Loopback Capability

to Identify a Problem as Internal or External

T1 and T3

Local, payload, and

remote

Configuring T1 Loopback Capability and

Configuring T3 Loopback Capability
See also Configuring the T1 Remote Loopback
Response

To configure loopback testing, include the loopback statement:

loopback mode;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name aggregated-ether-options]

[edit interfaces interface-name ds0-options]

[edit interfaces interface-name e1-options]

[edit interfaces interface-name e3-options]

[edit interfaces interface-name fastether-options]

[edit interfaces interface-name gigether-options]

[edit interfaces interface-name serial-options]

[edit interfaces interface-name sonet-options]

[edit interfaces interface-name t1-options]

[edit interfaces interface-name t3-options]

Interface Diagnostics
BERT allows you to troubleshoot problems by checking the quality of links. You can
configure any of the following interfaces to execute a BERT when the interface receives
a request to run this test: E1, E3, T1, T3; the channelized DS3, OC3, OC12, and STM1
interfaces; and the channelized DS3 IQ, E1 IQ, and OC12 IQ interfaces.
A BERT test requires a line loop to be in place on either the transmission devices or the
far-end router. The local router generates a known bit pattern and sends it out the transmit
path. The received pattern is then verified against the sent pattern. The higher the bit
error rate of the received pattern, the worse the noise is on the physical circuit. As you
move the position of the line loop increasingly downstream toward the far-end router,
you can isolate the troubled portion of the link.

Copyright 2014, Juniper Networks, Inc.

329

Interfaces Fundamentals for Routing Devices

To configure BERT, you must configure the duration of the test, the bit pattern to send
on the transmit path, and the error rate to monitor when the inbound pattern is received.
To configure the duration of the test, the pattern to send in the bit stream, and the error
rate to include in the bit stream, include the bert-period, bert-algorithm, and bert-error-rate
statements, respectively, at the [edit interfaces interface-name interface-type-options]
hierarchy level:
[edit interfaces interface-name interface-type-options]
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;

By default, the BERT period is 10 seconds. You can configure the BERT period to last
from 1 through 239 seconds on some PICs and from 1 through 240 seconds on other PICs.
rate is the bit error rate. This can be an integer from 0 through 7, which corresponds to a
0

bit error rate from 10

(1 error per bit) to 10

(1 error per 10 million bits).

algorithm is the pattern to send in the bit stream. For a list of supported algorithms, enter

a ? after the bert-algorithm statement; for example:

[edit interfaces t1-0/0/0 t1-options]
user@host# set bert-algorithm ?
Possible completions:
pseudo-2e11-o152
Pattern
pseudo-2e15-o151
Pattern
pseudo-2e20-o151
Pattern
pseudo-2e20-o153
Pattern
...

is
is
is
is

2^11
2^15
2^20
2^20

-1 (per O.152 standard)

- 1 (per O.152 standard)
- 1 (per O.151 standard)
- 1 (per O.153 standard)

For specific hierarchy information, see the individual interface types.

NOTE: The 4-port E1 PIC supports only the following algorithms:

pseudo-2e11-o152
pseudo-2e15-o151
pseudo-2e20-o151
pseudo-2e23-o151

Pattern
Pattern
Pattern
Pattern

is
is
is
is

2^11
2^15
2^20
2^23

-1 (per O.152 standard)

- 1 (per O.151 standard)
- 1 (per O.151 standard)
(per O.151 standard)

When you issue the help command from the CLI, all BERT algorithm options
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in system log messages.

330

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

NOTE: The 12-port T1/E1 Circuit Emulation (CE) PIC supports only the
following algorithms:
all-ones-repeating
Repeating one bits
all-zeros-repeating Repeating zero bits
alternating-double-ones-zeros Alternating pairs of ones and zeros
alternating-ones-zeros Alternating ones and zeros
pseudo-2e11-o152
Pattern is 2^11 -1 (per O.152 standard)
pseudo-2e15-o151
Pattern is 2^15 - 1 (per O.151 standard)
pseudo-2e20-o151
Pattern is 2^20 - 1 (per O.151 standard)
pseudo-2e7
Pattern is 2^7 - 1
pseudo-2e9-o153
Pattern is 2^9 - 1 (per O.153 standard)
repeating-1-in-4
1 bit in 4 is set
repeating-1-in-8
1 bit in 8 is set
repeating-3-in-24
3 bits in 24 are set

When you issue the help command from the CLI, all BERT algorithm options
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in system log messages.

NOTE: The IQE PICs support only the following algorithms:

all-ones-repeating
Repeating one bits
all-zeros-repeating Repeating zero bits
alternating-double-ones-zeros Alternating pairs of ones and zeros
alternating-ones-zeros Alternating ones and zeros
pseudo-2e9-o153
Pattern is 2^9 -1 (per O.153 (511 type) standard)
pseudo-2e11-o152
Pattern is 2^11 -1 (per O.152 and O.153 (2047 type)
standards)
pseudo-2e15-o151
Pattern is 2^15 -1 (per O.151 standard)
pseudo-2e20-o151
Pattern is 2^20 -1 (per O.151 standard)
pseudo-2e20-o153
Pattern is 2^20 -1 (per O.153 standard)
pseudo-2e23-o151
Pattern is 2^23 -1 (per O.151 standard)
repeating-1-in-4
1 bit in 4 is set
repeating-1-in-8
1 bit in 8 is set
repeating-3-in-24
3 bits in 24 are set

When you issue the help command from the CLI, all BERT algorithm options
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in system log messages.

Copyright 2014, Juniper Networks, Inc.

331

Interfaces Fundamentals for Routing Devices

NOTE: BERT is supported on the PDH interfaces of the Channelized

SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP and the DS3/E3 MIC.
The following BERT algorithms are supported:
all-ones-repeating
all-zeros-repeating
alternating-double-ones-zeros
alternating-ones-zeros
repeating-1-in-4
repeating-1-in-8
repeating-3-in-24
pseudo-2e9-o153
pseudo-2e11-o152
pseudo-2e15-o151
pseudo-2e20-o151
pseudo-2e20-o153
pseudo-2e23-o151

Repeating one bits

Repeating zero bits
Alternating pairs of ones and zeros
Alternating ones and zeros
1 bit in 4 is set
1 bit in 8 is set
3 bits in 24 are set
Pattern is 2^9 - 1 (per O.153 standard)
Pattern is 2^11 - 1 (per O.152 standard)
Pattern is 2^15 - 1 (per O.151 standard)
Pattern is 2^20 - 1 (per O.151 standard)
Pattern is 2^20 - 1 (per O.153 standard)
Pattern is 2^23 (per O.151 standard)

Table 48 on page 332 shows the BERT capabilities for various interface types.

Table 48: BERT Capabilities by Interface Type

Interface

T1 BERT

12-port T1/E1
Circuit Emulation

Yes (ports 011)

Limited algorithms

4-port
Channelized
OC3/STM1
Circuit Emulation

Yes (port 03)

Limited algorithms

E1 or T1

Yes (port 03)

Single port at a time

Limited algorithms

Yes (port 03)

Comments

E3 or T3

Yes (port 03)

Yes (port 03)

Single port at a time

Channelized
OC12

N/A

Yes (channel
011)

Single channel at a time

Limited algorithms

No bit count

Multiple channels

Only one algorithm

No error insert

No bit count

Multiple ports and channels

Limited algorithms for T1

No error insert for T1

No bit count for T1

Channelized
STM1

Channelized T3
and Multichannel
T3

332

T3 BERT

Yes (channel
062)

Yes (channel
027)

N/A

Yes (port 03 on
channel 0)

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

These limitations do not apply to channelized IQ interfaces. For information about BERT
capabilities on channelized IQ interfaces, see Channelized IQ and IQE Interfaces Properties.

Starting and Stopping a BERT Test

Before you can start the BERT test, you must disable the interface. To do this, include
the disable statement at the [edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
disable;

After you configure the BERT properties and commit the configuration, begin the test by
issuing the test interface interface-name interface-type-bert-start operational mode
command:
user@host> test interface interface-name interface-type-bert-start

The test runs for the duration you specify with the bert-period statement. If you wish to
terminate the test sooner, issue the test interface interface-name interface-type-bert-stop
command:
user@host> test interface interface-name interface-type-bert-stop

For example:
user@host> test interface t3-1/2/0 t3-bert-start
user@host> test interface t3-1/2/0 t3-bert-stop

To view the results of the BERT test, issue the show interfaces extensive | find BERT
command:
user@host> show interfaces interface-name extensive | find BERT

For more information about running and evaluating the results of the BERT procedure,
see the CLI Explorer.

NOTE: To exchange BERT patterns between a local router and a remote

router, include the loopback remote statement in the interface configuration
at the remote end of the link. From the local router, issue the test interface
command.

Example: Configuring Bit Error Rate Testing

Configure a BERT test on a T3 interface. In this example, the run duration lasts for 120
0
seconds. The configured error rate is 0, which corresponds to a bit error rate of 10 (1
error per bit). The configured bit pattern of all-ones-repeating means that every bit the
interface sends is a set to a value of 1.
[edit interfaces]
t3-1/2/0 {
t3-options {
bert algorithm all-ones-repeating;
bert-error-rate 0;
bert-period 120;

Copyright 2014, Juniper Networks, Inc.

333

Interfaces Fundamentals for Routing Devices

}
}

Troubleshooting: em0 Management Interface Link is Down

Problem

Diagnosis

Description: Ethernet Link Down alarm is raised when you run the show chassis alarm
operational mode command on a T640 router, a T1600 router, T4000 router, or a TX
Matrix Plus router.

Perform the following tests to check if the em0 management interface is down on the
master Routing Engine or the backup Routing Engine:
1.

Run the show chassis alarms command.

show chassis alarms

user@host0> show chassis alarms
1 alarms currently active
Alarm time Class Description
2011-10-19 11:13:02 MYT Major Host 1 em0 : Ethernet Link Down

Is the alarm Ethernet Link Down displayed against the em0 interface of the master
Routing Engine (Host 0)?

Yes: Contact JTAC for further assistance.

No: Continue to the next diagnostic test.

2. Run the show interfaces em0 and the show interfaces em0 terse operational mode

commands.
show interfaces em0
user@host> show interfaces em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 1, SNMP ifIndex: 1
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 100mbps
Device flags : Present Running
Interface flags: SNMP-Traps
...

show interfaces em0 terse

user@host> show interfaces em0 terse
Interface Admin Link Proto Local Remote
em0 up up
em0.0 up up inet 10.100.100.1/30

Is the em0 interface on the master Routing Engine up?

334

Yes: Continue to resolution.

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

Resolution

No: Contact JTAC for further assistance

To Resolve This Issue

From the aforementioned diagnosis, we ascertain that the chassis alarm has been raised
for the em0 management interface in the backup Routing Engine (Host 1) and not for
the master Routing Engine (Host 0).
Implement one of the following solutions on the backup Routing Engine to resolve this
issue:

Disable the em0 interface in the backup Routing Engine:

1.

In configuration mode, go to the [edit groups re1] hierarchy level.

user@host1# edit groups re1

2. Disable the em0 interface.

[edit groups re1]

user@host1# set interfaces em0 disable

Ignore the alarm:

1.

In configuration mode, go to the [edit chassis] hierarchy level.

user@host1# edit chassis

2. Ignore the Ethernet link down alarm on the management interface by setting the

management-ethernet link-down alarm option to ignore.

[edit chassis]
user@host1# set alarm management-ethernet link-down ignore

Related
Documentation

Supported Routing Engines by Router on page 14

show chassis alarms

Troubleshooting: fxp0 Management Interface Link is Down

Problem

Diagnosis

Description: Ethernet Link Down alarm is raised when you run the show chassis alarm
operational mode command on an M Series router, an MX Series router, a T320 router,
a T640 router, a T1600 router, or on a TX Matrix router.

Perform the following tests to check if the fxp0 interface is down on the master Routing
Engine or the backup Routing Engine:
1.

Run the show chassis alarms command.

show chassis alarms

user@host0> show chassis alarms
1 alarms currently active

Copyright 2014, Juniper Networks, Inc.

335

Interfaces Fundamentals for Routing Devices

Alarm time Class Description

2011-10-19 11:13:02 MYT Major Host 1 fxp0 : Ethernet Link Down

Is the alarm Ethernet Link Down displayed against the fxp0 interface of the master
Routing Engine (Host 0)?

Yes: Contact JTAC for further assistance.

No: Continue to the next diagnostic test.

2. Run the show interfaces fxp0 and the show interfaces fxp0 terse operational mode

commands.
show interfaces fxp0
user@host> show interfaces fxp0
Physical interface: fxp0, Enabled, Physical link is Up
Interface index: 1, SNMP ifIndex: 1
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 100mbps
Device flags : Present Running
Interface flags: SNMP-Traps
...

show interfaces fxp0 terse

user@host> show interfaces fxp0 terse
Interface Admin Link Proto Local Remote
fxp0 up up
fxp0.0 up up inet 10.100.100.1/30

Is the fxp0 interface on the master Routing Engine up?

Resolution

Yes: Continue to resolution.

No: Contact JTAC for further assistance

To Resolve This Issue

From the diagnosis, we ascertain that the chassis alarm has been raised for the fxp0
management interface in the backup Routing Engine (Host 1) and not for the master
Routing Engine (Host 0).
Implement one of the following solutions on the backup Routing Engine to avoid this
issue:

Disable the fxp0 interface in the backup Routing Engine:

1.

In configuration mode, go to the [edit groups re1] hierarchy level.

user@host1# edit groups re1

2. Disable the fxp0 interface.

[edit groups re1]

user@host1# set interfaces fxp0 disable

336

Ignore the alarm:

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

1.

In configuration mode, go to the [edit chassis] hierarchy level.

user@host1# edit chassis

2. Ignore the Ethernet link down alarm on the management interface by setting the

management-ethernet link-down alarm option to ignore.

[edit chassis]
user@host1# set alarm management-ethernet link-down ignore

Related
Documentation

Supported Routing Engines by Router on page 14

show chassis alarms

Troubleshooting: Faulty Ethernet Physical Interface on an M Series, an MX Series, or

a T Series Router
You can follow the basic troubleshooting checklist as explained in the following topics
from one through five to troubleshoot an Ethernet physical interface on an M Series, MX
Series, or a T Series router.
1.

Checking the Cable Connection on page 337

2. Checking the Physical Link Status of the Interface on page 338

3. Checking the Interface Statistics in Detail on page 339
4. Performing the Loopback Diagnostic Test on page 341
5. Checking Other Possibilities on page 343
6. To Enable a Physical Interface on page 344

Checking the Cable Connection

Problem

Diagnosis

Resolution

Description: Packets are not received or transmitted over the Ethernet physical interface.

1.

Is the correct cable connected to the correct port?

Yes: Continue to Checking the Physical Link Status of the Interface on page 338.

No: See Resolving Cabling Issue on page 337.

Resolving Cabling Issue

Perform one or more of the following steps to resolve the cabling issue:
1.

Connect the cable properly on the local and remote ends without any loose
connections.

2. Swap the Ethernet cable for a known good cable if the existing cable is damaged.

Copyright 2014, Juniper Networks, Inc.

337

Interfaces Fundamentals for Routing Devices

3. Connect a single-mode fiber cable to a single-mode interface only and a multimode

fiber cable to a multimode interface only. To check fiber optic cable integrity, see
Checking Fiber Optic Cable Integrity on page 338.
4. Connect the correct small form-factor pluggable transceiver (SFP) on both sides of

the cable.
Checking Fiber Optic Cable Integrity
To check the integrity of fiber optic cable with an external cable diagnostic testing tool:

NOTE: A single-mode fiber cable must be connected to a single-mode

interface and a multi-mode fiber cable must be connected to a multi-mode
interface.

1.

Measure the received light level at the receiver (R ) port to see whether the received
X

light level is within the receiver specification of the Ethernet interface.

2. Measure transmitted light level at the transmitter (T ) port to see whether the
X

transmitted light level is within the transmitter specification of the Ethernet interface.

Checking the Physical Link Status of the Interface

Problem

Description: Unable to transmit and receive packets on the Ethernet interface even
though the cable connection is correct.

Solution

To display the physical link status of the interface, run the show interface interface-name
media operational mode command. For example, on the ge-5/0/1 interface.
user@host> show interfaces ge-5/0/1 media
Physical interface: ge-5/0/1, Enabled, Physical link is Up
Interface index: 317, SNMP ifIndex: 1602
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online, Speed-negotiation: Disabled,
Auto-MDIX: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Current address: 2c:6b:f5:4c:26:73, Hardware address: 2c:6b:f5:4c:26:73
Last flapped
: 2012-11-30 01:25:37 UTC (03:46:55 ago)
Input rate
: 880 bps (1 pps)
Output rate
: 312 bps (0 pps)
Active alarms : None
Active defects : None
MAC statistics:
Input bytes: 901296, Input packets: 9799, Output bytes: 976587, Output packets:
10451
Filter statistics:
Filtered packets: 68, Padded packets: 0, Output packet errors: 0
Autonegotiation information:

338

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

Negotiation status: Complete

Link partner:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote fault:
OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Interface transmit statistics: Disabled

For information about show interfaces interface-name media, see show interfaces (Gigabit
Ethernet).

Diagnosis

1.

Are there any connectivity problems such as input errors and packet loss even though
the Enabled field displays Physical link is Up status and the Active alarms and Active
defect field displays None?

Yes: Go to Checking the Interface Statistics in Detail on page 339.

No: Continue to the next diagnostic test.

2. Does the Enabled field display Physical link is Down status and the Active alarms and

Active defect field display Link?

Yes: The interface is either not connected correctly or is not receiving a valid signal.
Go to Resolving Cabling Issue on page 337.

No: Continue.

Checking the Interface Statistics in Detail

Problem

Description: The physical interface is not working even though the Enabled field displays
Physical link is Up status and the Active alarms and Active defect field displays None.

Solution

To display the interface statistics in detail, run the show interface interface-name extensive
operational command. For example, on ge-5/0/1 interface.
user@host> show interfaces ge-5/0/1 extensive
Physical interface: ge-5/0/1, Enabled, Physical link is Up
Interface index: 317, SNMP ifIndex: 1602, Generation: 322
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online, Speed-negotiation: Disabled,
Auto-MDIX: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 2c:6b:f5:4c:26:73, Hardware address: 2c:6b:f5:4c:26:73
Last flapped
: 2012-11-30 01:25:37 UTC (04:38:32 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
806283
0 bps

Copyright 2014, Juniper Networks, Inc.

339

Interfaces Fundamentals for Routing Devices

Output bytes :
1153215
424 bps
Input packets:
10818
0 pps
Output packets:
11536
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Label-switched interface (LSI) traffic statistics:
Input bytes :
0
0 bps
Input packets:
0
0 pps
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: 233060,
L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 11, Errors: 0, Drops: 0, Collisions: 0, Aged packets:
0, FIFO errors: 0, HS link CRC errors: 0,
MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

3216

3216

1 expedited-fo

2 assured-forw

3 network-cont

8320

8320

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : None
Active defects : None
MAC statistics:
Receive
Total octets
1007655
Total packets
10886
Unicast packets
4350
Broadcast packets
32
Multicast packets
6504
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
10886
Input packet rejects
68
Input DA rejects
68

340

Transmit
1082219
11536
4184
77
7275
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

Input SA rejects
0
Output packet count
11536
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:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote fault:
OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Packet Forwarding Engine configuration:
Destination slot: 5
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
Interface transmit statistics: Disabled

For information about show interfaces interface-name detail, see show interfaces (Gigabit
Ethernet).

Diagnosis

1.

Does the Policed discards, L2 channel errors, Input DA rejects, or the Input SA rejects
field display any errors?
For information about the errors, seeshow interfaces (Gigabit Ethernet).

Yes: Resolve the errors as needed. Resolving these errors is beyond the scope of
this topic.

No: Continue with Performing the Loopback Diagnostic Test on page 341.

Performing the Loopback Diagnostic Test

Problem

Description: The interface cable is connected correctly and there are no alarms or errors
associated with the Ethernet physical interface yet the interface is not working.

Solution

To check whether the Ethernet port or PIC is faulty, you must perform the internal loopback
test and hardware loopback test.
To perform a internal loopback diagnostic test on an Ethernet interface, for example on
ge-5/0/1 interface:
1.

In configuration mode, go to the [edit interfaces ge-5/0/1] hierarchy level.

[edit]
user@host# edit interface ge-5/0/1

Copyright 2014, Juniper Networks, Inc.

341

Interfaces Fundamentals for Routing Devices

2. Set the gigether-options option as loopback, commit the configuration and quit

configuration mode.
[edit interfaces ge-5/0/1
user@host# set gigether-options loopback
user@host# commit
user@host# quit
3. In operational mode, execute the show interfaces ge-5/0/1 media command.
user@host> show interfaces ge-5/0/1 media
Physical interface: ge-5/0/1, Enabled, Physical link is Up
Interface index: 317, SNMP ifIndex: 1602
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Enabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online, Speed-negotiation: Disabled,
Auto-MDIX: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Current address: 2c:6b:f5:4c:26:73, Hardware address: 2c:6b:f5:4c:26:73
Last flapped
: 2012-11-30 01:25:37 UTC (03:46:55 ago)
Input rate
: 880 bps (1 pps)
Output rate
: 312 bps (0 pps)
Active alarms : None
Active defects : None
MAC statistics:
Input bytes: 901296, Input packets: 9799, Output bytes: 976587, Output
packets: 10451
Filter statistics:
Filtered packets: 68, Padded packets: 0, Output packet errors: 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote
fault: OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Interface transmit statistics: Disabled

NOTE: Delete the loopback statement after completing your diagnosis.

Execute one of the following steps for a hardware loopback diagnostic test as needed:

For an Ethernet PIC with a fiber optic interfacePhysically loop the T and R port
X

and check the status of the physical link with the show interfaces interface-name media
operational mode command.

For an Ethernet PIC with an RJ-45 Ethernet interfaceBuild a loopback plug by crossing
pin 1 (T +) to pin 3 (R +) together and pin 2 (T -) and pin 6 (R -) together and check
X

the status of the physical link with the show interfaces interface-name media operational
mode command.

342

Copyright 2014, Juniper Networks, Inc.

Chapter 12: Troubleshooting Interfaces

NOTE: For information about loopback testing, see Performing Loopback

Testing for Fast Ethernet and Gigabit Ethernet Interfaces.

Diagnosis

1.

Does the Enabled field display Physical link is Up status and the Active alarms and
Active defect field display None when you perform the loopback test?

Yes: Go to the Checking Other Possibilities on page 343 section.

No: Continue to the next diagnostic test.

2. When the Ethernet interface is connected to a remote Ethernet device over multiple

patch panels, check to see whether the connection can be looped back at the different
patch panels so you can conduct a loopback diagnostic test. Is the loopback diagnostic
test successful?

Yes: Go to the Checking Other Possibilities on page 343 section.

No: Contact JTAC for further assistance.

Checking Other Possibilities

Problem

Description: Loopback diagnostic test is successful but unable to transmit and receive
packets on the Ethernet interface.

Solution

Use the following commands as needed to troubleshoot an Ethernet interface, for

example, an ge-5/0/1 interface:

Run the show interfaces interface-name terse operational command to check if the
physical interface and logical interfaces are administratively disabled. For example,
on ge-5/0/1 interface.
user@host> show interfaces ge-5/0/1 terse
Interface
Admin Link Proto
ge-5/0/1
up
up
ge-5/0/1.0
up
up
inet

Diagnosis

1.

Local

Remote

20.1.1.2/24

Does the physical interface and its corresponding logical interfaces display down in
the output of the show interfaces interface-name terse operational mode command?

Yes: Enable the interfaces as shown in To Enable a Physical Interface on page 344.

No: Continue to the next diagnostic test.

2. Are the speed, duplex, and auto-negotiation fields in the output of show interfaces

interface-name extensive operational mode command correctly set for the interface?

Copyright 2014, Juniper Networks, Inc.

343

Interfaces Fundamentals for Routing Devices

NOTE: Check if the associated Flexible PIC Concentrator (FPC), Modular

Port Concentrator (MPC), or Dense Port Concentrator (DPC) and its
Modular Interface Card (MIC) or PIC with its 10-gigabit small form-factor
pluggable transceiver (XFP) or SFP supports speed and auto-negotiation
settings.

Yes: Check Monitoring Fast Ethernet and Gigabit Ethernet Interfaces for more
troubleshooting tips.

No: Contact JTAC for further assistance.

To Enable a Physical Interface

To enable a physical interface:
1.

In configuration mode, go to the [edit interfaces] hierarchy level.

[edit]
user@host# edit interfaces

2. Check if the interface is administratively disabled by executing the show command

on the interface. For example on ge-5/0/1 interface.

user@host# show ge-5/0/1
disable;
3. Enable the interface and commit.

[edit interfaces
user@host# delete interface-name disable
user@host# commit

344

Copyright 2014, Juniper Networks, Inc.

PART 5

Configuration Statements and

Operational Commands

Configuration Statements on page 347

Interface Operational Commands on page 993

ANCP Operational Commands on page 1411

BFD Operational Commands on page 1449

BGP Operational Commands on page 1461

ES-IS Operational Commands on page 1503

IP Multicast Operational Commands on page 1513

IPv6 Operational Commands on page 1753

IS-IS Operational Commands on page 1761

LLDP Operational Commands on page 1819

MVRP Operational Commands on page 1839

OSPF Operational Commands on page 1851

Protocol-Independent Routing Operational Commands on page 1929

RIP Operational Commands on page 2133

RIPng Operational Commands on page 2143

Firewall Filter Operational Commands on page 2153

Layer 2 Bridging and Switching Operational Commands on page 2175

VPN Operational Commands on page 2205

Copyright 2014, Juniper Networks, Inc.

345

Interfaces Fundamentals for Routing Devices

346

Copyright 2014, Juniper Networks, Inc.

CHAPTER 13

Configuration Statements

[edit chassis] Hierarchy Level on page 365

[edit firewall] Hierarchy Level on page 367

[edit interfaces] Hierarchy Level on page 368

[edit logical-systems] Hierarchy Level on page 384

[edit protocols connections] Hierarchy Level on page 389

[edit protocols dot1x] Hierarchy Level on page 390

[edit protocols iccp] Hierarchy Level on page 390

[edit protocols lacp] Hierarchy Level on page 391

[edit protocols oam] Hierarchy Level on page 391

[edit protocols ppp] Hierarchy Level on page 393

[edit protocols pppoe] Hierarchy Level on page 394

[edit protocols protection-group] Hierarchy Level on page 394

[edit protocols vrrp] Hierarchy Level on page 395

[edit system processes] Hierarchy Level on page 395

802.3ad on page 396

accept on page 397

accept-source-mac on page 399

access-concentrator on page 401

access-profile on page 402

accounting on page 403

accounting-profile on page 403

acfc on page 404

acknowledge-retries on page 405

acknowledge-timer on page 406

action (OAM) on page 406

action (Policer) on page 407

action-profile (Applying to CFM) on page 407

action-profile (Defining for CFM) on page 408

Copyright 2014, Juniper Networks, Inc.

347

Interfaces Fundamentals for Routing Devices

348

action-profile (Defining for LFM) on page 409

action-red-differential-delay on page 410

activation-delay on page 410

activation-priority on page 411

address on page 412

advertise-interval on page 414

age on page 414

agent-specifier on page 415

aggregate (Gigabit Ethernet CoS Policer) on page 416

aggregate (Hierarchical Policer) on page 417

aggregate (SONET/SDH) on page 417

aggregate-ports on page 418

aggregated-ether-options on page 419

aggregated-sonet-options on page 420

alarm (optics-options) on page 421

alias (Interfaces) on page 422

allow-any-vci on page 422

allow-fragmentation on page 423

allow-remote-loopback on page 423

annex on page 424

apply-action-profile on page 424

aps on page 425

arp (Interfaces) on page 426

asynchronous-notification on page 427

atm-encapsulation on page 427

atm-options on page 428

atm-scheduler-map on page 429

authentication on page 430

authentication-key on page 431

authentication-profile-name on page 431

authenticator on page 432

auto-configure on page 433

auto-discovery on page 434

auto-negotiation on page 435

auto-negotiation (J Series uPIM) on page 436

auto-reconnect on page 437

backup-destination on page 437

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

backup-interface on page 438

backup-options on page 438

bandwidth (Interfaces) on page 439

bandwidth-limit (Hierarchical Policer) on page 440

bandwidth-limit (Policer for Gigabit Ethernet Interfaces) on page 441

bchannel-allocation on page 441

bearer-bandwidth-limit on page 442

bert-algorithm on page 443

bert-error-rate on page 445

bert-period on page 447

bridge-domain on page 448

broadcast on page 449

buildout (E3 or T3 over ATM Interfaces) on page 450

buildout (T1 Interfaces) on page 451

bundle on page 452

burst-size-limit (Hierarchical Policer) on page 453

burst-size-limit (Policer for Gigabit Ethernet Interfaces) on page 454

byte-encoding on page 455

bytes on page 456

calculation-weight on page 457

callback on page 458

callback-wait-period on page 459

caller on page 460

calling-number on page 461

cbit-parity on page 461

cbr on page 462

cell-bundle-size on page 463

chap on page 464

chap-secret on page 465

circuit-type on page 465

cisco-interoperability on page 466

classifier on page 466

clear-dont-fragment-bit on page 467

client on page 467

clock-rate on page 468

clocking on page 469

clocking-mode on page 470

Copyright 2014, Juniper Networks, Inc.

349

Interfaces Fundamentals for Routing Devices

350

community (Policy Options) on page 471

compatibility-mode on page 474

compression (PPP Properties) on page 475

compression (Voice Services) on page 476

compression-device on page 476

connections on page 477

connection-protection-tlv on page 477

connectivity-fault-management on page 478

container-devices on page 480

container-list on page 480

container-options on page 481

container-type on page 481

continuity-check on page 482

control-channel on page 483

control-polarity on page 484

control-signal on page 484

copy-tos-to-outer-ip-header on page 485

core-dump on page 485

crc-major-alarm-threshold on page 486

crc-minor-alarm-threshold on page 487

cts on page 488

cts-polarity on page 488

current on page 489

cycle-time on page 489

damping (Interfaces) on page 490

data-channel on page 492

data-input on page 493

data-tlv-size on page 494

dcd on page 495

dcd-polarity on page 495

dce on page 496

dce-options on page 496

deactivation-delay on page 497

default-actions on page 497

default-chap-secret on page 498

default-pap-password on page 498

delimiter on page 499

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

demux-destination (Underlying Interface) on page 499

demux-destination (Demux Interface) on page 500

demux-options (Static Interface) on page 500

demux-source (Demux Interface) on page 501

demux-source (Underlying Interface) on page 502

demux0 (Static Interface) on page 503

demux0 (Dynamic Interface) on page 504

description (Interfaces) on page 505

destination (IPCP) on page 506

destination (Routing Instance) on page 506

destination (Tunnels) on page 507

destination-class-usage on page 508

destination-profile on page 508

dial-options on page 509

dial-string on page 510

dialer on page 510

dialer-options on page 511

dialin on page 512

direction on page 512

disable (Interface) on page 513

disable (Link Protection) on page 514

disable-mlppp-inner-ppp-pfc on page 514

dlci on page 515

do-not-fragment on page 516

domain-name on page 516

dot1x on page 517

down-count on page 518

drop (PPPoE Service Name Tables) on page 519

drop-timeout on page 519

ds0-options on page 520

dsl-options on page 520

dsr on page 521

dsr-polarity on page 521

dte-options on page 522

dtr on page 523

dtr-circuit on page 524

dtr-polarity on page 524

Copyright 2014, Juniper Networks, Inc.

351

Interfaces Fundamentals for Routing Devices

352

dump-on-flow-control on page 525

dynamic-call-admission-control on page 526

dynamic-profile (PPP) on page 527

dynamic-profile (PPPoE Service Name Tables) on page 528

dynamic-profile (Stacked VLAN) on page 529

dynamic-profile (VLAN) on page 530

dynamic-profiles on page 531

e1-options on page 538

e3-options on page 539

east-interface on page 540

egress-policer-overhead on page 541

encapsulation (Container Interface) on page 542

encapsulation (Logical Interface) on page 543

encapsulation (Physical Interface) on page 547

encoding on page 551

epd-threshold (Logical Interface) on page 552

epd-threshold (Physical Interface) on page 553

es-options on page 553

ethernet (Protocols OAM) on page 554

ethernet-policer-profile on page 557

ethernet-ring on page 558

ethernet-switch-profile on page 559

eui-64 on page 560

evcs on page 561

event (LFM) on page 562

event-thresholds on page 562

fast-aps-switch on page 563

f-max-period on page 564

facility-override on page 564

failover-delay on page 565

family (Dynamic Standard Interface) on page 566

family on page 568

fastether-options on page 572

fcs on page 573

feac-loop-respond on page 574

filter on page 575

filter (Applying to an Interface) on page 576

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

flexible-vlan-tagging on page 577

flow-control on page 578

flow-control-options on page 579

force on page 579

forward-and-send-to-re on page 580

forwarding-class (ATM2 IQ Scheduler Maps) on page 580

forwarding-class (Gigabit Ethernet IQ Classifier) on page 581

forward-only on page 581

fragment-threshold on page 582

frame-error on page 583

frame-period on page 584

frame-period-summary on page 585

framing (E1, E3, and T1 Interfaces) on page 586

framing (10-Gigabit Ethernet Interfaces) on page 587

framing (SONET and SDH Interfaces) on page 588

gigether-options on page 589

gratuitous-arp-reply on page 590

guard-interval on page 591

hardware-assisted-timestamping on page 592

high-plp-threshold on page 593

hello-timer on page 593

hierarchical-policer on page 594

hierarchical-scheduler (Subscriber Interfaces on MX Series Routers) on page 595

high-plp-max-threshold on page 596

high-plp-threshold on page 597

hold-interval (OAM) on page 597

hold-interval (Protection Group) on page 598

hold-time (APS) on page 598

hold-time (Physical Interface) on page 599

hold-time (SONET/SDH Defect Triggers) on page 601

host (Interfaces) on page 602

iccp on page 603

idle-cycle-flag on page 604

idle-timeout on page 605

ieee802.1p on page 605

if-exceeding on page 606

igmp-snooping on page 607

Copyright 2014, Juniper Networks, Inc.

353

Interfaces Fundamentals for Routing Devices

354

ignore on page 608

ignore-all on page 608

ignore-l3-incompletes on page 609

ilmi on page 609

ima-group-options on page 610

ima-link-options on page 612

inactivity-timeout on page 612

incoming-called-number on page 613

incoming-map on page 614

indication on page 615

indication-polarity on page 615

ingress-policer-overhead on page 616

ingress-rate-limit on page 616

init-command-string on page 617

initial-route-check on page 618

inner-tag-protocol-id on page 619

inner-vlan-id on page 620

inner-vlan-id-range on page 621

input on page 621

input-list on page 622

input-policer on page 623

input-priority-map on page 624

input-three-color on page 625

input-vlan-map (Aggregated Ethernet) on page 626

input-vlan-map on page 627

instance on page 627

interface (Hierarchical CoS Schedulers) on page 628

interface (IEEE 802.1x) on page 629

interface (IEEE 802.1ag OAM Connectivity-Fault Management) on page 630

interface (OAM Link-Fault Management) on page 631

interface (Port Mirroring) on page 632

interface-down on page 632

interface-name on page 633

interface-none on page 633

interface-range on page 634

interface-transmit-statistics on page 635

interface-set (Ethernet Interfaces) on page 635

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interface-set (IP Demux Interfaces) on page 636

interface-shared-with on page 636

interface-status-tlv on page 637

interface-switch on page 638

interface-type (Interfaces) on page 639

interfaces on page 640

interfaces (Static and Dynamic Subscribers) on page 641

interleave-fragments on page 645

interval on page 645

inverse-arp on page 646

invert-data on page 647

ipsec-sa on page 648

isdn-options on page 649

iteration-count on page 650

iteration-period on page 650

keep-address-and-control on page 651

keepalives on page 652

key on page 653

l2tp-interface-id on page 653

lacp (802.3ad) on page 654

lacp (Aggregated Ethernet) on page 655

layer2-policer on page 657

lcp-max-conf-req on page 658

lcp-restart-timer on page 658

level on page 659

line-encoding on page 660

line-protocol on page 661

line-rate on page 661

linear-red-profile on page 662

linear-red-profiles on page 663

link-adjacency-loss on page 663

link-discovery on page 664

link-down on page 664

link-event-rate on page 665

link-fault-management on page 666

link-layer-overhead on page 667

link-mode on page 668

Copyright 2014, Juniper Networks, Inc.

355

Interfaces Fundamentals for Routing Devices

356

link-protection on page 670

link-speed (Aggregated Ethernet) on page 671

link-speed (Aggregated SONET/SDH) on page 672

linktrace on page 673

lmi (Frame Relay) on page 674

lmi (Ethernet OAM) on page 676

lmi-type on page 677

load-interval on page 678

load-threshold on page 679

local-name on page 680

local-password on page 681

lockout on page 681

log-prefix (Interfaces) on page 682

logical-interface-fpc-redundancy (Aggregated Ethernet Subscriber

Interfaces) on page 682

logical-interface-policer on page 683

logical-systems on page 684

long-buildout on page 684

loop-timing on page 685

loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3) on page 686

loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) on page 688

loopback (Serial) on page 689

loopback-clear-timer on page 690

loss-priority on page 690

loss-threshold on page 691

low-plp-max-threshold on page 691

low-plp-threshold on page 692

lowest-priority-defect on page 693

lsq-failure-options on page 694

mac on page 694

mac-address (Accept Source Mac) on page 695

mac-address (VLAN and Stacked VLAN Interfaces) on page 695

mac-learn-enable on page 696

mac-validate on page 697

maintenance-association on page 698

maintenance-domain on page 699

master-only on page 700

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

maximum-contexts on page 701

maximum-requests on page 701

maximum-vcs on page 702

mc-ae on page 703

member-interface-speed on page 705

member-interface-type on page 706

mep on page 707

minimum-links on page 708

mip-half-function on page 709

mlfr-uni-nni-bundle-options on page 710

mode (Dynamic Profiles) on page 711

mode (Interfaces) on page 711

modem-options on page 712

monitor-session on page 712

mpls (Interfaces) on page 713

mrru on page 714

mtu on page 715

multi-chassis-protection on page 719

multicast-dlci on page 720

multicast-only on page 720

multicast-statistics on page 721

multicast-vci on page 722

multilink-max-classes on page 723

multipoint on page 723

multipoint-destination on page 724

multiservice-options on page 725

n391 on page 726

n392 on page 727

n393 on page 728

name-format on page 729

native-vlan-id on page 730

ncp-max-conf-req on page 731

ncp-restart-timer on page 732

nd6-stale-time on page 733

negotiate-address on page 734

negotiation-options on page 734

neighbor (Automatic Protection Switching for SONET/SDH) on page 735

Copyright 2014, Juniper Networks, Inc.

357

Interfaces Fundamentals for Routing Devices

358

no-allow-link-events on page 735

no-aggregate-delegate-processing on page 736

asynchronous-notification on page 736

no-auto-mdix on page 737

auto-negotiation on page 738

auto-negotiation (J Series uPIM) on page 739

cbit-parity on page 740

core-dump on page 740

feac-loop-respond on page 741

flow-control on page 742

gratuitous-arp-reply on page 743

no-gratuitous-arp-request on page 743

no-keepalives on page 744

long-buildout on page 745

loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) on page 746

mac-learn-enable on page 747

no-partition on page 748

payload-scrambler on page 750

no-pre-classifier on page 751

no-redirects on page 752

source-filtering on page 753

syslog (Monitoring) on page 754

no-termination-request on page 754

translate-discard-eligible on page 755

translate-fecn-and-becn on page 755

unframed on page 756

z0-increment on page 756

node-id on page 757

non-revertive (Interfaces) on page 757

oam on page 758

oam-liveness on page 761

oam-period on page 762

oc-slice on page 763

open-timeout on page 763

operating-mode on page 764

optics-options on page 765

option-82 on page 766

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

otn-options on page 767

output on page 768

output-list on page 769

output-policer on page 770

output-priority-map on page 771

output-three-color on page 772

output-vlan-map (Aggregated Ethernet) on page 773

output-vlan-map on page 774

overflow (Receive Bucket) on page 775

overflow (Transmit Bucket) on page 775

override on page 776

pado-advertise on page 777

paired-group on page 777

pap on page 778

pap-password on page 779

partition on page 780

passive (CHAP) on page 781

passive (PAP) on page 781

passive-monitor-mode on page 782

password (Interfaces) on page 783

path-database-size on page 783

path-trace on page 784

payload-scrambler on page 785

payload-size on page 786

pdu-interval on page 786

pdu-threshold on page 787

peer on page 788

peer-unit on page 789

per-unit-scheduler on page 790

performance-monitoring on page 791

periodic on page 792

pfc on page 792

pic-type on page 793

plp-to-clp on page 793

plp1 on page 794

point-to-point on page 795

policer (CFM Firewall) on page 795

Copyright 2014, Juniper Networks, Inc.

359

Interfaces Fundamentals for Routing Devices

360

policer (CFM Global) on page 796

policer (CFM Session) on page 797

policer (CoS) on page 798

policer (Interface) on page 799

policer (MAC) on page 800

policy-statement on page 801

pool on page 805

pop on page 806

pop-all-labels on page 807

pop-pop on page 808

pop-swap on page 809

port on page 810

port-priority on page 810

port-status-tlv on page 811

post-service-filter on page 811

ppp-options on page 812

pppoe-options on page 813

pppoe-underlying-options (Static and Dynamic Subscribers) on page 814

preferred on page 815

preferred-source-address on page 816

premium (Hierarchical Policer) on page 817

premium (Output Priority Map) on page 818

premium (Policer) on page 818

preserve-interface on page 819

primary (Address on Interface) on page 820

primary (AS PIC or Multiservices PIC Interfaces) on page 820

priority (OAM Connectivity-Fault Management) on page 821

priority (Schedulers) on page 821

promiscuous-mode on page 822

protect-circuit on page 823

protection-group on page 824

protocol-down on page 826

protocols on page 826

proxy on page 827

proxy-arp on page 828

push on page 829

push-push on page 830

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

queue-depth on page 831

queue-length on page 832

queues on page 832

quiet-period on page 833

radius-realm on page 833

ranges (Dynamic Stacked VLAN) on page 834

ranges (Dynamic VLAN) on page 834

rate on page 835

rate on page 835

rdi on page 836

reassemble-packets on page 836

reauthentication on page 837

receive-bucket on page 838

receive-options-packets on page 838

receive-ttl-exceeded on page 839

red-differential-delay on page 839

redial-delay on page 840

redundancy-options on page 841

remote on page 842

remote-loopback on page 842

remote-loopback-respond on page 843

remote-mep on page 844

remove-when-no-subscribers on page 844

request on page 845

required-depth on page 846

restore-interval on page 847

retries on page 848

revert-time (Interfaces) on page 848

revertive on page 849

rfc-2615 on page 849

ring-protection-link-end on page 850

ring-protection-link-owner on page 850

routing-instance on page 851

routing-instance (PPPoE Service Name Tables) on page 852

rpf-check (Dynamic Profiles) on page 853

rpf-check (interfaces) on page 854

rpf-loose-mode-discard on page 855

Copyright 2014, Juniper Networks, Inc.

361

Interfaces Fundamentals for Routing Devices

362

rtp on page 855

rts on page 856

rts-polarity on page 856

rtvbr on page 857

sa-multicast (100-Gigabit Ethernet) on page 859

sampling (Interfaces) on page 860

satop-options on page 861

shared-interface on page 862

scheduler-maps (For ATM2 IQ Interfaces) on page 863

schedulers on page 863

secondary on page 864

send-critical-event on page 864

serial-options on page 865

server on page 866

server-timeout on page 866

service (Logical Interfaces) on page 867

service (PPPoE) on page 868

service-domain on page 869

service-filter (Interfaces) on page 870

service-name on page 870

service-name-table on page 871

service-name-tables on page 872

service-set on page 873

services (Priority Level) on page 874

services-options on page 875

shaping on page 876

shdsl-options on page 877

short-name-format on page 878

short-sequence on page 879

sla-iterator-profile on page 880

sla-iterator-profiles on page 881

snext on page 882

snr-margin on page 883

sonet-options on page 884

source on page 886

source-address-filter on page 887

source-class-usage on page 888

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

source-filtering on page 889

speed (Ethernet) on page 890

speed (MX Series DPC) on page 891

speed (SONET/SDH) on page 892

spid1 on page 892

spid2 on page 893

stacked-vlan-ranges on page 894

stacked-vlan-tagging on page 895

start-end-flag on page 896

static-interface on page 897

static-tei-val on page 898

supplicant on page 898

supplicant-timeout on page 899

swap on page 900

swap-push on page 901

swap-swap on page 902

switch-options on page 903

switch-port on page 904

switch-type on page 905

switching-mode on page 906

symbol-period on page 907

syslog (Interfaces) on page 908

syslog (Monitoring) on page 908

syslog (OAM Action) on page 909

system-priority on page 909

t1-options on page 910

t310 on page 911

t391 on page 911

t392 on page 912

t3-options on page 913

tag-protocol-id (TPIDs Expected to Be Sent or Received) on page 914

tag-protocol-id (TPID to Rewrite) on page 915

targeted-broadcast on page 916

targeted-distribution (Static Interfaces over Aggregated Ethernet) on page 917

tei-option on page 917

terminate (PPPoE Service Name Tables) on page 918

then on page 918

Copyright 2014, Juniper Networks, Inc.

363

Interfaces Fundamentals for Routing Devices

364

threshold on page 919

timeslots on page 920

tm on page 921

tm-polarity on page 921

traceoptions (Individual Interfaces) on page 922

traceoptions (Interface Process) on page 924

traceoptions (LACP) on page 926

traceoptions (PPP Process) on page 928

traceoptions (PPPoE) on page 931

translate-discard-eligible on page 933

translate-fecn-and-becn on page 934

translate-plp-control-word-de on page 934

transmit-bucket on page 935

transmit-clock on page 935

transmit-period on page 936

transmit-weight (ATM2 IQ CoS Forwarding Class) on page 937

transmit-weight (ATM2 IQ Virtual Circuit) on page 938

traps on page 938

trigger on page 939

trigger-link-failure on page 940

trunk-bandwidth on page 940

trunk-id on page 941

ttl on page 941

tunnel on page 942

underlying-interface on page 943

unframed on page 944

unidirectional on page 944

unit (Dynamic Profiles Standard Interface) on page 945

unit on page 948

unnumbered-address (Demux) on page 954

unnumbered-address (Dynamic Profiles) on page 955

unnumbered-address (Ethernet) on page 957

unnumbered-address (PPP) on page 958

up-count on page 959

user-prefix on page 960

username-include on page 961

vbr on page 962

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vc-cos-mode on page 963

vci on page 964

vci-range on page 965

virtual-switch on page 965

vlan-id (Logical Port in Bridge Domain) on page 966

vlan-id (Outer VLAN ID) on page 966

vlan-id (VLAN ID to Be Bound to a Logical Interface) on page 967

vlan-id (VLAN ID to Rewrite) on page 968

vlan-id-list (Ethernet VLAN Circuit) on page 969

vlan-id-list (Interface in Bridge Domain) on page 970

vlan-id-range on page 971

vlan-ranges on page 972

vlan-rewrite on page 973

vlan-rule (100-Gigabit Ethernet Type 4 PIC with CFP) on page 974

vlan-steering (100-Gigabit Ethernet Type 4 PIC with CFP) on page 975

vlan-tagging on page 976

vlan-tags (Dual-Tagged Logical Interface) on page 977

vlan-tags (Stacked VLAN Tags) on page 979

vlan-tags-outer on page 980

vlan-vci-tagging on page 980

vpi (ATM CCC Cell-Relay Promiscuous Mode) on page 981

vpi (Define Virtual Path) on page 982

vpi (Logical Interface and Interworking) on page 983

vtmapping on page 983

warning on page 984

watch-list on page 985

wavelength on page 986

west-interface on page 990

working-circuit on page 991

yellow-differential-delay on page 991

z0-increment on page 992

[edit chassis] Hierarchy Level

chassis {
aggregated-devices {
ethernet {
device-count number;
}
sonet {

Copyright 2014, Juniper Networks, Inc.

365

Interfaces Fundamentals for Routing Devices

device-count number;
}
}
maximum-links {
}
channel-group number {
ethernet {
device-count number;
}
fpc slot-number{
pic pic-number {
adaptive-services{
service-package (layer-2 | layer-3);
}
aggregate-ports;
atm-cell-relay-accumulation;
atm-l2circuit-mode (aal5 | cell | trunk trunk);
ce1 {
e1 link-number {
channel-group group-number;
timeslots time-slot-range;
}
}
channelization;
ct1 {
t1 link-number {
channel-group group-number;
timeslots time-slot-range;
}
}
ct3 {
port port-number {
t1 link-number {
channel-group group-number;
timeslots time-slot-range;
}
}
framing sdh;
}
max-queues-per-interface number;
mlfr-uni-nni-bundles num-intf;
no-concatenate;
shdsl {
pic-mode (1-port-atm | 2-port-atm);
}
vtmapping (klm | itu-t);
}
}
fpc slot-number{
pic pic-number{
account-layer2-overhead
egress-policer-overhead bytes;
ingress-policer-overhead bytes;
mlfr-uni-nni-bundles-inline number;
multi-link-layer-2-inline;
}

366

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

}
}

Related
Documentation

Interfaces Fundamentals for Routing Devices

[edit firewall] Hierarchy Level

The following CoS statements can be configured at the [edit firewall] hierarchy level.
This is not a comprehensive list of statements available at the [edit firewall] hierarchy
level.
[edit firewall]
atm-policer policer-name {
cdvt rate;
logical-interface-policer;
max-burst-size max-burst-size;
peak-rate rate;
policing-action (discard | discard-tag | count);
sustained-rate rate;
}
family family-name {
filter filter-name {
term term-name {
from {
match-conditions;
}
then {
dscp 0;
forwarding-class class-name;
loss-priority (high | low);
three-color-policer {
(single-rate | two-rate) policer-name;
}
}
}
}
simple-filter filter-name {
term term-name {
from {
match-conditions;
}
then {
forwarding-class class-name;
loss-priority (high | low | medium);
}
}
}
}
policer policer-name {
logical-bandwidth-policer;
shared-bandwidth-policer ;
if-exceeding {
bandwidth-limit rate;
bandwidth-percent number;

Copyright 2014, Juniper Networks, Inc.

367

Interfaces Fundamentals for Routing Devices

burst-size-limit bytes;
}
then {
policer-action;
}
}
three-color-policer policer-name {
action {
loss-priority high then discard;
}
logical-interface-policer;
shared-bandwidth-policer ;
single-rate {
(color-aware | color-blind);
committed-information-rate bps;
committed-burst-size bytes;
excess-burst-size bytes;
}
two-rate {
(color-aware | color-blind);
committed-information-rate bps;
committed-burst-size bytes;
peak-information-rate bps;
peak-burst-size bytes;
}
}

[edit interfaces] Hierarchy Level

The statements at the [edit interfaces interface-name unit logical-unit-number] hierarchy
level can also be configured at the [edit logical-systems logical-system-name interfaces
interface-name unit logical-unit-number] hierarchy level.

NOTE: The accounting-profile statement is an exception to this rule. The

accounting-profile statement can be configured at the [edit interfaces
interface-name unit logical-unit-number] hierarchy level, but it cannot be
configured at the [edit logical-systems logical-system-name interfaces
interface-name unit logical-unit-number] hierarchy level.

interfaces {
traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable> ;
flag flag <disable>;
}
interface-name {
accounting-profile name;
aggregated-ether-options {
(flow-control | no-flow-control);
lacp {
(active | passive);
link-protection {

368

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

disable;
(revertive | non-revertive);
periodic interval;
system-priority priority;
}
link-protection;
link-speed speed;
(loopback | no-loopback);
mc-ae{
chassis-id chassis-id;
mc-ae-id mc-ae-id;
mode (active-active | active-standby);
redundancy-group group-id;
status-control (active | standby);
}
minimum-links number;
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
shared-scheduler;
aggregated-sonet-options {
link-speed speed | mixed;
minimum-links number;
}
atm-options {
cell-bundle-size cells;
ilmi;
linear-red-profiles profile-name {
high-plp-max-threshold percent;
low-plp-max-threshold percent;
queue-depth cells high-plp-threshold percent low-plp-threshold percent;
}
mpls {
pop-all-labels {
required-depth number;
}
}
pic-type (atm1 | atm2);
plp-to-clp;
promiscuous-mode {
vpi vpi-identifier;
}
scheduler-maps map-name {
forwarding-class class-name {
epd-threshold cells plp1 cells;
linear-red-profile profile-name;
priority (high | low);
transmit-weight (cells number | percent number);
}
vc-cos-mode (alternate | strict);
}
use-null-cw;
vpi vpi-identifier {
maximum-vcs maximum-vcs;

Copyright 2014, Juniper Networks, Inc.

369

Interfaces Fundamentals for Routing Devices

oam-liveness {
down-count cells;
up-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
}
}
clocking clock-source;
damping {
enable;
half-life seconds;
max-suppress seconds;
reuse number;
suppress number;
}
data-input (system | interface interface-name);
dce;
serial-options {
clock-rate rate;
clocking-mode (dce | internal | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;

370

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
description text;
alias alias-name;
dialer-options {
pool pool-name <priority priority>;
}
disable;
ds0-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
byte-encoding (nx56 | nx64);
fcs (16 | 32);
idle-cycle-flag (flags | ones);
invert-data;
loopback payload;
start-end-flag (filler | shared);
}
e1-options {
bert-error-rate rate;
bert-period seconds;
fcs (16 | 32);
framing (g704 | g704-no-crc4 | unframed);
idle-cycle-flag (flags | ones);
invert-data;
loopback (local | remote);
start-end-flag (filler | shared);
timeslots time-slot-range;
}
e3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
framing feet;
compatibility-mode (digital-link | kentrox | larscom) <subrate value>;
fcs (16 | 32);
framing (g.751 | g.832);
idle-cycle-flag (filler | shared);
invert-data;
loopback (local | remote);
(payload-scrambler | no-payload-scrambler);
start-end-flag (filler | shared);
(unframed | no-unframed);
}
encapsulation type;
es-options {
backup-interface es-fpc/pic/port;
}
fastether-options {
802.3ad aex;
(flow-control | no-flow-control);

Copyright 2014, Juniper Networks, Inc.

371

Interfaces Fundamentals for Routing Devices

ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
flexible-vlan-tagging;
gigether-options {
802.3ad aex;
(asynchronous-notification | no-asynchronous-notification);
(auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online |
local-interface-offline>;
auto-reconnect seconds;
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
no-auto-mdix;
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
ethernet-switch-profile {
(mac-learn-enable | no-mac-learn-enable);
tag-protocol-id [ tpids ];
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;

372

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

burst-size-limit bytes;
}
}
}
}
}
(gratuitous-arp-reply | no-gratuitous-arp-reply);
hold-time up milliseconds down milliseconds;
ima-group-options {
differential-delay number;
frame-length (32 | 64 | 128 | 256);
frame-synchronization {
alpha number;
beta number;
gamma number;
}
minimum-links number;
symmetry (symmetrical-config-and-operation |
symmetrical-config-asymmetrical-operation);
test-procedure {
ima-test-start;
ima-test-stop;
interface name;
pattern number;
period number;
}
transmit-clock (common | independent);
version (1.0 |1.1);
}
ima-link-options group-id group-id;
interface-set interface-set-name {
interface ethernet-interface-name {
(unit unit-number | vlan-tags-outer vlan-tag);
}
interface interface-name {
(unit unit-number);
}
}
isdn-options {
bchannel-allocation (ascending | descending);
calling-number number;
pool pool-name <priority priority>;
spid1 spid-string;
spid2 spid-string;
static-tei-val value;
switch-type (att5e | etsi | ni1 | ntdms100 | ntt);
t310 seconds;
tei-option (first-call | power-up);
}
keepalives <down-count number> <interval seconds> <up-count number>;
link-mode mode;
lmi {
lmi-type (ansi | itu | c-lmi);
n391dte number;
n392dce number;
n392dte number;

Copyright 2014, Juniper Networks, Inc.

373

Interfaces Fundamentals for Routing Devices

n393dce number;
n393dte number;
t391dte seconds;
t392dce seconds;
}
lsq-failure-options {
no-termination-request;
[ trigger-link-failure interface-name ];
}
mac mac-address;
mlfr-uni-nni-bundle-options {
acknowledge-retries number;
acknowledge-timer milliseconds;
action-red-differential-delay (disable-tx | remove-link);
drop-timeout milliseconds;
fragment-threshold bytes;
cisco-interoperability send-lip-remove-link-for-link-reject;
hello-timer milliseconds;
link-layer-overhead percent;
lmi-type (ansi | itu | c-lmi);
minimum-links number;
mrru bytes;
n391 number;
n392 number;
n393 number;
red-differential-delay milliseconds;
t391 seconds;
t392 seconds;
yellow-differential-delay milliseconds;
}
modem-options {
dialin (console | routable);
init-command-string initialization-command-string;
}
mtu bytes;
multi-chassis-protection {
peer a.b.c.d {
interfaceinterface-name;
}
}
multiservice-options {
(core-dump | no-core-dump);
(syslog | no-syslog);
}
native-vlan-id number;
no-gratuitous-arp-request;
no-keepalives;
no-partition {
interface-type type;
}
no-vpivci-swapping;
otn-options {
fec (efec | gfec | none);
(laser-enable | no-laser-enable);
(line-loopback | no-line-loopback);
pass-thru;

374

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

rate (fixed-stuff-bytes | no-fixed-stuff-bytes | pass-thru);

transmit-payload-type number;
trigger (oc-lof | oc-lom | oc-los | oc-wavelength-lock | odu-ais | odu-bbe-th | odu-bdi
| odu-es-th | odu-lck | odu-oci | odu-sd | odu-ses-th | odu-ttim | odu-uas-th |
opu-ptm | otu-ais | otu-bbe-th | otu-bdi | otu-es-th | otu-fec-deg | otu-fec-exe |
otu-iae | otu-sd | otu-ses-th | otu-ttim | otu-uas-th);
tti;
}
optics-options {
wavelength nm;
alarm alarm-name {
(syslog | link-down);
}
warning warning-name {
(syslog | link-down);
}
}
partition partition-number oc-slice oc-slice-range interface-type type;
timeslots time-slot-range;
passive-monitor-mode;
per-unit-scheduler;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
dynamic-profile profile-name;
no-termination-request;
pap {
access-profile name;
local-name name;
local-password password;
compression;
}
}
psn-vcipsn-vci-identifier;
psn-vpipsn-vpi-identifier;
receive-bucket {
overflow (discard | tag);
rate percentage;
threshold bytes;
}
redundancy-options {
priority sp-fpc/pic/port;
secondary sp-fpc/pic/port;
hot-standby;
}
satop-options {
payload-size n;
}

Copyright 2014, Juniper Networks, Inc.

375

Interfaces Fundamentals for Routing Devices

schedulers number;
serial-options {
clock-rate rate;
clocking-mode (dce | internal | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
services-options {
inactivity-timeout seconds;
open-timeout seconds;
session-limit {
maximum number;
rate new-sessions-per-second;
}
syslog {
host hostname {
facility-override facility-name;
log-prefix prefix-number;
services priority-level;
}
}
}
shdsl-options {

376

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

annex (annex-a | annex-b);

line-rate line-rate;
loopback (local | remote);
snr-margin {
current margin;
snext margin;
}
}
sonet-options {
aggregate asx;
aps {
advertise-interval milliseconds;
annex-b;
authentication-key key;
fast-aps-switch;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
preserve-interface;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
bytes {
c2 value;
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
fcs (16 | 32);
loopback (local | remote);
mpls {
pop-all-labels {
required-depth number;
}
}
path-trace trace-string;
(payload-scrambler | no-payload-scrambler);
rfc-2615;
trigger {
defect ignore;
hold-time up milliseconds down milliseconds;
}
vtmapping (itu-t | klm);
(z0-increment | no-z0-increment);
}
speed (10m | 100m | 1g | oc3 | oc12 | oc48);
stacked-vlan-tagging;
switch-options {

Copyright 2014, Juniper Networks, Inc.

377

Interfaces Fundamentals for Routing Devices

switch-port port-number {
(auto-negotiation | no-auto-negotiation);
speed (10m | 100m | 1g);
link-mode (full-duplex | half-duplex);
}
}
t1-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout value;
byte-encoding (nx56 | nx64);
crc-major-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5);
crc-minor-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5 | 5e-6 | 1e-6);
fcs (16 | 32);
framing (esf | sf);
idle-cycle-flag (flags | ones);
invert-data;
line-encoding (ami | b8zs);
loopback (local | payload | remote);
remote-loopback-respond;
start-end-flag (filler | shared);
timeslots time-slot-range;
}
t3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout feet;
(cbit-parity | no-cbit-parity);
compatibility-mode (adtran | digital-link | kentrox | larscom | verilink) <subrate
value>;
fcs (16 | 32);
(feac-loop-respond | no-feac-loop-respond);
idle-cycle-flag value;
(long-buildout | no-long-buildout);
(loop-timing | no-loop-timing);
loopback (local | payload | remote);
(mac | no-mac);
(payload-scrambler | no-payload-scrambler);
start-end-flag (filler | shared);
}
traceoptions {
flag flag <flag-modifier> <disable>;
}
transmit-bucket {
overflow discard;
rate percentage;
threshold bytes;
}
(traps | no-traps);
unidirectional;
vlan-tagging;
vlan-vci-tagging;
unit logical-unit-number {

378

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
accounting-profile name;
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
allow-any-vci;
atm-scheduler-map (map-name | default);
backup-options {
interface interface-name;
}
bandwidth rate;
cell-bundle-size cells;
clear-dont-fragment-bit;
compression {
rtp {
f-max-period number;
maximum-contexts number <force>;
queues [ queue-numbers ];
port {
minimum port-number;
maximum port-number;
}
}
}
compression-device interface-name;
copy-tos-to-outer-ip-header;
demux-destination family;
demux-source family;
demux-options {
underlying-interface interface-name;
}
description text;
alias alias-name;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
callback;
callback-wait-period time;
deactivation-delay seconds;
dial-string [ dial-string-numbers ];
idle-timeout seconds;
incoming-map {
caller (caller-id | accept-all);
initial-route-check seconds;
load-interval seconds;

Copyright 2014, Juniper Networks, Inc.

379

Interfaces Fundamentals for Routing Devices

load-threshold percent;
pool pool-name;
redial-delay time;
watch-list {
[ routes ];
}
}
}
disable;
disable-mlppp-inner-ppp-pfc;
dlci dlci-identifier;
drop-timeout milliseconds;
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
encapsulation type;
epd-threshold cells plp1 cells;
fragment-threshold bytes;
inner-vlan-id-range start start-id end end-id;
input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
link-layer-overhead percent;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;
oam-liveness {
down-count cells;
up-count cells;
}
oam-period (seconds | disable);
output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
passive-monitor-mode;
peer-unit unit-number;

380

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

plp-to-clp;
point-to-point;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
pap;
default-pap-password password;
local-name name;
local-password password;
passive;
}
dynamic-profile profile-name;
lcp-max-conf-req number;
lcp-restart-timer milliseconds;
loopback-clear-timer seconds;
ncp-max-conf-req number;
ncp-restart-timer milliseconds;
}
pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
short-sequence;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
vci-range start start-vci end end-vci;

Copyright 2014, Juniper Networks, Inc.

381

Interfaces Fundamentals for Routing Devices

vpi vpi-identifier;
vlan-id number;
vlan-id-list [vlan-id vlan-idvlan-id];
vlan-id-range number-number;
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
vlan-tags-outer tpid.vlan-id inner-list [vlan-id vlan-idvlan-id];
family family {
accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
access-concentrator name;
address address {
destination address;
}
bundle ml-fpc/pic/port | ls-fpc/pic/port);
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
group filter-group-number;
input filter-name;
input-list {
[ filter-names ];
output filter-name;
}
output-list {
[ filter-names ];
}
}
ipsec-sa sa-name;
keep-address-and-control;
max-sessions number;
max-sessions-vsa-ignore;
mtu bytes;
multicast-only;
negotiate-address;
no-redirects;
policer {
arp policer-template-name;
disable-arp-policer
input policer-template-name;
output policer-template-name;
}
primary;
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 {

382

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

direction;
}
service {
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-names <service-filter filter-name>;
}
}
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds lockout-time-max
maximum-seconds>;
targeted-broadcast {
forward-and-send-to-re;
forward-only;
}
(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 | preferred-source-address address>;
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
multipoint-destination address (dlci dlci-identifier | vci vci-identifier);
multipoint-destination address {
epd-threshold cells plp1 cells;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained
rate burst length);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
preferred;
primary;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}

Copyright 2014, Juniper Networks, Inc.

383

Interfaces Fundamentals for Routing Devices

priority-number number;
track {
priority-cost seconds;
priority-hold-time interface-name {
bandwidth-threshold bits-per-second {
priority;
}
interface priority;
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
virtual-address [ addresses ];
}
}
}
}
}
}

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

[edit logical-systems] Hierarchy Level

The following lists the statements that can be configured at the [edit logical-systems]
hierarchy level that are also documented in this manual. For more information about
logical systems, see the Logical Systems Feature Guide for Routing Devices.
logical-systems logical-system-name {
interfaces interface-name {
unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
allow-any-vci;
atm-scheduler-map (map-name | default);
bandwidth rate;
backup-options {
interface interface-name;
}
cell-bundle-size cells;
clear-dont-fragment-bit;
compression {
rtp {
f-max-period number;
port {
minimum port-number;

384

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

maximum port-number;
}
queues [ queue-numbers ];
}
}
compression-device interface-name;
description text;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
deactivation-delay seconds;
dial-string [ dial-string-numbers ];
idle-timeout seconds;
initial-route-check seconds;
load-threshold number;
pool pool;
remote-name remote-callers;
watch-list {
[ routes ];
}
}
disable;
dlci dlci-identifier;
drop-timeout milliseconds;
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
encapsulation type;
epd-threshold cells plp1 cells;
fragment-threshold bytes;
input-vlan-map {
inner-tag-protocol-id;
inner-vlan-id;
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
link-layer-overhead percent;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;

Copyright 2014, Juniper Networks, Inc.

385

Interfaces Fundamentals for Routing Devices

oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
output-vlan-map {
inner-tag-protocol-id;
inner-vlan-id;
(pop | pop-pop | pop-swap | push | push-push | swap | swap-swap);
tag-protocol-id tpid;
vlan-id number;
}
passive-monitor-mode;
peer-unit unit-number;
plp-to-clp;
point-to-point;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
}
dynamic-profile profile-name;
pap {
default-pap-password password;
local-name name;
local-password password;
passive;
}
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
short-sequence;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;

386

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

ttl number;
}
vci vpi-identifier.vci-identifier;
vlan-id number;
vlan-id-list [vlan-id vlan-idvlan-id]
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
vlan-tags outer tpid.vlan-id inner-list [vlan-id vlan-idvlan-id]
vpi vpi-identifier;
family family {
accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
bundle interface-name;
filter {
group filter-group-number;
input filter-name;
input-list {
[ filter-names ];
}
output filter-name;
output-list {
[ filter-names ];
}
}
ipsec-sa sa-name;
keep-address-and-control;
mtu bytes;
multicast-only;
no-redirects;
policer {
arp policer-template-name;
input policer-template-name;
output policer-template-name;
}
primary;
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 {
direction;
}
service {
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-name <service-filter filter-name>;
}

Copyright 2014, Juniper Networks, Inc.

387

Interfaces Fundamentals for Routing Devices

}
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
unnumbered-address interface-name destination address destination-profile
profile-name;
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
multipoint-destination address (dlci dlci-identifier | vci vci-identifier);
multipoint-destination address {
epd-threshold cells plp1 cells;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained
rate burst length);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
preferred;
primary;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority-number number;
track {
priority-cost seconds;
priority-hold-time interface-name {
interface priority;
bandwidth-threshold bits-per-second {
priority;
}
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
}
virtual-address [ addresses ];
}
}
}
}
}

388

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

[edit protocols connections] Hierarchy Level

The following statements can also be configured at the [edit logical-systems
logical-system-name protocols connections] hierarchy level.
interface-switch connection-name {
interface interface-name.unit-number;
interface interface-name.unit-number;
}

Copyright 2014, Juniper Networks, Inc.

389

Interfaces Fundamentals for Routing Devices

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

[edit protocols dot1x] Hierarchy Level

dot1x {
authenticator
authentication-profile-name access-profile-name;
interface interface-ids {
maximum-requests integer;
retries integer;
quiet-period seconds;
transmit-period seconds;
reauthentication (disable | interval seconds);
server-timeout seconds;
supplicant (single);
supplicant-timeout seconds;
}
}
}

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

[edit protocols iccp] Hierarchy Level

The following statement hierarchy can also be included at the [edit logical-systems
logical-system-name] hierarchy level.
iccp {
traceoptions;
local-ip-address ip address;
session-establishment-hold-time value;
authentication-key string;
peer ip-address {
local-ip-address ip address;
session-establishment-hold-time value;
authentication-key string;
redundancy-group-id-list redundancy-group-id-list;
liveness-detection;
}
}

Related
Documentation

390

iccp on page 603

Configuring ICCP for MC-LAG on page 199

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

[edit protocols lacp] Hierarchy Level

ppm (Ethernet Switching)
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <disable>);
}
fast-hello-issu

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Configuring Distributed Periodic Packet Management

Junos OS Network Interfaces Library for Routing Devices

[edit protocols oam] Hierarchy Level

ethernet {
connectivity-fault-management {
action-profile profile-name {
default-actions {
interface-down;
}
event {
adjacency-loss;
interface-status-tlv (down | lower-layer-down);
port-status-tlv blocked;
rdi;
}
}
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
maintenance-domain domain-name {
bridge-domain name;
routing-instance r1 {
bridge-domain name;
instance vpls-instance;
interface (ge | xe) fpc/pic/port.domain;
level number;
maintenance-association name{
mep identifier {
direction (up | down)
interface (ge | xe) fpc/pic/port.domain (working | protect );
auto-discovery;
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon);
priority number;
}
}
mip-half-function (none | default | explicit);

Copyright 2014, Juniper Networks, Inc.

391

Interfaces Fundamentals for Routing Devices

name-format (character-string | none | dns | mac+2oct);

short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
continuity-check {
hold-interval minutes;
interval (10m | 10s | 1m | 1s | 100ms);
loss-threshold number;
}
maintenance-association ma-name {
mip-half-function (none | default | explicit);
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (working |protect);
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size bytes;
iteration-count frames;
priority priority-value;
}
}
}
}
}
performance-monitoring {
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
no-aggregate-delegate-processing;
}
link-fault-management {
action-profile profile-name {
action {
syslog;
link-down;
send-critical-event;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;

392

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
interface interface-name {
apply-action-profile profile-name;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
link-discovery (active | passive);
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
}
}
fnp {
interval <100ms | 1s | 10s | 1m | 10m>;
loss-threshold number
interface interface name {
domain-id domain-id
}
}
}

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

[edit protocols ppp] Hierarchy Level

monitor-session (interface-name | all);
traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable> ;
flag flag <disable>;
}

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

393

Interfaces Fundamentals for Routing Devices

[edit protocols pppoe] Hierarchy Level

pppoe {
no-send-pads-error;
no-send-pads-ac-info
pado-advertise;
service-name-tables table-name {
service service-name {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
max-sessions number;
agent-specifier {
aci circuit-id-string ari remote-id-string {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
static-interface interface-name;
}
}
}
}
traceoptions {
file <filename> <files number> <match regular-expression > <size maximum-file-size>
<world-readable | no-world-readable>;
filter {
aci regular-expression;
ari regular-expresion;
service-name regular-expresion;
underlying-interface interface-name;
}
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
}
}

[edit protocols protection-group] Hierarchy Level

ethernet-ringring-name {
east-interface {
control-channel channel-name {
vlan number;
}
}
guard-interval number;
node-id mac-address;
restore-interval number;
ring-protection-link-owner;
west-interface {

394

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

control-channel channel-name {
vlan number;
}
}
}

Related
Documentation

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

[edit protocols vrrp] Hierarchy Level

The following statement hierarchy can also be included at the [edit logical-systems
logical-system-name] hierarchy level.
protocols {
vrrp {
asymmetric-hold-time;
delegate-processing;
failover-delay milliseconds;
global-advertisements-threshold advertisement-value;
skew-timer-disable;
startup-silent-period seconds;
traceoptions {
file <filename> <files number> <match regular-expression> <microsecond-stamp>
<size maximum-file-size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
version-3;
}
}

Related
Documentation

Notational Conventions Used in Junos OS Configuration Hierarchies

[edit protocols] Hierarchy Level

Junos OS Hierarchy and RFC Reference

Ethernet Interfaces Feature Guide for Routing Devices

Junos OS Network Interfaces Library for Routing Devices

[edit system processes] Hierarchy Level

dialer-services {
disable;
}
isdn-signaling {
disable;
reject-incoming;
}

Copyright 2014, Juniper Networks, Inc.

395

Interfaces Fundamentals for Routing Devices

Related
Documentation

ISDN Configuration Overview

Disabling ISDN Processes

802.3ad
Syntax

Hierarchy Level

Release Information

Description
Options

802.3ad {
ae interface-number (primary | backup);
lacp {
port-priority;
}
}
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]

Statement introduced before Junos OS Release 7.4.

primary and backup options added in Junos OS Release 8.3.
Specify aggregated Ethernet logical interface number.
ae interface-numberAggregated Ethernet logical interface number.

Range: 0 through 15
primaryFor link protection configurations, specify the primary link for egress traffic.
backupFor link protection configurations, specify the backup link for egress traffic.

Required Privilege
Level
Related
Documentation

396

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an Aggregated Ethernet Interface

Configuring Aggregated Ethernet Link Protection

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

accept
Syntax
Hierarchy Level

Release Information

Description

Options

accept (any | dhcp-v4 | dhcp-v6 | inet | inet6 | pppoe);

[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]

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.
Specify the type of VLAN Ethernet packet accepted by an interface that is associated
with a VLAN dynamic profile or stacked VLAN dynamic profile.
anyAny 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-v4IPv4 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-v6IPv6 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.
inetIPv4 Ethernet and ARP packet type.
inet6IPv6 Ethernet packet type.
pppoePoint-to-Point Protocol over Ethernet packet type.

NOTE: The pppoe VLAN Ethernet packet type option is supported only for
Trio MPC/MIC interfaces on MX Series routers.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

397

Interfaces Fundamentals for Routing Devices

Related
Documentation

398

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

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

accept-source-mac
Syntax

Hierarchy Level

accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Packet Transport Routers.
Statement introduced in Junos OS Release 13.2 for the QFX Series.

Description

For Gigabit Ethernet intelligent queuing (IQ) interfaces only, accept traffic from and to
the specified remote media access control (MAC) address.
The accept-source-mac statement is equivalent to the source-address-filter statement,
which is valid for aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces
only. To allow the interface to receive packets from specific MAC addresses, include the
accept-source-mac statement.
On untagged Gigabit Ethernet interfaces, you should not configure the source-address-filter
statement and the accept-source-mac statement simultaneously. On tagged Gigabit
Ethernet interfaces, you should not configure the source-address-filter statement and
the accept-source-mac statement with an identical MAC address specified in both filters.
The statements are explained separately.

NOTE: The policer statement is not supported on PTX Series Packet Transport
Routers.

NOTE: On QFX platforms, if you configure source MAC addresses for an

interface using the static-mac or persistent-learning statements and later
configure a different MAC address for the same interface using the
accept-source-mac statement, the MAC addresses that you previously
configured for the interface remain in the ethernet-switching table and can
still be used to send packets to the interface.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

399

Interfaces Fundamentals for Routing Devices

Related
Documentation

400

Configuring MAC Address Filtering

Configuring MAC Address Filtering on PTX Series Packet Transport Routers

source-filtering on page 753

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

access-concentrator
Syntax
Hierarchy Level

Release Information

Description

access-concentrator name;
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family
pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit interfaces interface-name unit logical-unit-number family pppoe],
[edit interfaces interface-name unit logical-unit-number pppoe-options],
[edit interfaces interface-name unit logical-unit-number pppoe-underlying-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family pppoe],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
pppoe-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
pppoe-underlying-options]

Statement introduced before Junos OS Release 7.4.

Support at the [edit interfaces interface-name unit logical-unit-number
pppoe-underlying-options] and [edit logical-systems logical-system-name interfaces
interface-name unit logical-unit-number pppoe-underlying-options] hierarchy levels
introduced in Junos OS Release 10.1.
Support at the [edit ... family pppoe] hierarchies introduced in Junos OS Release 11.2.
(Intelligent Queuing 2 (IQ2) PICs on M120 and M320 routers; MPCs on MX Series routers)
Configure an alternative access concentrator name in the AC-NAME tag in a PPPoE
control packet for use with a dynamic PPPoE subscriber interface. If you do not configure
the access concentrator name, the AC-NAME tag contains the system name.

NOTE: The [edit ... family pppoe] hierarchies are supported only on MX Series
routers with MPCs.

Options
Required Privilege
Level
Related
Documentation

nameName of the access concentrator.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Identifying the Access Concentrator

Configuring the PPPoE Family for an Underlying Interface

Configuring Dynamic PPPoE Subscriber Interfaces Using Dynamic Profiles

PPPoE Overview

Copyright 2014, Juniper Networks, Inc.

401

Interfaces Fundamentals for Routing Devices

access-profile
Syntax
Hierarchy Level

Release Information

Description

access-profile name;
[edit interfaces interface-name ppp-options chap],
[edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options chap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options pap]

Statement introduced before Junos OS Release 7.4.

Support for PAP added in Junos OS Release 8.3.
Support for VLAN and stacked VLAN ranges added in Junos OS Release 10.0.
For CHAP authentication, the mapping between peer names (or clients ) and the secrets
associated with their respective links. For PAP authentication, the peer's username and
password.
For Asynchronous Transfer Mode 2 (ATM2) IQ interfaces only, you can configure a
Challenge Handshake Authentication Protocol (CHAP) access profile on the logical
interface unit if the logical interface is configured with one of the following PPP over ATM
encapsulation types:

Options
Required Privilege
Level
Related
Documentation

402

atm-ppp-llcPPP over AAL5 logical link control (LLC) encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

nameName of the access profile.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Challenge Handshake Authentication Protocol on page 126

Configuring the PPP Password Authentication Protocol on page 129

default-chap-secret on page 498

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

accounting
Syntax

Hierarchy Level

Release Information
Description

accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
[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]

Statement introduced before Junos OS Release 7.4.

Enable IP packet counters on an interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Enabling Source Class and Destination Class Usage on page 242

accounting-profile
Syntax
Hierarchy Level

Release Information

Description

Options
Required Privilege
Level
Related
Documentation

accounting-profile name;
[edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-range name]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Enable collection of accounting data for the specified physical or logical interface or
interface range.
nameName of the accounting profile.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying an Accounting Profile to the Physical Interface on page 155

Applying an Accounting Profile to the Logical Interface on page 182

Copyright 2014, Juniper Networks, Inc.

403

Interfaces Fundamentals for Routing Devices

acfc
Syntax
Hierarchy Level

Release Information
Description

acfc;
[edit interfaces interface-name ppp-options compression],
[edit interfaces interface-name unit logical-unit-number ppp-options compression],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options compression]

Statement introduced before Junos OS Release 7.4.

For interfaces with PPP encapsulation, configure compression of the Data Link Layer
address and control fields. The acfc option is not supported with frame-relay-ppp
encapsulation.
On M320, M120, and T Series routers, address and control field compression (ACFC) is
not supported for any ISO family protocols. Do not include the acfc statement at the
[edit interfaces interface-name ppp-options compression] hierarchy level when you include
the family iso statement at the [edit interfaces interface-name unit logical-unit-number]
hierarchy level.

Required Privilege
Level
Related
Documentation

404

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPP Address and Control Field Compression on page 133

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

acknowledge-retries
Syntax
Hierarchy Level
Release Information

acknowledge-retries number;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

Description

For link services and voice services interfaces only, configure the number of retransmission
attempts to be made for consecutive hello or remove link messages following the
expiration of the acknowledgment timer.

Options

numberNumber of retransmission attempts to be made following the expiration of the

acknowledgment timer.
Range: 1 through 5
Default: 2
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

action-red-differential-delay on page 410

hello-timer on page 593

Copyright 2014, Juniper Networks, Inc.

405

Interfaces Fundamentals for Routing Devices

acknowledge-timer
Syntax
Hierarchy Level
Release Information
Description

Options

acknowledge-timer milliseconds;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voice services interfaces only, configure the maximum time, in
milliseconds, to wait for an add link acknowledgment, hello acknowledgment, or remove
link acknowledgment message.
millisecondsTime, in milliseconds, to wait for an add link acknowledgment, hello
acknowledgment, or remove link acknowledgment message.
Range: 1 through 10 milliseconds
Default: 4 milliseconds

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

address on page 412, hello-timer on page 593

hello-timer on page 593

action (OAM)
Syntax

Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

406

action {
link-down;
send-critical-event;
syslog;
}
[edit protocols oam ethernet link-fault-management action-profile]

Statement introduced in Junos OS Release 8.5.

Define the action or actions to be taken when the OAM fault event occurs.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Specifying the Actions to Be Taken for Link-Fault Management Events

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

action (Policer)
Syntax

Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

action {
loss-priority high then discard;
}
[edit firewall three-color-policer policer-name]

Statement introduced in Junos OS Release 8.2.

This statement discards high loss priority traffic as part of a configuration using tricolor
marking on a logical interface.
firewallTo view this statement in the configuration.
firewall-controlTo add this statement to the configuration.

Class of Service Feature Guide for Routing Devices

logical-interface-policer on page 683

action-profile (Applying to CFM)

Syntax
Hierarchy Level

Release Information
Description
Options
Required Privilege
Level
Related
Documentation

action-profile profile-name;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id remote-mep mep-id]

Statement introduced in Junos OS Release 8.4.

Identify the action profile to use.
profile-nameName of the action profile to use.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Maintenance Endpoint

Copyright 2014, Juniper Networks, Inc.

407

Interfaces Fundamentals for Routing Devices

action-profile (Defining for CFM)

Syntax

Hierarchy Level
Release Information
Description
Options

action-profile profile-name {
event {
ais-trigger-condition {
adjacency-loss;
all-defects;
cross-connect-ccm;
erroneous-ccm;
receive-ais;
}
interface-status-tlv (down | lower-layer-down);
port-status-tlv blocked;
rdi;
}
action {
interface-down;
log-and-generate-ais {
interval(1m | 1s);
levelvalue;
priority value;
}
}
default-actions {
interface-down;
}
}
[edit protocols oam ethernet connectivity-fault-management]

Statement introduced in Junos OS Release 8.4.

Configure a name and default action for an action profile.
profile-nameName of the action profile.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

408

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Connectivity Fault Management Action Profile

default-actions on page 497

event (CFM)

interface-down on page 632

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

action-profile (Defining for LFM)

Syntax

Hierarchy Level
Release Information
Description

Options

action-profile profile-name {
action {
link-down;
send-critical-event;
syslog;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
[edit protocols oam ethernet link-fault-management]

Statement introduced in Junos OS Release 8.5.

Configure a name, one or more actions, and the events that trigger the action for an action
profile.
profile-nameName of the action profile.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an OAM Action Profile

Copyright 2014, Juniper Networks, Inc.

409

Interfaces Fundamentals for Routing Devices

action-red-differential-delay
Syntax
Hierarchy Level
Release Information
Description

Options

action-red-differential-delay (disable-tx | remove-link);

[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voice services interfaces only, configure the action to be taken when
the differential delay exceeds the red limit.
disable-txDisable transmission on the bundle link.
remove-linkRemove bundle link from service.

Default: disable-tx
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

remote on page 842

yellow-differential-delay on page 991

activation-delay
Syntax
Hierarchy Level
Release Information

activation-delay seconds;
[edit interfaces dln unit logical-unit-number dialer-options]

Statement introduced before Junos OS Release 7.4.

Description

(J Series Services Routers) For ISDN interfaces, configure the ISDN dialer activation delay.
Used only for dialer backup and dialer watch cases.

Options

secondsInterval before the backup interface is activated after the primary interface has

gone down.
Range: 1 through 4,294,967,295 seconds
Required Privilege
Level
Related
Documentation

410

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Dialer Interface

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

activation-priority
Syntax
Hierarchy Level

Release Information

activation-priority priority;
[edit interfaces interface-name unit logical-unit-number dynamic-call-admission-control],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
dynamic-call-admission-control]

Statement introduced in Junos OS Release 8.2.

Description

(J4350 and J6350 Services Routers supporting voice over IP with the TGM550 media
gateway module) For Fast Ethernet and Gigabit Ethernet interfaces, ISDN BRI interfaces,
and serial interfaces with PPP or Frame Relay encapsulation, configure the dynamic call
admission control (dynamic CAC) activation priority value.

Options

priorityThe activation priority in which the interface is used for providing call bandwidth.

The interface with the highest activation priority value is used as the primary link for
providing call bandwidth. If the primary link becomes unavailable, the TGM550
switches over to the next active interface with the highest activation priority value,
and so on.
Range: 0 through 255
Default: 50
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dynamic Call Admission Control on page 181

Junos OS Services Interfaces Library for Routing Devices

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

411

Interfaces Fundamentals for Routing Devices

address

412

Syntax

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 peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
primary;
preferred;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority-number number;
track {
priority-cost seconds;
priority-hold-time interface-name {
interface priority;
bandwidth-threshold bits-per-second {
priority;
}
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
virtual-address [ addresses ];
}
}

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]

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Release Information

Description
Options

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
Configure the interface address.
addressAddress of the interface.

In Junos OS Release 13.3 and later, when you configure an IPv6 host address and an
IPv6 subnet address on an interface, the commit operation fails.

In releases earlier than Junos OS Release 13.3, when you use the same configuration
on an interface, the commit operation succeeds, but only one of the IPv6 addresses
that was entered is assigned to the interface. The other address is not applied.

The remaining statements are explained separately.

NOTE: The edit logical-systems hierarchy is not available on QFabric systems.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Protocol Family on page 190

Junos OS Administration Library for Routing Devices

family

negotiate-address on page 734

unnumbered-address (Ethernet) on page 957

Copyright 2014, Juniper Networks, Inc.

413

Interfaces Fundamentals for Routing Devices

advertise-interval
Syntax
Hierarchy Level
Release Information
Description

Options

advertise-interval milliseconds;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Modify the Automatic Protection Switching (APS) interval at which the protect and
working routers send packets to their neighbors to advertise that they are operational. A
router considers its neighbor to be operational for a period, called the hold time, that is,
by default, three times the advertisement interval.
millisecondsInterval between advertisement packets.

Range: 1 through 65,534 milliseconds

Default: 1000 milliseconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring APS Timers

age
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

414

age (30m | 10m | 1m | 30s | 10s);

[edit protocols oam ethernet connectivity-fault-management linktrace]

Statement introduced in Junos OS Release 8.5.

Time to wait (in minutes or seconds) for a response. If no response is received, the request
and response entry is deleted from the linktrace database.
10 minutes
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Linktrace Protocol in CFM

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

agent-specifier
Syntax

Hierarchy Level
Release Information

Description

agent-specifier {
aci circuit-id-string ari remote-id-string {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
static-interface interface-name;
}
}
[edit protocols pppoe service-name-tables table-name service service-name]

Statement introduced in Junos OS Release 10.0.

drop, delay, terminate, dynamic-profile, routing-instance, and static-interface options
introduced in Junos OS Release 10.2.
Specify the action taken by the interface for the specified agent circuit identifier/agent
remote identifier (ACI/ARI) pair when the interface receives a PPPoE Active Discovery
Initiation (PADI) control packet that includes the vendor-specific tag with ACI/ARI pair
information. You can configure an ACI/ARI pair for a named service, empty service, or any
service in a PPPoE service name table. A maximum of 8000 ACI/ARI pairs are supported
per PPPoE service name table. You can distribute the ACI/ARI pairs in any combination
among the named, empty, and any service entries in the service name table.
You can use an asterisk (*) as a wildcard character to match ACI/ARI pairs, the ACI alone,
or the ARI alone. The asterisk can be placed only at the beginning, the end, or both the
beginning and end of the identifier string. You can also specify an asterisk alone for either
the ACI or the ARI. You cannot specify only an asterisk for both the ACI and the ARI. When
you specify a single asterisk as the identifier, that identifier is ignored in the PADI packet.
For example, suppose you care about matching only the ACI and do not care what value
the ARI has in the PADI packet, or even whether the packet contains an ARI value. In this
case you can set the remote-id-string to a single asterisk. Then the interface ignores the
ARI received in the packet and the interface takes action based only on matching the
specified ACI.

Default
Options

The default action is terminate.

aci circuit-id-stringIdentifier for the agent circuit ID that corresponds to the DSLAM

interface that initiated the service request. This is a string of up to 63 characters.

ari remote-id-stringIdentifier for the subscriber associated with the DSLAM interface

that initiated the service request. This is a string of up to 63 characters.

The remaining statements are explained separately.

Copyright 2014, Juniper Networks, Inc.

415

Interfaces Fundamentals for Routing Devices

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the
Client Request Includes ACI/ARI Information

aggregate (Gigabit Ethernet CoS Policer)

Syntax

Hierarchy Level

Release Information
Description

aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name]

Statement introduced before Junos OS Release 7.4.

Define a policer to apply to nonpremium traffic.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

416

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Policers

premium (Hierarchical Policer) on page 817

ieee802.1p on page 605

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

aggregate (Hierarchical Policer)

Syntax

Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

aggregate {
if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
then {
discard;
}
}
[edit firewall hierarchical-policer]

Statement introduced in Junos OS Release 9.5.

On M40e, M120, and M320 (with FFPC and SFPC) edge routers and T320, T640, and
T1600 core routers with Enhanced Intelligent Queuing (IQE) PICs, T4000 routers with
Type 5 FPC and Enhanced Scaling Type 4 FPC, configure an aggregate hierarchical policer.
Options are described separately.
firewallTo view this statement in the configuration.
firewall-controlTo add this statement to the configuration.

Applying Policers on page 210

Class of Service Feature Guide for Routing Devices

aggregate (SONET/SDH)
Syntax
Hierarchy Level
Release Information
Description
Options

aggregate asx;
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

Specify aggregated SONET/SDH logical interface number.
asxAggregated SONET/SDH logical interface number.

Range: 0 through 15
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Aggregated SONET/SDH Interfaces

Copyright 2014, Juniper Networks, Inc.

417

Interfaces Fundamentals for Routing Devices

aggregate-ports
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

418

aggregate-ports;
[edit chassis fpc slot-number pic pic-number]

Statement introduced in Junos OS Release 8.1.

For T Series routers only, specify OC768-over-OC192 mode on the 4-port OC192C PIC.
Four OC192 links are aggregated into one OC768 link with one logical interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring 4-Port OC192 PIC to Operate in OC768-over-OC192 Mode

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

aggregated-ether-options
Syntax

aggregated-ether-options {
ethernet-switch-profile {
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
}
(mac-learn-enable | no-mac-learn-enable);
}
(flow-control | no-flow-control);
lacp {
(active | passive);
link-protection {
disable;
(revertive | non-revertive);
periodic interval;
system-priority priority;
system-id system-id;
}
link-protection;
load-balance;
link-speed speed;
logical-interface-chassis-redundancy;
logical-interface-fpc-redundancy;
(loopback | no-loopback);
minimum-links number;
rebalance-periodic time hour:minute <interval hours>;
source-address-filter {
mac-address;
(source-filtering | no-source-filtering);
}
}

Copyright 2014, Juniper Networks, Inc.

419

Interfaces Fundamentals for Routing Devices

Hierarchy Level
Release Information
Description

[edit interfaces aex]

Statement introduced before Junos OS Release 7.4.

Configure aggregated Ethernet-specific interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Interfaces Overview

aggregated-sonet-options
Syntax

Hierarchy Level
Release Information
Description

aggregated-sonet-options {
link-speed speed;
minimum-links number;
}
[edit interfaces asx]

Statement introduced before Junos OS Release 7.4.

Configure aggregated SONET/SDH-specific interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

420

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Aggregated SONET/SDH Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

alarm (optics-options)
Syntax

Hierarchy Level
Release Information

Description

Options

alarm low-lightalarm {
(link-down | syslog);
}
[edit interfaces interface-name optics-options]

Statement introduced in Junos OS Release 10.0.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Specify the action to take if the receiving optics signal is below the optics low-light alarm
threshold.
link-downDrop the 10-Gigabit Ethernet link and marks link as down.
syslogWrite the optics information to the system log.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or
Warning

100-Gigabit Ethernet OTN Options Configuration Overview

Copyright 2014, Juniper Networks, Inc.

421

Interfaces Fundamentals for Routing Devices

alias (Interfaces)
Syntax
Hierarchy Level

Release Information

alias alias-name;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 13.3.

Description

Configure a textual description of a physical interface or the logical unit of an interface

to be the alias of an interface name. The alias name can be a single line of text. If the text
contains spaces, enclose it in quotation marks. If you configure an alias name, the alias
name is displayed instead of the interface name in the output of all show, show interfaces,
and other operational mode commands. In Junos OS Release 13.3R3 and later, display
of the alias can be suppressed in favor of the actual interface name by using the display
no-interface-alias parameter along with the show command.

Options

alias-nameText to denote an easily identifiable, meaningful alias name for the interface.

If the text includes spaces, enclose the entire text in quotation marks.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Example: Adding an Interface Alias Name on page 111

Junos OS Network Interfaces Library for Routing Devices

allow-any-vci
Syntax
Hierarchy Level

Release Information

Description
Required Privilege
Level
Related
Documentation

422

allow-any-vci;
[edit interfaces interface-name unit 0],
[edit logical-systems logical-system-name interfaces interface-name unit 0]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
routers.
Dedicate entire ATM device to ATM cell relay circuit.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring an ATM1 Cell-Relay Circuit

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

allow-fragmentation
Syntax
Hierarchy Level

Release Information

allow-fragmentation;
[edit interfaces gr-fpc/pic/port unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number
tunnel]

Statement introduced in Junos OS Release 9.2.

Description

Enable fragmentation of generic routing encapsulation (GRE) encapsulated packets

regardless of maximum transmission unit (MTU) value.

Default

By default, the GRE encapsulated packets are dropped if the packet size exceeds the
MTU setting of the egress interface.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

reassemble-packets on page 836

allow-remote-loopback
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

allow-remote-loopback;
[edit protocols oam link-fault-management interface interface-name negotiation-options]

Statement introduced in Junos OS Release 8.4.

Enable the remote loopback on IQ2 and IQ2-E Gigabit Ethernet interfaces, and Ethernet
interfaces on the MX Series routers and EX Series switches.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling Remote Loopback Support on the Local Interface

Copyright 2014, Juniper Networks, Inc.

423

Interfaces Fundamentals for Routing Devices

annex
Syntax
Hierarchy Level

Release Information
Description

annex (annex-a | annex-b);

[edit interfaces interface-name shdsl-options],
[edit interfaces interface-name sonet-options aps],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options]

Statement introduced in Junos OS Release 7.4.

For J Series Services Routers only, configure the type of SHDSL annex.
For M320 and M120 routers only, for Multiplex Section Protection (MSP) switching on
SDH interfaces, set annex-b. You must also configure the working protection circuit under
the [edit interfaces so-fpc/pic/port sonet-options aps] hierarchy level.

Default
Options

annex-b
annex-aUse for North American SHDSL network implementations.
annex-bUse for European SHDSL network implementations.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-SHDSL Overview

apply-action-profile
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

424

apply-action-profile profile-name;
[edit protocols oam ethernet link-fault-management interface]

Statement introduced in Junos OS Release 8.5.

Apply the specified action profile to the interface for link-fault management.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Applying an Action Profile

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

aps
Syntax

Hierarchy Level
Release Information
Description

aps {
advertise-interval milliseconds;
annex-b
authentication-key key;
(break-before-make | no-break-before-make);
fast-aps-switch;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
preserve-interface;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

Configure Automatic Protection Switching (APS) on the router.
For DS3 channels on a channelized OC12 interface, configure APS on channel 0 only. If
you configure APS on channels 1 through 11, it is ignored.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Automatic Protection Switching and Multiplex Section Protection Overview

Copyright 2014, Juniper Networks, Inc.

425

Interfaces Fundamentals for Routing Devices

arp (Interfaces)
Syntax
Hierarchy Level

Release Information

Description

Options

arp ip-address (mac | multicast-mac) mac-address publish;

[edit interfaces interface-name unit logical-unit-number family inet address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
For Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces only, configure Address
Resolution Protocol (ARP) table entries, mapping IP addresses to MAC addresses.
ip-addressIP address to map to the MAC address. The IP address specified must be

part of the subnet defined in the enclosing address statement.

mac mac-addressMAC address to map to the IP address. Specify the MAC address as

six hexadecimal bytes in one of the following formats: nnnn.nnnn.nnnn or

nn:nn:nn:nn:nn:nn. For example, 0011.2233.4455 or 00:11:22:33:44:55.
multicast-mac mac-addressMulticast MAC address to map to the IP address. Specify

the multicast MAC address as six hexadecimal bytes in one of the following formats:
nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn. For example, 0011.2233.4455 or 00:11:22:33:44:55.
publish(Optional) Have the router or switch reply to ARP requests for the specified IP

address. If you omit this option, the router or switch uses the entry to reach the
destination but does not reply to ARP requests.

NOTE: The edit logical-systems hierarchy is not available on QFabric systems.

Required Privilege
Level
Related
Documentation

426

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Static ARP Table Entries

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

asynchronous-notification
Syntax
Hierarchy Level

(asynchronous-notification | no-asynchronous-notification);
[edit interfaces ge-fpc/pic/port gigether-options ]

Release Information

Statement introduced in Junos OS Release 8.3.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For all 10-Gigabit Ethernet interfaces, M120, M320, and T Series routers, configure support
for notification of link down alarm generation and transfer.

asynchronous-notificationSupport notification of link down alarm generation and

transfer.

no-asynchronous-notificationProhibit notification of link down alarm generation and

transfer.
Default
Required Privilege
Level
Related
Documentation

Support for notification of link down alarm generation and transfer is not enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

10-Gigabit Ethernet Notification of Link Down Alarm Overview

atm-encapsulation
Syntax
Hierarchy Level

Release Information
Description
Default

Options

atm-encapsulation (direct | plcp);

[edit interfaces at-fpc/pic/port e3-options],
[edit interfaces at-fpc/pic/port t3-options]

Statement introduced before Junos OS Release 7.4.

Configure encapsulation for E3 and T3 traffic over ATM interfaces.
Physical Layer Convergence Protocol (PLCP) encapsulation is the default for T3 traffic
and for E3 traffic using G.751 framing.
directUse direct encapsulation. G.832 framing on E3 interfaces requires direct

encapsulation.
plcpUse PLCP encapsulation.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring E3 and T3 Parameters on ATM Interfaces

encapsulation (Physical Interface) on page 547

Copyright 2014, Juniper Networks, Inc.

427

Interfaces Fundamentals for Routing Devices

atm-options
Syntax

Hierarchy Level
Release Information

Description

atm-options {
cell-bundle-size cells;
ilmi;
linear-red-profiles profile-name {
high-plp-max-threshold percent;
low-plp-max-threshold percent;
queue-depth cells high-plp-threshold percent low-plp-threshold percent;
}
mpls {
pop-all-labels {
required-depth number;
}
}
pic-type (atm1 | atm2);
plp-to-clp;
promiscuous-mode {
vpi vpi-identifier;
}
scheduler-maps map-name {
forwarding-class class-name {
epd-threshold cells plp1 cells;
linear-red-profile profile-name;
priority (high | low);
transmit-weight (cells number | percent number);
}
vc-cos-mode (alternate | strict);
}
use-null-cw;
vpi vpi-identifier {
maximum-vcs maximum-vcs;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
}
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure ATM-specific physical interface properties.
The statements are explained separately.

428

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

NOTE: Certain options apply only to specific platforms.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Interface Encapsulations Overview on page 40

multipoint-destination on page 724

shaping on page 876

vci on page 964

atm-scheduler-map
Syntax
Hierarchy Level

Release Information
Description
Options

atm-scheduler-map (map-name | default);

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Associate a scheduler map with a virtual circuit on a logical interface.
map-nameName of scheduler map that you define at the [edit interfaces interface-name
atm-options scheduler-maps] hierarchy level.
defaultThe default scheduler mapping.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

scheduler-maps (For ATM2 IQ Interfaces) on page 863

Copyright 2014, Juniper Networks, Inc.

429

Interfaces Fundamentals for Routing Devices

authentication
Syntax

Hierarchy Level

Release Information
Description

authentication {
packet-types [packet-types];
password password-string;
username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-82 <circuit-id> <remote-id>;
radius-realm radius-realm-string;
user-prefix user-prefix-string;
}
}
[edit interfaces interface-name auto-configure vlan-ranges],
[edit interfaces interface-name auto-configure stacked-vlan-ranges]

Statement introduced in Junos OS Release 10.0.

Specify the authentication parameters that trigger the Access-Request message to AAA
for the interface.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

430

systemTo view this statement in the configuration.

system-controlTo add this statement to the configuration.

Configuring Subscribers over Static Interfaces

Configuring the Static Subscriber Global Authentication Password

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

authentication-key
Syntax
Hierarchy Level
Release Information
Description
Options

authentication-key key;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Configure the Automatic Protection Switching (APS) authentication key (password).
keyAuthentication password. It can be 1 through 8 characters long. Configure the same

key for both the working and protect routers.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Basic Automatic Protect Switching

For information about the authentication-key statement at the [edit interfaces

interface-name unit unit-number family inet address address (vrrp-group |
vrrp-inet6-group) group-number] or [edit logical-systems logical-system-name interfaces
interface-name unit unit-number family (inet | inet6) address address (vrrp-group |
vrrp-inet6-group) group-number] hierarchy level, see the Junos OS High Availability

Library for Routing Devices.

authentication-profile-name
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

authentication-profile-name access-profile-name;
[edit protocols dot1x authenticator]

Statement introduced in Junos OS Release 9.3.

Specify the RADIUS authentication profile to use for user authentication when establishing
an IEEE 802.1x Port-Based Network Access Control (dot1x) connection.
interfaceTo view this statement in the configuration.
interface controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

Copyright 2014, Juniper Networks, Inc.

431

Interfaces Fundamentals for Routing Devices

authenticator
Syntax

Hierarchy Level
Release Information
Description

Options

authenticator {
authentication-profile-name access-profile-name;
interface interface-id {
maximum-requests integer;
quiet-period seconds;
reauthentication (disable | interval seconds);
retries integer;
server-timeout seconds;
supplicant (single);
supplicant-timeout seconds;
transmit-period seconds;
}
}
[edit protocols dot1x]

Statement introduced in Junos OS Release 9.3.

Specify an authentication profile for user or client authentication and configure the
Ethernet interface for 802.1x protocol operation.
authentication-profile-name access-profile-nameSpecifies the RADIUS authentication

profile for user or client authentication.

The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

432

protocolsTo view this statement in the configuration.

protocols-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authentication-profile-name on page 431

dot1x on page 517

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

auto-configure
Syntax

auto-configure {
vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
password password-string;
username-include{
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-18;
option-37;
option-82 <circuit-id> <remote-id>;
radius-realm radius-realm-string;
user-prefix user-prefix-string;
}
}
dynamic-profile profile-name {
accept (any | dhcp-v4 |dhcp-v6| inet | inet6 | pppoe);
ranges (any | low-tag)(any | high-tag);
}
override;
}
stacked-vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
password password-string;
username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-18;
option-37;
option-82 <circuit-id> <remote-id>;
radius-realm radius-realm-string;
user-prefix user-prefix-string;
}
}
dynamic-profile profile-name {
accept (any | dhcp-v4 |dhcp-v6| inet | inet6 | pppoe);
ranges (any | low-taghigh-tag),(any | low-taghigh-tag);
}
override;
}
remove-when-no-subscribers;
}

Copyright 2014, Juniper Networks, Inc.

433

Interfaces Fundamentals for Routing Devices

Hierarchy Level
Release Information
Description

[edit interfaces interface-name]

Statement introduced in Junos OS Release 9.5.

Enable the configuration of dynamic, auto-sensed VLANs.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo 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

auto-discovery
Syntax
Hierarchy Level

Release Information
Description
Required Privilege
Level
Related
Documentation

434

auto-discovery;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id]

Statement introduced in Junos OS Release 8.4.

Enable the MEP to accept continuity check messages from all remote MEPs.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring a Maintenance Endpoint

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

auto-negotiation
Syntax

Hierarchy Level

Release Information

Description

(auto-negotiation | no-auto-negotiation) <remote-fault (local-interface-online |

local-interface-offline)>;
[edit interfaces interface-name ether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces ge-pim/0/0 switch-options switch-port port-number]

Statement introduced in Junos OS Release 7.6.

Statement introduced in Junos OS Release 8.4 for J Series Services Routers.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
For Gigabit Ethernet interfaces on M Series, MX Series, T Series, TX Matrix routers, and
ACX Series routers explicitly enable autonegotiation and remote fault. For EX Series
switches and J Series Services Routers, explicitly enable autonegotiation only.

auto-negotiationEnables autonegotiation. This is the default.

no-auto-negotiationDisable autonegotiation. When autonegotiation is disabled, you

must explicitly configure the link mode and speed.

When you configure Tri-Rate Ethernet copper interfaces to operate at 1 Gbps,
autonegotiation must be enabled.

NOTE: On EX Series switches, an interface configuration that disables

autonegotiation and manually sets the link speed to 1 Gbps is accepted when
you commit the configuration; however, if the interface you are configuring
is a Tri-Rate Ethernet copper interface, the configuration is ignored as invalid
and autonegotiation is enabled by default.
To correct the invalid configuration and disable autonegotiation:
1.

Delete the no-auto-negotiation statement and commit the configuration.

2. Set the link speed to 10 or 100 Mbps, set no-auto-negotiation, and commit

the configuration.

On J Series Services Routers with universal Physical Interface Modules (uPIMs) and on
EX Series switches, if the link speed and duplex mode are also configured, the interfaces
use the values configured as the desired values in the negotiation. If autonegotiation is
disabled, the link speed and link mode must be configured.

NOTE: On T4000 routers, the auto-negotiation command is ignored for

interfaces other than Gigabit Ethernet.

Copyright 2014, Juniper Networks, Inc.

435

Interfaces Fundamentals for Routing Devices

Default

Options

Autonegotiation is automatically enabled. No explicit action is taken after the

autonegotiation is complete or if the negotiation fails.
remote-fault (local-interface-online | local-interface-offline)(Optional) For M Series,

MX Series, T Series, TX Matrix routers, and ACX Series routers only, manually configure
remote fault on an interface.
Default: local-interface-online
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Gigabit Ethernet Autonegotiation Overview

Configuring Gigabit Ethernet Interfaces on J Series Services Routers

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

auto-negotiation (J Series uPIM)

Syntax
Hierarchy Level
Release Information
Description

(auto-negotiation | no-auto-negotiation);
[edit interfaces ge-pim/0/0 switch-options switch-port port-number]

Statement introduced in Junos OS Release 8.4.

For universal Physical Interface Modules (uPIMs) on J Series Services Routers only,
explicitly enable autonegotiation. If the link speed and duplex are also configured, the
interfaces use the values configured as the desired values in the negotiation. Include the
no-auto-negotiation statement to disable autonegotiation.
If autonegotiation is disabled, the link speed and link mode must be configured.

Default
Options

Autonegotiation is enabled by default.

auto-negotiationEnables autonegotiation.
no-auto-negotiationDisables autonegotiation.

Required Privilege
Level
Related
Documentation

436

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Interfaces on J Series Services Routers

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

auto-reconnect
Syntax
Hierarchy Level

Release Information
Description

Options

auto-reconnect seconds;
[edit interfaces interface-name unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces interface-name
unit logical-unit-number pppoe-options]

Statement introduced before Junos OS Release 7.4.

For J Series Services Routers with PPP over Ethernet interfaces, configure the amount
of time to wait before reconnecting after a session has terminated.
secondsTime to wait before reconnecting after a session has terminated.

Range: 0 through 4,294,967,295 seconds

Default: 0 (immediately)
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPPoE Automatic Reconnect Wait Timer

Junos OS Interfaces and Routing Configuration Guide

backup-destination
Syntax
Hierarchy Level

Release Information
Description
Options
Required Privilege
Level
Related
Documentation

backup-destination address;
[edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel]

Statement introduced before Junos OS Release 7.4.

For tunnel interfaces, specify the remote address of the backup tunnel.
addressAddress of the remote side of the connection.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

destination (Tunnels) on page 507

Copyright 2014, Juniper Networks, Inc.

437

Interfaces Fundamentals for Routing Devices

backup-interface
Syntax
Hierarchy Level
Release Information
Description

backup-interface es-fpc/pic/port;
[edit interfaces es-fpc/pic/port es-options]

Statement introduced before Junos OS Release 7.4.

Configure a backup ES Physical Interface Card (PIC). If the primary ES PIC fails, the
backup becomes active, inherits all the tunnels and security associations (SAs), and acts
as the new next hop for IP Security (IPsec) traffic.

Options

es-fpc/pic/portName of ES interface to serve as the backup.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Related
Documentation

Junos OS Services Interfaces Library for Routing Devices

backup-options
Syntax

Hierarchy Level

Release Information
Description

backup-options {
interface interface-name;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Configure an interface to be used as a backup interface if the primary interface goes
down. This is used to support ISDN dial backup operation.
The remaining statement is explained separately.

Required Privilege
Level
Related
Documentation

438

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an ISDN Dialer Interface as a Backup Interface

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

bandwidth (Interfaces)
Syntax
Hierarchy Level

Release Information

Description

bandwidth rate;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Configure an informational-only bandwidth value for an interface. This statement is valid
for all logical interface types except multilink and aggregated interfaces.

NOTE: We recommend that you be careful when setting this value. Any
interface bandwidth value that you configure using the bandwidth statement
affects how the interface cost is calculated for a dynamic routing protocol,
such as OSPF. By default, the interface cost for a dynamic routing protocol
is calculated using the following formula:
cost = reference-bandwidth/bandwidth,

where bandwidth is the physical interface speed. However, if you specify a

value for bandwidth using the bandwidth statement, that value is used to
calculate the interface cost, rather than the actual physical interface
bandwidth.

Options

ratePeak 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.
Range: Not limited.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Interface Bandwidth on page 172

Copyright 2014, Juniper Networks, Inc.

439

Interfaces Fundamentals for Routing Devices

bandwidth-limit (Hierarchical Policer)

Syntax
Hierarchy Level

bandwidth-limit bps;
[edit dynamic-profiles profile-name firewall hierarchical-policer aggregate if-exceeding],
[editdynamic-profiles profile-name firewall hierarchical-policer premium if-exceeding],
[edit firewall hierarchical-policer aggregate if-exceeding],
[edit firewall hierarchical-policer premium if-exceeding]

Release Information

Statement introduced in Junos OS Release 9.5.

Support at the [edit dynamic-profiles ... if-exceeding] hierarchy level introduced in Junos
OS Release 11.4.

Description

On M40e, M120, and M320 (with FFPC and SFPC) edge routers; on MPCs hosted on MX
Series routers; on T320, T640, and T1600 core routers with Enhanced Intelligent Queuing
(IQE) PICs; and on T4000 routers with Type 5 FPC and Enhanced Scaling Type 4 FPC,
configure the maximum average bandwidth for premium or aggregate traffic in a
hierarchical policer.

Options

bpsYou can specify the number of bits per second either as a decimal number or as a

decimal number followed by the abbreviation k (1000), m (1,000,000), or g

(1,000,000,000).
Range: 32,000 through 50,000,000,000 (32,000 through 100,000,000,000 on MX
Series and T Series routers)
Required Privilege
Level
Related
Documentation

440

firewallTo view this statement in the configuration.

firewall-controlTo add this statement to the configuration.

Hierarchical Policer Configuration Overview

Policer Bandwidth and Burst-Size Limits

Policer Color-Marking and Actions

Single Token Bucket Algorithm

Determining Proper Burst Size for Traffic Policers

aggregate (Hierarchical Policer)

burst-size-limit (Hierarchical Policer) on page 453

premium (Hierarchical Policer) on page 817

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

bandwidth-limit (Policer for Gigabit Ethernet Interfaces)

Syntax
Hierarchy Level

Release Information
Description
Options

bandwidth-limit bps;
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name aggregate],
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name premium]

Statement introduced before Junos OS Release 7.4.

Define a policer to apply to nonpremium traffic.
bpsBandwidth limit, in bits per second. Specify 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: 32 Kbps through 32 gigabits per second (Gbps). For IQ2 and IQ2-E interfaces
65,536 bps through 1 Gbps. For 10-Gigabit IQ2 and IQ2-E interfaces 65,536 bps
through 10 Gbps.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Policers

burst-size-limit (Policer for Gigabit Ethernet Interfaces) on page 454

bchannel-allocation
Syntax
Hierarchy Level
Release Information
Description

Options

bchannel-allocation (ascending | descending);

[edit interfaces interface-name isdn-options]

Statement introduced in Junos OS Release 8.3.

(J Series Services Routers equipped with a Dual-Port Channelized T1/E1 PIM) For
Integrated Services Digital Network Primary Rate Interfaces (ISDN PRI), allocate PRI
dialout B-channels in ascending or descending order.
(ascending | descending)Allocate the B-channels in ascending (from low to high) or
descending (from high to low) order.
Default: Descending order

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Allocating B-Channels for Dialout

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

441

Interfaces Fundamentals for Routing Devices

bearer-bandwidth-limit
Syntax
Hierarchy Level

Release Information
Description

Options

bearer-bandwidth-limit kilobits-per-second;
[edit interfaces interface-name unit logical-unit-number dynamic-call-admission-control],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
dynamic-call-admission-control]

Statement introduced in Junos OS Release 8.2.

(J4350 and J6350 Services Routers supporting voice over IP with the TGM550 media
gateway module) For Fast Ethernet and Gigabit Ethernet interfaces, ISDN BRI interfaces,
and serial interfaces with PPP or Frame Relay encapsulation, configure the bearer
bandwidth limit (BBL). BBL is used for dynamic call admission control (dynamic CAC)
to provide enhanced control over WAN bandwidth.
kilobits-per-secondThe bearer bandwidth limit to be reported to a TGM550 media

gateway module, in kilobits per second (kbps).

Range: 0 through 9999 kbps
Default: 1 (dynamic CAC is not enabled on the interface)
Required Privilege
Level
Related
Documentation

442

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dynamic Call Admission Control on page 181

Junos OS Services Interfaces Library for Routing Devices

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

bert-algorithm
Syntax
Hierarchy Level

Release Information

Description

bert-algorithm algorithm;
[edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure the pattern to send in the bit stream during a bit error rate test (BERT). Applies
to T1, E3, T3, and multichannel DS3 interfaces, the channelized interfaces (DS3, OC12,
STM1), and channelized IQ and IQE interfaces (E1, E3 and DS3).

NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1

IQE PICs, the bert-algorithm statement must be included at the [edit interfaces
ce1-fpc/pic/port] or [edit interfaces ct1-fpc/pic/port] hierarchy level as
appropriate.

Options

algorithmPattern to send in the bit stream. There are two categories of test patterns:

pseudorandom and repetitive. Both patterns conform to CCITT/ITU O.151, O.152,

O.153, and O.161 standards. The algorithm can be one of the following patterns:

all-ones-repeatingPattern is all ones.

all-zeros-repeatingPattern is all zeros.

alternating-double-ones-zerosPattern is alternating pairs of ones and zeros.

alternating-ones-zerosPattern is alternating ones and zeros.

pseudo-2e3Pattern is 2 1.

pseudo-2e4Pattern is 2 1.

pseudo-2e5Pattern is 2 1.

pseudo-2e6Pattern is 2 1.

pseudo-2e7Pattern is 2 1.

pseudo-2e9-o153Pattern is 2 1, as defined in the O153 standard.

pseudo-2e10Pattern is 2

pseudo-2e11-o152Pattern is 2 1, as defined in the O152 standard.

Copyright 2014, Juniper Networks, Inc.

10

1.
11

443

Interfaces Fundamentals for Routing Devices

15

pseudo-2e15-o151Pattern is 2 1, as defined in the O151 standard.

pseudo-2e17Pattern is 2 1.

pseudo-2e18Pattern is 2

pseudo-2e20-o151Pattern is 2

pseudo-2e20-o153Pattern is 2

pseudo-2e21Pattern is 2 1.

pseudo-2e22Pattern is 2

pseudo-2e23-o151Pattern is 2

17

18

1.
20

1, as defined in the O151 standard.

20

1, as defined in the O153 standard.

21

22

pseudo-2e25Pattern is 2

1.
23

25

1.

28

1.

29

1.

1, as defined in the O151 standard.

pseudo-2e28Pattern is 2

pseudo-2e29Pattern is 2

pseudo-2e31Pattern is 2 1.

pseudo-2e32Pattern is 2

repeating-1-in-4One bit in four is set to 1; the others are set to 0.

repeating-1-in-8One bit in eight is set to 1; the others are set to 0.

repeating-3-in-24Three bits in twenty four are set to 1; the others are set to 0.

31

32

1.

Default: pseudo-2e3
Required Privilege
Level
Related
Documentation

444

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Interface Diagnostics on page 329

Configuring E1 BERT Properties

Configuring E3 BERT Properties

Configuring T1 BERT Properties

Configuring T3 BERT Properties

Examples: Configuring T3 Interfaces

bert-error-rate on page 445

bert-period on page 447

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

bert-error-rate
Syntax
Hierarchy Level

Release Information

Description

bert-error-rate rate;
[edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure the bit error rate to use in a BERT procedure. Applies to E1, E3, T1, or T3
interfaces, and to the channelized interfaces (DS3, OC3, OC12, and STM1).

NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1

IQE PICs, the bert-error-rate statement must be included at the [edit interfaces
ce1-fpc/pic/port] or [edit interfaces ct1-fpc/pic/port] hierarchy level as
appropriate.
When configuring t3-options bert-error-rate on J Series routers, only 0 and 3
through 7 are valid values. If you enter 1 or 2, Junos OS will return the error
message configuration check-out failed.

Options

rateBit error rate.

1

Range: 0 through 7, which corresponds to 10 (1 error per bit) to 10

(1 error per 10

million bits)
Default: 0
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

bert-algorithm on page 443

bert-period on page 447

ds0-options on page 520

e1-options on page 538

e3-options on page 539

t1-options on page 910

t3-options on page 913

Copyright 2014, Juniper Networks, Inc.

445

Interfaces Fundamentals for Routing Devices

446

Interface Diagnostics on page 329

Configuring E1 BERT Properties

Configuring E3 BERT Properties

Configuring T1 BERT Properties

Configuring T3 BERT Properties

Examples: Configuring T3 Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

bert-period
Syntax
Hierarchy Level

Release Information

Description

bert-period seconds;
[edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure the duration of a BERT test. Applies to E1, E3, T1, and T3 interfaces, and to E1,
E3, T1, and T3 partitions on the channelized interfaces (CE1, CT1, DS3, OC3, OC12, OC48,
STM1, STM4, and STM16).
E1 and T1 IQ, IQE, and standard interfaces support an extended BERT period range, up
to 86,400 seconds (24 hours).

NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1

IQE PICs, the bert-period statement must be included at the [edit interfaces
ce1-fpc/pic/port] or [edit interfaces ct1-fpc/pic/port] hierarchy level as
appropriate.

Options

secondsTest duration. Range and default values vary by interface type.

Range:

PIC-dependentNormal BERT period: either 1 through 239 seconds or 1 through 240

seconds

PIC-dependentExtended BERT period: from 1 through 86,400 seconds

Default:

Required Privilege
Level
Related
Documentation

Normal BERT period: 10 seconds

Extended BERT period (on supported E1 interfaces): 10 seconds

Extended BERT period (on supported T1 interfaces): 240 seconds

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Interface Diagnostics on page 329

Configuring E1 BERT Properties

Copyright 2014, Juniper Networks, Inc.

447

Interfaces Fundamentals for Routing Devices

Configuring E3 BERT Properties

Configuring T1 BERT Properties

Configuring T3 BERT Properties

bert-algorithm on page 443

bert-error-rate on page 445

bridge-domain
Syntax

Hierarchy Level

Release Information
Description

Options

bridge-domain name;
vlan-id [ vlan-identifiers ];
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
maintenance-domain-name],
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
maintenance-domain-name virtual-switch virtual-switch-name]

Statement introduced in Junos OS Release 9.4.

(MX Series routers only) Specify the OAM Ethernet CFM maintenance domain bridge
domain.
nameSpecify the name of the bridge domain.
vlan-identifiersSpecify one or more VLAN identifiers.

Required Privilege
Level
Related
Documentation

448

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Maintenance Intermediate Points

maintenance-domain on page 699

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

broadcast
Syntax
Hierarchy Level

Release Information

Description

Default
Options

broadcast address;
[edit interfaces interface-name unit logical-unit-number family family address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Set the broadcast address on the network or subnet. On a subnet you cannot specify a
host address of 0, nor can you specify a broadcast address.
The default broadcast address has a host portion of all ones.
addressBroadcast address. The address must have a host portion of either all ones or

all zeros. You cannot specify the addresses 0.0.0.0 or 255.255.255.255.

NOTE: The edit logical-systems hierarchy is not available on QFabric systems.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Interface Address on page 192

Copyright 2014, Juniper Networks, Inc.

449

Interfaces Fundamentals for Routing Devices

buildout (E3 or T3 over ATM Interfaces)

Syntax
Hierarchy Level

Release Information
Description
Options

buildout feet;
[edit interfaces at-fpc/pic/port e3-options],
[edit interfaces at-fpc/pic/port t3-options]

Statement introduced before Junos OS Release 7.4.

For E3 and T3 traffic over ATM interfaces, set the buildout value.
feetThe buildout value in feet.

Range: 0 through 450 feet (137 meters)

Default: 10 feet (3 meters)
Required Privilege
Level
Related
Documentation

450

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring E3 and T3 Parameters on ATM Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

buildout (T1 Interfaces)

Syntax
Hierarchy Level

Release Information

Description

buildout value;
[edit interfaces ct1-fpc/pic/port]
[edit interfaces interface-name t1-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
For T1 interfaces, set the buildout value.

NOTE: When configuring CT1 interfaces on 10-port Channelized E1/T1 IQE

PICs and 16-Port Channelized E1/T1 Circuit Emulation MICs, the buildout
statement must be included at the hierarchy level.

Default

The default buildout value is 0 through 132 feet.

Options

You can set the buildout value to one of the following:

0-1320 through 132 feet (0 through 40 meters)

133-265133 through 265 feet (40 through 81 meters)

266-398266 through 398 feet (81 through 121 meters)

399-531399 through 531 feet (121 through 162 meters)

532-655532 through 655 feet (162 through 200 meters)

long-0dbFor J Series routers only, long buildout with 0 decibel (dB) transmit

attenuation

long-7.5dbFor MX Series and J Series routers only, long buildout with 7.5 dB transmit

attenuation

long-15dbFor MX Series and J Series routers only, long buildout with 15 dB transmit

attenuation

long-22.5dbFor MX Series and J Series routers only, long buildout with 22.5 dB transmit

attenuation
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the T1 Buildout

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

451

Interfaces Fundamentals for Routing Devices

bundle
Syntax
Hierarchy Level

Release Information
Description

bundle (ml-fpc/pic/port | ls-fpc/pic/port);

[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]

Statement introduced before Junos OS Release 7.4.

Associate the multilink interface with the logical interface it is joining. You can include
this statement for the mlfr-end-to-end and mlfr-uni-nni protocol families only.

NOTE:
For M Series routers and T Series routers, the following caveats apply:

Options

Maximum supported throughput on the bundle interfaces is 45 Mbps.

Bundling of the logical interfaces under a T3 physical interface into the

same or different bundles is not supported.

ml-fpc/pic/portName of the multilink interface you are linking.

ls-fpc/pic/portName of the link services interface you are linking.

Required Privilege
Level
Related
Documentation

452

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

burst-size-limit (Hierarchical Policer)

Syntax
Hierarchy Level

burst-size-limit bytes;
[edit dynamic-profiles profile-name firewall hierarchical-policer aggregate if-exceeding],
[editdynamic-profiles profile-name firewall hierarchical-policer premium if-exceeding],
[edit firewall hierarchical-policer aggregate if-exceeding],
[edit firewall hierarchical-policer premium if-exceeding]

Release Information

Statement introduced in Junos OS Release 9.5.

Support at the [edit dynamic-profiles ... if exceeding] hierarchy level introduced in Junos
OS Release 11.4.

Description

On M40e, M120, and M320 (with FFPC and SFPC) edge routers; on MPCs hosted on MX
Series routers; on T320, T640, and T1600 core routers with Enhanced Intelligent Queuing
(IQE) PICs; and on T4000 routers with Type 5 FPC and Enhanced Scaling Type 4 FPC,
configure the burst-size limit for premium or aggregate traffic in a hierarchical policer.

Options

bytesBurst-size limit in bytes. The minimum recommended value is the maximum

transmission unit (MTU) of the IP packets being policed. You can specify the value
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: 1500 through 2,147,450,880 (1500 through 100,000,000,000 on MPCs hosted
on MX Series routers)
Required Privilege
Level
Related
Documentation

firewallTo view this statement in the configuration.

firewall-controlTo add this statement to the configuration.

Hierarchical Policer Configuration Overview

Policer Bandwidth and Burst-Size Limits

Policer Color-Marking and Actions

Single Token Bucket Algorithm

Determining Proper Burst Size for Traffic Policers

Hierarchical Policers

aggregate (Hierarchical Policer)

bandwidth-limit (Hierarchical Policer) on page 440

premium (Hierarchical Policer) on page 817

Copyright 2014, Juniper Networks, Inc.

453

Interfaces Fundamentals for Routing Devices

burst-size-limit (Policer for Gigabit Ethernet Interfaces)

Syntax
Hierarchy Level

Release Information
Description
Options

burst-size-limit bytes;
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name aggregate],
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name premium]

Statement introduced before Junos OS Release 7.4.

Define a policer to apply to nonpremium traffic.
bytesBurst length.

Range: 1500 through 100,000,000 bytes

Required Privilege
Level
Related
Documentation

454

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Policers

bandwidth-limit (Policer for Gigabit Ethernet Interfaces) on page 441

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

byte-encoding
Syntax
Hierarchy Level

Release Information

Description

byte-encoding (nx56 | nx64);

[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name t1-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Set the byte encoding on a DS0 or T1 interface to use 7 bits per byte or 8 bits per byte.

NOTE: When configuring T1 interfaces on the 10-port Channelized E1/T1 IQE

PIC, the byte-encoding statement must be included at the [edit interfaces
t1-fpc/pic/port] hierarchy level.

Default
Options

The default byte encoding is 8 bits per byte (nx64).

nx56Use 7 bits per byte.
nx64Use 8 bits per byte.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring T1 Byte Encoding

Copyright 2014, Juniper Networks, Inc.

455

Interfaces Fundamentals for Routing Devices

bytes
Syntax

Hierarchy Level
Release Information
Description
Options

bytes {
c2 value;
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

Set values in some SONET/SDH header bytes.
c2 valuePath signal label SONET/SDH overhead byte. SONET/SDH frames use the C2

byte to indicate the contents of the payload inside the frame. SONET/SDH interfaces
use the C2 byte to indicate whether the payload is scrambled.
Range: 0 through 255
Default: 0xCF
e1-quiet valueDefault idle byte sent on the orderwire SONET/SDH overhead bytes. The

router does not support the orderwire channel, and hence sends this byte
continuously.
Range: 0 through 255
Default: 0x7F
f1 value, f2 value, z3 value, z4 valueSONET/SDH overhead bytes.

Range: 0 through 255

Default: 0x00
s1 valueSynchronization message SONET overhead byte. This byte is normally controlled

as a side effect of the system reference clock configuration and the state of the
external clock coming from an interface if the system reference clocks have been
configured to use an external reference.
Range: 0 through 255
Default: 0xCC
Required Privilege
Level
Related
Documentation

456

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring SONET/SDH Header Byte Values to Identify Error Conditions

no-concatenate

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

calculation-weight
Syntax

Hierarchy Level

Release Information

Description

calculation-weight {
delay delay-value;
delay-variation delay-variation-value;
}
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]

Statement introduced in Junos OS Release 11.1.

Statement introduced in Junos OS Release 11.4 for EX Series switches.
Configure the calculation weight for delay and delay variation.

NOTE: This option is applicable only for two-way delay measurement.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

Configuring an Iterator Profile

Configuring an Iterator Profile on a Switch (CLI Procedure)

delay

delay-variation

Copyright 2014, Juniper Networks, Inc.

457

Interfaces Fundamentals for Routing Devices

callback
Syntax
Hierarchy Level

Release Information
Description

callback;
[edit interfaces dln unit logical-unit-number dialer-options incoming-map],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options incoming-map]

Statement introduced in Junos OS Release 7.5.

On J Series Services Routers with interfaces configured for ISDN, configure the dialer to
terminate the incoming call and call back the originator after the callback wait period.
The default wait time is 5 seconds. To configure the wait time, include the
callback-wait-period statement at the [edit interfaces dl n unit logical-unit-number
dialer-options] hierarchy level.

NOTE: The incoming-map statement is mandatory for the router to accept

any incoming ISDN calls.

If the callback statement is configured, you cannot use the caller caller-id statement at
the [edit interfaces dln unit logical-unit-number dialer-options] hierarchy level.
Required Privilege
Level
Related
Documentation

458

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dial-In and Callback

Junos OS Interfaces and Routing Configuration Guide

callback-wait-period on page 459

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

callback-wait-period
Syntax
Hierarchy Level

Release Information
Description

callback-wait-period time;
[edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options]

Statement introduced in Junos OS Release 7.5.

On J Series Services Routers with interfaces configured for ISDN with callback, specify
the amount of time the dialer waits before calling back the caller. The default wait time
is 5 seconds. The wait time is necessary because, when a call is rejected, the switch waits
for up to 4 seconds on point-to-multipoint connections to ensure no other device accepts
the call before sending the DISCONNECT message to the originator of the call. However,
the default time of 5 seconds may not be sufficient for different switches or may not be
needed on point-to-point connections.
To configure callback mode, include the callback statement at the [edit interfaces dln
unit logical-unit-number dialer-options] hierarchy level.
If the callback statement is configured, you cannot use the caller caller-id statement at
the [edit interfaces dln unit logical-unit-number dialer-options] hierarchy level.

Options
Required Privilege
Level
Related
Documentation

timeTime the dialer waits before calling back the caller.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dial-In and Callback

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

459

Interfaces Fundamentals for Routing Devices

caller
Syntax
Hierarchy Level

Release Information
Description

Options

caller (caller-id | accept-all);

[edit interfaces dln unit logical-unit-number dialer-options incoming-map],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options incoming-map]

Statement introduced in Junos OS Release 7.5.

On J Series Services Routers with interfaces configured for ISDN, specify the dialer to
accept a specified caller number or accept all incoming calls.
caller-idIncoming caller number. You can configure multiple caller IDs on a dialer. The

caller ID of the incoming call is matched against all caller IDs configured on all dialers.
The dialer matching the caller ID is looked at for further processing. Only a precise
match is a valid match, For example, the configured caller ID 1-222-333-4444 or
222-333-4444 will match the incoming caller ID 1-222-333-4444.
If the incoming caller ID has fewer digits than the number configured, it is not a valid
match. Duplicate caller IDs are not allowed on different dialers; however, for example,
the numbers 1-408-532-1091, 408-532-1091, and 532-1091 can still be configured
on different dialers.
Only one B-channel can map to one dialer. If one dialer is already mapped, any other call
mapping to the same dialer is rejected (except in the case of a multilink dialer). If no
dialer caller is configured on a dialer, that dialer will not accept any calls.
accept-allAny incoming call in an associated interface is accepted.

Required Privilege
Level
Related
Documentation

460

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ISDN Interfaces Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

calling-number
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

calling-number number;
[edit interfaces br-pim/0/port isdn-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers with ISDN interfaces, configure the calling number to include
in outgoing calls.
numberCalling number.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

cbit-parity
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(cbit-parity | no-cbit-parity);
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

For T3 interfaces only, enable or disable C-bit parity mode, which controls the type of
framing that is present on the transmitted T3 signal. When C-bit parity mode is enabled,
the C-bit positions are used for the far-end block error (FEBE), far-end alarm and control
(FEAC), terminal data link, path parity, and mode indicator bits, as defined in ANSI
T1.107a-1989. For ATM and ATM2 IQ2 and IQ2-E interfaces, M23 framing is used when
the no-cbit-parity statement is included. For all other interfaces, M13 framing is used
when the no-cbit-parity statement is included.
C-bit parity mode is enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring E3 and T3 Parameters on ATM Interfaces

Disabling T3 C-Bit Parity Mode

Copyright 2014, Juniper Networks, Inc.

461

Interfaces Fundamentals for Routing Devices

cbr
Syntax
Hierarchy Level

Release Information
Description

Default
Options

cbr rate;
[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]

Statement introduced before Junos OS Release 7.4.

For ATM encapsulation only, define a constant bit rate bandwidth utilization in the
traffic-shaping profile.
Unspecified bit rate (UBR); that is, bandwidth utilization is unlimited.
ratePeak 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.
Required Privilege
Level
Related
Documentation

462

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Defining the ATM Traffic-Shaping Profile

rtvbr on page 857

shaping on page 876

vbr on page 962

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

cell-bundle-size
Syntax
Hierarchy Level

Release Information
Description

Options

cell-bundle-size cells;
[edit interfaces at-fpc/pic/port atm-options],
[edit interfaces at-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces using ATM Layer 2 circuit cell-relay transport mode only, configure
the maximum number of ATM cells per frame.
cellsMaximum number of cells.

Default: 1 cell
Range: 1 through 176 cells
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Layer 2 Circuit Cell-Relay Cell Maximum

Copyright 2014, Juniper Networks, Inc.

463

Interfaces Fundamentals for Routing Devices

chap
Syntax

Hierarchy Level

Release Information
Description

chap {
access-profile name;
challenge-length minimum minimum-length maximum maximum-length;
default-chap-secret name;
local-name name;
passive;
}
[edit interfaces interface-name ppp-options],
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options]

Statement introduced before Junos OS Release 7.4.

Allow each side of a link to challenge its peer, using a secret known only to the
authenticator and that peer. The secret is not sent over the link.
By default, PPP CHAP is disabled. If CHAP is not explicitly enabled, the interface makes
no CHAP challenges and denies all incoming CHAP challenges.
For ATM2 IQ interfaces only, you can configure CHAP on the logical interface unit if the
logical interface is configured with one of the following PPP over ATM encapsulation
types:

atm-ppp-llcPPP over AAL5 LLC encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

BEST PRACTICE: On inline service (si) interfaces for L2TP, only the chap
statement itself is typically used for subscriber management. We recommend
that you leave the subordinate statements at their default values.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

464

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Challenge Handshake Authentication Protocol on page 126

Applying PPP Attributes to L2TP LNS Subscribers with a User Group Profile

Applying PPP Attributes to L2TP LNS Subscribers Per Inline Service Interface

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

chap-secret
Syntax
Hierarchy Level
Release Information
Description

chap-secret chap-secret;
[edit access profile profile-name client client-name]

Statement introduced before Junos OS Release 7.4.

For interfaces with PPP encapsulation on which the PPP Challenge Handshake
Authentication Protocol (CHAP) is configured, configure the shared secret (the CHAP
secret key associated with a peer), as defined in RFC 1994.

NOTE: This statement is not supported for L2TP LNS on MX Series routers.

Options
Required Privilege
Level
Related
Documentation

chap-secretThe secret key associated with a peer.

adminTo view this statement in the configuration.

admin-controlTo add this statement to the configuration.

Configuring the CHAP Secret for an L2TP Profile

Configuring PPP CHAP Authentication on page 178

pap-password on page 779

Junos OS Administration Library for Routing Devices

circuit-type
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

circuit-type;
[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include],

Statement introduced in Junos OS Release 10.0.

Specify that the circuit type is concatenated with the username during the subscriber
authentication process.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

Copyright 2014, Juniper Networks, Inc.

465

Interfaces Fundamentals for Routing Devices

cisco-interoperability
Syntax
Hierarchy Level
Release Information
Description
Options

cisco-interoperability send-lip-remove-link-for-link-reject;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced in Junos OS Release 7.4.

FRF.16 interoperability settings.
send-lip-remove-link-for-link-rejectSend Link Integrity Protocol remove link when an

add-link rejection message is received.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

classifier
Syntax

Hierarchy Level

Release Information
Description

classifier {
per-unit-scheduler {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map]

Statement introduced before Junos OS Release 7.4.

For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, define the classifier for
the output priority map to be applied to outgoing frames on this interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

466

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying an Output Priority Map

input-priority-map on page 624

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

clear-dont-fragment-bit
Syntax
Hierarchy Level

Release Information
Description

clear-dont-fragment-bit;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Clear the dont-fragment (DF) bit on all IP version 4 (IPv4) packets entering a generic
routing encapsulation (GRE) tunnel. If the encapsulated packets size exceeds the tunnels
maximum transmission unit (MTU), the packet is fragmented before encapsulation. The
statement is supported only on MX Series routers and all M Series routers except the
M320 router.
When you configure the clear-dont-fragment-bit statement on an interface with the MPLS
protocol family enabled, you must specify an MTU value. This MTU value must not be
greater than maximum supported value, which is 9192.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

client
Syntax
Hierarchy Level

Release Information
Description
Required Privilege
Level
Related
Documentation

client;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options]

Statement introduced in Junos OS Release 8.5.

On J Series Services Routers, configure the router to operate in the PPPoE client mode.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the PPPoE Client Mode

Copyright 2014, Juniper Networks, Inc.

467

Interfaces Fundamentals for Routing Devices

clock-rate
Syntax
Hierarchy Level
Release Information
Description
Options

clock-rate rate;
[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces, configure the interface speed, in megahertz (MHz).
rateYou can specify one of the following rates:

2.048 MHz

2.341 MHz

2.731 MHz

3.277 MHz

4.096 MHz

5.461 MHz

8.192 MHz

16.384 MHz

Default: 16.384 MHz

Required Privilege
Level
Related
Documentation

468

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Clocking Mode on page 307

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

clocking
Syntax
Hierarchy Level
Release Information

Description

clocking (external [interface interface-name ] | internal);

[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

interface option added in Junos OS Release 8.2.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
For interfaces that can use various clock sources, configure the source of the transmit
clock on each interface.

NOTE: On Channelized SONET/SDH PICs, if you set the parent (or the master)
controller clock to external, then you must set the child controller clocks to
the default valuethat is, internal.
For example, on the Channelized STM1 PIC, if the clock on the Channelized
STM1 interface (which is the master controller) is set to external, then you
must not configure the CE1 interface (which is the child controller) clock to
external. Instead you must configure the CE1 interface clock to internal.

Options

externalThe clock source is provided by the data communication equipment (DCE).

interface interface-nameFor interfaces operating on T1/E1 PIMs for J Series Services

Routers only, configure clocking for the drop-and insert feature. When configuring
this feature, both ports must use the same clock source: either the routers internal
clock or an external clock on one of the interfaces. If an external clock source is
required, one interface must specify clocking external and the other must specify
the same clock.
internalUse the internal stratum 3 clock as the reference clock.

Default: internal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Clock Source on page 116

Configuring the Clock Source on SONET/SDH Interfaces

Clock Sources on Channelized Interfaces

Configuring a Channelized T1/E1 Interface to Drop and Insert Time Slots

loop-timing on page 685

Copyright 2014, Juniper Networks, Inc.

469

Interfaces Fundamentals for Routing Devices

clocking-mode
Syntax
Hierarchy Level
Release Information
Description

Options

clocking-mode (dce | internal | loop);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces, configure the clock mode. You cannot configure
clocking-mode dce on a DTE router using an X.21 serial line protocol (detected
automatically when an X.21 cable is plugged into the serial interface).
dceDCE timing (DTE mode only, not valid for X.21).
internalInternal baud timing.
loopLoop timing.

Default: loop
Required Privilege
Level
Related
Documentation

470

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration

Configuring the Serial Clocking Mode on page 307

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

community (Policy Options)

Syntax

Hierarchy Level

Release Information

community name {
invert-match;
members [ community-ids ];
}
[edit dynamic policy-options],
[edit logical-systems logical-system-name policy-options],
[edit policy-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5
for EX Series switches.

Description

Define a community or extended community for use in a routing policy match condition.

Options

nameName that identifies the regular expression. The name can contain letters, numbers,

and hyphens (-) and can be up to 255 characters. To include spaces in the name,
enclose it in quotation marks ( ).
invert-matchInvert the results of the community expression matching. The community

match condition defines a regular expression and if it matches the community

attribute of the received prefix, Junos OS returns a TRUE result. If not, Junos OS
returns a FALSE result. The invert-match statement makes Junos OS behave to the
contrary. If there is a match, Junos OS returns a FALSE result. If there is no match,
Junos OS returns a TRUE result.
members community-idsOne or more community members. If you specify more than

one member, you must enclose all members in brackets.

The format for community-ids is:
as-number:community-value
as-number is the AS number and can be a value in the range from 0 through 65,535.
community-value is the community identifier and can be a number in the range from 0

through 65,535.
You also can specify community-ids for communities as one of the following well-known
community names, which are defined in RFC 1997, BGP Communities Attribute:

no-exportRoutes containing this community name are not advertised outside a BGP

confederation boundary.

no-advertiseRoutes containing this community name are not advertised to other

BGP peers.

no-export-subconfedRoutes containing this community name are not advertised to

external BGP peers, including peers in other members' ASs inside a BGP confederation.

Copyright 2014, Juniper Networks, Inc.

471

Interfaces Fundamentals for Routing Devices

You can explicitly exclude BGP community information with a static route using the none
option. Include none when configuring an individual route in the route portion of the
static statement to override a community option specified in the defaults portion of
the statement.
The format for extended community-ids is the following:
type:administrator:assigned-number
type is the type of extended community and can be either a bandwidth, target, origin,
domain-id, src-as, or rt-import community or a 16-bit number that identifies a specific

BGP extended community. The target community identifies the destination to which
the route is going. The origin community identifies where the route originated. The
domain-id community identifies the OSPF domain from which the route originated.
The src-as community identifies the autonomous system from which the route
originated. The rt-import community identifies the route to install in the routing table.

NOTE: For src-as, you can specify only an AS number and not an IP address.
For rt-import, you can specify only an IP address and not an AS number.

administrator is the administrator. It is either an AS number or an IPv4 address prefix,

depending on the type of extended community.

assigned-number identifies the local provider.

The format for linking a bandwidth with an AS number is:

bandwidth:as-number:bandwidth
as-number specifies the AS number and bandwidth specifies the bandwidth in bytes per

second.

NOTE: In Junos OS Release 9.1 and later, you can specify 4-byte AS numbers
as defined in RFC 4893, BGP Support for Four-octet AS Number Space, as
well as the 2-byte AS numbers that are supported in earlier releases of the
Junos OS. In plain-number format, you can configure a value in the range
from 1 through 4,294,967,295. To configure a target or origin extended
community that includes a 4-byte AS number in the plain-number format,
append the letter L to the end of number. For example, a target community
with the 4-byte AS number 334,324 and an assigned number of 132 is
represented as target:334324L:132.
In Junos OS Release 9.2 and later, you can also use AS-dot notation when
defining a 4-byte AS number for the target and origin extended communities.
Specify two integers joined by a period: 16-bit high-order value in decimal.16-bit
low-order value in decimal. For example, the 4-byte AS number represented
in plain-number format as 65546 is represented in AS-dot notation as 1.10.

472

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Required Privilege
Level
Related
Documentation

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

Understanding BGP Communities and Extended Communities as Routing Policy Match

Conditions

Understanding How to Define BGP Communities and Extended Communities

dynamic-db

Copyright 2014, Juniper Networks, Inc.

473

Interfaces Fundamentals for Routing Devices

compatibility-mode
Syntax
Hierarchy Level

Release Information
Description

compatibility-mode (adtran | digital-link | kentrox | larscom | verilink) <subrate value>;

[edit interfaces interface-name e3-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Configure the E3 or T3 interface to be compatible with the channel service unit (CSU)
at the remote end of the line.

NOTE: The compatibility-mode statement at the [edit interfaces interface-name

e3-options] hierarchy level is not valid for IQE PICs.

Default
Options

If you omit this option, the full E3 or T3 rate is used.

adtranFor T3 IQ interfaces only, configure compatibility with Adtran CSUs.
digital-linkConfigure compatibility with Digital Link CSUs. If you include this option on

an E3 interface, you must also disable payload scrambling.

kentroxConfigure compatibility with Kentrox CSUs. Kentrox subrate is valid for E3 IQ

and T3 IQ interfaces only.

larscomFor T3 and T3 IQ interfaces only, configure compatibility with Larscom CSUs.
verilinkFor T3 IQ and T3 IQE interfaces only, configure compatibility with Verilink CSUs.

NOTE: Verilink configuration is not functional if an IQ interface is paired with

an IQE interface.

subrate valueSubrate of the E3 or T3 line.

Range: For Kentrox CSUs on E3 IQ interfaces and T3 IQ interfaces the subrate value
must match the value configured on the CSU. Each increment of the subrate value
corresponds to a rate increment of about 0.5 Mbps.
Required Privilege
Level
Related
Documentation

474

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the E3 CSU Compatibility Mode

Configuring the T3 CSU Compatibility Mode

payload-scrambler on page 750

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

compression (PPP Properties)

Syntax

Hierarchy Level

Release Information
Description

compression {
acfc;
pfc;
}
[edit interfaces interface-name ppp-options],
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options]

Statement introduced before Junos OS Release 7.4.

For interfaces with PPP encapsulation, set Link Control Protocol (LCP) compression
options.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPP Address and Control Field Compression on page 133

Configuring the PPP Protocol Field Compression on page 135

Copyright 2014, Juniper Networks, Inc.

475

Interfaces Fundamentals for Routing Devices

compression (Voice Services)

Syntax

Hierarchy Level

Release Information
Description

compression {
rtp {
f-max-period number;
queues [ queue-numbers ];
port {
minimum port-number;
maximum port-number;
}
}
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Configure the compression properties for voice services traffic.
The remaining statements are described separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

compression-device
Syntax
Hierarchy Level

Release Information
Description
Options
Required Privilege
Level
Related
Documentation

476

compression-device interface-name;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Specify the compression interface for voice services traffic.
interface-nameLogical interface used for compression.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

connections
Syntax

Hierarchy Level
Release Information
Description

connections {
interface-switch connection-name {
interface interface-name.unit-number;
interface interface-name.unit-number;
}
}
[edit protocols]

Statement introduced before Junos OS Release 7.4.

Define the connection between two circuits in a circuit cross-connect (CCC) connection.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

Defining the Connection for Switching Cross-Connects on page 261

Junos OS MPLS Applications Library for Routing Devices

connection-protection-tlv
Syntax
Hierarchy Level
Description

Required Privilege
Level
Related
Documentation

connection-protection-tlv <using-protection-path | using-working-path>

[edit protocols oam ethernet connectivity-fault-management]

This statement determines which path the connection protection TLV will use. An action
profile using connection-protection-tlv using-protection-path should apply the
statement for a CFM sessions that is monitoring the working path and an action profile
using connection-protection-tlv using-working-path should apply the command for a
CFM session that is monitoring the protection path. Using them in the opposite way could
mean drop of service traffic.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

connectivity-fault-management on page 478

Configuring MAC Flush Message Processing in CET Mode

Example: Configuring an Action Profile Based on Connection Protection TLVs

Copyright 2014, Juniper Networks, Inc.

477

Interfaces Fundamentals for Routing Devices

connectivity-fault-management
Syntax

478

connectivity-fault-management {
action-profile profile-name {
action {
interface-down;
log-and-generate-ais {
interval(1m | 1s);
levelvalue;
priority value;
}
}
default-actions {
interface-down;
}
event {
ais-trigger-condition {
adjacency-loss;
all-defects;
cross-connect-ccm;
erroneous-ccm;
receive-ais;
}
adjacency-loss;
interface-status-tlv (down | lower-layer-down);
port-status-tlv blocked;
rdi;
}
}
performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
maintenance-domain domain-name {
bridge-domain <vlan-id [ vlan-ids ]>;
instance routing-instance-name;
interface interface-name;
level number;

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

name-format (character-string | none | dns | mac+2oct);

maintenance-association ma-name {
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number;
port-status-tlv;
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
detect-loc;
}
}
}
}
virtual-switch routing-instance-name {
bridge-domain name <vlan-ids [ vlan-ids ]>;
}
}
no-aggregate-delegate-processing;
}

Hierarchy Level
Release Information
Description

[edit protocols oam ethernet]

Statement introduced in Junos OS Release 8.4.

For Ethernet interfaces on M7i and M10i routers with Enhanced CFEB (CFEB-E), and on
M120, M320, MX Series, and T Series routers, specify connectivity fault management for
IEEE 802.1ag Operation, Administration, and Management (OAM) support.
In Junos OS Release 9.3 and later, this statement is also supported on aggregated Ethernet
interfaces.
The remaining statements are explained separately.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

479

Interfaces Fundamentals for Routing Devices

Related
Documentation

IEEE 802.1ag OAM Connectivity Fault Management Overview

container-devices
Syntax

Hierarchy Level
Release Information
Description

Options

container-devices {
device-count number;
}
[edit chassis]

Statement introduced in Junos OS Release 9.2.

Specify the container devices configuration. The number option specifies the number of
sequentially numbered container interfaces, from ci0 to ci127 maximum.
numberNumber of container devices.

Range: 1 through 128

Required Privilege
Level
Related
Documentation

chassisTo view this statement in the configuration.

chassis-controlTo add this statement to the configuration.

Displaying APS Using a Container Interface with ATM Encapsulation

Configuring Container Interfaces for APS on SONET Links

container-list
Syntax
Hierarchy Level
Release Information
Description

[edit interfaces container-options]

Statement introduced in Junos OS Release 9.2.

Specify a list of container interfaces; for example: ci0, ci1, and up to ci127.

Options

container-interface-namesName of each container interface.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Related
Documentation

480

container-list [ container-interface-names ];

Displaying APS Using a Container Interface with ATM Encapsulation

Configuring Container Interfaces for APS on SONET Links

container-options on page 481

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

container-options
Syntax

Hierarchy Level
Release Information
Description
Options

container-options {
container-list [ container-interface-names ];
container-type aps;
member-interface-type sonet {
member-interface-speed [ speed ];
}
}
[edit interfaces]

Statement introduced in Junos OS Release 9.2.

Specify the container interface options.
interface-nameName of the SONET or the container interface.
apsSpecify the member link interface type of the container as APS.
sonetProtocol type of the container interface.
speedSet interface speed to OC3, OC12, OC48, OC192, OC768, or mixed.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Displaying APS Using a Container Interface with ATM Encapsulation

Configuring Container Interfaces for APS on SONET Links

container-type
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

container-type aps;
[edit interfaces container-options]

Statement introduced in Junos OS Release 9.2.

Specify the container-options interface type.
apsConfigure the interface type to be Automatic Protection Switching (APS).

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Displaying APS Using a Container Interface with ATM Encapsulation

Configuring Container Interfaces for APS on SONET Links

Copyright 2014, Juniper Networks, Inc.

481

Interfaces Fundamentals for Routing Devices

continuity-check
Syntax

Hierarchy Level

Release Information
Description
Options

continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms | 10ms);
loss-threshold number;
port-status-tlv;
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name]

Statement introduced in Junos OS Release 8.4.

Specify continuity check protocol options.
convey-loss-thresholdEnable loss-threshold-tlv transmission.
hold-interval minutesSpecify the continuity check hold-interval, in minutes.
interface-status-tlvEnable interface-status-tlv transmission.
interval (10m | 10s | 1m | 1s| 100ms | 10ms)Specify the continuity check interval.
loss-threshold minutesSpecify the loss-threshold, in minutes.
port-status-tlvEnable port-status-tlv transmission.

Required Privilege
Level
Related
Documentation

482

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Continuity Check Protocol

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

control-channel
Syntax

Hierarchy Level
Release Information

control-channel channel-name {
vlan vlan-id;
interface name interface-name
}
[edit protocols protection-group ethernet-ring name (east-interface | west-interface)]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.

Description

Configure the Ethernet RPS control channel logical interface to carry the RAPS PDU. The
related physical interface is the physical ring port.

Options

vlan vlan-idIf the control channel logical interface is a trunk port, then a dedicated vlan
vlan-id defines the dedicated VLAN channel to carry the RAPS traffic. Only configure

the vlan-id when the control channel logical interface is the trunk port.
interface name interface-nameInterface name of the control channel.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

483

Interfaces Fundamentals for Routing Devices

control-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

control-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

For X.21 interfaces only, configure the control signal polarity.
positivePositive signal polarity.
negativeNegative signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

control-signal
Syntax
Hierarchy Level

control-signal (assert | de-assert | normal);

[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Release Information

Statement introduced before Junos OS Release 7.4.

Description

For X.21 interfaces only, configure the to-DCE signal.

Options

assertThe to-DCE signal must be asserted.

de-assertThe to-DCE signal must be deasserted.
normalNormal request-to-send (RTS) signal handling, as defined by ITU-T

Recommendation X.21.
Default: normal
Required Privilege
Level
Related
Documentation

484

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

copy-tos-to-outer-ip-header
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

copy-tos-to-outer-ip-header;
[edit interfaces at-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number]

Statement introduced in Junos OS Release 8.2.

For GRE tunnel interfaces only, enable the inner IP headers TOS bits to be copied to the
outer IP packet header.
If you omit this statement, the TOS bits in the outer IP header are set to 0.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Class of Service Feature Guide for Routing Devices

core-dump
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

(core-dump | no-core-dump);
[edit interfaces mo-fpc/pic/port multiservice-options]

Statement introduced before Junos OS Release 7.4.

For monitoring services interfaces only, a useful tool for isolating the cause of a problem.
Core dumping is enabled by default. The directory /var/tmp contains core files. The Junos
OS saves the current core file (0) and the four previous core files, which are numbered
1 through 4 (from newest to oldest):

core-dumpEnable the core dumping operation.

no-core-dumpDisable the core dumping operation.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Multiservice Physical Interface Properties on page 153

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

485

Interfaces Fundamentals for Routing Devices

crc-major-alarm-threshold
Syntax
Hierarchy Level
Release Information

crc-major-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5);

[edit interfaces interface-name t1-options]

Statement introduced in Junos OS Release 8.5.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.

Description

Major alarm error thresholds for T1 CRC errors. When the threshold is exceeded for one
second, a defect condition is declared. If the defect condition continues for the monitoring
period, an alarm condition is declared.

Default

10-second monitoring period for all settings except 1e-5. The 1e-5 value uses a 50-second
monitoring period.

Options

1e-3Error rate expressed as the number of errors per number of bits. The value 1e-3 is
3

one crc error in 10 bits.

1e-4Error rate expressed as the number of errors per number of bits. The value 1e-4 is
4

one crc error in 10 bits.

1e-5Error rate expressed as the number of errors per number of bits. The value 1e-5 is
5

one crc error in 10 bits.

5e-4Error rate expressed as the number of errors per number of bits. The value 5e-4 is
4

five crc errors in 10 bits.

5e-5Error rate expressed as the number of errors per number of bits. The value 5e-5 is
5

five crc errors in 10 bits.

Default: 5e-5
Required Privilege
Level
Related
Documentation

486

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring T1 CRC Error Major Alarm Thresholds

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

crc-minor-alarm-threshold
Syntax
Hierarchy Level
Release Information

crc-minor-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5 | 5e-6 | 1e-6);

[edit interfaces interface-name t1-options]

Statement introduced in Junos OS Release 8.5.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.

Description

Minor alarm error thresholds for T1 CRC errors. When the threshold is exceeded for one
second, a defect condition is declared. If the defect condition continues for the monitoring
period, an alarm condition is declared.

Default

10-second monitoring period for values 1e-3, 5e-4, 1e-4, and 5e-5. The 1e-5 value uses a
50-second monitoring period. The 5e-6 value uses a 100-second monitoring period. The
1e-6 value uses a 500-second monitoring period.

Options

1e-3Error rate expressed as the number of errors per number of bits. The value 1e-3 is
3

one crc error in 10 bits.

1e-4Error rate expressed as the number of errors per number of bits. The value 1e-4 is
4

one crc error in 10 bits.

1e-5Error rate expressed as the number of errors per number of bits. The value 1e-5 is
5

one crc error in 10 bits.

1e-6Error rate expressed as the number of errors per number of bits. The value 1e-5 is
6

one crc error in 10 bits.

5e-4Error rate expressed as the number of errors per number of bits. The value 5e-4 is
4

five crc errors in 10 bits.

5e-5Error rate expressed as the number of errors per number of bits. The value 5e-5 is
5

five crc errors in 10 bits.

5e-6Error rate expressed as the number of errors per number of bits. The value 5e-5 is
6

five crc errors in 10 bits.

Default: 5e-6
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring T1 CRC Error Minor Alarm Thresholds

Copyright 2014, Juniper Networks, Inc.

487

Interfaces Fundamentals for Routing Devices

cts
Syntax
Hierarchy Level

Release Information
Description
Options

cts (ignore | normal | require);

[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces only, configure the from-DCE signal, clear-to-send (CTS).
ignoreThe from-DCE signal is ignored.
normalNormal CTS signal handling as defined by the TIA/EIA Standard 530.
requireThe from-DCE signal must be asserted.

Default: normal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

cts-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

cts-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure CTS signal polarity.
positivePositive signal polarity.
negativeNegative signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

488

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

current
Syntax
Hierarchy Level

Release Information

current margin;
[edit interfaces interface-name shdsl-options snr-margin],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options
snr-margin]

Statement introduced in Junos OS Release 7.4.

Description

For J Series Services Routers only, configure the current target signal-to-noise ratio (SNR)
margin to be used when training the SHDSL line. The current margin is the difference
between desired SNR and the actual SNR. When configured, the line trains at higher than
the current margin plus SNR threshold.

Options

marginDesired current SNR margin. Specify either disabled or a value from 0 dB through

10 dB.
Default: 0 dB
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-SHDSL Overview

cycle-time
Syntax
Hierarchy Level

Release Information

Description

Options

cycle-time cycle-time-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]

Statement introduced in Junos OS Release 11.1.

Statement introduced in Junos OS Release 11.4 for EX Series switches.
Configure the time (in milliseconds) taken between back-to-back transmissions of SLA
frames for a single connection.
cycle-time-valueCycle time value in milliseconds.

Range: 10 through 3,600,000

Default: 1000
Required Privilege
Level
Related
Documentation

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

Configuring an Iterator Profile

Configuring an Iterator Profile on a Switch (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

489

Interfaces Fundamentals for Routing Devices

damping (Interfaces)
Syntax

Hierarchy Level

damping {
enable;
half-life seconds;
max-suppress seconds;
reuse number;
suppress number;
}
[edit interfaces on page 368 interface--name],
[edit interfaces on page 368 interface--range]

Release Information

Statement introduced in Junos OS Release 14.1 for PTX Series Packet Transport Routers
and T Series Core Routers.
Statement introduced in Junos OS Release 14.2 for MX960, MX480, MX240, and MX80
3D Universal Edge Routers and M10i Multiservice Edge Routers.

Description

Limit the number of advertisements of the up and down transitions (flapping) on an

interface. Each time a transition occurs, the interface state is changed, which generates
an advertisement to the upper-level routing protocols. Damping helps reduce the number
of these advertisements. Every time an interface goes down, a penalty is added to the
interface penalty counter. If at some point the accumulated penalty exceeds the suppress
level max-suppress, the interface is placed in the suppress state, and further interface
state up and down transitions are not reported to the upper-level protocols.

Options

enableEnable damping on a per-interface basis. If damping is enabled on an interface,

it is suppressed during interface flaps that match the configuration settings.

Default: Disabled
half-life secondsDecay half-life. seconds is the interval after which the accumulated

interface penalty counter is reduced by half if the interface remains stable.

NOTE: For the half-life, configure a value that is less than the max-suppress
value. If you do not, the configuration is rejected.
Range: 1 through 30
Default: 5
max-suppress secondsMaximum hold-down time. seconds is the maximum time that

an interface can be suppressed no matter how unstable the interface has been.

NOTE: For max-suppress, configure a value that is greater than the half-life.
If you do not, the configuration is rejected.
Range: 1 through 20,000

490

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Default: 20
reuse numberReuse threshold. When the accumulated interface penalty counter falls

below number, the interface is no longer suppressed.

Range: 1 through 20,000
Default: 1000
suppress numberCutoff (suppression) threshold. When the accumulated interface

penalty counter exceeds number, the interface is suppressed.

Range: 1 through 20,000
Default: 2000
Required Privilege
Level
Related
Documentation

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

Physical Interface Damping Overview on page 143

Damping Shorter Physical Interface Transitions on page 149

Damping Longer Physical Interface Transitions on page 150

show interfaces extensive on page 1372

hold-time on page 599

Copyright 2014, Juniper Networks, Inc.

491

Interfaces Fundamentals for Routing Devices

data-channel
Syntax

Hierarchy Level
Release Information

Description

data-channel {
vlan number;
}
[edit protocols protection-group ethernet-ring ring-name]

Statement introduced in Junos OS Release 10.2.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.
For Ethernet ring protection, configure a data channel to define a set of VLAN IDs that
belong to a ring instance.
VLANs specified in the data channel use the same topology used by the ERPS PDU in
the control channel. Therefore, if a ring interface is blocked in the control channel, all
traffic in the data channel is also blocked on that interface.

Options
Required Privilege
Level
Related
Documentation

492

vlan numberSpecify (by VLAN ID) one or more VLANs that belong to a ring instance.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Using Ring Instances for Load Balancing

Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series
Routers

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

data-input
Syntax
Hierarchy Level
Release Information
Description

data-input (system | interface interface-name);

[edit interfaces ds-pim/0/port:channel]

Statement introduced in Junos OS Release 8.2.

For interfaces operating on T1/E1 PIMs for J Series Services Routers only, configure whether
an interface should send and receive data from the Routing Engine or from a given
interface name. On channelized T1/E1 interfaces partitioned into channels, you can insert
time slots from one port directly into the other port on the same PIM, to replace time
slots coming through the Routing Engine.
To avoid slips, both ports must use the same clock source: either the routers internal
clock or an external clock on one of the interfaces. If an external clock source is required,
one interface must specify clocking external and the other must specify the same clock
by including the clocking external interface interface-name statement at the [edit interfaces
interface-name] hierarchy level.

Options

systemInterface sends and receives data from the Routing Engine.

interface interface-nameInterface sends and receives data from a specific interface.

Default: Data is sent and received from the Routing Engine (system).
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Channelized T1/E1 Interface to Drop and Insert Time Slots

Junos OS Interfaces and Routing Configuration Guide

clocking on page 469

Copyright 2014, Juniper Networks, Inc.

493

Interfaces Fundamentals for Routing Devices

data-tlv-size
Syntax
Hierarchy Level

Release Information
Description
Options

data-tlv-size size;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-name]

Statement introduced in Junos OS Release 11.1.

Configure the size of the data TLV portion of the Y.1731 data frame.
sizeSize of the data TLV portion of the Y.1731 data frame.

NOTE: This option is applicable only for two-way delay measurement.

Range: 1 through 1400 bytes
Default: 1
Required Privilege
Level
Related
Documentation

494

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

sla-iterator-profile on page 880

Configuring a Remote MEP with an Iterator Profile

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dcd
Syntax
Hierarchy Level

Release Information
Description

Options

dcd (ignore | normal | require);

[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces only, configure the from-DCE signal, data-carrier-detect
(DCD).
ignoreThe from-DCE signal is ignored.
normalNormal DCD signal handling as defined by the TIA/EIA Standard 530.
requireThe from-DCE signal must be asserted.

Default: normal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

dcd-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

dcd-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure DCD signal polarity.
positivePositive signal polarity.
negativeNegative signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

Copyright 2014, Juniper Networks, Inc.

495

Interfaces Fundamentals for Routing Devices

dce
Syntax
Hierarchy Level

Release Information
Description

dce;
[edit interfaces interface-name],
[edit interfaces interface-name serial-options clocking-mode]

Statement introduced before Junos OS Release 7.4.

For Frame Relay only, respond to status enquiry message keepalives.
When you configure the router to be a DCE, keepalives are disabled by default.

Default
Required Privilege
Level
Related
Documentation

The router operates in DTE mode.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the Router as a DCE with Frame Relay Encapsulation on page 138

dce-options
Syntax

Hierarchy Level
Release Information

Description

dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
[edit interfaces interface-name serial-options]

Statement introduced in Junos OS Release 8.3.

Statement previously known as control-leads.
For J Series Services Routers, configure the serial interface signal characteristics.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

496

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

deactivation-delay
Syntax
Hierarchy Level
Release Information
Description

Options

deactivation-delay seconds;
[edit interfaces dln unit logical-unit-number dialer-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers with ISDN interfaces, configure the ISDN deactivation delay.
Used only for dialer backup and dialer watch cases.
secondsInterval before the backup interface is deactivated after the primary interface

has comes up.

Range: 1 through 4,294,967,295 seconds
Default: 0 (zero)
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Logical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

default-actions
Syntax

Hierarchy Level
Release Information
Description
Default
Options

default-actions {
interface-down;
}
[edit protocols oam ethernet connectivity-fault-management action-profile profile-name]

Statement introduced in Junos OS Release 8.4.

Define the action to be taken when connectivity to the remote MEP is lost.
If no action is configured, no action is taken.
interface-downWhen a remote MEP connectivity failure is detected, bring the interface

down.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Connectivity Fault Management Action Profile

Copyright 2014, Juniper Networks, Inc.

497

Interfaces Fundamentals for Routing Devices

default-chap-secret
Syntax
Hierarchy Level

Release Information
Description

default-chap-secret name;
[edit interfaces interface-name ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options chap]

Statement introduced in Junos OS Release 8.0.

Define the default CHAP secret to be used when no matching CHAP access profile exists.
For ATM2 IQ interfaces only, you can configure a default CHAP secret on the logical
interface unit if the logical interface is configured with one of the following PPP over ATM
encapsulation types:

Default

Required Privilege
Level
Related
Documentation

atm-ppp-llcPPP over AAL5 LLC encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

If you do not include the default-chap-secret statement in the configuration, and an

interface receives a CHAP challenge or response from a peer that is not in the applied
access profile, the link is immediately dropped.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring a Default CHAP Secret on page 128

access-profile on page 402

default-pap-password
Syntax
Hierarchy Level

Release Information
Description
Required Privilege
Level
Related
Documentation

498

default-pap-password password;
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options pap]

Statement introduced in Junos OS Release 8.3.

For PAP authentication, the default PAP password.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring a Default PAP Password on page 179

access-profile on page 402

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

delimiter
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

delimiter delimiter-character;
[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include]

Statement introduced in Junos OS Release 10.0.

Specify the character used as the delimiter between the concatenated components of
the username. You cannot use the semicolon (;) as a delimiter.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

demux-destination (Underlying Interface)

Syntax
Hierarchy Level

Release Information

Description

demux-destination family;
[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]

Statement introduced in Junos OS Release 9.0.

Support for aggregated Ethernet added in Junos OS Release 9.4.
Configure the logical demultiplexing (demux) destination 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.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Copyright 2014, Juniper Networks, Inc.

499

Interfaces Fundamentals for Routing Devices

demux-destination (Demux Interface)

Syntax

Hierarchy Level

Release Information

Description

Required Privilege
Level
Related
Documentation

demux-destination {
destination-prefix;
}
[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],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
interface-name unit logical-unit-number family family]

Statement introduced in Junos OS Release 9.0.

Support for aggregated Ethernet added in Junos OS Release 9.4.
Configure one or more logical demultiplexing (demux) destination prefixes. The prefixes
are matched against the destination address of packets that the underlying interface
receives. When a match occurs, the packet is processed as if it was received on the demux
interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

demux-options (Static Interface)

Syntax

Hierarchy Level

Release Information
Description

demuxoptions {
underlying-interface interface-name
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 9.0.

Configure logical demultiplexing (demux) interface options.
The statement is explained separately.

Required Privilege
Level
Related
Documentation

500

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

demux-source (Demux Interface)

Syntax

Hierarchy Level

Release Information

Description

Required Privilege
Level
Related
Documentation

demux-source {
source-prefix;
}
[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],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
interface-name unit logical-unit-number family family]

Statement introduced in Junos OS Release 9.0.

Support for aggregated Ethernet added in Junos OS Release 9.4.
Configure one or more logical demultiplexing (demux) source prefixes. The prefixes are
matched against the source address of packets that the underlying interface receives.
When a match occurs, the packet is processed as if it was received on the demux interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Copyright 2014, Juniper Networks, Inc.

501

Interfaces Fundamentals for Routing Devices

demux-source (Underlying Interface)

Syntax
Hierarchy Level

Release Information

Description

demux-source family;
[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],

Statement introduced in Junos OS Release 9.0.

Support for aggregated Ethernet added in Junos OS Release 9.4.
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.

Required Privilege
Level
Related
Documentation

502

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

demux0 (Static Interface)

Syntax

Hierarchy Level

Release Information
Description

demux0 {
unit logical-unit-number {
demux-options {
underlying-interface interface-name
}
family family {
access-concentrator name;
{
destination-prefix;
}
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
{
source-prefix;
}
max-sessions number;
service-name-table table-name
targeted-distribution;
unnumbered-address interface-name <preferred-source-address address>;
}
vlan-id number;
vlan-tags outer [tpid].vlan-id [inner [tpid].vlan-id];
}
}
[edit interfaces],
[edit logical-systems logical-system-name interfaces]

Statement introduced in Junos OS Release 9.0.

Configure the logical demultiplexing (demux) interface.
Logical IP demux interfaces do not support IPv4 and IPv6 dual stack.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Copyright 2014, Juniper Networks, Inc.

503

Interfaces Fundamentals for Routing Devices

demux0 (Dynamic Interface)

Syntax

Hierarchy Level
Release Information
Description

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;
}
}
[edit dynamic-profiles profile-name interfaces]

Statement introduced in Junos OS Release 9.3.

Configure the logical demultiplexing (demux) interface in a dynamic profile.
Logical IP demux interfaces do not support IPv4 and IPv6 dual stack.
The remaining statements are explained separately.

Required Privilege
Level

504

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Related
Documentation

Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles

Demultiplexing Interface Overview on page 281

description (Interfaces)
Syntax

description text;

Hierarchy Level

[edit interfaces interface-name],

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

Provide a textual description of the interface or the logical unit. Any descriptive text you
include is displayed in the output of the show interfaces commands, and is also exposed
in the ifAlias Management Information Base (MIB) object. It has no effect on the operation
of the interface on the router or switch.
The textual description can also be included in the extended DHCP relay option 82 Agent
Circuit ID suboption.

Options

textText to describe the interface. If the text includes spaces, enclose the entire text

in quotation marks.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Interface Description on page 92

Adding a Logical Unit Description to the Configuration on page 171

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit and 10-Gigabit Ethernet Interfaces

Using DHCP Relay Agent Option 82 Information

Junos OS Network Interfaces Library for Routing Devices

Example: Connecting Access Switches to a Distribution Switch

Copyright 2014, Juniper Networks, Inc.

505

Interfaces Fundamentals for Routing Devices

destination (IPCP)
Syntax
Hierarchy Level

Release Information
Description

Options

destination address destination-profile profile-name;

[edit interfaces interface-name unit logical-unit-number family inet unnumbered-address
interface-name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet unnumbered-address interface-name]

Statement introduced before Junos OS Release 7.4.

For unnumbered interfaces with PPP encapsulation, specify the IP address of the remote
interface.
addressIP address of the remote interface.

The remaining statement is explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring IPCP Options on page 200

address on page 412

negotiate-address on page 734

Junos OS Administration Library for Routing Devices

destination (Routing Instance)

Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

506

destination routing-instance-name;
[edit interfaces interface-name unit logical-unit-number tunnel routing-instance],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel routing-instance]

Statement introduced before Junos OS Release 7.4.

Specify the destination routing instance that points to the routing table containing the
tunnel destination address.
The default Internet routing table inet.0.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

destination (Tunnels)
Syntax
Hierarchy Level

Release Information

Description

Options
Required Privilege
Level
Related
Documentation

destination address;
[edit interfaces interface-name unit logical-unit-number family inet address address],
[edit interfaces interface-name unit logical-unit-number family inet unnumbered-address
interface-name],
[edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet unnumbered-address interface-name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for the QFX Series.
For encrypted, PPP-encapsulated, and tunnel interfaces, specify the remote address of
the connection.
addressAddress of the remote side of the connection.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Interface Address on page 192

Configuring Generic Routing Encapsulation Tunneling (CLI Procedure)

Junos OS Services Interfaces Library for Routing Devices

point-to-point on page 795

Copyright 2014, Juniper Networks, Inc.

507

Interfaces Fundamentals for Routing Devices

destination-class-usage
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

destination-class-usage;
[edit interfaces interface-name unit logical-unit-number family inet accounting],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet accounting]

Statement introduced before Junos OS Release 7.4.

Enable packet counters on an interface that count packets that arrive from specific
customers and are destined for specific prefixes on the provider core router.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling Source Class and Destination Class Usage on page 242

accounting on page 403

source-class-usage on page 888

destination-profile
Syntax
Hierarchy Level

Release Information

[edit interfaces interface-name unit logical-unit-number family inet address address],

[edit interfaces interface-name unit logical-unit-number family inet unnumbered-address
interface-name destination address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet unnumbered-address interface-name destination address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.

Description

For interfaces with PPP encapsulation, assign PPP properties to the remote destination
end. You define the profile at the [edit access group-profile name ppp] hierarchy level.

Options

nameProfile name defined at the [edit access group-profile name ppp] hierarchy level.

Required Privilege
Level
Related
Documentation

508

destination-profile name;

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring IPCP Options on page 200

destination (IPCP) on page 506

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dial-options
Syntax

Hierarchy Level

Release Information

Description

Options

dial-options {
ipsec-interface-id name;
l2tp-interface-id name;
(shared | dedicated);
}
[edit interfaces sp-fpc/pic/port unit logical-unit-number],
[edit interfaces si-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces sp-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces si-fpc/pic/port unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

The [edit ...si-...] hierarchy levels introduced in Junos OS Release 11.4.
Specify the options for configuring logical interfaces for group and user sessions in L2TP
or IPsec dynamic endpoint tunneling.
dedicated(LNS on M Series routers and MX Series routers only) Specify that a logical

interface can host only one session at a time.

ipsec-interface-id name(M Series routers only) Interface identifier for group of dynamic

peers. This identifier must be replicated at the [edit access profile name client * ike]
hierarchy level.
l2tp-interface-id nameInterface identifier that must be replicated at the [edit access
profile name] hierarchy level.
shared(LNS on M Series routers only) Specify that a logical interface can host multiple

(shared) sessions at a time.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Identifier for Logical Interfaces that Provide L2TP Services

Configuring Dynamic Endpoints for IPsec Tunnels

Configuring Options for the LNS Inline Services Logical Interface

Copyright 2014, Juniper Networks, Inc.

509

Interfaces Fundamentals for Routing Devices

dial-string
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

dial-string [ dial-string-numbers ];
[edit interfaces br-pim/0/port unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces br-pim/0/port unit logical-unit-number
dialer-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers with ISDN interfaces, specify one or more ISDN dial strings
used to reach a destination subnetwork.
dial-string-numbersOne or more strings of numbers to call.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Dialer Interface

dialer
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

510

dialer filter-name;
[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]

Statement introduced before Junos OS Release 7.4.

Apply a dialer filter to an interface. To create the dialer filter, include the dialer-filter
statement at the [edit firewall filter family family] hierarchy level.
filter-nameDialer filter name.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying the Dial-on-Demand Dialer Filter to the Dialer Interfaces

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dialer-options
Syntax

Hierarchy Level

Release Information
Description

dialer-options {
activation-delay seconds;
callback;
callback-wait-period time;
deactivation-delay seconds;
dial-string [ dial-string-numbers ];
idle-timeout seconds;
incoming-map {
caller caller-number | accept-all;
initial-route-check seconds;
load-interval seconds;
load-threshold percent;
pool pool-name;
redial-delay time;
watch-list {
[ routes ];
}
}
}
[edit interfaces umd0],
[edit interfaces dln unit logical-unit-number],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Specify the dialer options for configuring logical interfaces for group and user sessions.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Logical Interface Properties

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

511

Interfaces Fundamentals for Routing Devices

dialin
Syntax
Hierarchy Level
Release Information

dialin (console | routable);

[edit interfaces umd0 modem-options]

Statement introduced in Junos OS Release 8.5.

Description

For J Series Services Routers, configure a USB modem port to act as a dial-in console or
WAN backup port.

Options

consoleConfigure the USB modem port to operate as a dial-in console for management.
routableConfigure the USB modem port to operate as a dial-in WAN backup interface.

Default: console
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying a USB Modem Interface on J Series Routers on page 316

direction
Syntax
Hierarchy Level

Release Information
Description
Options

direction (up | down);

[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id]

Statement introduced in Junos OS Release 8.4.

Configure the direction of the MEP.
upAn UP MEP CCM is transmitted out of every logical interface which is part of the

same bridging or vpls instance except for the interface configured on this MEP.

NOTE: The up direction for MEP is not supported on T Series routers.

downDown MEP CCMs are transmitted only out the interface configured on this MEP.

Required Privilege
Level
Related
Documentation

512

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Maintenance Endpoint

IEEE 802.1ag OAM Connectivity Fault Management Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

disable (Interface)
Syntax

disable;

Hierarchy Level

[edit interfaces interface-name],

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

Disable a physical or a logical interface, effectively unconfiguring it.

CAUTION:

Dynamic subscribers and logical interfaces use physical interfaces for

connection to the network. The Junos OS allows you to set the interface
to disable and commit the change while dynamic subscribers and logical
interfaces are still active. This action results in the loss of all subscriber
connections on the interface. Use care when disabling interfaces.

If aggregated SONET links are configured between a T1600 router and a

T4000 router, interface traffic is disrupted when you disable the physical
interface configured on the T1600 router. If you want to remove the
interface, we recommend that you deactivate the interface instead of
disabling it.

NOTE:

When you use the disable statement at the [edit interfaces] hierarchy level,
depending on the PIC type, the interface might or might not turn off the
laser. Older PIC transceivers do not support turning off the laser, but newer
Gigabit Ethernet (GE) PICs with SFP and XFP transceivers and ATM MIC
with SFP do support it and the laser will be turned off when the interface
is disabled. If the ATM MIC with SFP is part of an APS group, then the laser
will not be turned off when you use the disable statement at the [edit
interfaces] hierarchy level..

When you disable or deactivate an interface, then all the references made
to the deactivated interface must be removed from the routing instance.

WARNING: Do not stare into the laser beam or view it directly with optical
instruments even if the interface has been disabled.

Copyright 2014, Juniper Networks, Inc.

513

Interfaces Fundamentals for Routing Devices

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Disabling a Physical Interface on page 156

Disabling a Logical Interface on page 184

disable (Link Protection)

Syntax
Hierarchy Level
Release Information

Description
Required Privilege
Level
Related
Documentation

disable;
[edit interfaces aeX aggregated-ether-options lacp link-protection]

Statement introduced in Junos OS Release 9.3.

Statement introduced in Junos OS Release 11.4 for EX Series switches.
Disable LACP link protection on the interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring LACP for Aggregated Ethernet Interfaces

Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure)

disable-mlppp-inner-ppp-pfc
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

514

disable-mlppp-inner-ppp-pfc;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 8.2.

For MLPPP interfaces only, disable compression of the inner PPP header in the MLPPP
payload. By default, compression is enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dlci
Syntax
Hierarchy Level

Release Information
Description

dlci dlci-identifier;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For Frame Relay and Multilink Frame Relay (MLFR) user-to-network interface (UNI)
network-to-network interface (NNI) encapsulation only, and for link services, voice
services and point-to-point interfaces only, configure the data-link connection identifier
(DLCI) for a permanent virtual circuit (PVC) or an switched virtual circuit (SVC).
To configure a DLCI for a point-to-multipoint interface, use the multipoint-destination
statement to specify the DLCI.

Options

dlci-identifierData-link connection identifier.

Range: 16 through 1022.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Data-Link Connection Identifiers on Channelized Interfaces

Configuring Frame Relay DLCIs

Junos OS Services Interfaces Library for Routing Devices

encapsulation (Logical Interface) on page 543

multicast-dlci on page 720

multipoint-destination on page 724

Copyright 2014, Juniper Networks, Inc.

515

Interfaces Fundamentals for Routing Devices

do-not-fragment
Syntax
Hierarchy Level

Release Information
Description
Default
Required Privilege
Level
Related
Documentation

do-not-fragment;
[edit interfaces gr-fpc/pic/port unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number
tunnel]

Statement introduced in Junos OS Release 9.2.

Disable fragmentation of GRE encapsulated packets.
By default fragmentation is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

reassemble-packets on page 836

domain-name
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

516

domain-name domain-name-string;
[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include]

Statement introduced in Junos OS Release 10.0.

Specify the domain name that is concatenated with the username during the subscriber
authentication process.
domain-name-stringThe domain name formatted string.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dot1x
Syntax

Hierarchy Level
Release Information
Description

dot1x {
authenticator {
authentication-profile-name access-profile-name;
interface interface-id {
maximum-requests integer;
quiet-period seconds;
reauthentication (disable | interval seconds);
retries integer;
server-timeout seconds;
supplicant (single);
supplicant-timeout seconds;
transmit-period seconds;
}
}
}
[edit protocols]

Statement introduced in Junos OS Release 9.3.

For the MX Series only, specifies settings for using 802.1x Port-Based Network Access
Control.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

authentication-profile-name on page 431

interface (IEEE 802.1x) on page 629

Copyright 2014, Juniper Networks, Inc.

517

Interfaces Fundamentals for Routing Devices

down-count
Syntax
Hierarchy Level

Release Information
Description

down-count cells;
[edit interfaces interface-name atm-options vpi vpi-identifier oam-liveness],
[edit interfaces interface-name unit logical-unit-number oam-liveness],
[edit interfaces interface-name unit logical-unit-number family family address address
multipoint-destination address oam-liveness],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
oam-liveness],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address multipoint-destination address oam-liveness]

Statement introduced before Junos OS Release 7.4.

For ATM encapsulation only, configure Operation, Administration, and Maintenance
(OAM) F5 loopback cell count thresholds. This feature is not supported on
ATM-over-SHDSL interfaces.
For ATM2 IQ PICs only, configure OAM F4 loopback cell count thresholds at the [edit
interfaces interface-name atm-options vpi vpi-identifier] hierarchy level.

Options

cellsMinimum number of consecutive OAM F4 or F5 loopback cells lost before a VC is

declared down.
Range: 1 through 255
Default: 5 cells
Required Privilege
Level
Related
Documentation

518

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the ATM OAM F5 Loopback Cell Threshold

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

drop (PPPoE Service Name Tables)

Syntax

drop;

Hierarchy Level

[edit protocols pppoe service-name-tables table-name service service-name],

[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]

Release Information

Statement introduced in Junos OS Release 10.0.

Support at [edit protocols pppoe service-name-tables table-name service service-name
agent-specifier aci circuit-id-string ari remote-id-string] hierarchy level introduced in Junos
OS Release 10.2.

Description

Direct the router to drop (ignore) a PPPoE Active Discovery Initiation (PADI) control
packet received from a PPPoE client that contains the specified service name tag or
agent circuit identifier/agent remote identifier (ACI/ARI) information. This action
effectively denies the clients request to provide the specified service, or to accept requests
from the subscriber or subscribers represented by the ACI/ARI information.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

drop-timeout
Syntax
Hierarchy Level

Release Information
Description

Options

drop-timeout milliseconds;
[edit interfaces interface-name mlfr-uni-nni-bundle-options],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For link services, multilink, and voice services interfaces only, configure the drop timeout
period, in milliseconds.
millisecondsDrop timeout period.

Range: 0 through 2000 milliseconds

Default: 0 ms (disabled)
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

519

Interfaces Fundamentals for Routing Devices

ds0-options
Syntax

Hierarchy Level
Release Information
Description

ds0-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
byte-encoding (nx56 | nx64);
fcs (16 | 32);
idle-cycle-flag (flags | ones);
invert-data;
loopback payload;
start-end-flag (filler | shared);
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Configure DS0-specific physical interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Channelized DS3-to-DS0 Interfaces

dsl-options
Syntax

Hierarchy Level
Release Information
Description

dsl-options {
loopback local;
operating-mode mode;
}
[edit interfaces at-fpc/pic/port]

Statement introduced before Junos OS Release 7.4.

For J Series Services Routers only, modify the properties of the digital subscriber line for
an ATM interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

520

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-ADSL Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dsr
Syntax
Hierarchy Level

Release Information
Description

Options

dsr (ignore | normal | require);

[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces only, configure the from-DCE signal, data-set-ready
(DSR).
ignoreThe from-DCE signal is ignored.
normalNormal DSR signal handling as defined by the TIA/EIA Standard 530.
requireThe from-DCE signal must be asserted.

Default: normal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

dsr-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

dsr-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure DSR signal polarity.
positivePositive signal polarity.
negativeNegative signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

Copyright 2014, Juniper Networks, Inc.

521

Interfaces Fundamentals for Routing Devices

dte-options
Syntax

Hierarchy Level
Release Information

Description

dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
[edit interfaces interface-name serial-options]

Statement introduced in Junos OS Release 8.3.

Statement previously known as control-leads.
For M Series and T Series routers, configure the serial interface signal characteristics.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

522

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dtr
Syntax
Hierarchy Level

Release Information
Description

Options

dtr signal-handling-option;
[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces only, configure the to-DCE signal, data-transmit-ready
(DTR).
signal-handling-optionSignal handling for the DTR signal. The signal handling can be

one of the following:

assertThe to-DCE signal must be asserted.
auto-synchronizeNormal DTR signal with automatic synchronization. This statement

has two substatements:

duration millisecondsPulse duration of resynchronization.

Range: 1 through 1000 milliseconds

Default: 1000 milliseconds
interval secondsOffset interval for resynchronization.

Range: 1 through 31 seconds

Default: 15 seconds
de-assertThe to-DCE signal must be deasserted.
normalNormal DTR signal handling as defined by the TIA/EIA Standard 530.

Default: normal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

Copyright 2014, Juniper Networks, Inc.

523

Interfaces Fundamentals for Routing Devices

dtr-circuit
Syntax
Hierarchy Level
Release Information
Description
Options

dtr-circuit (balanced | unbalanced);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces only, configure a DTR circuit.
balancedBalanced DTR signal.
unbalancedUnbalanced DTR signal.

Default: balanced
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial DTR Circuit on page 313

dtr-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

dtr-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure DTR signal polarity.
positivePositive signal polarity.
negativeNegative signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

524

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dump-on-flow-control
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

dump-on-flow-control;
[edit interfaces interface-name multiservice-options]

Statement introduced in Junos OS Release 9.5.

This option supports high availability functionality and can be used with various service
interfaces, including rsp, rms, lsq, and rlsq.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Multiservice Physical Interface Properties on page 153

Junos OS Services Interfaces Library for Routing Devices

passive-monitor-mode on page 782

Copyright 2014, Juniper Networks, Inc.

525

Interfaces Fundamentals for Routing Devices

dynamic-call-admission-control
Syntax

Hierarchy Level

Release Information
Description

dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 8.2.

(J4350 and J6350 Services Routers supporting voice over IP with the TGM550 media
gateway module) For Fast Ethernet and Gigabit Ethernet interfaces, ISDN BRI interfaces,
and serial interfaces with PPP or Frame Relay encapsulation, configure dynamic call
admission control (CAC). Dynamic CAC provides enhanced control over WAN bandwidth.
When dynamic CAC is configured on an interface responsible for providing call bandwidth,
the TGM550 informs the Media Gateway Controller (MGC) of the bandwidth limit
available for voice packets on the interface and requests the MGC to block new calls
when the bandwidth is exhausted.
Dynamic CAC must be configured on each Services Router interface responsible for
providing call bandwidth.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

526

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dynamic Call Admission Control on page 181

Junos OS Services Interfaces Library for Routing Devices

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dynamic-profile (PPP)
Syntax
Hierarchy Level
Release Information

Description

Required Privilege
Level
Related
Documentation

dynamic-profile profile-name;
[edit interfaces interface-name unit logical-unit-number ppp-options]

Statement introduced in Junos OS Release 9.5.

Support for MLPPP on LSQ interfaces introduced in Junos OS Release 10.2.
Specify the dynamic profile that is attached to the interface. On the MX Series routers,
this statement is currently supported on PPPoE interfaces only. On the M120 and M320
routers, this statement is supported for MLPPP bundles only on LSQ interfaces on
Adaptive Services PICs and Multiservices PICs.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Dynamic Profiles Overview

Configuring a Basic Dynamic Profile

Attaching Dynamic Profiles to Static PPP Subscriber Interfaces

Attaching Dynamic Profiles to MLPPP Bundles

For hardware requirements, see Hardware Requirements for PPP Subscriber Services
on Non-Ethernet Interfaces

Copyright 2014, Juniper Networks, Inc.

527

Interfaces Fundamentals for Routing Devices

dynamic-profile (PPPoE Service Name Tables)

Syntax
Hierarchy Level

Release Information
Description

dynamic-profile profile-name;
[edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]

Statement introduced in Junos OS Release 10.2.

Specify a dynamic profile to instantiate a dynamic PPPoE interface. You can associate
a dynamic profile with a named service entry, empty service entry, or any service entry
configured in a PPPoE service name table, or with an agent circuit identifier/agent remote
identifier (ACI/ARI) pair defined for these services.
The dynamic profile associated with a service entry in a PPPoE service name table
overrides the dynamic profile associated with the PPPoE underlying interface on which
the dynamic PPPoE interface is created.
If you include the dynamic-profile statement at the [edit protocols pppoe
service-name-tables table-name service service-name agent-specifier aci circuit-id-string
ari remote-id-string] hierarchy level, you cannot also include the static-interface statement

at this level. The dynamic-profile and static-interface statements are mutually exclusive
for ACI/ARI pair configurations.
Options

profile-nameName of the dynamic profile that the router uses to instantiate a dynamic

PPPoE interface.
Required Privilege
Level
Related
Documentation

528

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for
Dynamic PPPoE Interface Creation

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dynamic-profile (Stacked VLAN)

Syntax

Hierarchy Level
Release Information
Description
Options

dynamic-profile profile-name {
accept (any | dhcp-v4 |dhcp-v6| inet | inet6 | pppoe);
ranges (any | low-taghigh-tag) ,(any | low-taghigh-tag);
}
[edit interfaces interface-name auto-configure stacked-vlan-ranges]

Statement introduced in Junos OS Release 9.5.

Configure a dynamic profile for use when configuring dynamic stacked VLANs.
profile-nameName of the dynamic profile that you want to use when configuring dynamic

stacked VLANs.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Dynamic Profiles Overview

Configuring a Basic Dynamic Profile

Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs

Copyright 2014, Juniper Networks, Inc.

529

Interfaces Fundamentals for Routing Devices

dynamic-profile (VLAN)
Syntax

Hierarchy Level
Release Information
Description
Options

dynamic-profile profile-name {
accept (any | dhcp-v4 |dhcp-v6| inet | inet6 | pppoe);
ranges (any | low-tag)(any | high-tag);
}
[edit interfaces interface-name auto-configure vlan-ranges]

Statement introduced in Junos OS Release 9.5.

Configure a dynamic profile for use when configuring dynamic VLANs.
profile-nameName of the dynamic profile that you want to use when configuring dynamic

VLANs.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

530

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Dynamic Profiles Overview

Configuring a Basic Dynamic Profile

Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag

VLANs

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

dynamic-profiles
Syntax

dynamic-profiles {
profile-name {
class-of-service {
interfaces {
interface-name ;
}
unit logical-unit-number {
classifiers {
type (classifier-name | default);
}
output-traffic-control-profile (profile-name | $junos-cos-traffic-control-profile);
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 {
forwarding-class class-name scheduler scheduler-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>;
priority priority-level;
shaping-rate (rate | predefined-variable);
transmit-rate (percent percentage | rate | remainder) <exact | rate-limit>;
}
}
traffic-control-profiles profile-name {
delay-buffer-rate (percent percentage | rate | $junos-cos-delay-buffer-rate);
excess-rate (percent percentage | proportion value | percent $junos-cos-excess-rate);
guaranteed-rate (percent percentage | rate | $junos-cos-guaranteed-rate);
overhead-accounting (shaping-mode) <bytes (byte-value>;
scheduler-map map-name;
shaping-rate (rate | predefined-variable);
}
}
firewall {
family family {
fast-update-filter filter-name {
interface-specific;
match-order [match-order];

Copyright 2014, Juniper Networks, Inc.

531

Interfaces Fundamentals for Routing Devices

term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
only-at-create;
}
}
filter uid {
enhanced-mode-override;
interface-shared;
interface-specific;
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
}
}
}
policer uid {
filter-specific;
if-exceeding {
(bandwidth-limit bps | bandwidth-percent percentage);
burst-size-limit bytes;
}
logical-bandwidth-policer;
logical-interface-policer;
physical-interface-policer;
then {
policer-action;
}
}
hierarchical-policer uid {
aggregate {
if-exceeding {
bandwidth-limit-limit bps;
burst-size-limit bytes;
}
then {
policer-action;
}
}
premium {
if-exceeding {
bandwidth-limit bps;
burst-size-limit bytes;
}
then {
policer-action;

532

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

}
}
}
three-color-policer uid {
action {
loss-priority high then discard;
}
logical-interface-policer;
single-rate {
(color-aware | color-blind);
committed-burst-size bytes;
committed-information-rate bps;
excess-burst-size bytes;
}
two-rate {
(color-aware | color-blind);
committed-burst-size bytes;
committed-information-rate bps;
peak-burst-size bytes;
peak-information-rate bps;
}
}
}
}
policy-options {
prefix-list uid {
ip-addresses;
dynamic-db;
}
}
interfaces interface-name {
interface-set interface-set-name {
interface interface-name {
unit logical unit number {
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
}
}
}
unit logical-unit-number {
auto-configure {
agent-circuit-identifier {
dynamic-profile profile-name;
}
}
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 {

Copyright 2014, Juniper Networks, Inc.

533

Interfaces Fundamentals for Routing Devices

address address;
filter {
adf {
counter;
input-precedence precedence;
not-mandatory;
output-precedence precedence;
rule rule-value;
}
input filter-name (
precedence precedence;
}
output filter-name {
precedence precedence;
}
}
rpf-check {
fail-filter filter-name;
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 {
service-set service-set-name {
service-filter filter-name;
}
}
output-vlan-map {
inner-tag-protocol-id tpid;
inner-vlan-id number;
(pop | swap);
tag-protocol-id tpid;
vlan-id number;
}
}
unnumbered-address interface-name <preferred-source-address address>;
}
ppp-options {
chap;
pap;
}
vlan-id number;
vlan-tags outer [tpid].vlan-id [inner [tpid].vlan-id];
}

534

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

}
interfaces {
demux0 {...}
}
interfaces {
pp0 {...}
}
protocols {
igmp {
interface interface-name {
accounting;
disable;
group-policy;
immediate-leave
no-accounting;
promiscuous-mode;
ssm-map ssm-map-name;
static {
group group {
source source;
}
}
version version;
}
mld {
interfaceinterface-name {
disable;
(accounting | no-accounting);
group-policy;
immediate-leave;
oif-map;
passive;
ssm-map ssm-map-name;
static {
group multicast-group-address {
exclude;
group-count number;
group-increment increment;
source ip-address {
source-count number;
source-increment increment;
}
}
}
version version;
}
}
router-advertisement {
interface interface-name {
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;

Copyright 2014, Juniper Networks, Inc.

535

Interfaces Fundamentals for Routing Devices

reachable-time milliseconds;
retransmit-timer milliseconds;
}
}
}
}
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;
}
}
access-internal {
route subscriber-ip-address {
qualified-next-hop underlying-interface {
mac-address address;
}
}
}
multicast {
interface interface-name {
no-qos-adjust;
}
}
}
rib routing-table-name {
access {
route prefix {
next-hop next-hop;
metric route-cost;
preference route-distance;
tag route-tag;
}
}
access-internal {
route subscriber-ip-address {
qualified-next-hop underlying-interface {
mac-address address;
}
}
}
}
}
routing-options {
access {
route prefix {
next-hop next-hop;
metric route-cost;
preference route-distance;
tag route-tag;
}

536

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

}
access-internal {
route subscriber-ip-address {
qualified-next-hop underlying-interface {
mac-address address;
}
}
}
multicast {
interface interface-name {
no-qos-adjust;
}
}
}
variables {
variable-name {
default-value default-value;
equals expression;
mandatory;
uid;
uid-reference;
}
}
}
}

Hierarchy Level
Release Information

Description
Options

[edit]

Statement introduced in Junos OS Release 9.2.

Support at the filter, policer, hierarchical-policer, three-color-policer, and policy options
hierarchy levels introduced in Junos OS Release 11.4.
Create dynamic profiles for use with DHCP or PPP client access.
profile-nameName of the dynamic profile; string of up to 80 alphanumeric characters.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

Configuring a Basic Dynamic Profile

Configuring Dynamic VLANs Based on Agent Circuit Identifier Information

Dynamic Profiles Overview

Copyright 2014, Juniper Networks, Inc.

537

Interfaces Fundamentals for Routing Devices

e1-options
Syntax

Hierarchy Level
Release Information

Description

e1-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
fcs (16 | 32);
framing (g704 | g704-no-crc4 | unframed);
idle-cycle-flag (flags | ones);
invert-data;
loopback (local | remote);
start-end-flag (filler | shared);
timeslots time-slot-range;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure E1-specific physical interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

538

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Channelized E1 IQ and IQE Interfaces Overview

Channelized STM1 Interfaces Overview

E1 Interfaces Overview

T1 Interfaces Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

e3-options
Syntax

Hierarchy Level

e3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout feet;
compatibility-mode (digital-link | kentrox | larscom) <subrate value>;
fcs (16 | 32);
framing (g.751 | g.832);
idle-cycle-flag value;
invert-data;
loopback (local | remote);
(payload-scrambler | no-payload-scrambler);
start-end-flag value;
(unframed | no-unframed);
}
[edit interfaces interface-name]

Release Information

Statement introduced before Junos OS Release 7.4.

Description

Configure E3-specific physical interface properties.

For ATM1 interfaces, you can configure a subset of E3 options statements.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

E3 Interfaces Overview

T3 Interfaces Overview

atm-options on page 428

Copyright 2014, Juniper Networks, Inc.

539

Interfaces Fundamentals for Routing Devices

east-interface
Syntax

Hierarchy Level
Release Information

Description

east-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
}
[edit protocols protection-group ethernet-ring ring-name]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.
Define one of the two interface ports for Ethernet ring protection, the other being defined
by the west-interface statement at the same hierarchy level. The interface must use the
control channel's logical interface name. The control channel is a dedicated VLAN channel
for the ring port.
EX Series switches do not use the node-id statement--the node ID is automatically
configured on the switches using the MAC address.

NOTE: Always configure this port first, before configuring the west-interface
statement.

NOTE: The Node ID is not configurable on EX Series switches. The node ID

is automatically configured using the MAC address.

The statements are explained separately.

Required Privilege
Level
Related
Documentation

540

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Ethernet Ring Protection Using Ring Instances for Load Balancing

west-interface on page 990

ethernet-ring on page 558

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

egress-policer-overhead
Syntax
Hierarchy Level
Release Information
Description

egress-policer-overhead bytes;
[edit chassis fpc slot-number pic pic-number]

Statement introduced before Junos OS Release 11.1.

Add the specified number of bytes to the actual length of an Ethernet frame when
determining the actions of Layer 2 policers, MAC policers, or queue rate limits applied to
output traffic on the line card. You can configure egress policer overhead to account for
egress shaping overhead bytes added to output traffic on the line card.
On M Series and T Series routers, this statement is supported on Gigabit Ethernet
Intelligent Queuing 2 (IQ2) PICs and Enhanced IQ2 (IQ2E) PICs. On MX Series routers,
this statement is supported for interfaces configured on Dense Port Concentrators (DPCs).

NOTE: This statement is not supported on Modular Interface Cards (MICs)

or Modular Port Concentrators (MPCs) in MX Series routers.

Options

bytesNumber of bytes added to a packet exiting an interface.

Range: 0255 bytes

Default: 0
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

egress-shaping-overhead

Policer Overhead to Account for Rate Shaping Overview

Example: Configuring Policer Overhead to Account for Rate Shaping

Configuring a Policer Overhead

CoS on Enhanced IQ2 PICs Overview

Copyright 2014, Juniper Networks, Inc.

541

Interfaces Fundamentals for Routing Devices

encapsulation (Container Interface)

Syntax
Hierarchy Level
Release Information
Description
Options

encapsulation (cisco-hdlc | ppp);

[edit interfaces cin]

Statement introduced in Junos OS Release 9.2.

Container link-layer encapsulation type.
cisco-hdlcUse Cisco-compatible High-Level Data Link Control (HDLC) framing.
pppUse serial PPP encapsulation.

Required Privilege
Level
Related
Documentation

542

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Displaying APS Using a Container Interface with ATM Encapsulation

Configuring Container Interfaces for APS on SONET Links

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

encapsulation (Logical Interface)

Syntax

encapsulation (atm-ccc-cell-relay | atm-ccc-vc-mux | atm-cisco-nlpid | atm-mlppp-llc |

atm-nlpid | atm-ppp-llc | atm-ppp-vc-mux | atm-snap | atm-tcc-snap | atm-tcc-vc-mux
| atm-vc-mux | ether-over-atm-llc | ether-vpls-over-atm-llc | ether-vpls-over-fr |
ether-vpls-over-ppp | ethernet | ethernet-ccc | ethernet-vpls | ethernet-vpls-fr |
frame-relay-ccc | frame-relay-ether-type | frame-relay-ether-type-tcc | frame-relay-ppp
| frame-relay-tcc | gre-fragmentation | 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);

Hierarchy Level

[edit interfaces interface-name unit logical-unit-number],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit interfaces rlsq number unit logical-unit-number]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers (ethernet,vlan-ccc, and vlan-tcc options only).
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers. Only the atm-ccc-cell-relay and atm-ccc-vc-mux options are supported on ACX
Series routers.

Description
Options

Configure a logical link-layer encapsulation type.

atm-ccc-cell-relayUse ATM cell-relay encapsulation.
atm-ccc-vc-muxUse ATM virtual circuit (VC) multiplex encapsulation on CCC circuits.

When you use this encapsulation type, you can configure the ccc family only.
atm-cisco-nlpidUse Cisco ATM network layer protocol identifier (NLPID) encapsulation.

When you use this encapsulation type, you can configure the inet family only.
atm-mlppp-llcFor ATM2 IQ interfaces only, use Multilink Point-to-Point (MLPPP) over

AAL5 LLC. For this encapsulation type, your router must be equipped with a Link
Services or Voice Services PIC. MLPPP over ATM encapsulation is not supported on
ATM2 IQ OC48 interfaces.
atm-nlpidUse ATM NLPID encapsulation. When you use this encapsulation type, you

can configure the inet family only.

atm-ppp-llc(ATM2 IQ interfaces and MX Series routers with MPC/MIC interfaces using

the ATM MIC with SFP only) Use PPP over AAL5 LLC encapsulation.
atm-ppp-vc-mux(ATM2 IQ interfaces and MX Series routers with MPC/MIC interfaces

using the ATM MIC with SFP only) Use PPP over ATM AAL5 multiplex encapsulation.
atm-snap(All interfaces including MX Series routers with MPC/MIC interfaces using

the ATM MIC with SFP) Use ATM subnetwork attachment point (SNAP)
encapsulation.
atm-tcc-snapUse ATM SNAP encapsulation on translational cross-connect (TCC)

circuits.

Copyright 2014, Juniper Networks, Inc.

543

Interfaces Fundamentals for Routing Devices

atm-tcc-vc-muxUse ATM VC multiplex encapsulation on TCC circuits. When you use

this encapsulation type, you can configure the tcc family only.
atm-vc-mux(All interfaces including MX Series routers with MPC/MIC interfaces using

the ATM MIC with SFP) Use ATM VC multiplex encapsulation. When you use this
encapsulation type, you can configure the inet family only.
ether-over-atm-llc(All IP interfaces including MX Series routers with MPC/MIC interfaces

using the ATM MIC with SFP) For interfaces that carry IP traffic, use Ethernet over
ATM LLC encapsulation. When you use this encapsulation type, you cannot configure
multipoint interfaces.
ether-vpls-over-atm-llcFor ATM2 IQ interfaces only, use the Ethernet virtual private

LAN service (VPLS) over ATM LLC encapsulation to bridge Ethernet interfaces and
ATM interfaces over a VPLS routing instance (as described in RFC 2684, Multiprotocol
Encapsulation over ATM Adaptation Layer 5). Packets from the ATM interfaces are
converted to standard ENET2/802.3 encapsulated Ethernet frames with the frame
check sequence (FCS) field removed.
ether-vpls-over-frFor E1, T1, E3, T3, and SONET interfaces only, use the Ethernet virtual

private LAN service (VPLS) over Frame Relay encapsulation to support Bridged
Ethernet over Frame Relay encapsulated TDM interfaces for VPLS applications, per
RFC 2427, Multiprotocol Interconnect over Frame Relay.

NOTE: The SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP, the

Channelized SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP, and the
DS3/E3 MIC do not support Ethernet over Frame Relay encapsulation.

ether-vpls-over-pppFor E1, T1, E3, T3, and SONET interfaces only, use the Ethernet

virtual private LAN service (VPLS) over Point-to-Point Protocol (PPP) encapsulation
to support Bridged Ethernet over PPP-encapsulated TDM interfaces for VPLS
applications.
ethernetUse Ethernet II encapsulation (as described in RFC 894, A Standard for the

Transmission of IP Datagrams over Ethernet Networks).

ethernet-cccUse Ethernet CCC encapsulation on Ethernet interfaces.
ethernet-vplsUse Ethernet VPLS encapsulation on Ethernet interfaces that have VPLS

enabled and that must accept packets carrying standard Tag Protocol ID (TPID)
values.

NOTE: The built-in Gigabit Ethernet PIC on an M7i router does not support
extended VLAN VPLS encapsulation.

544

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

ethernet-vpls-frUse in a VPLS setup when a CE device is connected to a PE device over

a time-division multiplexing (TDM) link. This encapsulation type enables the PE

device to terminate the outer layer 2 Frame Relay connection, use the 802.1p bits
inside the inner Ethernet header to classify the packets, look at the MAC address
from the Ethernet header, and use the MAC address to forward the packet into a
given VPLS instance.
frame-relay-cccUse Frame Relay encapsulation on CCC circuits. When you use this

encapsulation type, you can configure the ccc family only.

frame-relay-ether-typeUse Frame Relay ether type encapsulation for compatibility with

Cisco Frame Relay. The physical interface must be configured with

flexible-frame-relay encapsulation.
frame-relay-ether-type-tccUse Frame Relay ether type TCC for Cisco-compatible Frame

Relay on TCC circuits to connect different media. The physical interface must be
configured with flexible-frame-relay encapsulation.
frame-relay-pppUse PPP over Frame Relay circuits. When you use this encapsulation

type, you can configure the ppp family only.

frame-relay-tccUse Frame Relay encapsulation on TCC circuits for connecting different

media. When you use this encapsulation type, you can configure the tcc family only.
gre-fragmentationFor adaptive services interfaces only, use GRE fragmentation

encapsulation to enable fragmentation of IPv4 packets in GRE tunnels. This

encapsulation clears the do not fragment (DF) bit in the packet header. If the packets
size exceeds the tunnels maximum transmission unit (MTU) value, the packet is
fragmented before encapsulation.
multilink-frame-relay-end-to-endUse MLFR FRF.15 encapsulation. This encapsulation

is used only on multilink, link services, and voice services interfaces and their
constituent T1 or E1 interfaces, and is supported on LSQ and redundant LSQ interfaces.
multilink-pppUse MLPPP encapsulation. This encapsulation is used only on multilink,

link services, and voice services interfaces and their constituent T1 or E1 interfaces.
ppp-over-etherYou use PPP over Ethernet encapsulation to configure an underlying

Ethernet interface for a dynamic PPPoE logical interface on M120 and M320 routers
with Intelligent Queuing 2 (IQ2) PICs, and on MX Series routers with MPCs.
ppp-over-ether-over-atm-llc(MX Series routers with MPCs using the ATM MIC with SFP

only) For underlying ATM interfaces, use PPP over Ethernet over ATM LLC
encapsulation. When you use this encapsulation type, you cannot configure the
interface address. Instead, configure the interface address on the PPP interface.
vlan-bridgeUse Ethernet VLAN bridge encapsulation on Ethernet interfaces that have

IEEE 802.1Q tagging, flexible-ethernet-services, and bridging enabled and that must
accept packets carrying TPID 0x8100 or a user-defined TPID.
vlan-cccUse Ethernet virtual LAN (VLAN) encapsulation on CCC circuits. When you use

this encapsulation type, you can configure the ccc family only.

Copyright 2014, Juniper Networks, Inc.

545

Interfaces Fundamentals for Routing Devices

vlan-vci-cccUse ATM-to-Ethernet interworking encapsulation on CCC circuits. When

you use this encapsulation type, you can configure the ccc family only.
vlan-tccUse Ethernet VLAN encapsulation on TCC circuits. When you use this

encapsulation type, you can configure the tcc family only.

vlan-vplsUse Ethernet VLAN encapsulation on VPLS circuits.

Required Privilege
Level
Related
Documentation

546

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Layer 2 Switching Cross-Connects Using CCC

Configuring the Encapsulation for Layer 2 Switching TCCs

Configuring Interface Encapsulation on Logical Interfaces on page 172

Configuring MPLS LSP Tunnel Cross-Connects Using CCC

Circuit and Translational Cross-Connects Overview on page 255

Identifying the Access Concentrator

Configuring ATM Interface Encapsulation

Configuring VLAN Encapsulation

Configuring Extended VLAN Encapsulation

Configuring ATM-to-Ethernet Interworking on page 262

Configuring Interface Encapsulation on PTX Series Packet Transport Routers on page 123

Configuring CCC Encapsulation for Layer 2 VPNs

Configuring TCC Encapsulation for Layer 2 VPNs and Layer 2 Circuits

Configuring ATM for Subscriber Access

CoS on ATM IMA Pseudowire Interfaces Overview

Configuring Policing on an ATM IMA Pseudowire

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

encapsulation (Physical Interface)

Syntax

Hierarchy Level

Release Information

Description

Default
Options

encapsulation (atm-ccc-cell-relay | atm-pvc | cisco-hdlc | cisco-hdlc-ccc | cisco-hdlc-tcc |

ethernet-bridge | ethernet-ccc | ethernet-over-atm | ethernet-tcc | ethernet-vpls |
ethernet-vpls-fr | ether-vpls-over-atm-llc | ethernet-vpls-ppp |extended-frame-relay-ccc
| extended-frame-relay-ether-type-tcc | extended-frame-relay-tcc | extended-vlan-bridge
| extended-vlan-ccc | extended-vlan-tcc | extended-vlan-vpls | flexible-ethernet-services
| flexible-frame-relay | frame-relay | frame-relay-ccc | frame-relay-ether-type |
frame-relay-ether-type-tcc | frame-relay-port-ccc | frame-relay-tcc | generic-services |
multilink-frame-relay-uni-nni | ppp | ppp-ccc | ppp-tcc | vlan-ccc | vlan-vci-ccc | vlan-vpls);
[edit interfaces interface-name],
[edit interfaces rlsq number:number]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for EX Series switches.
Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers (flexible-ethernet-services, ethernet-ccc, and ethernet-tcc options only).
Specify the physical link-layer encapsulation type. Not all encapsulation types are
supported on the switches. See the switch CLI.
pppUse serial PPP encapsulation.
atm-ccc-cell-relayUse ATM cell-relay encapsulation.
atm-pvcUse ATM PVC encapsulation.
cisco-hdlcUse Cisco-compatible High-Level Data Link Control (HDLC) framing.
cisco-hdlc-cccUse Cisco-compatible HDLC framing on CCC circuits.
cisco-hdlc-tccUse Cisco-compatible HDLC framing on TCC circuits for connecting

different media.
ethernet-bridgeUse Ethernet bridge encapsulation on Ethernet interfaces that have

bridging enabled and that must accept all packets.

ethernet-cccUse Ethernet CCC encapsulation on Ethernet interfaces that must accept

packets carrying standard Tag Protocol ID (TPID) values. For 8-port, 12-port, and
48-port Fast Ethernet PICs, CCC is not supported.
ethernet-over-atmFor interfaces that carry IPv4 traffic, use Ethernet over ATM

encapsulation. When you use this encapsulation type, you cannot configure multipoint
interfaces. As defined in RFC 2684, Multiprotocol Encapsulation over ATM Adaptation
Layer 5, this encapsulation type allows ATM interfaces to connect to devices that
support only bridge protocol data units (BPDUs). Junos OS does not completely
support bridging, but accepts BPDU packets as a default gateway. If you use the
router as an edge device, then the router acts as a default gateway. It accepts
Ethernet LLC/SNAP frames with IP or ARP in the payload, and drops the rest. For
packets destined to the Ethernet LAN, a route lookup is done using the destination

Copyright 2014, Juniper Networks, Inc.

547

Interfaces Fundamentals for Routing Devices

IP address. If the route lookup yields a full address match, the packet is encapsulated
with an LLC/SNAP and MAC header, and the packet is forwarded to the ATM interface.
ethernet-tccFor interfaces that carry IPv4 traffic, use Ethernet TCC encapsulation on

interfaces that must accept packets carrying standard TPID values. For 8-port,
12-port, and 48-port Fast Ethernet PICs, TCC is not supported.
ethernet-vplsUse Ethernet VPLS encapsulation on Ethernet interfaces that have VPLS

enabled and that must accept packets carrying standard TPID values. On M Series
routers, except the M320 router, the 4-port Fast Ethernet TX PIC and the 1-port,
2-port, and 4-port, 4-slot Gigabit Ethernet PICs can use the Ethernet VPLS
encapsulation type.
ethernet-vpls-frUse in a VPLS setup when a CE device is connected to a PE device over

a time division multiplexing (TDM) link. This encapsulation type enables the PE
device to terminate the outer Layer 2 Frame Relay connection, use the 802.1p bits
inside the inner Ethernet header to classify the packets, look at the MAC address
from the Ethernet header, and use the MAC address to forward the packet into a
given VPLS instance.
ethernet-vpls-pppUse in a VPLS setup when a CE device is connected to a PE device

over a time division multiplexing (TDM) link. This encapsulation type enables the PE
device to terminate the outer Layer 2 PPP connection, use the 802.1p bits inside the
inner Ethernet header to classify the packets, look at the MAC address from the
Ethernet header, and use it to forward the packet into a given VPLS instance.
ether-vpls-over-atm-llcFor ATM intelligent queuing (IQ) interfaces only, use the Ethernet

virtual private LAN service (VPLS) over ATM LLC encapsulation to bridge Ethernet
interfaces and ATM interfaces over a VPLS routing instance (as described in
RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5). Packets from
the ATM interfaces are converted to standard ENET2/802.3 encapsulated Ethernet
frames with the frame check sequence (FCS) field removed.
extended-frame-relay-cccUse Frame Relay encapsulation on CCC circuits. This

encapsulation type allows you to dedicate DLCIs 1 through 1022 to CCC.

extended-frame-relay-ether-type-tccUse extended Frame Relay ether type TCC for

Cisco-compatible Frame Relay for DLCIs 1 through 1022. This encapsulation type is
used for circuits with different media on either side of the connection.
extended-frame-relay-tccUse Frame Relay encapsulation on TCC circuits to connect

different media. This encapsulation type allows you to dedicate DLCIs 1 through 1022
to TCC.
extended-vlan-bridgeUse extended VLAN bridge encapsulation on Ethernet interfaces

that have IEEE 802.1Q VLAN tagging and bridging enabled and that must accept
packets carrying TPID 0x8100 or a user-defined TPID.

548

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

extended-vlan-cccUse extended VLAN encapsulation on CCC circuits with Gigabit

Ethernet and 4-port Fast Ethernet interfaces that must accept packets carrying
802.1Q values. For 8-port, 12-port, and 48-port Fast Ethernet PICs, extended VLAN
CCC is not supported. For 4-port Gigabit Ethernet PICs, extended VLAN CCC is not
supported.
extended-vlan-tccFor interfaces that carry IPv4 traffic, use extended VLAN encapsulation

on TCC circuits with Gigabit Ethernet interfaces on which you want to use 802.1Q
tagging. For 4-port Gigabit Ethernet PICs, extended VLAN TCC is not supported.
extended-vlan-vplsUse extended VLAN VPLS encapsulation on Ethernet interfaces

that have VLAN 802.1Q tagging and VPLS enabled and that must accept packets
carrying TPIDs 0x8100, 0x9100, and 0x9901. On M Series routers, except the M320
router, the 4-port Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot
Gigabit Ethernet PICs can use the Ethernet VPLS encapsulation type.

NOTE: The built-in Gigabit Ethernet PIC on an M7i router does not support
extended VLAN VPLS encapsulation.

flexible-ethernet-servicesFor Gigabit Ethernet IQ interfaces and Gigabit Ethernet PICs

with small form-factor pluggable transceivers (SFPs) (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), use flexible
Ethernet services encapsulation when you want to configure multiple per-unit
Ethernet encapsulations. Aggregated Ethernet bundles can use this encapsulation
type. This encapsulation type allows you to configure any combination of route, TCC,
CCC, Layer 2 virtual private networks (VPNs), and VPLS encapsulations on a single
physical port. If you configure flexible Ethernet services encapsulation on the physical
interface, VLAN IDs from 1 through 511 are no longer reserved for normal VLANs.
flexible-frame-relayFor IQ interfaces only, use flexible Frame Relay encapsulation when

you want to configure multiple per-unit Frame Relay encapsulations. This

encapsulation type allows you to configure any combination of TCC, CCC, and
standard Frame Relay encapsulations on a single physical port. Also, each logical
interface can have any DLCI value from 1 through 1022.
frame-relayUse Frame Relay encapsulation.
frame-relay-cccUse Frame Relay encapsulation on CCC circuits.
frame-relay-ether-typeUse Frame Relay ether type encapsulation for compatibility with

the Cisco Frame Relay.

frame-relay-ether-type-tccUse Frame Relay ether type TCC for Cisco-compatible Frame

Relay on TCC circuits to connect different media.

frame-relay-port-cccUse Frame Relay port CCC encapsulation to transparently carry

all the DLCIs between two customer edge (CE) routers without explicitly configuring
each DLCI on the two provider edge (PE) routers with Frame Relay transport. When
you use this encapsulation type, you can configure the ccc family only.

Copyright 2014, Juniper Networks, Inc.

549

Interfaces Fundamentals for Routing Devices

frame-relay-tccUse Frame Relay encapsulation on TCC circuits to connect different

media.
generic-servicesUse generic services encapsulation for services with a hierarchical

scheduler.
multilink-frame-relay-uni-nniUse MLFR UNI NNI encapsulation. This encapsulation is

used on link services, voice services interfaces functioning as FRF.16 bundles, and
their constituent T1 or E1 interfaces, and is supported on LSQ and redundant LSQ
interfaces.
pppUse serial PPP encapsulation.
ppp-cccUse serial PPP encapsulation on CCC circuits. When you use this encapsulation

type, you can configure the ccc family only.

ppp-tccUse serial PPP encapsulation on TCC circuits for connecting different media.

When you use this encapsulation type, you can configure the tcc family only.
vlan-cccUse Ethernet VLAN encapsulation on CCC circuits.
vlan-vci-cccUse ATM-to-Ethernet interworking encapsulation on CCC circuits. When

you use this encapsulation type, you can configure the ccc family only. All logical
interfaces configured on the Ethernet interface must also have the encapsulation
type set to vlan-vci-ccc.
vlan-vplsUse VLAN VPLS encapsulation on Ethernet interfaces with VLAN tagging and

VPLS enabled. Interfaces with VLAN VPLS encapsulation accept packets carrying
standard TPID values only. On M Series routers, except the M320 router, the 4-port
Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot Gigabit Ethernet PICs
can use the Ethernet VPLS encapsulation type.

NOTE:

Required Privilege
Level

550

Label-switched interfaces (LSIs) do not support VLAN VPLS encapsulation.

Therefore, you can only use VLAN VPLS encapsulation on a
PE-router-to-CE-router interface and not a core-facing interface.

Starting with Junos OS release 13.3, a commit error occurs when you
configure vlan-vpls encapsulation on a physical interface and configure
family inet on one of the logical units. Previously, it was possible to commit
this invalid configuration.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Related
Documentation

Configuring Interface Encapsulation on Physical Interfaces on page 117

Configuring CCC Encapsulation for Layer 2 VPNs

Configuring Layer 2 Switching Cross-Connects Using CCC

Configuring TCC Encapsulation for Layer 2 VPNs and Layer 2 Circuits

Configuring ATM Interface Encapsulation

Configuring ATM-to-Ethernet Interworking on page 262

Configuring VLAN Encapsulation

Configuring Extended VLAN Encapsulation

Configuring Encapsulation for Layer 2 Wholesale VLAN Interfaces

Configuring Interfaces for Layer 2 Circuits

Configuring Interface Encapsulation on PTX Series Packet Transport Routers on page 123

Configuring MPLS LSP Tunnel Cross-Connects Using CCC

Configuring TCC

Configuring VPLS Interface Encapsulation

Configuring Interfaces for VPLS Routing

Defining the Encapsulation for Switching Cross-Connects on page 257

encoding
Syntax
Hierarchy Level
Release Information
Description
Default
Options

encoding (nrz | nrzi);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

For serial interfaces, set the line encoding format.
The default line encoding is non-return to zero (NRZ).
nrzUse NRZ line encoding.
nrziUse non-return to zero inverted (NRZI) line encoding.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Line Encoding on page 315

Copyright 2014, Juniper Networks, Inc.

551

Interfaces Fundamentals for Routing Devices

epd-threshold (Logical Interface)

Syntax
Hierarchy Level

Release Information

Description

Default

epd-threshold cells plp1 cells;

[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number address address family family
multipoint-destination address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
address address family family multipoint-destination address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
For ATM2 IQ interfaces only, define the early packet discard (EPD) threshold on a VC.
The EPD threshold is a limit on the number of transmit packets that can be queued.
Packets that exceed the limit are discarded. For interfaces configured in trunk mode, you
can also configure dual EPD thresholds depending on the packet loss priorities (PLPs).
Approximately 1 percent of the available cell buffers. If shaping is enabled, the default
EPD threshold is proportional to the shaping rate according to the following formula:
default epd-threshold = number of buffers * shaping rate / line rate

The minimum EPD threshold value is 48 cells. If the default EPD threshold formula results
in an EPD threshold of less than 48 cells, the result will be ignored, and the minimum
value of 48 cells will be used.
Options

cellsMaximum number of cells.

Range: For 1-port and 2-port OC12 interfaces, 48 through 425,984 cells
Required Privilege
Level
Related
Documentation

552

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the ATM2 IQ EPD Threshold

Configuring Two EPD Thresholds per Queue

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

epd-threshold (Physical Interface)

Syntax
Hierarchy Level

Release Information
Description

Default

Options

epd-threshold cells plp1 cells;

[edit interfaces at-fpc/pic/port atm-options scheduler-maps map-name forwarding-class
class-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define the EPD threshold on a VC. The EPD threshold is a
limit on the number of transmit packets that can be queued. Packets that exceed the
limit are discarded.
If you do not include either the epd-threshold or the linear-red-profile statement in the
forwarding class configuration, the Junos OS uses an EPD threshold based on the available
bandwidth and other parameters.
cellsMaximum number of cells.

Range: For 1-port and 2-port OC12 interfaces, 48 through 425,984 cells. For 1-port OC48
interfaces, 48 through 425,984 cells. For 2-port OC3, DS3, and E3 interfaces, 48
through 212,992 cells. For 4-port DS3 and E3 interfaces, 48 through 106,496 cells.
The plp1 statement is explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an ATM Scheduler Map

linear-red-profile on page 662

es-options
Syntax

Hierarchy Level
Release Information
Description

es-options {
backup-interface interface-name;
}
[edit interfaces es-fpc/pic/port]

Statement introduced before Junos OS Release 7.4.

On ES interfaces, configure ES interface-specific interface properties.
The backup-interface statement is explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

553

Interfaces Fundamentals for Routing Devices

ethernet (Protocols OAM)

Syntax

554

ethernet {
connectivity-fault-management {
action-profile profile-name {
default-actions {
interface-down;
}
}
performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
maintenance-domain domain-name {
level number;
name-format (character-string | none | dns | mac+2octet);
maintenance-association ma-name {
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number;
port-status-tlv;
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
}
}
}
evcs evc-id {
evc-protocol cfm management-domain domain-id (management-association
association-id | vpls (routing-instance instance-id);
remote-uni-count count;
multipoint-to-multipoint;
}
link-fault-management {
action-profile profile-name {
action {
link-down;
send-critical-event;
syslog;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
interface interface-name {
apply-action-profile;
link-discovery (active | passive);
loopback-tracking;
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
}
}
lmi {
status-counter count;
polling-verification-timer value;
interface name {

Copyright 2014, Juniper Networks, Inc.

555

Interfaces Fundamentals for Routing Devices

uni-id uni-name;
status-counter number;
polling-verification-timer value;
evc-map-type (all-to-one-bundling | bundling | service-multiplexing);
evc evc-name {
default-evc;
vlan-list vlan-id-list;
}
}
}
}

Hierarchy Level
Release Information
Description

[edit protocols oam]

Statement introduced in Junos OS Release 8.2.

For Ethernet interfaces on EX Series switches, and M320, MX Series, and T Series routers,
provide fault signaling and detection for 802.3ah Operation, Administration, and
Management (OAM) support.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

556

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Enabling IEEE 802.3ah OAM Support

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

ethernet-policer-profile
Syntax

Hierarchy Level

Release Information

ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile]

Statement introduced before Junos OS Release 7.4.

Description

NOTE: On QFX Series standalone switches, this statement hierarchy is only

supported on the Enhanced Layer 2 Switching CLI.

For Gigabit Ethernet IQ, 10-Gigabit Ethernet, Gigabit Ethernet PICs with SFPs (except the
10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), and
100-Gigabit Ethernet Type 5 PIC with CFP, configure a class of service (CoS)-based
policer. Policing applies to the inner VLAN identifiers, not to the outer tag. For Gigabit
Ethernet interfaces with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in
Gigabit Ethernet port on the M7i router), the premium policer is not supported.
The statements are explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Policers

Copyright 2014, Juniper Networks, Inc.

557

Interfaces Fundamentals for Routing Devices

ethernet-ring
Syntax

Hierarchy Level
Release Information

Description

Options

ethernet-ring ring-name {
control-vlan (vlan-id | vlan-name);
data-channel {
vlan number
}
east-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
}
guard-interval number;
node-id mac-address;
restore-interval number;
ring-protection-link-owner;
west-interface {
control-channel channel-name {
vlan number;
}
}
}
[edit protocols protection-group]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.
For Ethernet PICs on MX Series routers or for EX Series switches, , specify the Ethernet
ring in an Ethernet ring protection switching configuration.
ring-nameName of the Ethernet protection ring.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

558

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

ethernet-switch-profile
Syntax

Hierarchy Level

Release Information

ethernet-switch-profile {
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [values];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
tag-protocol-id tpid;
}
mac-learn-enable;
}
[edit interfaces interface-name gigether-options],
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Statement introduced in Junos OS Release 13.2 for the QFX Series.
Statement introduced in Junos OS Release 13.2X50-D15 for the EX Series switches.

Description

NOTE: On QFX Series standalone switches, the ethernet-policer-profile CLI

hierarchy and the mac-learn-enable statement are supported only on the
Enhanced Layer 2 Switching CLI.

For Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ2 and IQ2-E, and Gigabit Ethernet PICs
with SFPs (except the 10-port Gigabit Ethernet PIC, aggregated Ethernet with Gigabit
Ethernet IQ interfaces, the built-in Gigabit Ethernet port on the M7i router); 100-Gigabit
Ethernet Type 5 PIC with CFP; and Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit

Copyright 2014, Juniper Networks, Inc.

559

Interfaces Fundamentals for Routing Devices

Ethernet, and aggregated Ethernet interfaces on EX Series switches, configure VLAN tag
and MAC address accounting and filtering properties.
The remaining statements are explained separately.

NOTE: When you gather interfaces into a bridge domain, the

no-mac-learn-enable statement at the [edit interfaces interface-name
gigether-options ethernet-switch-profile] hierarchy level is not supported. You
must use the no-mac-learning statement at the [edit bridge-domains
bridge-domain-name bridge-options interface interface-name] hierarchy level
to disable MAC learning on an interface in a bridge domain. For information
on disabling MAC learning for a bridge domain, see the MX Series Layer 2
Configuration Guide.

Default

Required Privilege
Level
Related
Documentation

If the ethernet-switch-profile statement is not configured, Gigabit Ethernet IQ and Gigabit

Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit
Ethernet port on the M7i router) behave like Gigabit Ethernet interfaces.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Policers

Configuring MAC Address Filtering

Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview

Configuring Q-in-Q Tunneling (CLI Procedure)

eui-64
Syntax
Hierarchy Level
Release Information

Description

Required Privilege
Level
Related
Documentation

560

eui-64;
[edit interfaces interface-name unit number family inet6 address address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.3 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for the QFX Series.
For interfaces that carry IP version 6 (IPv6) traffic, automatically generate the host
number portion of interface addresses.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the Interface Address on page 192

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

evcs
Syntax

Hierarchy Level
Release Information
Description

Options

evcs evc-id {
evc-protocol cfm management-domain domain-id (management-association association-id
| vpls (routing-instance instance-id);
remote-uni-count count;
multipoint-to-multipoint;
}
[edit protocols oam ethernet]

Statement introduced in Junos OS Release 9.5.

On MX Series routers with ge, xe, or ae interfaces, configure an OAM Ethernet virtual
connection.
evc-protocol cfm | vplsSpecify connectivity fault management (CFM) or virtual private

LAN service (VPLS) as the Ethernet Virtual Connection (EVC) protocol.

management-domain domain-id(Optional) For CFM, specify the CFM management

domain.
management-association association-id(Optional) For CFM, specify the CFM

management association.
routing-instance instance-id(Optional) For VPLS, specify the VPLS routing instance.
remote-uni-count count(Optional) Specify the number of remote UNIs in the EVC

configuration, the default is 1.

multipoint-to-multipoint(Optional) Specify multiple points in the EVC configuration,

the default is point-to-point if remote-uni-count is 1.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Ethernet Local Management Interface

lmi (Ethernet OAM) on page 676

Copyright 2014, Juniper Networks, Inc.

561

Interfaces Fundamentals for Routing Devices

event (LFM)
Syntax

Hierarchy Level
Release Information
Description

event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
[edit protocols oam ethernet link-fault-management action-profile]

Statement introduced in Junos OS Release 8.5.

Configure threshold values for link events in an action profile.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Monitoring Protocol Status

event-thresholds
Syntax

Hierarchy Level
Release Information
Description

event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
[edit protocols oam link-fault-management interface interface-name]

Statement introduced in Junos OS Release 8.4.

Configure threshold limit values for link events in periodic OAM PDUs.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

562

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Threshold Values for Local Fault Events on an Interface

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

fast-aps-switch
Syntax
Hierarchy Level
Release Information
Description

fast-aps-switch;
[edit interfaces interface-name sonet-options aps]

Statement introduced in Junos OS Release 12.1.

(M320 routers with Channelized OC3/STM1 Circuit Emulation PIC with SFP only and EX
Series switches) Reduce the Automatic Protection Switching (APS) switchover time in
Layer 2 circuits.

NOTE:

Required Privilege
Level
Related
Documentation

Configuring this statement reduces the APS switchover time only when
the Layer 2 circuit encapsulation type for the interface receiving traffic from
a Layer 2 circuit neighbor is SAToP.

When the fast-aps-switch statement is configured in revertive APS mode,

you must configure an appropriate value for revert time to achieve reduction
in APS switchover time.

To prevent the logical interfaces in the data path from being shut down,
configure appropriate hold-time values on all the interfaces in the data
path that support TDM.

The fast-aps-switch statement cannot be configured when the APS annex-b

option is configured.

The interfaces that have the fast-aps-switch statement configured cannot

be used in virtual private LAN service (VPLS) environments.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Reducing APS Switchover Time in Layer 2 Circuits

Copyright 2014, Juniper Networks, Inc.

563

Interfaces Fundamentals for Routing Devices

f-max-period
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

f-max-period number;
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number rtp]

Statement introduced before Junos OS Release 7.4.

For all adaptive services interfaces and for ISDN interfaces on J Series Services Routers.
Specify the maximum number of compressed packets allowed between the transmission
of full headers in a compressed Real-Time Transport Protocol (RTP) traffic stream.
numberMaximum number of packets. The value can be from 1 through 65535.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Bandwidth on Demand

Junos OS Services Interfaces Library for Routing Devices

facility-override
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

564

facility-override facility-name;
[edit interfaces interface-name services-options sysloghost hostname]

Statement introduced before Junos OS Release 7.4.

Override default facility for system log reporting.
facility-nameName of facility that overrides the default assignment.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

failover-delay
Syntax
Hierarchy Level
Release Information
Description
Options

failover-delay milliseconds;
[edit protocols vrrp]

Statement introduced in Junos OS Release 9.4.

Configure the failover delay for VRRP and VRRP for IPv6 operations.
millisecondsSpecify the failover delay time, in milliseconds.

Range: 50 through 2000

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VRRP and VRRP for IPv6

Copyright 2014, Juniper Networks, Inc.

565

Interfaces Fundamentals for Routing Devices

family (Dynamic Standard Interface)

Syntax

Hierarchy Level
Release Information

566

family family {
access-concentrator name;
address address;
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
adf {
counter;
input-precedence precedence;
not-mandatory;
output-precedence precedence;
rule rule-value;
}
input filter-name {
precedence precedence;
}
output filter-name {
precedence precedence;
}
}
mac-validate (loose | strict);
max-sessions number;
max-sessions-vsa-ignore;
rpf-check {
fail-filter filter-name;
mode loose;
}
service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-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>;
unnumbered-address interface-name <preferred-source-address address>;
}
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 9.2.

pppoe option added in Junos OS Release 11.2.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Description

Configure protocol family information for the logical interface.

NOTE: Not all subordinate stanzas are available to every protocol family.

Options

familyProtocol family:

inetIP version 4 suite

inet6IP version 6 suite

pppoe(MX Series routers with MPCs only) Point-to-Point Protocol over Ethernet

vplsVirtual private LAN service

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Example: Configuring Static Routing on Logical Systems

Configuring the Protocol Family on page 190

Copyright 2014, Juniper Networks, Inc.

567

Interfaces Fundamentals for Routing Devices

family
Syntax

568

family family {
accounting {
destination-class-usage;
source-class-usage {
(input | output | input output);
}
}
access-concentrator name;
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;
duplicate-protection;
dynamic-profile profile-name;
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);
max-sessions number;
max-sessions-vsa-ignore;
mtu bytes;
multicast-only;
negotiate-address;
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 {

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

fail-filter filter-name
mode loose;
}
sampling {
input;
output;
}
service {
input {
post-service-filter filter-name;
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>;
(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];
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;

Copyright 2014, Juniper Networks, Inc.

569

Interfaces Fundamentals for Routing Devices

(preempt | no-preempt) {
hold-time seconds;
}
priority number;
track {
interface interface-name {
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 ];
}
virtual-link-local-address ipv6-address;
}
}

Hierarchy Level

Release Information

Description

[edit interfaces interface-name unit logical-unit-number],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Option max-sessions-vsa-ignore introduced in Junos OS Release 11.4.
Configure protocol family information for the logical interface.

NOTE: Not all subordinate stanzas are available to every protocol family.

570

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Options

familyProtocol family:

anyProtocol-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

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

cccCircuit cross-connect protocol suite

inetInternet Protocol version 4 suite

inet6Internet Protocol version 6 suite

isoInternational Organization for Standardization Open Systems Interconnection

(ISO OSI) protocol suite

mlfr-end-to-endMultilink Frame Relay FRF.15

mlfr-uni-nniMultilink Frame Relay FRF.16

multilink-pppMultilink Point-to-Point Protocol

mplsMultiprotocol Label Switching (MPLS)

pppoePoint-to-Point Protocol over Ethernet

tccTranslational cross-connect protocol suite

tnpTrivial Network Protocol

vpls(M Series and T Series routers only) Virtual private LAN service

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Protocol Family on page 190

Copyright 2014, Juniper Networks, Inc.

571

Interfaces Fundamentals for Routing Devices

fastether-options
Syntax

Hierarchy Level
Release Information
Description

fastether-options {
802.3ad {
aex (primary | backup);
lacp {
port-priority;
}
}
(flow-control | no-flow-control);
ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Configure Fast Ethernet-specific interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

572

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Interfaces Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

fcs
Syntax
Hierarchy Level

Release Information

Description

fcs (16 | 32);

[edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name sonet-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
For E1/E3, SONET/SDH, and T1/T3 interfaces, configure the frame checksum (FCS) on
the interface. The checksum must be the same on both ends of the interface.
On a channelized OC12 interface, the SONET/SDH fcs statement is not supported. To
configure FCS on each DS3 channel, you must include the t3-options fcs statement in
the configuration for each channel. For SONET/SDH, the channelized OC12 interface
supports DS3 to STS-1 to OC12. For SDH, the channelized OC12 interface supports NxDS3
to NxVC3 to AU3 to STM.

NOTE: When configuring E1 or T1 interfaces on 10-port Channelized E1/T1 IQE

PICs, the fcs statement must be included at the [edit interfaces e1-fpc/pic/port]
or [edit interfaces t1-fpc/pic/port] hierarchy level as appropriate.

Options

16Use a 16-bit frame checksum on the interface.

32Use a 32-bit frame checksum on the interface. Using a 32-bit checksum provides

more reliable packet verification, but some older equipment might not support 32-bit
checksums.
Default: 16
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the E1 Frame Checksum

Configuring the E3 Frame Checksum

Configuring the SONET/SDH Frame Checksum

Configuring the T1 Frame Checksum

Configuring the T3 Frame Checksum

Copyright 2014, Juniper Networks, Inc.

573

Interfaces Fundamentals for Routing Devices

feac-loop-respond
Syntax
Hierarchy Level
Release Information
Description

(feac-loop-respond | no-feac-loop-respond);
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

For T3 interfaces only, configure the router so a remote CSU can place the local router
into loopback.
If you configure remote or local loopback with the T3 loopback statement, the router
does not respond to FEAC requests from the CSU even if you include the feac-loop-respond
statement in the configuration. For the router to respond, you must delete the loopback
statement from the configuration.
You must rollback the setting done on the remote CSU prior to deactivating the
feac-loop-respond statement. If the remote CSU cannot comply, clear the remote loop
through local configuration to achieve the cleanup. For example, configure remote
loopback on the interface and then delete the remote loopback.

Default
Required Privilege
Level
Related
Documentation

574

The router does not respond to FEAC requests.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the T3 FEAC Response

loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3) on page 686

remote-loopback-respond on page 843

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

filter
Syntax

Hierarchy Level

Release Information

Description

filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
}
[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]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Apply a filter to an interface. You can also use filters for encrypted traffic. When you
configure filters, you can configure them under the family ethernet-switching, inet, inet6,
mpls, or vpls only.

NOTE: On QFX3500 and QFX3600 switches running Enhanced Layer 2

Software, VPLS is not supported.

Options

group filter-group-numberDefine an interface to be part of a filter group.

Range: 1 through 255

input filter-nameName of one filter to evaluate when packets are received on the

interface.
output filter-nameName of one filter to evaluate when packets are transmitted on the

interface.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying a Filter to an Interface on page 219

Junos OS Services Interfaces Library for Routing Devices

Routing Policies, Firewall Filters, and Traffic Policers Feature Guide for Routing Devices

Junos OS Administration Library for Routing Devices

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

575

Interfaces Fundamentals for Routing Devices

Configuring Firewall Filters (CLI Procedure)

Configuring Firewall Filters and Policers for VPLS

family

family

filter (Applying to an Interface)

Syntax

Hierarchy Level

Release Information
Description

Options

filter {
input filter-name;
output filter-name;
}
[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]

Statement introduced before Junos OS Release 7.4.

Apply a filter to an interface. You can also use filters for encrypted traffic. When you
configure filters, you can configure the family inet, inet6, mpls, or vpls only.
input filter-nameName of one filter to evaluate when packets are received on the

interface.
output filter-nameName of one filter to evaluate when packets are transmitted on the

interface.
Required Privilege
Level
Related
Documentation

576

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

simple-filter

Applying Firewall Filter Tricolor Marking Policers to Interfaces

Example: Classifying Packets Based on Their Destination Address

Example: Configuring and Verifying a Complex Multifield Filter

Example: Writing Different DSCP and EXP Values in MPLS-Tagged IP Packets

Example: Configuring a Simple Filter

Example: Configuring a Logical Bandwidth Policer

Two-Color Policers and Shaping Rate Changes

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

flexible-vlan-tagging
Syntax
Hierarchy Level

Release Information

Description

flexible-vlan-tagging;
[edit interfaces aex],
[edit interfaces ge-fpc/pic/port],
[edit interfaces et-fpc/pic/port],
[edit interfaces ps0],
[edit interfaces xe-fpc/pic/port]

Statement introduced in Junos OS Release 8.1.

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.
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 switches.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Mixed Tagging

Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers

Copyright 2014, Juniper Networks, Inc.

577

Interfaces Fundamentals for Routing Devices

flow-control
Syntax
Hierarchy Level

(flow-control | no-flow-control);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-name multiservice-options],
[edit interfaces interface-range name aggregated-ether-options],
[edit interfaces interface-range name ether-options]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 in EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces only, explicitly
enable flow control, which regulates the flow of packets from the router or switch to the
remote side of the connection. Enabling flow control is useful when the remote device
is a Gigabit Ethernet switch. Flow control is not supported on the 4-port Fast Ethernet
PIC.

NOTE: On the Type 5 FPC, to prioritize control packets in case of ingress

oversubscription, you must ensure that the neighboring peers support MAC
flow control. If the peers do not support MAC flow control, then you must
disable flow control.

Default
Required Privilege
Level
Related
Documentation

578

Flow control is enabled.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Flow Control

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

flow-control-options
Syntax

Hierarchy Level
Release Information
Description

Usage Guidelines
Required Privilege
Level

flow-control-options {
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
}
[edit interfaces mo-fpc/pic/port multiservice-options]

Statement introduced before Junos OS Release 8.4.

Configure the flow control options for application recovery in case of a prolonged flow
control failure.

down-on-flow-controlBring interface down during prolonged flow control.

dump-on-flow-controlCause core dump during prolonged flow control.

reset-on-flow-controlReset interface during prolonged flow control.

See Configuring Flow Monitoring.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

force
Syntax
Hierarchy Level
Release Information
Description

Options

force (protect | working);

[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Perform a forced switch between the protect and working circuits. This statement is
honored only if there are no higher-priority reasons to switch. It can be overridden by a
signal failure on the protect circuit, thus causing a switch to the working circuit.
protectRequest the circuit to become the protect circuit.
workingRequest the circuit to become the working circuit.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Switching Between the Working and Protect Circuits

request on page 845

Copyright 2014, Juniper Networks, Inc.

579

Interfaces Fundamentals for Routing Devices

forward-and-send-to-re
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

forward-and-send-to-re;
[edit interfaces interface-name unit logical-unit-number family inet targeted-broadcast],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet targeted-broadcast]

Statement introduced in Junos OS Release 10.2.

Specify that IP packets destined for a Layer 3 broadcast address be forwarded to an
egress interface and the Routing Engine. The packets are broadcast only if the egress
interface is a LAN interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Targeted Broadcast on page 251

targeted-broadcast on page 916

Understanding Targeted Broadcast on page 250

forwarding-class (ATM2 IQ Scheduler Maps)

Syntax

Hierarchy Level
Release Information
Description
Options

forwarding-class class-name {
epd-threshold cells plp1 cells;
linear-red-profile profile-name;
priority (high | low);
transmit-weight (cells number | percent number);
}
[edit interfaces at-fpc/pic/port atm-options scheduler-maps map-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define forwarding class name and option values.
class-nameName of forwarding class.

The statements are explained separately.

Required Privilege
Level
Related
Documentation

580

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

Configuring Scheduler Maps on ATM Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

forwarding-class (Gigabit Ethernet IQ Classifier)

Syntax

Hierarchy Level

Release Information
Description
Options

forwarding-class class-name {
loss-priority (high | low);
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map classifier premium]

Statement introduced before Junos OS Release 7.4.

For Gigabit Ethernet IQ interfaces only, define forwarding class name and option values.
class-nameName of forwarding class.

The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying an Output Priority Map

input-priority-map on page 624

forwarding-class statement in the Class of Service Feature Guide for Routing Devices

forward-only
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

forward-only;
[edit interfaces interface-name unit logical-unit-number family inet targeted-broadcast],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet targeted-broadcast]

Statement introduced in Junos OS Release 10.2.

Specify that IP packets destined for a Layer 3 broadcast address be forwarded to an
egress interface only. The packets are broadcast only if the egress interface is a LAN
interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Targeted Broadcast on page 251

targeted-broadcast on page 916

Understanding Targeted Broadcast on page 250

Copyright 2014, Juniper Networks, Inc.

581

Interfaces Fundamentals for Routing Devices

fragment-threshold
Syntax
Hierarchy Level

Release Information
Description

Options

fragment-threshold bytes;
[edit interfaces interface-name mlfr-uni-nni-bundle-options],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For multilink, link services, and voice services interfaces, and for J Series Services Routers
ISDN interfaces, set the fragmentation threshold.
bytesMaximum size, in bytes, for multilink packet fragments. Any nonzero value must

be a multiple of 64 bytes.
Range: 128 through 16,320 bytes
Default: 0 bytes (no fragmentation)
Required Privilege
Level
Related
Documentation

582

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Logical Interface Properties

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

frame-error
Syntax
Hierarchy Level

Release Information
Description

frame-error count;
[edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]

Statement introduced in Junos OS Release 8.4.

Threshold for sending frame error events or taking the action specified in the action
profile.
A frame error is any frame error on the underlying physical layer. The threshold is reached
when the number of frame errors reaches the configured value within the window.
The window or period during which frame errors are counted is 5 seconds or multiples
of it (with a maximum value of 1 minute). This window denotes the duration as intervals
of 100 milliseconds, encoded as a 16-bit unsigned integer. This window is not configurable
in Junos OS. According to the IEEE 802.3ah standard, the default value of the frame-errors
window is 1 second. This window has a lower bound of 1 second and an upper bound of
1 minute.

Options

countThreshold count for frame error events.

Range: 1 through 100

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Threshold Values for Local Fault Events on an Interface

Configuring Threshold Values for Fault Events in an Action Profile

Copyright 2014, Juniper Networks, Inc.

583

Interfaces Fundamentals for Routing Devices

frame-period
Syntax
Hierarchy Level

Release Information
Description

frame-period count;
[edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]

Statement introduced in Junos OS Release 8.4.

Threshold for sending frame period error events or taking the action specified in the action
profile.
A frame error is any frame error on the underlying physical layer. The frame period
threshold is reached when the number of frame errors reaches the configured value within
the period window. The default period window is the number of minimum-size frames
that can be transmitted on the underlying physical layer in 1 second. The window is not
configurable.

Options

countThreshold count for frame period error events.

Range: 1 through 100

Required Privilege
Level
Related
Documentation

584

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Threshold Values for Local Fault Events on an Interface

Configuring Threshold Values for Fault Events in an Action Profile

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

frame-period-summary
Syntax
Hierarchy Level

Release Information
Description

frame-period-summary count;
[edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]

Statement introduced in Junos OS Release 8.4.

Threshold for sending frame period summary error events or taking the action specified
in the action profile.
An errored frame second is any 1-second period that has at least one errored frame. This
event is generated if the number of errored frame seconds is equal to or greater than the
specified threshold for that period window. The default window is 60 seconds. The
window is not configurable.

Options

countThreshold count for frame period summary error events.

Range: 1 through 100

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Threshold Values for Local Fault Events on an Interface

Configuring Threshold Values for Fault Events in an Action Profile

Copyright 2014, Juniper Networks, Inc.

585

Interfaces Fundamentals for Routing Devices

framing (E1, E3, and T1 Interfaces)

Syntax
Hierarchy Level

Release Information

Description

framing (g704 | g704-no-crc4 | g.751 | g.832 | unframed | sf | esf);

[edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces at-fpc/pic/port e3-options],
[edit interfaces e1-fpc/pic/port e1-options],
[edit interfaces t1-fpc/pic/port t1-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure the framing format.

NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1

IQE PICs, the framing statement must be included at the [edit interfaces
ce1-fpc/pic/port] or [edit interfaces ct1-fpc/pic/port] hierarchy level as
appropriate.

Default

esf for T1 interfaces; g704 for E1 interfaces. There is no default value for E3 over ATM

interfaces.
Options

esfExtended superframe (ESF) mode for T1 interfaces.

g704G.704 framing format for E1 interfaces.
g704-no-crc4G.704 framing with no cyclic redundancy check 4 (CRC4) for E1 interfaces.
g.751G.751 framing format for E3 over ATM interfaces.
g.832G.832 framing format for E3 over ATM interfaces.
sfSuperframe (SF) mode for T1 interfaces.
unframedUnframed mode for E1 interfaces.

Required Privilege
Level
Related
Documentation

586

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring E1 Framing

Configuring E3 and T3 Parameters on ATM Interfaces

Configuring T1 Framing

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

framing (10-Gigabit Ethernet Interfaces)

Syntax
Hierarchy Level

framing (lan-phy | wan-phy);

[edit interfaces xe-fpc/pic/port]
[edit interfaces et-fpc/pic/port] (PTX Series Packet Transport Routers and MX Series Routers)

Release Information

Description

Statement introduced in Junos OS Release 8.0.

Statement introduced in Junos OS Release 12.3R2 for PTX Series Packet Transport
Routers.
For routers supporting the 10-Gigabit Ethernet interface, configure the framing format.
WAN PHY mode is supported on MX240, MX480, MX960, T640, T1600,T4000, and
PTX Series Packet Transport Routers routers only.

NOTE:

Default
Options

The T4000 Core Router supports only LAN PHY mode in Junos OS Release
12.1R1. Starting with Junos OS Release 12.1R2, WAN PHY mode is supported
on the T4000 routers with the 12-port 10-Gigabit Ethernet LAN/WAN PIC
with SFP+ (PF-12XGE-SFPP). Starting with Junos OS Release 12.2, WAN
PHY mode is supported on the T4000 routers with the 24-port 10-Gigabit
Ethernet LAN/WAN PIC with SFP+ (PF-24XGE-SFPP).

On PTX Series routers, WAN PHY mode is supported only on the 24-port
10-Gigabit Ethernet LAN/WAN PIC with SFP+ .

When the PHY mode changes, interface traffic is disrupted because of port
reinitialization.

Operates in LAN PHY mode.

lan-phy10GBASE-R interface framing format that bypasses the WIS sublayer to directly

stream block-encoded Ethernet frames on a 10-Gigabit Ethernet serial interface.

wan-phy10GBASE-W interface framing format that allows 10-Gigabit Ethernet wide

area links to use fiber-optic cables and SONET devices.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

10-Gigabit Ethernet Framing Overview

Configuring SONET Options for 10-Gigabit Ethernet Interfaces

Copyright 2014, Juniper Networks, Inc.

587

Interfaces Fundamentals for Routing Devices

framing (SONET and SDH Interfaces)

Syntax
Hierarchy Level
Release Information
Description

Default
Options

framing (sdh | sonet);

[edit interfaces so-fpc/pic/port]

Statement introduced in Junos OS Release 8.1.

This functionality allows you to mix SONET and SDH modes on interfaces on the same
PIC.

For the 4-port OC48 PIC with SFP installed and the 4-port OC192 PIC in T Series and
M Series routers, configure SONET or SDH framing on a per-port basis.

For 1-port OC192/STM64 MICs with XFP on MX Series routers, configure the SONET
or SDH framing on the single port.

Default framing mode is SONET.

sdhSDH framing.
sonetSONET framing.

Required Privilege
Level
Related
Documentation

588

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring SONET/SDH Framing Mode for Ports

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

gigether-options
Syntax

gigether-options {
802.3ad {
aex (primary | backup);
lacp {
port-priority;
}
}
(asynchronous-notification | no-asynchronous-notification);
(auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online |
local-interface-offline>;
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
no-auto-mdix
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
speed
ethernet-switch-profile {
(mac-learn-enable | no-mac-learn-enable);
tag-protocol-id [ tpids ];
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
}
}

Copyright 2014, Juniper Networks, Inc.

589

Interfaces Fundamentals for Routing Devices

Hierarchy Level
Release Information
Description

[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Configure Gigabit Ethernet specific interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Interfaces Overview

gigether-options (ACX Series)

gratuitous-arp-reply
Syntax
Hierarchy Level

(gratuitous-arp-reply | no-gratuitous-arp-reply);
[edit interfaces interface-name]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 in EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For Ethernet interfaces, enable updating of the Address Resolution Protocol (ARP) cache
for gratuitous ARPs.

Default
Required Privilege
Level
Related
Documentation

590

Updating of the ARP cache is disabled on all Ethernet interfaces.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Gratuitous ARP

no-gratuitous-arp-request on page 743

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

guard-interval
Syntax
Hierarchy Level
Release Information

Description

Options

guard-interval number;
[edit protocols protection-group ethernet-ring ring-name]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.
When a link goes down, the ring protection link (RPL) activates. When the downed link
comes back up, the RPL link receives notification, restores the link, and waits for the
restore interval before issuing another block on the same link. This configuration is a
global configuration and applies to all Ethernet rings if the Ethernet ring does not have
a more specific configuration for this value. If no parameter is configured at the protection
group level, the global configuration of this parameter uses the default value.
numberGuard timer interval, in milliseconds.

Range: 10 through 2000 ms

Default: 500 ms
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

591

Interfaces Fundamentals for Routing Devices

hardware-assisted-timestamping
Syntax
Hierarchy Level
Release Information
Description

hardware-assisted-timestamping;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring]

Statement introduced in Junos OS Release 9.5.

For Ethernet interfaces on Enhanced and Enhanced Queuing Dense Port Concentrators
(DPCs) in MX Series routers only, enable hardware-assisted timestamping support for
Ethernet frame delay measurement.
By default, the ETH-DM feature calculates frame delays using software-based
timestamping of the ETH-DM PDU frames sent and received by the MEPs in the session.
As an option that can increase the accuracy of ETH-DM calculations when the DPC is
loaded with heavy traffic in the receive direction, you can enable hardware-assisted
timestamping of session frames in the receive direction.

Required Privilege
Level
Related
Documentation

592

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Frame Delay Measurements Overview

Guidelines for Configuring Routers to Support an ETH-DM Session

Enabling the Hardware-Assisted Timestamping Option

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

high-plp-threshold
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

high-plp-threshold percent;
[edit interfaces at-fpc/pic/port atm-options linear-red-profiles profile-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define CoS VC drop profile fill-level percentage when linear
RED is applied to cells with high PLP. When the fill level exceeds the defined percentage,
packets with high PLP are randomly dropped by RED. This statement is mandatory.
percentFill-level percentage when linear RED is applied to cells with PLP.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

high-plp-max-threshold on page 596

low-plp-max-threshold on page 691

low-plp-threshold on page 692

queue-depth on page 831

hello-timer
Syntax
Hierarchy Level
Release Information
Description

Options

hello-timer milliseconds;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voice services interfaces only, configure the rate at which hello
messages are sent. A hello message is transmitted after a period defined in milliseconds
has elapsed.
millisecondsThe rate at which hello messages are sent.

Range: 1 through 180 milliseconds

Default: 10 milliseconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

acknowledge-timer on page 406

address on page 412

Copyright 2014, Juniper Networks, Inc.

593

Interfaces Fundamentals for Routing Devices

hierarchical-policer
Syntax

Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

594

hierarchical-policer name {
aggregate {
if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
then {
discard;
}
}
premium {
if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
then {
discard;
}
}
[edit firewall]

Statement introduced in Junos OS Release 9.5.

For M40e, M120, and M320 (with FFPC and SFPC) edge routers and T320, T640, and
T1600 core routers with Enhanced Intelligent Queuing (IQE) PICs, specify a hierarchical
policer.
Options are described separately.
firewallTo view this statement in the configuration.
firewall-controlTo add this statement to the configuration.

Applying Policers on page 210

Class of Service Feature Guide for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

hierarchical-scheduler (Subscriber Interfaces on MX Series Routers)

Syntax

Hierarchy Level
Release Information

Description

hierarchical-scheduler {
implicit-hierarchy;
maximumhierarchylevels number;
}
[edit interfaces interface-name]

Statement introduced in Junos OS Release 10.1.

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.
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-hierarchyConfigure three-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, and level 3. The implicit-hierarchy option is

supported only on MPC/MIC subscriber interfaces and interface sets running over
aggregated Ethernet on MX Series routers.
maximum-hierarchy-levels numberConfigure two-level hierarchical scheduling. Specify

the maximum number of hierarchical scheduling levels allowed for node scaling.
The only supported value is 2. The maximum-hierarchy-levels option is supported
on MPC/MIC or EQ DPC subscriber interfaces and interface sets running over
aggregated Ethernet on MX Series routers.

If you include the maximum-hierarchy-levels option, interface sets are allowed only at
level 3; they are not allowed at level 2. 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, 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.

Copyright 2014, Juniper Networks, Inc.

595

Interfaces Fundamentals for Routing Devices

Required Privilege
Level
Related
Documentation

view-levelTo view this statement in the configuration.

control-levelTo add this statement to the configuration.

Understanding Two-Level and Three-level Hierarchical CoS for Subscriber Interfaces

Configuring Hierarchical CoS for a Subscriber Interface of Aggregated Ethernet Links

Configuring Hierarchical Schedulers for CoS

Configuring Hierarchical CoS on a Static PPPoE Subscriber Interface

Hierarchical CoS on MPLS Pseudowire Subscriber Interfaces Overview

high-plp-max-threshold
Syntax
Hierarchy Level
Release Information
Description

Options

high-plp-max-threshold percent;
[edit interfaces at-fpc/pic/port atm-options linear-red-profiles profile-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define the drop profile fill-level for the high PLP CoS VC.
When the fill level exceeds the defined percentage, all packets are dropped.
percentFill-level percentage when linear random early discard (RED) is applied to cells

with PLP.
Required Privilege
Level
Related
Documentation

596

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

low-plp-max-threshold on page 691

low-plp-threshold on page 692

queue-depth on page 831

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

high-plp-threshold
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

high-plp-threshold percent;
[edit interfaces at-fpc/pic/port atm-options linear-red-profiles profile-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define CoS VC drop profile fill-level percentage when linear
RED is applied to cells with high PLP. When the fill level exceeds the defined percentage,
packets with high PLP are randomly dropped by RED. This statement is mandatory.
percentFill-level percentage when linear RED is applied to cells with PLP.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

high-plp-max-threshold on page 596

low-plp-max-threshold on page 691

low-plp-threshold on page 692

queue-depth on page 831

hold-interval (OAM)
Syntax
Hierarchy Level

hold-interval minutes;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name continuity-check]

Release Information

Statement introduced in Junos OS Release 8.4.

Statement introduced in junos os release 12.1X48 for PTX Series Packet Transport Routers.

Description

The time to wait before flushing the maintenance association end point (MEP) database,
if no updates occur.

Options
Required Privilege
Level
Related
Documentation

minutesTime to wait, in minutes.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Continuity Check Protocol

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

Copyright 2014, Juniper Networks, Inc.

597

Interfaces Fundamentals for Routing Devices

hold-interval (Protection Group)

Syntax
Hierarchy Level
Release Information
Description
Options

hold-interval number;
[edit protocols protection-group ethernet-ring name]

Statement introduced in Junos OS Release 9.4.

Specify the hold-off timer interval for all rings in 100 millisecond (ms) increments.
numberHold-timer interval, in milliseconds.

Range: 0 through 10,000 ms

Default: 100 ms
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

hold-time (APS)
Syntax
Hierarchy Level
Release Information
Description
Options

hold-time milliseconds;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Hold-time value to use to determine whether a neighbor APS router is operational.
millisecondsHold-time value.

Range: 1 through 65,534 milliseconds

Default: 3000 milliseconds (3 times the advertisement interval)
Required Privilege
Level
Related
Documentation

598

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring APS Timers

advertise-interval on page 414

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

hold-time (Physical Interface)

Syntax
Hierarchy Level

hold-time up milliseconds down milliseconds;

[edit interfaces interface-name],
[edit interfaces interface-range interface-range-name]

Release Information

Statement introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 10.4R5 for EX Series switches.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

Specify the hold-time value to use to damp shorter interface transitions milliseconds.
When an interface goes from up to down, it is not advertised to the rest of the system as
being down until it has remained down for the hold-time period. Similarly, an interface
is not advertised as being up until it has remained up for the hold-time period.

NOTE:

We recommend that you configure the hold-time value after determining

an appropriate value by performing repeated tests in the actual hardware
environment. This is because the appropriate value for hold-time depends
on the hardware (XFP, SFP, SR, ER, or LR) used in the networking
environment.

The hold-time option is not available for controller interfaces.

NOTE: On MX Series routers with MPC3E and MPC4E, we recommend that

you do not configure the hold-down timer by using the hold-time down
milliseconds statement to be less than 1 second or as a subsecond. Unlike
other MPCs such as MPC2E, a hold-down timer with a value less than 1 second
is not supported on MPC3Es and MPC4Es. This limitation exists because a
detection of the received loss-of-signal alarm can occur in less than a second
on these MPCs and a hold-down timer less than a second causes additional
processing overhead.

Default
Options

Interface transitions are not damped.

down millisecondsHold time to use when an interface transitions from up to down.

Junos OS advertises the transition within 100 milliseconds of the time value you
specify.
Range: 0 through 4,294,967,295
Default: 0 (interface transitions are not damped)

Copyright 2014, Juniper Networks, Inc.

599

Interfaces Fundamentals for Routing Devices

up millisecondsHold time to use when an interface transitions from down to up. Junos

OS advertises the transition within 100 milliseconds of the time value you specify.
Range: 0 through 4,294,967,295
Default: 0 (interface transitions are not damped)
Required Privilege
Level
Related
Documentation

600

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

advertise-interval on page 414

interfaces (for EX Series switches)

Physical Interface Damping Overview on page 143

Damping Shorter Physical Interface Transitions on page 149

Damping Longer Physical Interface Transitions on page 150

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

hold-time (SONET/SDH Defect Triggers)

Syntax
Hierarchy Level
Release Information
Description

hold-time up milliseconds down milliseconds;

[edit interfaces interface-name sonet-options trigger defect]

Statement introduced before Junos OS Release 7.4.

For ATM over SONET/SDH and SONET/SDH interfaces only, apply up and down hold
times to SONET/SDH defect triggers. When you apply a down hold time to a defect, the
defect must remain present for at least the hold-time period before the interface is
marked down. When you apply an up hold time to a defect, the defect must remain
absent for at least the hold-time period before the interface is marked up, assuming no
other defect is outstanding.

NOTE:

Default

Options

When up or down hold times are applied to SONET defect triggers of a

10-Gigabit Ethernet WAN-PHY interface, only the defects generated in the
WAN Interface Sublayer (WIS) are damped. Therefore, if the hold times
are applied to SONET defect triggers only, a 10-Gigabit Ethernet WAN-PHY
interface might be marked up or down because of the faults that are
generated in other layers, such as the Physical Coding Sublayer (PCS) or
Physical Medium Attachment Sublayer (PMA), 10 Gigabit Media
Independent Interface (XGMII) Extender Sublayer (XGXS), and Media
Access Control (MAC). To damp the interface up or down events of a
10-Gigabit Ethernet WAN-PHY interface, you need to apply up or down
hold-times for the interface at the [edit interfaces interface-name] hierarchy
level.

On M Series and T Series platforms with Channelized SONET IQ PICs and

Channelized SONET IQE PICs, the SONET defect alarm trigger hold-time
statement is not supported.

If you do not include this statement, when a defect is detected the interface is marked
down immediately, and when the defect becomes absent the interface is marked up
immediately.
down millisecondsHold time to wait before the interface is marked down.

Range: 1 through 65,534 milliseconds

Default: No hold time
up millisecondsHold time to wait before the interface is marked up.

Range: 1 through 65,534 milliseconds

Default: No hold time

Copyright 2014, Juniper Networks, Inc.

601

Interfaces Fundamentals for Routing Devices

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring SONET/SDH Defect Triggers

hold-time (Physical Interface) on page 599

host (Interfaces)
Syntax

Hierarchy Level

host hostname {
services severity-level;
facility-override facility-name;
log-prefix prefix-value;
port port-number;
}
[edit interfaces interface-name services-options syslog]

Release Information

Statement introduced before Junos OS Release 7.4.

Description

Specify the hostname for the system logging utility.

Options

hostnameName of the system logging utility host machine. This can be the local Routing

Engine or an external server address.

The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

602

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying Filters and Services to Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

iccp
Syntax

Hierarchy Level

Release Information

iccp {
traceoptions; {
file <filename> <files number> <match regular-expression> <microsecond-stamp>
<size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
local-ip-address ip address;
session-establishment-hold-time value;
authentication-key string;
peer ip-address {
local-ip-address ip address;
session-establishment-hold-time value;
authentication-key string;
redundancy-group-id-list redundancy-group-id-list;
liveness-detection;
}
}
[edit protocols iccp]
[edit logical-systems logical-system-name protocols iccp]

Statement introduced in Junos OS Release 10.0.

Support for logical systems introduced in Junos OS Release 14.1.

Description

Configure Interchassis Control Protocol (ICCP) between the multichassis link aggregation
group (MC-LAG) peers. ICCP replicates forwarding information, validates configurations,
and propagates the operational state of the MC-LAG members.

Default

If you do not include this statement, no ICCP protocol tracing operations are performed.

Options

traceoptionsSet Interchassis Control Protocol (ICCP) tracing options.

local-ip-addressSpecify the source address where the ICCP packet is routed.
session-establishment-hold-timeSpecify if the chassis takes over as the master at the

ICCP session.
authentication-key Specify TCP Message Digest 5 (MD5) option for an ICCP TCP session.
peer ip-addressSpecify the IP address of the peer that hosts an MC-LAG. You must

configure ICCP for both peers that host the MC-LAG.

redundancy-group-id-listSpecify the redundancy groups between two ICCP peers.
liveness-detectionSpecify Bidirectional Forwarding Detection (BFD) protocol options.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

603

Interfaces Fundamentals for Routing Devices

Related
Documentation

Configuring ICCP for MC-LAG on page 199

idle-cycle-flag
Syntax
Hierarchy Level

Release Information

Description

idle-cycle-flag value;
[edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name serial-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure the value that the DS0, E1, E3, T1, or T3 interface transmits during idle cycles.

NOTE: When configuring E1 or T1 interfaces on 10-port Channelized E1/T1 IQE

PICs, the idle-cycle-flag statement must be included at the [edit interfaces
e1-fpc/pic/port] or [edit interfaces t1-fpc/pic/port] hierarchy level as
appropriate.

Options

valueValue to transmit in the idle cycles:

flagsTransmit the value 0x7E.

onesTransmit the value 0xFF (all ones).

Default: Flags
Required Privilege
Level
Related
Documentation

604

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the E1 Idle Cycle Flag

Configuring the E3 Idle Cycle Flag

Configuring the T1 Idle Cycle Flag

Configuring the T3 Idle Cycle Flag

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

idle-timeout
Syntax
Hierarchy Level
Release Information
Description

Options

idle-timeout seconds;
[edit interfaces dln unit logical-unit-number dialer-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers with ISDN interfaces, configure the number of seconds the
link is idle before losing connectivity.
secondsTime for which the connection can remain idle. For interfaces configured to

use a filter for traffic, the idle timeout is based on traffic.

Range: 1 through 429497295
Default: 120 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Logical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

ieee802.1p
Syntax
Hierarchy Level

Release Information

Description

Options

ieee802.1p premium [ values ];

[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile input-priority-map]
[edit interfaces interface-name ether-options ethernet-switch-profile ethernet-policer-profile
input-priority-map]

Statement introduced before Junos Release 7.4.

Statement introduced in Junos OS Release 13.2 for the QFX Series.
For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, configure premium priority
values for IEEE 802.1p input traffic.
valuesDefine IEEE 802.1p priority values to be treated as premium.

Range: 0 through 7
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying an Input Priority Map

Copyright 2014, Juniper Networks, Inc.

605

Interfaces Fundamentals for Routing Devices

if-exceeding
Syntax

Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

606

if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
[edit firewall hierarchical-policer aggregate],
[edit firewall hierarchical-policer premium]

Statement introduced in Junos OS Release 9.5.

For M40e, M120, and M320 (with FFPC and SFPC) edge routers and T320, T640, and
T1600 core routers with Enhanced Intelligent Queuing (IQE) PICs, specify bandwidth
and burst limits for an aggregate level of a hierarchical policer.
Options are described separately.
firewallTo view this statement in the configuration.
firewall-controlTo add this statement to the configuration.

Applying Policers on page 210

Class of Service Feature Guide for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

igmp-snooping
Syntax

Hierarchy Level

Release Information
Description

igmp-snooping {
immediate-leave;
interface interface-name {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group ip-address {
source ip-address;
}
}
}
proxy {
source-address ip-address;
}
query-interval seconds;
query-last-member-interval seconds;
query-response-interval seconds;
robust-count number;
vlan vlan-id {
immediate-leave;
interface interface-name {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group ip-address {
source ip-address;
}
}
}
proxy {
source-address ip-address;
}
query-interval seconds;
query-last-member-interval seconds;
query-response-interval seconds;
robust-count number;
}
}
[edit bridge-domains bridge-domain-name protocols],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols]
[edit routing-instances routing-instance-name protocols]
[edit protocols]

Statement introduced in Junos OS Release 8.5.

Enable IGMP snooping on the router.

Copyright 2014, Juniper Networks, Inc.

607

Interfaces Fundamentals for Routing Devices

Default

IGMP snooping is disabled on the router.

Options

The statements are explained separately.

Required Privilege
Level
Related
Documentation

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

Understanding IGMP Snooping

IGMP Snooping in MC-LAG Active-Active on MX Series Routers Overview

ignore
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

ignore;
[edit interfaces interface-name sonet-options trigger defect]

Statement introduced before Junos OS Release 7.4.

For ATM over SONET/SDH and SONET/SDH interfaces only, ignore a specific SONET/SDH
defect trigger.
If you do not include this statement, all defects are honored with no hold time.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring SONET/SDH Defect Triggers

hold-time (Physical Interface) on page 599

ignore-all
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

608

ignore-all;
[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

Ignore all control leads. You can include the ignore-all statement in the configuration
only if you do not explicitly enable other signal handling options at the dte-options
hierarchy level.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

ignore-l3-incompletes
Syntax
Hierarchy Level

ignore-l3-incompletes;
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]

Release Information

Statement introduced in Junos OS Release 9.0.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

Ignore the counting of Layer 3 incomplete errors on Fast Ethernet, Gigabit Ethernet, and
10-Gigabit Ethernet interfaces.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ignoring Layer 3 Incomplete Errors

ilmi
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

ilmi;
[edit interfaces at-fpc/pic/port atm-options]

Statement introduced before Junos OS Release 7.4.

Enable the router to communicate with directly attached ATM switches and routers. The
router uses the VC 0.16 to communicate with the ATM switch or router. Once configured,
you can display the IP address and port number of an ATM switch or router using the
show interfaces interface-name switch-id command.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Communication with Directly Attached ATM Switches and Routers

show ilmi

show ilmi statistics

Copyright 2014, Juniper Networks, Inc.

609

Interfaces Fundamentals for Routing Devices

ima-group-options
Syntax

Hierarchy Level
Release Information

Description
Options

ima-group-options {
differential-delay number;
frame-length (32 |64 |128 |256);
frame-synchronization {
alpha number;
beta number;
gamma number;
}
minimum-links number;
symmetry (symmetrical-config-and-operation |
symmetrical-config-asymmetrical-operation);
test-procedure {
ima-test-start;
ima-test-stop;
interface name;
pattern number;
period number;
}
transmit-clock (common |independent);
version (1.0 |1.1);
}
[edit interfaces (t1-fpc/pic/port:m:n | e1-fpc/pic/port:n | t1|e1-fpc/pic/port)]

Statement introduced in Junos OS Release 10.0.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Specify IMA group options.
differential-delay msecMaximum differential delay among links in msec.

Range: 1 through 56
Default: The default value is 25
frame-length (32 |64 |128 |256)IMA frame length in number of cells.

Default: The default value is 128

frame-synchronizationIMA group frame synchronization selection.
alpha numberNumber of consecutive invalid ICP cells for IFSM.

Range: 1 through 2
Default: The default value is 2
beta numberNumber of consecutive errored ICP cells for IFSM.

Range: 1 through 2
Default: The default value is 2
gamma numberNumber of consecutive valid ICP cells for IFSM.

Range: 1 through 5

610

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Default: The default value is 1

minimum-links numberIMA group minimum active links.

Range: 1 through 8
Default: The default value is 1
symmetry (symmetrical-config-and-operation |
symmetrical-config-asymmetrical-operation)IMA group symmetry mode selection.
test-procedureSpecify an IMA link interface test.
ima-test-startStart IMA group test.
ima-test-stopStop IMA group test.
interface nameInterface name of the IMA link to test.
pattern numberIMA test pattern.

Range: 1 through 254

Default: The default value is 170
period secondsLength of IMA pattern test in seconds.

Range: 1 through 4294967294.

Default: The default value is 10
transmit-clock (common |independent)Transmit clock configuration.

Default: The default value is common

version (1.0 |1.1)IMA specification version.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM Support on Circuit Emulation PICs Overview

ima-link-options on page 612

Understanding Inverse Multiplexing for ATM

Copyright 2014, Juniper Networks, Inc.

611

Interfaces Fundamentals for Routing Devices

ima-link-options
Syntax
Hierarchy Level
Release Information

Description
Options
Required Privilege
Level
Related
Documentation

ima-link-options group g
[edit interfaces (t1-fpc/pic/port:m:n | e1-fpc/pic/port:n | t1|e1-fpc/pic/port)]

Statement introduced in Junos OS Release 10.0.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Specify an interface as a member of an IMA group.
group gImplying at-x/y/g.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM Support on Circuit Emulation PICs Overview

ima-group-options on page 610

Inverse Multiplexing for ATM (IMA) Overview

inactivity-timeout
Syntax
Hierarchy Level
Release Information
Description

Options

inactivity-timeout seconds;
[edit interfaces interface-name services-options]

Statement introduced before Junos OS Release 7.4.

For adaptive services interfaces, configure the inactivity timeout period for established
flows. The timeout configured in the application protocol definition overrides this value.
secondsTimeout period, in seconds.

Range: 4 through 86,400 seconds

Default: 30 seconds
Required Privilege
Level
Related
Documentation

612

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

incoming-called-number
Syntax
Hierarchy Level
Release Information

incoming-called-number number <reject>;

[edit interfaces br-pim/0/port isdn-options]

Statement introduced on Junos OS Release 7.5.

Description

On J Series Services Routers with interfaces configured for ISDN, screen incoming calls.
If the incoming number is configured, the call is accepted. If the reject option is specified
with the number, the call is rejected. If no numbers are configured, all calls are accepted.

Options

number(Optional) Incoming caller number. Multiple numbers can be configured, up to

a maximum of 30 entries. Only a precise match is a valid match, For example, the
configured caller number 1-222-333-4444 or 222-333-4444 will match the incoming
caller number 1-222-333-4444.
reject(Optional) Rejects the incoming number.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an ISDN Interface to Screen Incoming Calls

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

613

Interfaces Fundamentals for Routing Devices

incoming-map
Syntax

Hierarchy Level

Release Information
Description

incoming-map {
caller caller-number | accept-all;
}
[edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options]

Statement introduced in Junos OS Release 7.5.

On J Series Services Routers with interfaces configured for ISDN, specify the dialer to
accept incoming calls.
The statements are explained separately.

NOTE: The incoming-map statement is mandatory for the router to accept

any incoming ISDN calls.

Required Privilege
Level
Related
Documentation

614

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dial-In and Callback

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

indication
Syntax
Hierarchy Level

Release Information
Description
Options

indication (ignore | normal | require);

[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

For X.21 interfaces only, configure the from-DCE signal indication.
ignoreThe from-DCE signal is ignored.
normalNormal indication signal handling as defined by ITU-T Recommendation X.21.
requireThe from-DCE signal must be asserted.

Default: normal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

indication-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

indication-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

For X.21 interfaces only, configure the indication signal polarity.
positivePositive signal polarity.
negativeNegative signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

Copyright 2014, Juniper Networks, Inc.

615

Interfaces Fundamentals for Routing Devices

ingress-policer-overhead
Syntax
Hierarchy Level
Release Information
Description
Options

ingress-policer-overhead bytes;
[edit chassis fpc slot-number pic pic-number]

Statement introduced before Junos OS Release 11.1

Add the configured number of bytes to the length of a packet entering the interface.
bytesNumber of bytes added to a packet entering an interface.

Range: 0255 bytes

Default: 0
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ingress-shaping-overhead

Policer Overhead to Account for Rate Shaping Overview

Example: Configuring Policer Overhead to Account for Rate Shaping

Configuring a Policer Overhead

CoS on Enhanced IQ2 PICs Overview

ingress-rate-limit
Syntax
Hierarchy Level
Release Information
Description

Options

ingress-rate-limit rate;
[edit interfaces interface-name fastether-options]

Statement introduced before Junos OS Release 7.4.

Perform port-based rate limiting on ingress traffic arriving on Fast Ethernet 8-port, 12-port,
and 48-port PICs.
rateTraffic rate, in megabits per second (Mbps).

Range: 1 through 100 Mbps

Required Privilege
Level
Related
Documentation

616

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Ingress Rate Limit

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

init-command-string
Syntax
Hierarchy Level
Release Information
Description

init-command-string initialization-command-string;
[edit interfaces umd0 modem-options]

Statement introduced in Junos OS Release 8.2.

For J Series Services Routers, configure the command string used to initialize the USB
modem.
When you connect the USB modem to the USB port on a Services Router, the router
applies the modem AT commands configured in the init-command-string command to
the initialization commands on the modem.
For example, the initialization command string ATS0 = 2\n configures the USB modem
to pick up a call after 2 rings.
If you do not include the init-command-string statement, the router applies the default
initialization string to the modem.

Options

initialization-command-stringSpecify an initialization command string using the following

AT command values:

%C0Disables data compression.

&C1Disables reset of the modem when it loses the carrier signal.

&Q8Enables Microcom Networking Protocol (MNP) error control mode.

ATAttention. Informs the modem that a command follows.

E0Disables the display on the local terminal of commands issued to the modem

from the local terminal.

Q0Enables the display of result codes.

S0=0Disables the auto-answer feature, whereby the modem automatically answers

calls.

S7=45Instructs the modem to wait 45 seconds for a telecommunications service

provider (carrier) signal before terminating the call.

V1Displays result codes as words.

Default: AT S7=45 S0=0 V1 X4 &C1 E0 Q0 &Q8 %C0

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying a USB Modem Interface on J Series Routers on page 316

Copyright 2014, Juniper Networks, Inc.

617

Interfaces Fundamentals for Routing Devices

initial-route-check
Syntax
Hierarchy Level
Release Information
Description

Options

initial-route-check seconds;
[edit interfaces dln unit logical-unit-number dialer-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers with ISDN interfaces, allows the router to check whether
the primary route is up after the initial startup of the router is complete and the timer
expires.
secondsHow long to wait to check if the primary interface is up after the router comes

up.
Range: 1 through 300 seconds
Default: 120 seconds
Required Privilege
Level
Related
Documentation

618

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ISDN Interfaces Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

inner-tag-protocol-id
Syntax
Hierarchy Level

Release Information

Description

inner-tag-protocol-id tpid;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Configure the IEEE 802.1Q TPID value to rewrite for the inner tag.
All TPIDs you include in input and output VLAN maps must be among those you specify
at the [edit interfaces interface-name gigether-options ethernet-switch-profile
tag-protocol-id [ tpids ]] hierarchy level.
On MX Series routers, you can use this statement for Gigabit Ethernet IQ, IQ2 and IQ2-E
interfaces, and for aggregated Ethernet interfaces using Gigabit Ethernet IQ2 and IQ2-E
or 10-Gigabit Ethernet PICs.

Default
Required Privilege
Level
Related
Documentation

If the inner-tag-protocol-id statement is not configured, the TPID value is 0x8100.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Inner and Outer TPIDs and VLAN IDs

Copyright 2014, Juniper Networks, Inc.

619

Interfaces Fundamentals for Routing Devices

inner-vlan-id
Syntax
Hierarchy Level

Release Information

Description

inner-vlan-id number;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
For Gigabit Ethernet IQ, IQ2 and IQ2-E interfaces, and for aggregated Ethernet interfaces
using Gigabit Ethernet IQ2 and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers
or 100-Gigabit Ethernet Type 5 PIC with CFP, or on Ethernet interfaces on EX Series
switches, specify the VLAN ID to rewrite for the inner tag of the final packet.
You cannot include the inner-vlan-id statement with the swap statement, swap-push
statement, push-push statement, or push-swap statement and the inner-vlan-id statement
at the [edit interfaces interface-name unit logical-unit-numberoutput-vlan-map] hierarchy
level. If you include any of those statements in the output VLAN map, the VLAN ID in the
outgoing frame is rewritten to the inner-vlan-id statement you include at the [edit
interfaces interface-name unit logical-unit-number] hierarchy level.

Options

numberVLAN ID number.

Range: 0 through 4094

Required Privilege
Level
Related
Documentation

620

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Inner and Outer TPIDs and VLAN IDs

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

inner-vlan-id-range
Syntax
Hierarchy Level

Release Information
Description

Options

inner-vlan-id-range start start-id end end-id;

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],

Statement introduced in Junos OS Release 9.0.

The range of VLAN IDs to be used in the ATM-to-Ethernet interworking cross-connect.
Specify the starting VLAN ID and ending VLAN ID.
start-idThe lowest VLAN ID to be used.
end-idThe highest VLAN ID to be used.

Range: 32 through 4094

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM-to-Ethernet Interworking on page 262

input
Syntax

Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
[edit interfaces interface-name unit logical-unit-number family inet service],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service]

Statement introduced before Junos OS Release 7.4.

Define one or more input service sets and filters, and one postservice filter to be applied
to traffic.
The remaining statements are explained separately.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

621

Interfaces Fundamentals for Routing Devices

input-list
Syntax
Hierarchy Level

Release Information
Description
Options

input-list [ filter-names ];
[edit interfaces interface-name unit logical-unit-number family family filter],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family filter]

Statement introduced in Junos OS Release 7.6.

Apply a group of filters to evaluate when packets are received on an interface.
[ filter-names ]Name of a filter to evaluate when packets are received on the interface.

Up to 16 filters can be included in a filter input list.

Required Privilege
Level
Related
Documentation

622

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying a Filter to an Interface on page 219

Routing Policies, Firewall Filters, and Traffic Policers Feature Guide for Routing Devices

Junos OS Administration Library for Routing Devices

output-list on page 769

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

input-policer
Syntax
Hierarchy Level

Release Information

Description

Options

input-policer policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]

Statement introduced in Junos OS Release 8.2.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Apply a single-rate two-color policer to the Layer 2 input traffic at the logical interface.
The input-policer and input-three-color statements are mutually exclusive.
policer-nameName of the single-rate two-color policer that you define at the [edit
firewall] hierarchy level.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Two-Color and Three-Color Policers at Layer 2

Applying Layer 2 Policers to Gigabit Ethernet Interfaces

Configuring a Gigabit Ethernet Policer

input-three-color on page 625

layer2-policer on page 657

logical-interface-policer on page 683

output-policer on page 770

output-three-color on page 772

Copyright 2014, Juniper Networks, Inc.

623

Interfaces Fundamentals for Routing Devices

input-priority-map
Syntax

Hierarchy Level

Release Information

Description

input-priority-map {
ieee802.1p premium [ values ];
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile]
[edit interfaces interface-name ether-options ethernet-switch-profile
ethernet-policer-profile]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 13.2 for the QFX Series.
For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, define the input policer
priority map to be applied to incoming frames on this interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

624

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying an Input Priority Map

output-priority-map on page 771

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

input-three-color
Syntax
Hierarchy Level

Release Information

Description

Options
Required Privilege
Level
Related
Documentation

input-three-color policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]

Statement introduced in Junos OS Release 8.2.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Apply a single-rate or two-rate three-color policer to the Layer 2 input traffic at the logical
interface. The input-three-color and input-policer statements are mutually exclusive.
policer-nameName of the single-rate or two-rate three-color policer.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Two-Color and Three-Color Policers at Layer 2

Applying Layer 2 Policers to Gigabit Ethernet Interfaces

Configuring a Gigabit Ethernet Policer

input-policer on page 623

layer2-policer on page 657

logical-interface-policer on page 683

output-policer on page 770

output-three-color on page 772

Copyright 2014, Juniper Networks, Inc.

625

Interfaces Fundamentals for Routing Devices

input-vlan-map (Aggregated Ethernet)

Syntax

Hierarchy Level

Release Information
Description

input-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 8.2.

For aggregated Ethernet interfaces using Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ2
and IQ2-E interfaces and 100-Gigabit Ethernet Type 5 PIC with CFP only, define the
rewrite profile to be applied to incoming frames on this logical interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

626

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Stacking a VLAN Tag

output-vlan-map (Aggregated Ethernet) on page 773

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

input-vlan-map
Syntax

Hierarchy Level

Release Information

Description

input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

pop-pop, pop-swap, push-push, swap-push, and swap-swap statements introduced in
Junos OS Release 8.1.
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.
For Gigabit Ethernet IQ, 10-Gigabit Ethernet SFPP interfaces, 100-Gigabit Ethernet Type
5 PIC with CFP only as well as Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet,
and aggregated Ethernet interfaces, define the rewrite profile to be applied to incoming
frames on this logical interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Stacking a VLAN Tag

output-vlan-map on page 774

Configuring Q-in-Q Tunneling (CLI Procedure)

instance
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

instance vpls-instance-name;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain name]

Statement introduced in Junos OS Release 9.4.

Specify the VPLS instance of the default maintenance domain.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Maintenance Intermediate Points

maintenance-domain on page 699

Copyright 2014, Juniper Networks, Inc.

627

Interfaces Fundamentals for Routing Devices

interface (Hierarchical CoS Schedulers)

Syntax

interface interface-name;

Hierarchy Level

[edit interfaces interface-set interface-set-name]

Release Information

Statement introduced in Junos OS Release 8.5.

Description

Required Privilege
Level
Related
Documentation

628

Specify an interface that is a member of the interface set. Supported on Ethernet

interfaces on an MX Series router, Ethernet interfaces on IQ2E PIC on M Series and T
Series routers, and IP demux interfaces on an MX Series router.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Class of Service Feature Guide for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interface (IEEE 802.1x)

Syntax

Hierarchy Level
Release Information
Description

interface interface-id {
maximum-requests integer;
quiet-period seconds;
reauthentication (disable | interval seconds);
retries integer;
server-timeout seconds;
supplicant (single);
supplicant-timeout seconds;
transmit-period seconds;
}
[edit protocols dot1x authenticator]

Statement introduced in Junos OS Release 9.3.

Use this statement to configure the 802.1x Port-Based Network Access Control
protocol-specific Ethernet interface options.

Default

The default values are provided for the options below on the respective statement pages.

Options

maximum-requestsSpecify the maximum number of retransmission times for an EAPOL

Request packet to the client before it times out the authentication session.
quiet-periodSpecify the number of seconds the port remains in the wait state following

a failed authentication exchange with the client, before reattempting the

authentication.
reauthenticationIncludes two options:

disablePeriodic reauthentication of the client is disabled.

intervalSpecify the periodic reauthentication time interval.

retriesSpecify the number of tries after which the port remains in the wait state for
quiet-period seconds before reattempting the authentication.
server-timeoutSpecify the number of seconds the port waits for a reply when relaying

a response from the client to the authentication server before timing out and invoking
the server-fail action.
supplicant (single)Specify supplicant single mode. See the usage guidelines to configure

other modes.
supplicant-timeoutSpecify the number of seconds the port waits for a response when

relaying a request from the authentication server to the client before resending the
request.
transmit-periodSpecify the number of seconds the port waits before retransmitting the

initial EAPOL PDUs to the client.

Copyright 2014, Juniper Networks, Inc.

629

Interfaces Fundamentals for Routing Devices

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

interface (IEEE 802.1ag OAM Connectivity-Fault Management)

Syntax

Hierarchy Level

Release Information
Description

interface (interface-name | ((ge- | xe-) (fpc/pic/port | fpc/pic/port.unit-number |

fpc/pic/port.unit-number vlan vlan-id)));
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id]

Statement introduced in Junos OS Release 8.4.

For Ethernet interfaces on M320, MX Series, and T Series routers, configure IEEE 802.1ag
Operation, Administration, and Management (OAM) support.
For Gigabit Ethernet interfaces and 10-Gigabit Ethernet interfaces on MX Series routers,
configure IEEE 802.1ag Connectivity Fault Management (CFM) support on trunk interface
ports.

Options

interface-nameInterface to which the MEP is attached. It could be a physical Ethernet

interface, logical Ethernet interface, or on a specific VLAN of a trunk port interface

(MX Series only).
Required Privilege
Level
Related
Documentation

630

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Maintenance Endpoint

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interface (OAM Link-Fault Management)

Syntax

Hierarchy Level
Release Information

interface interface-name {
apply-action-profile profile-name;
link-discovery (active | passive);
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
}
[edit protocols oam ethernet link-fault-management]

Statement introduced in Junos OS Release 8.2.

Description

For Ethernet interfaces on M320, MX Series, and T Series routers, configure IEEE 802.3ah
Operation, Administration, and Management (OAM) support.

Options

interface interface-nameInterface to be enabled for IEEE 802.3ah link fault management

OAM support.
The remaining statements are described separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Enabling IEEE 802.3ah OAM Support

Copyright 2014, Juniper Networks, Inc.

631

Interfaces Fundamentals for Routing Devices

interface (Port Mirroring)

Syntax

Hierarchy Level
Release Information
Description
Options

interface interface-name {
next-hop address;
}
[edit forwarding-options port-mirroring family (inet | inet6) output]

Statement introduced before Junos OS Release 7.4.

Specify the output interface for sending copies of packets elsewhere to be analyzed.
interface-nameName of the interface.

The remaining statements are explained separately.

Usage Guidelines
Required Privilege
Level

See Configuring Port Mirroring.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

interface-down
Syntax
Hierarchy Level

Release Information
Description
Required Privilege
Level
Related
Documentation

632

interface-down;
[edit protocols oam ethernet connectivity-fault-management action-profile profile-name
default-actions]

Statement introduced in Junos OS Release 8.5.

Bring the interface down when a remote MEP connectivity failure is detected.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring a Connectivity Fault Management Action Profile

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interface-name
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

interface-name;
[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include],

Statement introduced in Junos OS Release 10.0.

Append the interface name and VLAN ID or stacked VLAN ID to the username string used
for authentication. The appended information takes the following format:

For single VLAN<interface-name>:<4-digit-vlan-id>

For stack VLANs<interface-name>:<4-digit-svlan-id>-<4-digit-vlan-id>

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

interface-none
Syntax
Hierarchy Level

interface-none;
[edit protocols protection-group ethernet-ring ring-name east-interface]
[edit protocols protection-group ethernet-ring ring-name west-interface]

Description
Required Privilege
Level
Related
Documentation

Designates port as not used for Ethernet ring protection.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Ethernet Ring Protection Using Ring Instances for Load Balancing

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

633

Interfaces Fundamentals for Routing Devices

interface-range
Syntax

Hierarchy Level
Release Information
Description

Options

interface-range name {
member-range interface-name-fpc/pic/port to interface-name-fpc/pic/port;
member interface-name-fpc/pic/port;
member interface-name-fpc/[low-high]/*;
member interface-name-fpc/[pic1,pic2,pic3...picN]/port
/*Common config is added as part of interface-range definition, as follows*/
mtu 256;
hold-time up 10;
ether-options {
flow-control;
speed {
100m;
}
802.3ad primary;
}
}
[edit interfaces]

Statement introduced in Junos OS Release 10.0.

Specify a set of identical interfaces as an interface group, to which you can apply a
common configuration to the entire set of interfaces. This group can consist of both
lexical member ranges of interfaces specified using the member-range
interface-type-fpc/pic/port to xx-fpc/pic/port option (regex not supported), and of
individual or non-sequential members using the member interface-type-fpc/pic/port
option (with regex support to specify the fpc/pic/port values).
member-rangeAdds interfaces in lexical order. Regex is not supported.
Format:member-range <start-range> to <end-range>
Example:member-range ge-0/0/0 to ge-4/0/40;
memberTo add individual interfaces or multiple interfaces using regex.
Format:member <list of interface names>
Example:member ge-0/0/0;
member ge-0/1/1;
member ge-0/*/*;
member ge-0/[1-10]/0;
member ge-1/[1,3,6,10]/12

Required Privilege
Level

634

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Related
Documentation

Configuring Interface Ranges on page 83

interface-transmit-statistics
Syntax
Hierarchy Level
Release Information
Description

interface-transmit-statistics;
[edit interface interface-name]

Statement introduced in Junos OS Release 11.4 R3 for MX Series devices.

Configure the interface to report the transmitted load statistics. If this statement is not
included in the configuration, the interface statistics show the offered load on the
interface, and not the actual transmitted load.

NOTE: This is not supported on Enhanced IQ (IQE) and Enhanced IQ2 (IQ2E)
PICs.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Improvements to Interface Transmit Statistics Reporting on page 1001

show interfaces (Gigabit Ethernet) on page 1189

interface-set (Ethernet Interfaces)

Syntax

Hierarchy Level
Release Information
Description

interface-set interface-set-name {
interface ethernet-interface-name {
(unit unit-number | vlan-tags-outer vlan-tag);
}
}
[edit interfaces]

Statement introduced in Junos OS Release 8.5.

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.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

interface-set (Hierarchical Schedulers)

Copyright 2014, Juniper Networks, Inc.

635

Interfaces Fundamentals for Routing Devices

interface-set (IP Demux Interfaces)

Syntax

Hierarchy Level
Release Information
Description

interface-set interface-set-name {
interface interface-name {
unit unit-number;
}
}
[edit interfaces]

Statement introduced in Junos OS Release 9.2.

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.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos Subscriber Access Configuration Guide

Interfaces Fundamentals for Routing Devices

interface-shared-with
Syntax
Hierarchy Level

Release Information

Description

Options

interface-shared-with psdn;
[edit interfaces ge-fpc/pic/slot unit logical-unit-number],
[edit interfaces so-fpc/pic/slot unit logical-unit-number],
[edit interfaces xe-fpc/pic/slot unit logical-unit-number]

Statement introduced in Junos OS Release 9.3.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Assign a logical interface under a shared physical interface to a Protected System Domain
(PSD).
nPSD identification as a numeric value.

Range: 1 through 31
Required Privilege
Level

view-levelTo view this statement in the configuration.

control-levelTo add this statement to the configuration.

Related
Documentation

636

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interface-status-tlv
Syntax
Hierarchy Level

Release Information
Description

Options

interface-status-tlv [ down lower-layer-down ];

[edit protocols oam ethernet connectivity-fault-management action-profile profile-name
event]

Statement introduced in Junos OS Release 9.6.

Defines an action-profile consisting of various events and the action. Based on values of
interface-status-tlv in the received CCM packets, specific action such as interface-down
can be taken using action-profile options.
downWhen the incoming CCM packet contains interface status TLV with value down,

the action will be triggered for this action-profile.

lower-layer-downWhen the incoming CCM packet contains interface status TLV with

value lower-layer-down, the action will be triggered for this action-profile.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Remote MEP Action Profile Support

Copyright 2014, Juniper Networks, Inc.

637

Interfaces Fundamentals for Routing Devices

interface-switch
Syntax

Hierarchy Level

Release Information
Description

interface-switch connection-name {
interface interface-name.unit-number;
}
[edit logical-systems logical-system-name protocols connections],
[edit protocols connections]

Statement introduced before Junos OS Release 7.4.

Configure Layer 2 switching cross-connects. The cross-connect is bidirectional, so packets
received on the first interface are transmitted out the second interface, and those received
on the second interface are transmitted out the first.
For Layer 2 switching cross-connects to work, you must also configure MPLS.

Options

connection-nameConnection name (up to 128 characters in Junos 12.3 and later).

interface interface-name.unit-numberInterface name. Include the logical portion of the

name, which corresponds to the logical unit number.

Required Privilege
Level
Related
Documentation

638

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration

Configuring the CCC Connection for Layer 2 Switching Cross-Connects

Defining the Connection for Switching Cross-Connects on page 261

Junos OS MPLS Applications Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interface-type (Interfaces)
Syntax
Hierarchy Level

Release Information
Description
Options

interface-type (bc | coc1 | ct1 | ct3 | dc | ds |so | t1 | t3);

[edit interfaces interface-range name no-partition],
[edit interfaces interface-range name partition partition-number],
[edit interfaces interface-range name partition partition-number oc-slice oc-slice-range],
[edit interfaces interface-range name partition partition-number timeslot timeslot-range]

Statement introduced before Junos OS Release 7.4.

For IQ and IQE interfaces only, configure the sublevel interface type.
bcDualPort Channelized E1 and T1 ISDN PRI interface type. You can specify this

interface type at the [edit interfaces interface-name partition partition-number timeslot

timeslot-range] hierarchy level to create a bearer (B) channel bc-pim/0/port:channel
interface for each time you want to function as an ISDN PRI B-channel.
coc1Channelized OC1 interface type. You can specify this interface type at the [edit
interfaces interface-name partition partition-number oc-slice oc-slice-range
interface-type coc12-fpc/pic/port] hierarchy level.
ct1Channelized T1 interface type. You can specify this interface type at the [edit
interfaces interface-name partition partition-number interface-type
ct3-fpc/pic/port<:channel>] hierarchy level.
ct3Channelized T3 interface type. You can specify this interface type at the [edit
interfaces interface-name partition partition-number oc-slice oc-slice-range
interface-type coc1-fpc/pic/port:channel no-partition] hierarchy level.
dcDual-Port Channelized E1 and T1 ISDN PRI interface type. You can specify this interface

type at the [edit interfaces interface-name partition partition-number timeslot

timeslot-range] hierarchy level to create a (D) channel dc-pim/0/port to control the
B-channels.
dsDS0 interface type. You can specify this interface type at the [edit interfaces
interface-namepartition partition-number interface-type (ce1-fpc/pic/port |
ct1-fpc/pic/port<:channel>)] hierarchy level.
soSONET/SDH interface type. You can specify this interface type at the [edit interfaces
interface-name partition partition-number oc-slice oc-slice-range interface-type
coc12-fpc/pic/port] hierarchy level.
t1T1 interface type. You can specify this interface type at the [edit interfaces
interface-name partition partition-number oc-slice oc-slice-range interface-type
(coc12-fpc/pic/port | coc1-fpc/pic/port)] hierarchy level.
t3T3 interface type. You can specify this interface type at the [edit interfaces
interface-name partition partition-number oc-sliceoc-slice-range interface-type
(coc12-fpc/pic/port | coc1-fpc/pic/port:channel no-partition)] hierarchy level.

Copyright 2014, Juniper Networks, Inc.

639

Interfaces Fundamentals for Routing Devices

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Channelized E1 IQ and IQE Interfaces Overview

Channelized OC12/STM4 IQ and IQE Interfaces Overview

Configuring Channelized T3 IQ Interfaces

interfaces
Syntax
Hierarchy Level
Release Information
Description
Default

Required Privilege
Level
Related
Documentation

640

interfaces { ... }
[edit]

Statement introduced before Junos OS Release 7.4.

Configure interfaces on the router or switch.
The management and internal Ethernet interfaces are automatically configured. You
must configure all other interfaces.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Physical Interface Configuration Statements Overview on page 56

Configuring Aggregated Ethernet Link Protection

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interfaces (Static and Dynamic Subscribers)

Syntax

interfaces {
interface-name {
unit logical-unit-number {
auto-configure {
agent-circuit-identifier {
dynamic-profile profile-name;
}
}
family family {
access-concentrator name;
address address;
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
adf {
counter;
input-precedence precedence;
not-mandatory;
output-precedence precedence;
rule rule-value;
}
input filter-name (
precedence precedence;
shared-name filter-shared-name;
}
output filter-name {
precedence precedence;shared-name filter-shared-name;
}
}
max-sessions number;
max-sessions-vsa-ignore;
rpf-check {
mode loose;
}
service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-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>;
unnumbered-address interface-name <preferred-source-address address>;

Copyright 2014, Juniper Networks, Inc.

641

Interfaces Fundamentals for Routing Devices

}
filter {
input filter-name;
shared-name filter-shared-name;
output filter-name;
shared-name filter-shared-name;
}
ppp-options {
chap;
pap;
}
proxy-arp;
vlan-id;
vlan-tags outer [tpid].vlan-id [inner [tpid].vlan-id];
}
vlan-tagging;
}
interface-set interface-set-name {
interface interface-name {
unit logical unit number {
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
}
}
pppoe-underlying-options {
max-sessions number;
}
}
demux0 {
unit logical-unit-number {
demux-options {
underlying-interface interface-name
}
family family {
access-concentrator name;
address address;
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
demux-source {
source-prefix;
}
filter{
input filter-name (
precedence precedence;
shared-name filter-shared-name;
}
output filter-name {
precedence precedence;
shared-name filter-shared-name;
}
}
mac-validate (loose | strict):
max-sessions number;

642

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

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;
vlan-tags outer [tpid].vlan-id [inner [tpid].vlan-id];
}
}
pp0 {
unit logical-unit-number {
keepalives interval seconds;
no-keepalives;
pppoe-options {
underlying-interface interface-name;
server;
}
ppp-options {
authentication [ authentication-protocols ];
chap {
challenge-length minimum minimum-length maximum maximum-length;
}
pap;
}
family inet {
unnumbered-address interface-name;
address address;
service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-service-filter filter-name;
}
output {
service-set service-set-name {
service-filter filter-name;
}
}
}
filter {
input filter-name {
precedence precedence;
shared-name filter-shared-name;
}
output filter-name {
precedence precedence;

Copyright 2014, Juniper Networks, Inc.

643

Interfaces Fundamentals for Routing Devices

shared-name filter-shared-name;
}
}
}
}
}
}

Hierarchy Level
Release Information
Description
Options

[edit dynamic-profiles profile-name]

Statement introduced in Junos OS Release 9.2.

Define interfaces for dynamic profiles.
interface-nameThe 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.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

644

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

Configuring Dynamic Subscriber Interfaces Using IP Demux Interfaces in Dynamic Profiles

Configuring Dynamic PPPoE Subscriber Interfaces Using Dynamic Profiles

Configuring Dynamic VLANs Based on Agent Circuit Identifier Information

DHCP Subscriber Interface Overview

Configuring Subscribers over Static Interfaces

Demultiplexing Interface Overview on page 281

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

interleave-fragments
Syntax
Hierarchy Level

Release Information
Description

interleave-fragments;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For link services interfaces only, interleave long packets with high-priority packets.
Allows small delay-sensitive packets, such as Voice over IP (VoIP) packets, to interleave
with long fragmented packets. This minimizes the latency of delay-sensitive packets.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

interval
Syntax
Hierarchy Level

Release Information

Description
Options

interval (10m | 10s | 1m | 1s | 100ms | 10ms);

[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name continuity-check]

Statement introduced in Junos OS Release 8.4.

Ten milliseconds option introduced in Junos OS Release 9.1.
The time between continuity check messages.
10m10 minutes.
10s10 seconds.
1m1 minute.
1s1 second.
100ms100 milliseconds.
10ms10 milliseconds.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Continuity Check Protocol

Copyright 2014, Juniper Networks, Inc.

645

Interfaces Fundamentals for Routing Devices

inverse-arp
Syntax
Hierarchy Level

Release Information

Description

Default
Required Privilege
Level
Related
Documentation

646

inverse-arp;
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number family inet address address
multipoint-destination destination],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet address address multipoint-destination destination]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
For ATM encapsulation, enable responses to receive inverse ATM ARP requests. For
Frame Relay encapsulation, enable responses to receive inverse Frame Relay ARP
requests.
Inverse ARP is disabled on all ATM and Frame Relay interfaces.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Inverse ATM1 or ATM2 ARP

Configuring Inverse Frame Relay ARP

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

invert-data
Syntax
Hierarchy Level

Release Information

Description

invert-data;
[edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name e3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Invert the transmission of unused data bits on the DS0, E1, E3, and T1 interface.

NOTE: When configuring E1 or T1 interfaces on 10-port Channelized E1/T1 IQE

PICs, the invert-data statement must be included at the [edit interfaces
e1-fpc/pic/port] or [edit interfaces t1-fpc/pic/port] hierarchy level as
appropriate.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring E1 Data Inversion

Configuring E3 Data Inversion

Configuring T1 Data Inversion

Copyright 2014, Juniper Networks, Inc.

647

Interfaces Fundamentals for Routing Devices

ipsec-sa
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

648

ipsec-sa sa-name;
[edit interfaces es-fpc/pic/port unit logical-unit-number family inet],
[edit logical-systems logical-system-name interfaces es-fpc/pic/port unit logical-unit-number
family inet]

Statement introduced before Junos OS Release 7.4.

Specify the IP Security (IPsec) security association (SA) name associated with the
interface.
sa-nameIPsec security association name.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

isdn-options
Syntax

Hierarchy Level

Release Information

Description

isdn-options {
bchannel-allocation (ascending | descending);
calling-number number;
incoming-called-number number <reject>;
spid1 spid-string;
spid2 spid-string;
static-tei-val value;
switch-type (att5e | etsi | ni1 | ntdms100 | ntt);
t310 seconds;
tei-option (first-call | power-up);
}
[edit interfaces br-pim/0/port],
[edit interfaces ct1-pim/0/port],
[edit interfaces ce1-pim/0/port]

Statement introduced before Junos OS Release 7.4.

bchannel-allocation option added in Junos OS Release 8.3.
For J Series Services Routers only. Specify the ISDN options for configuring ISDN interfaces
for group and user sessions.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

Allocating B-Channels for Dialout

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

649

Interfaces Fundamentals for Routing Devices

iteration-count
Syntax
Hierarchy Level

Release Information
Description

Options

iteration-count count-value;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-name]

Statement introduced in Junos OS Release 11.1.

Configure the number of iterations for which the connection partakes in the iterator for
acquiring SLA measurements.
count-valueNumber of iterations for which the connection should partake in the iterator

for acquiring SLA measurements.

Range: 1 through 65,535
Default: 0 (or infinite iterations)
Required Privilege
Level
Related
Documentation

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

sla-iterator-profile on page 880

Configuring a Remote MEP with an Iterator Profile

iteration-period
Syntax
Hierarchy Level

Release Information

Description

Options

iteration-period iteration-period-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]

Statement introduced in Junos OS Release 11.1.

Statement introduced in Junos OS Release 11.4 for EX Series switches.
Configure the iteration period, which is the maximum number of cycles per iteration (that
is, the number of connections registered to an iterator cannot exceed this value).
iteration-period-valueMaximum number of cycles per iteration.

Range: 1 through 2000

Default: 2000
Required Privilege
Level
Related
Documentation

650

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

Configuring an Iterator Profile

Configuring an Iterator Profile on a Switch (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

keep-address-and-control
Syntax
Hierarchy Level

Release Information
Description

Default

Required Privilege
Level
Related
Documentation

keep-address-and-control;
[edit interfaces interface-name unit logical-unit-number family ccc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family ccc]

Statement introduced before Junos OS Release 7.4.

For interfaces with encapsulation type PPP CCC, do not remove the address and control
bytes before encapsulating the packet into a tunnel.
If you do not include this statement, address and control bytes are removed before
encapsulating the packet into a tunnel.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Disabling the Removal of Address and Control Bytes on page 209

Copyright 2014, Juniper Networks, Inc.

651

Interfaces Fundamentals for Routing Devices

keepalives
Syntax
Hierarchy Level

Release Information
Description

keepalives <interval seconds> <down-count number> <up-count number>;

[edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Enable the sending of keepalives on a physical interface configured with PPP, Frame
Relay, or Cisco HDLC encapsulation.
For ATM2 IQ interfaces only, you can enable keepalives on a logical interface unit if the
logical interface is configured with one of the following PPP over ATM encapsulation
types:

atm-ppp-llcPPP over AAL5 LLC encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

Default

Sending of keepalives is enabled by default. The default keepalive interval is 10 seconds

for PPP, Frame Relay, or Cisco HDLC. The default down-count is 3 and the default
up-count is 1 for PPP or Cisco HDLC.

Options

down-count numberThe number of keepalive packets a destination must fail to receive

before the network takes down a link.

Range: 1 through 255
Default: 3
interval secondsThe time in seconds between successive keepalive requests.

Range: 1 through 32767 seconds

Default: 10 seconds
up-count numberThe number of keepalive packets a destination must receive to change

a links status from down to up.

Range: 1 through 255
Default: 1
Required Privilege
Level
Related
Documentation

652

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Keepalives on page 124

Configuring Frame Relay Keepalives

Applying PPP Attributes to L2TP LNS Subscribers Per Inline Service Interface

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

key
Syntax
Hierarchy Level

Release Information
Description

Options

key number;
[edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel]

Statement introduced before Junos OS Release 7.4.

For Adaptive Services PICs on M Series routers (except the M320 and M120 routers),
identify an individual traffic flow within a tunnel, as defined in RFC 2890, Key and Sequence
Number Extensions to GRE.
numberValue of the key.

Range: 0 through 4,294,967,295

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

l2tp-interface-id
Syntax

Hierarchy Level

Release Information
Description
Options

l2tp-interface-id name;
(dedicated | shared);
[edit interfaces sp-fpc/pic/port unit logical-unit-number interface],
[edit logical-systems logical-system-name interfaces sp-fpc/pic/port unit logical-unit-number
interface]

Statement introduced before Junos OS Release 7.4.

Specify the L2TP options for configuring logical interfaces for group and user sessions.
(dedicated | shared)Specifies whether a logical interface can host one (dedicated) or
multiple (shared) sessions at one time.
nameInterface identifier that must be replicated at the [edit access profile name]

hierarchy level.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

653

Interfaces Fundamentals for Routing Devices

lacp (802.3ad)
Syntax

Hierarchy Level

Release Information

Description

lacp {
traceoptions {
file lacpd;
flag all;
}
ppm (centralized | distributed);
}
[edit interfaces interface-name fastether-options 802.3ad],
[edit interfaces interface-name gigether-options 802.3ad]

Statement introduced in Junos OS Release 9.3.

The ppm (centralized | distributed) option introduced in Junos OS Release 9.4.
For aggregated Ethernet interfaces only, configure the Link Aggregation Control Protocol
(LACP).
On MX and T Series routers you can specify distributed or centralized periodic packet
management (PPM).

Default

If you do not specify lacp as either active or passive, LACP remains passive.
If you do not specify ppm as either centralized or distributed, PPM is distributed.

Options

activeInitiate transmission of LACP packets.

passiveRespond to LACP packets.

ppmSet PPM to centralized or distributed.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

654

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring LACP for Aggregated Ethernet Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

lacp (Aggregated Ethernet)

Syntax

Hierarchy Level

Release Information

Description

lacp {
(active | passive);
admin-key key;
accept-data;
fast-failover;
link-protection {
disable;
(revertive |non-revertive);
}
periodic interval;
system-id mac-address;
system-priority priority;
}
[edit interfaces aex aggregated-ether-options]
[edit logical-systems logical-system-name interfaces aeX aggregated-ether-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
fast-failover option introduced in Junos OS Release 12.2.
Support for logical systems introduced in Junos OS Release 14.1.
Configure the Link Aggregation Control Protocol (LACP) for aggregated Ethernet interfaces
only.
When you configure the accept-data statement at the [edit interfaces aeX
aggregated-ether-options lacp] hierarchy level, the router processes packets received on
a member link irrespective of the LACP state if the aggregated Ethernet bundle is up.

NOTE: When you configure the accept-data statement at the [edit interfaces
aeX aggregated-ether-options lacp] hierarchy level, this behavior occurs:

Default
Options

By default, the accept-data statement is not configured when LACP is

enabled.

You can configure the accept-data statement to improve convergence and

reduce the number of dropped packets when member links in the bundle
are enabled or disabled.

When LACP is down and a member link receives packets, the router or
switch does not process packets as defined in the IEEE 802.1ax standard.
According to this standard, the packets should be dropped, but they are
processed instead because the accept-data statement is configured.

If you do not specify LACP as either active or passive, LACP remains passive.
activeInitiate transmission of LACP packets.

Copyright 2014, Juniper Networks, Inc.

655

Interfaces Fundamentals for Routing Devices

admin-key numberSpecify an administrative key for the router or switch.

NOTE: You must also configure multichassis link aggregation (MC-LAG)

when you configure the admin-key.

fast-failoverSpecify to override the IEEE 802.3ad standard and allow the standby link

to receive traffic. Overriding the default behavior facilitates subsecond failover.

passiveRespond to LACP packets.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

656

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring LACP for Aggregated Ethernet Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

layer2-policer
Syntax

Hierarchy Level

Release Information

Description

layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],

Statement introduced in Junos OS Release 8.2.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
For 1-Gigabit Ethernet and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces on M Series, MX
Series, and T Series routers, and for aggregated Ethernet, Gigabit Ethernet, and 10-Gigabit
Ethernet interfaces on EX Series switches, apply Layer 2 logical interface policers. The
following policers are supported:

Two-color

Single-rate tricolor marking (srTCM)

Two-rate tricolor marking (trTCM)

Two-color and tricolor policers are configured at the [edit firewall] hierarchy level.
Options

input-policer policer-nameTwo-color input policer to associate with the interface. This

statement is mutually exclusive with the input-three-color statement.

input-three-color policer-nameTricolor input policer to associate with the interface. This

statement is mutually exclusive with the input-policer statement.

output-policer policer-nameTwo-color output policer to associate with the interface.

This statement is mutually exclusive with the output-three-color statement.

output-three-color policer-nameTricolor output policer to associate with the interface.

This statement is mutually exclusive with the output-policer statement.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying Layer 2 Policers to Gigabit Ethernet Interfaces

Configuring Gigabit Ethernet Two-Color and Tricolor Policers

Copyright 2014, Juniper Networks, Inc.

657

Interfaces Fundamentals for Routing Devices

lcp-max-conf-req
Syntax
Hierarchy Level
Release Information
Description

Options

lcp-max-conf-req number
[edit interfaces so-fpc/pic/port unit number ppp-options]

Statement introduced in Junos OS Release 9.6.

Set the maximum number of LCP Configure-Requests to be sent, after which the router
goes to LCP down state.
numberFrom 0 to 65,535, where 0 means send infinite LCP Configure-Requests, and

any other value specifies the maximum number LCP Configure-Requests to send
and then stop sending.
Default254

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the LCP Configure-Request Maximum Sent on page 177

ppp-options on page 812

lcp-restart-timer
Syntax
Hierarchy Level

Release Information

lcp-restart-timer milliseconds;
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-nameunit logical-unit-number
ppp-options]

Statement introduced in Junos OS Release 8.1.

Description

For interfaces with PPP, PPP TCC, PPP over Ethernet, PPP over ATM, and PPP over Frame
Relay encapsulations, configure a restart timer for the Link Control Protocol (LCP)
component of a PPP session.

Options

millisecondsThe time, in milliseconds, between successive LCP configuration requests.

Range: 20 through 10000 milliseconds

Default: 3 seconds
Required Privilege
Level
Related
Documentation

658

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Restart Timers on page 176

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

level
Syntax
Hierarchy Level

Release Information

Description
Options

level number;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name]

Statement introduced in Junos OS Release 8.4.

Statement introduced in junos os release 12.1X48 for PTX Series Packet Transport Routers.
A number used in CFM messages to identify the maintenance association.
numberA number used to identify the maintenance domain to which the CFM message

belongs.
Range: 0 through 7
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Maintenance Domain Level

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

Copyright 2014, Juniper Networks, Inc.

659

Interfaces Fundamentals for Routing Devices

line-encoding
Syntax
Hierarchy Level

Release Information

Description

line-encoding (ami | b8zs);

[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name t1-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Set the line encoding format on the T1 interface.

NOTE: When configuring CT1 interfaces on the 10-port Channelized E1/T1

IQE PIC, the line-encoding statement must be included at the [edit interfaces
ct1-fpc/pic/port] hierarchy level.

Default
Options

The default line encoding is B8ZS.

amiUse Alternate Mark Inversion (AMI) line encoding.
b8zsUse bipolar with 8-zeros substitution (B8ZS) line encoding.

Required Privilege
Level
Related
Documentation

660

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring T1 Line Encoding

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

line-protocol
Syntax
Hierarchy Level
Release Information
Description
Options

Required Privilege
Level
Related
Documentation

line-protocol protocol;
[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

For serial interfaces only, configure the line protocol.
protocolYou can specify the one of the following line protocols:

eia530Line protocol EIA-530

v.35Line protocol V.35

x.21Line protocol X.21

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Line Protocol on page 304

line-rate
Syntax
Hierarchy Level

Release Information
Description
Options

line-rate line-rate;
[edit interfaces interface-name shdsl-options],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options]

Statement introduced in Junos OS Release 7.4.

For J Series Services Routers only, configure the SHDSL line rate.
line-rateSHDSL line rate, in Kbps. Possible values are:

2-wire (Kbps): 192, 256, 320, 384, 448, 512, 576, 640, 704, 768, 832, 896, 960, 1024, 1088,
1152, 1216, 1280, 1344, 1408, 1472, 1536, 1600, 1664, 1728, 1792, 1856, 1920, 1984, 2048,
2112, 2176, 2240, 2304, auto
4-wire (Kbps): 384, 512, 640, 768, 896, 1024, 1152, 1280, 1408, 1536, 1664, 1792, 1920,
2048, 2176, 2304, 2432, 2560, 2688, 2816, 2944, 3072, 3200, 3328, 3456, 3584, 3712,
3840, 3968, 4096, 4224, 4352, 4480, 4608
Default: For 2-wire mode, auto; for 4-wire mode, 4608 Kbps
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-SHDSL Overview

Copyright 2014, Juniper Networks, Inc.

661

Interfaces Fundamentals for Routing Devices

linear-red-profile
Syntax
Hierarchy Level

Release Information
Description

Default

Options
Required Privilege
Level
Related
Documentation

662

linear-red-profile profile-name;
[edit interfaces at-fpc/pic/port atm-options scheduler-maps map-name forwarding-class
class-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, assign a linear RED profile to a specified forwarding class.
To define the linear RED profiles, include the linear-red-profiles statement at the [edit
interfaces at-fpc/pic/port atm-options] hierarchy level.
If you do not include either the epd-threshold or the linear-red-profile statement in the
forwarding class configuration, the Junos OS uses an EPD threshold based on the available
bandwidth and other parameters.
profile-nameName of the linear RED profile.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an ATM Scheduler Map

linear-red-profiles on page 663

Configuring Scheduler Maps on ATM Interfaces

epd-threshold

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

linear-red-profiles
Syntax

Hierarchy Level
Release Information
Description

Options

linear-red-profiles profile-name {
high-plp-threshold percent;
low-plp-threshold percent;
queue-depth cells;
}
[edit interfaces at-fpc/pic/port atm-options]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define CoS virtual circuit 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.
profile-nameName of the drop profile.

The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

Configuring Linear RED Profiles on ATM Interfaces

link-adjacency-loss
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

link-adjacency-loss;
[edit protocols oam ethernet link-fault-management action-profile event]

Statement introduced in Junos OS Release 8.5.

Loss of adjacency with IEEE 802.3ah link-fault management peer event. When included,
the loss-of-adjacency event triggers the action specified under the action statement.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Monitoring the Loss of Link Adjacency

Copyright 2014, Juniper Networks, Inc.

663

Interfaces Fundamentals for Routing Devices

link-discovery
Syntax
Hierarchy Level
Release Information
Description

Options

link-discovery (active | passive);

[edit protocols oam ethernet link-fault-management interface interface-name]

Statement introduced in Junos OS Release 8.2.

For Ethernet interfaces on EX Series switches, and M320, M120, MX Series, and T Series
routers, specify the discovery mode used for IEEE 802.3ah Operation, Administration,
and Management (OAM) support. The discovery process is triggered automatically when
OAM 802.3ah functionality is enabled on a port. Link monitoring is done when the interface
sends periodic OAM PDUs.
(active | passive)Passive or active mode. In active mode, the interface discovers and

monitors the peer on the link if the peer also supports IEEE 802.3ah OAM functionality.
In passive mode, the peer initiates the discovery process. Once the discovery process
is initiated, both sides participate in discovery.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Link Discovery

link-down
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

664

link-down;
[edit protocols oam ethernet link-fault-management ]

Statement introduced in Junos OS Release 8.5.

Mark the interface down for transit traffic.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Specifying the Actions to Be Taken for Link-Fault Management Events

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

link-event-rate
Syntax

Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
[edit protocols oam ethernet link-fault-management action-profile event]

Statement introduced in Junos OS Release 8.5.

Configure the number of link-fault management events per second.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Threshold Values for Fault Events in an Action Profile

Copyright 2014, Juniper Networks, Inc.

665

Interfaces Fundamentals for Routing Devices

link-fault-management
Syntax

Hierarchy Level
Release Information
Description

link-fault-management {
action-profile profile-name {
action {
link-down;
send-critical-event;
syslog;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
interface interface-name {
apply-action-profile profile-name;
link-discovery (active | passive);
loopback-tracking;
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
}
}
[edit protocols oam ethernet]

Statement introduced in Junos OS Release 8.2.

For Ethernet interfaces on M320, M120, MX Series, and T Series routers and EX Series
switches, specify fault signaling and detection for IEEE 802.3ah Operation, Administration,
and Management (OAM) support.
The remaining statements are explained separately.

Required Privilege
Level

666

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Related
Documentation

Enabling IEEE 802.3ah OAM Support

link-layer-overhead
Syntax
Hierarchy Level

Release Information
Description

Options

link-layer-overhead percent;
[edit interfaces interface-name mlfr-uni-nni-bundle-options],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For AS PIC or MultiServices PIC link services IQ interfaces (lsq) only, configure the
percentage of total bundle bandwidth to be set aside for link-layer overhead.
percentPercentage of total bundle bandwidth to be set aside for link-layer overhead.

Range: 0 through 50 percent

Default: 4 percent
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

667

Interfaces Fundamentals for Routing Devices

link-mode
Syntax
Hierarchy Level

Release Information

Description
Options

link-mode mode;
[edit interfaces interface-name],
[edit interfaces interface-name ether-options],
[edit interfaces ge-pim/0/0 switch-options switch-port port-number]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Set the devices link connection characteristic.
modeLink characteristics:

automaticLink mode is negotiated. This is the default for EX Series switches.

full-duplexConnection is full duplex.

half-duplexConnection is half duplex.

Default: Fast Ethernet interfaces, except the J Series ePIM Fast Ethernet interfaces, can
operate in either full-duplex or half-duplex mode. The routers management Ethernet
interface, fxp0 or em0, the built-in Fast Ethernet interfaces on the FIC (M7i router),
and the Gigabit Ethernet ports on J Series Services Routers with uPIMs installed and
configured for access switching mode autonegotiate whether to operate in full-duplex
or half-duplex mode. Unless otherwise noted here, all other interfaces operate only
in full-duplex mode.

NOTE: On J Series ePIM Fast Ethernet interfaces, if you specify half-duplex

(or if full-duplex mode is not autonegotiated), the following message is
written to the system log: "Half-duplex mode not supported on this PIC,
forcing full-duplex mode."

NOTE:

On EX4300 switches, the interfaces operate in full-duplex mode only.

On EX Series switches, if no-auto-negotiation is specified in [edit interfaces

interface-name ether-options], you can select only full-duplex or
half-duplex. If auto-negotiation is specified, you can select any mode.

NOTE: Member links of an aggregated Ethernet bundle must not be explicitly

configured with a link mode. You must remove any such link-mode
configuration before committing the aggregated Ethernet configuration.

668

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Link Characteristics on Ethernet Interfaces

Understanding Management Ethernet Interfaces on page 10

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

669

Interfaces Fundamentals for Routing Devices

link-protection
Syntax

Hierarchy Level

Release Information

Description

linkprotection {
disable;
(revertive |non-revertive);
}
[edit interfaces aex aggregated-ether-options]
[edit interfaces aex aggregated-ether-options lacp]

Statement introduced in Junos OS Release 8.3.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for disable, revertive, and non-revertive statements added in Junos OS Release
9.3.
On the router, for aggregated Ethernet interfaces only, configure link protection. In addition
to enabling link protection, a primary and a secondary (backup) link must be configured
to specify what links egress traffic should traverse. To configure primary and secondary
links on the router, include the primary and backup statements at the [edit interfaces
ge-fpc/pic/port gigether-options 802.3ad aex] hierarchy level or the [edit interfaces
fe-fpc/pic/port fastether-options 802.3ad aex] hierarchy level.
On the switch, you can configure either Junos OS link protection for aggregated Ethernet
interfaces or the LACP standards link protection for aggregated Ethernet interfaces.
For Junos OS link protection, specify link-protection at the following hierarchy levels:

[edit interfaces ge-fpc/pic/port ether-options 802.3ad aex]

[edit interfaces xe-fpc/pic/port ether-options 802.3ad aex]

For LACP standards link protection, specify link-protection at the following hierarchy
levels:

For global LACP link protection, specify at [edit chassis aggregated-devices ethernet
lacp]

For a specific aggregated Ethernet interface, specify at [edit interfaces aeX

aggregated-ether-options lacp]

To disable link protection, use the delete interface ae aggregate-ether-options

link-protection statement at the [edit interfaces aex aggregated-ether-options] hierarchy
level or the [edit interfaces aex aggregated-ether-options lacp]] hierarchy level.
Options
Required Privilege
Level
Related
Documentation

670

The statements are explained separately.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Aggregated Ethernet Link Protection

Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

link-speed (Aggregated Ethernet)

Syntax
Hierarchy Level

Release Information

Description
Options

link-speed speed;
[edit interfaces aex aggregated-ether-options],
[edit interfaces interface-range name aggregated-ether-options],
[edit interfaces interface-range name aggregated-sonet-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
For aggregated Ethernet interfaces only, set the required link speed.
speedFor aggregated Ethernet links, you can specify speed 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).
Aggregated Ethernet links on the M120 router can have one of the following speeds:

100mLinks are 100 Mbps.

10gLinks are 10 Gbps.

1gLinks are 1 Gbps.

oc192Links are OC192 or STM64c.

Aggregated Ethernet links on EX Series switches can be configured to operate at one of

the following speeds:

10mLinks are 10 Mbps.

100mLinks are 100 Mbps.

1gLinks are 1 Gbps.

10gLinks are 10 Gbps.

Aggregated Ethernet links on T Series routers can be configured to operate at one of the
following speeds:

100gLinks are 100 Gbps.

100mLinks are 100 Mbps.

10gLinks are 10 Gbps.

1gLinks are 1 Gbps.

40gLinks are 40 Gbps.

50gLinks are 50 Gbps.

80gLinks are 80 Gbps.

8gLinks are 8 Gbps.

Copyright 2014, Juniper Networks, Inc.

671

Interfaces Fundamentals for Routing Devices

Required Privilege
Level
Related
Documentation

mixedLinks are of various speeds.

oc192Links are OC192.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Aggregated Ethernet Interfaces Overview

Configuring Aggregated Ethernet Link Speed

Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles

Configuring Aggregated Ethernet Links (CLI Procedure)

Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200

Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch

link-speed (Aggregated SONET/SDH)

Syntax
Hierarchy Level
Release Information

Description
Options

link-speed (speed | mixed);

[edit interfaces asx aggregated-sonet-options]

Statement introduced before Junos OS Release 7.4.

mixed option added in Release 8.0.
For aggregated SONET/SDH interfaces only, set the required link speed.
speedAggregated SONET/SDH links can have one of the following speed values.

oc3Links are OC3c or STM1c.

oc12Links are OC12c or STM4c.

oc48Links are OC48c or STM16c.

oc192Links are OC192c or STM64c.

oc768Links are OC768c or STM256c.

mixedFor aggregated SONET/SDH links on T Series routers, you can mix interface

speeds in SONET/SDH aggregation bundles. Interface speeds from OC3 through

OC768 are supported.
Required Privilege
Level
Related
Documentation

672

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Aggregated Ethernet Link Speed

Configuring Aggregated SONET/SDH Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

linktrace
Syntax

Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
[edit protocols oam ethernet connectivity-fault-management]

Statement introduced in Junos OS Release 8.5.

Configure connectivity fault management linktrace parameters.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Linktrace Protocol in CFM

Copyright 2014, Juniper Networks, Inc.

673

Interfaces Fundamentals for Routing Devices

lmi (Frame Relay)

Syntax

Hierarchy Level
Release Information
Description
Options

lmi {
lmi-type (ansi | itu | c-lmi);
n391dte number;
n392dce seconds;
n392dte number;
n393dce number;
n393dte number;
t391dte number;
t392dce seconds;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Set Frame Relay keepalive parameters.
n391dteDTE full status polling interval.

Range: 1 through 255

Default: 6
n392dceDCE error threshold, in number of errors.

Range: 1 through 10
Default: 3
n392dteDTE error threshold, in number of errors.

Range: 1 through 10
Default: 3
n393dceDCE monitored event-count.

Range: 1 through 10
Default: 4
n393dteDTE monitored event-count.

Range: 1 through 10
Default: 4
t391dteDTE polling timer.

Range: 5 through 30 seconds

Default: 10 seconds
t392dceDCE polling timer.

Range: 5 through 30 seconds

Default: 15 seconds
The remaining statements are explained separately.

674

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Tunable Keepalives for Frame Relay LMI

lmi-type on page 677

mlfr-uni-nni-bundle-options on page 710

Copyright 2014, Juniper Networks, Inc.

675

Interfaces Fundamentals for Routing Devices

lmi (Ethernet OAM)

Syntax

Hierarchy Level
Release Information
Description

Options

lmi {
status-counter count;
polling-verification-timer value;
interface name {
uni-id uni-name;
status-counter number;
polling-verification-timer value;
evc-map-type (all-to-one-bundling | bundling | service-multiplexing);
evc evc-name {
default-evc;
vlan-list vlan-id-list;
}
}
}
[edit protocols oam ethernet]

Statement introduced in Junos OS Release 9.5.

On routers with ge, xe, or ae interfaces, configure an OAM Ethernet local management
interface.
status-counter countStatus counter (N393), defaults to 4.
interface namePolling verification timer (T392), defaults to 15 seconds.
uni-id uni-name(Optional) Defaults to the physical interface name.
status-counter number(Optional) Defaults to a global value.
polling-verification-timer value(Optional) Defaults to a global value.
evc-map-type (all-to-one-bundling | bundling | service-multiplexing)Specify the Ethernet

virtual connection (EVC) map type.

evc evc-nameSpecify the name of the EVC.
default-evcSet the specified EVC as the default EVC.
vlan-list vlan-id-listSpecify a group of VLANs to assign to the EVC.

Required Privilege
Level
Related
Documentation

676

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Ethernet Local Management Interface

evcs on page 561

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

lmi-type
Syntax
Hierarchy Level

Release Information
Description

lmi-type (ansi | itu | c-lmi);

[edit interfaces interface-name lmi],
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

Set Frame Relay Local Management Interface (LMI) type.

NOTE: Consortium LMI is supported on all MPCs and I-chip based FPCs.

Options

ansiUse ANSI T1.167 Annex D LMIs.

ituUse ITU Q933 Annex A LMIs.
c-lmiUse Consortium LMI.

Default: ansi
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Frame Relay Keepalives

mlfr-uni-nni-bundle-options on page 710

lmi (Frame Relay) on page 674

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

677

Interfaces Fundamentals for Routing Devices

load-interval
Syntax
Hierarchy Level

Release Information
Description

Options

load-interval seconds;
[edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers with ISDN logical interfaces, specify the interval used to
calculate the average load on the network. By default, the average interface load is
calculated every 60 seconds.
secondsNumber of seconds at which the average load calculation is triggered.

Range: 20 through 180, in 10-second intervals

Default: 60 seconds
Required Privilege
Level
Related
Documentation

678

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Logical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

load-threshold
Syntax
Hierarchy Level

Release Information

load-threshold percent;
[edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options]

Statement introduced before Junos OS Release 7.4.

Description

On J Series Services Routers with ISDN logical interfaces, specify the bandwidth threshold
percentage used for adding interfaces. Another link is added to the multilink bundle when
the load reaches the threshold value you set. Specify a percentage between 0 and 100.

Options

percentBandwidth threshold percentage used for adding interfaces. When set to 0, all

available channels are dialed.

Range: 0 through 100 seconds
Default: 100 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Bandwidth on Demand

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

679

Interfaces Fundamentals for Routing Devices

local-name
Syntax

local-name name;

Hierarchy Level

[edit interfaces interface-name ppp-options chap],

[edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options chap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options pap]
[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

Statement introduced before Junos OS Release 7.4.

Support for PAP added in Junos OS Release 8.3.
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
14.2.

Description

For CHAP authentication, the value sent in CHAP challenge and response packets on a
per interface basis. For PAP authentication, the local hostname for sending PAP
authentication requests.
For ATM2 IQ interfaces only, you can configure a CHAP local name on the logical interface
unit if the logical interface is configured with one of the following PPP over ATM
encapsulation types:

Default

atm-ppp-llcPPP over AAL5 LLC encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

For CHAP authentication, if you do not include the local-name statement in the
configuration, the interface sends the routers system hostname in CHAP challenge and
response packets.

NOTE: The name range is from 1 through 8 characters.

Required Privilege
Level
Related
Documentation

680

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Challenge Handshake Authentication Protocol on page 126

Configuring the PPP Password Authentication Protocol on page 129

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

local-password
Syntax
Hierarchy Level

Release Information
Description
Required Privilege
Level
Related
Documentation

local-password password;
[edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options pap]

Statement introduced in Junos OS Release 8.3.

Configure the host password for sending PAP requests.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the Local Password on page 180

Configuring the PPP Password Authentication Protocol on page 129

lockout
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

lockout;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Configure a lockout of protection, forcing the use of the working circuit and locking out
the protect circuit regardless of anything else.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Switching Between the Working and Protect Circuits

Copyright 2014, Juniper Networks, Inc.

681

Interfaces Fundamentals for Routing Devices

log-prefix (Interfaces)
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

log-prefix prefix-value;
[edit interfaces interface-name services-options syslog host hostname]

Statement introduced before Junos OS Release 7.4.

Set the system logging prefix value.
prefix-valueSystem logging prefix value.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Configuring System Logging for Services Interfaces

logical-interface-fpc-redundancy (Aggregated Ethernet Subscriber Interfaces)

Syntax
Hierarchy Level
Release Information

Description

logical-interface-fpc-redundancy;
[edit interfaces aenumber aggregated-ether-options]

Statement introduced in Junos OS Release 11.2.

Statement introduced in Junos OS Release 13.2R2 for EX Series switches.
Provide module redundancy for demux subscribers on aggregated Ethernet bundles
configured with targeted distribution. Backup links for a subscriber are chosen on a
different EQ DPC or MPC from the primary link, based on the link with the fewest number
of subscribers among the links on different modules. If all links are on a single module
when this is configured, backup links are not provisioned.
By default, link redundancy is provided for the aggregated Ethernet bundle.

Required Privilege
Level
Related
Documentation

682

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Link and Module Redundancy for Demux Subscribers in an Aggregated Ethernet
Interface

Configuring Module Redundancy for a Virtual Chassis

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

logical-interface-policer
Syntax
Hierarchy Level

Release Information

Description

logical-interface-policer;
[edit dynamic-profiles profile-name firewall policer policer-name],
[edit dynamic-profiles profile-name firewall three-color-policer name],
[edit firewall atm-policeratm-policer-name]
[edit firewall policer policer-name],
[edit firewall policer policer-template-name],
[edit firewall three-color-policer policer-name],
[edit logical-systems logical-system-name firewall policer policer-name],
[edit logical-systems logical-system-name firewall three-color-policer name]

Statement introduced before Junos OS Release 7.4.

Support at the [edit firewall three-color-policer policer-name] hierarchy level introduced
in Junos OS Release 8.2.
Logical systems support introduced in Junos OS Release 9.3.
Support at the [edit dynamic-profiles ... policer policer-name] and [edit dynamic-profiles
... three-color-policer name] hierarchy levels introduced in Junos OS Release 11.4.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Configure a logical interface policer.

NOTE: Starting in Junos OS Release 12.2R2, on T Series Core Routers only,

you can configure an MPLS LSP policer for a specific LSP to be shared across
different protocol family types. You must include the logical-interface-policer
statement to do so.

Required Privilege
Level
Related
Documentation

firewallTo view this statement in the configuration.

firewall-controlTo add this statement to the configuration.

Two-Color and Three-Color Logical Interface Policers

Traffic Policer Types

Configuring Tricolor Marking Policers

action

Configuring Gigabit Ethernet Two-Color and Tricolor Policers

action on page 407

Copyright 2014, Juniper Networks, Inc.

683

Interfaces Fundamentals for Routing Devices

logical-systems
Syntax

Hierarchy Level
Release Information

Description
Options
Required Privilege
Level
Related
Documentation

logical-systems {
logical-system-name {
...logical-system-configuration...
}
}
[edit]

Statement introduced before Junos OS Release 7.4.

Statement name changed from logical-routers in Junos OS Release 9.3.
Configure a logical system.
logical-system-nameName of the logical system.

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

Logical Systems Feature Guide for Routing Devices

long-buildout
Syntax
Hierarchy Level
Release Information
Description

(long-buildout | no-long-buildout);
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Configure the T3 line buildout. A T3 interface has two settings for the T3 line buildout: a
short setting, which is less than 255 feet (68 meters), and a long setting, which is greater
than 255 feet and shorter than 450 feet (137 meters).
This statement applies to copper-cable-based T3 interfaces only. You cannot configure
a line buildout for a DS3 channel on a channelized OC12 interface, which runs over
fiber-optic cable.

Default

Required Privilege
Level
Related
Documentation

684

A T3 interface uses the short line buildout setting (no-long-buildout) for wires shorter
than 255 feet (68 meters).
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the T3 Line Buildout

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

loop-timing
Syntax
Hierarchy Level

Release Information
Description

(loop-timing | no-loop-timing);
[edit interfaces ct3-fpc/pic/port t3-options],
[edit interfaces e1-fpc/pic/port:0 sonet-options],
[edit interfaces stm1-fpc/pic/port sonet-options]

Statement introduced before Junos OS Release 7.4.

For channelized IQ interfaces and non-IQ channelized STM1 interfaces only, configure
the SONET/SDH or DS3-level clocking source.

NOTE: On M Series, MX Series, and T Series routers, under E1 channels, loop

timing can be configured only at channel 0. When you configure on channel
0, it is applicable on all channels as internal by default.

Options

loop-timingConfigure loop timing (external) clocking.

no-loop-timingConfigure line timing (internal) clocking.

Default: no-loop-timing
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Channelized IQ and IQE SONET/SDH Loop Timing

Configuring the Channelized T3 Loop Timing

clocking on page 469

Copyright 2014, Juniper Networks, Inc.

685

Interfaces Fundamentals for Routing Devices

loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3)

Syntax
Hierarchy Level

Release Information

Description

loopback (local | payload | remote);

[edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name dsl-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name shdsl-options},
[edit interfaces interface-name sonet-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure a loopback connection. To turn off the loopback capability, remove the loopback
statement from the configuration.

NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1

IQE PICs, the loopback statement must be included with the local or remote
option at the [edit interfaces ce1-fpc/pic/port] or [edit interfaces
ct1-fpc/pic/port] hierarchy level as appropriate.
When configuring T1 interfaces on 10-port Channelized E1/T1 IQE PICs, the
loopback statement must be included with the payload option at the [edit
interfaces t1-fpc/pic/port] hierarchy level.

NOTE: When configuring CE1 or CT1 interfaces on the 16-port Channelized

E1/T1 MIC (MIC-3D-16CHE1-T1-CE), you must include the loopback statement
at the [edit interfaces ce1-fpc/pic/port] hierarchy level, or [edit interfaces
ct1-fpc/pic/port]

To configure loopback on channelized IQ and IQE PICs, SONET/SDH level, use the
sonet-options loopback statement local and remote options at the controller interface
(coc48, cstm16, coc12, cstm4, coc3, cstm1). It is ignored for path-level interfaces
so-fpc/pic/port or so-fpc/pic/port:channel.
Options

localLoop packets, including both data and timing information, back on the local routers

PIC. NxDS0 IQ interfaces do not support local loopback.

686

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

payloadFor channelized T3, T1, and NxDS0 IQ interfaces only, loop back data only

(without clocking information) on the remote routers PIC. With payload loopback,
overhead is recalculated. Neither ATM-over-asymmetrical digital subscriber line
(ADSL) interfaces nor ATM-over-SHDSL interfaces support payload loopback.
remoteLoop packets, including both data and timing information, back on the remote

routers interface card. NxDS0 IQ interfaces do not support remote loopback.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring E3 and T3 Parameters on ATM Interfaces

Configuring E1 Loopback Capability

Configuring E3 Loopback Capability

Configuring SONET/SDH Loopback Capability to Identify a Problem as Internal or External

Configuring SHDSL Operating Mode on an ATM Physical Interface

Configuring T1 Loopback Capability

Configuring T3 Loopback Capability

feac-loop-respond on page 574

Copyright 2014, Juniper Networks, Inc.

687

Interfaces Fundamentals for Routing Devices

loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet)

Syntax
Hierarchy Level

Release Information

Description

(loopback | no-loopback);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-range name ether-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
For aggregated Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet
interfaces, enable or disable loopback mode.

NOTE:

Required Privilege
Level
Related
Documentation

688

By default, local aggregated Ethernet, Fast Ethernet, Tri-Rate Ethernet

copper, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces connect to a
remote system.

IPv6 Neighbor Discovery Protocol (NDP) addresses are not supported on

Gigabit Ethernet interfaces when loopback mode is enabled on the
interface. That is, if the loopback statement is configured at the [edit
interfaces ge-fpc/pic/port gigether-options] hierarchy level, an NDP address
cannot be configured at the [edit interfaces ge-fpc/pic/port unit
logical-unit-number family inet6 address] hierarchy level.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Ethernet Loopback Capability

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

loopback (Serial)
Syntax
Hierarchy Level
Release Information
Description
Default
Options

Required Privilege
Level
Related
Documentation

loopback mode;
[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure a loopback connection.
If you do not include this statement, there is no loopback connection.
modeYou can specify the one of the following loopback modes:

dce-localFor EIA-530 interfaces only, loop packets back on the local DCE.

dce-remoteFor EIA-530 interfaces only, loop packets back on the remote DCE.

localLoop packets back on the local routers PIC.

remoteLoop packets back on the line interface unit (LIU).

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Loopback Capability on page 314

Copyright 2014, Juniper Networks, Inc.

689

Interfaces Fundamentals for Routing Devices

loopback-clear-timer
Syntax
Hierarchy Level

Release Information

loopback-clear-timer seconds;
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-nameunit logical-unit-number
ppp-options]

Statement introduced in Junos OS Release 8.5.

Description

For interfaces with PPP, PPP TCC, PPP over Ethernet, PPP over ATM, and PPP over Frame
Relay encapsulations, configure a loop detection clear timer for the Link Control Protocol
(LCP) component of a PPP session.

Options

secondsThe time in seconds to wait before the loop detection flag is cleared if it is not

cleared by the protocol.

Range: 1 through 60 seconds
Default: 9 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Clear Loop Detected Timer on page 177

loss-priority
Syntax
Hierarchy Level

Release Information
Description
Options

loss-priority (high | low);

[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map classifier premium forwarding-class
class-name]

Statement introduced before Junos OS Release 7.4.

Specify the packet loss priority value.
highPacket has high loss priority.
lowPacket has low loss priority.

Required Privilege
Level
Related
Documentation

690

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying an Output Priority Map

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

loss-threshold
Syntax
Hierarchy Level

Release Information

loss-threshold number;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name continuity-check]

Statement introduced in Junos OS Release 8.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers.

Description

Specify the number of continuity check messages lost before marking the remote MEP
as down.

Options

numberThe number of continuity check messages that can be lost before the remote

MEP is considered down.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Continuity Check Protocol

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

low-plp-max-threshold
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

low-plp-max-threshold percent;
[edit interfaces at-fpc/pic/port atm-options linear-red-profiles profile-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define the drop profile fill-level for the low PLP CoS VC.
When the fill level exceeds the defined percentage, all packets are dropped.
percentFill-level percentage when linear RED is applied to cells with PLP.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

high-plp-max-threshold on page 596

low-plp-threshold on page 692

Configuring Linear RED Profiles on ATM Interfaces

high-plp-max-threshold

queue-depth on page 831

Copyright 2014, Juniper Networks, Inc.

691

Interfaces Fundamentals for Routing Devices

low-plp-threshold
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

692

low-plp-threshold percent;
[edit interfaces at-fpc/pic/port atm-options linear-red-profiles profile-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define the CoS VC drop profile fill-level percentage when
linear RED is applied to cells with low PLP. When the fill level exceeds the defined
percentage, packets with low PLP are randomly dropped by RED. This statement is
mandatory.
percentFill-level percentage when linear RED is applied to cells with low PLP.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

high-plp-max-threshold on page 596

high-plp-threshold on page 593

Configuring Linear RED Profiles on ATM Interfaces

high-plp-max-threshold

high-plp-threshold

low-plp-max-threshold on page 691

queue-depth on page 831

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

lowest-priority-defect
Syntax

Hierarchy Level

Release Information
Description

Options

lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect | rem-err-xcon

| xcon)
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id]

Statement introduced in Junos OS Release 10.0.

Specify the lowest priority defect that is allowed to generate a Fault Alarm whenever
CFM detects a defect. This configuration is done at the MEP level.
Specify one of the following lowest priority defect options:
all-defectsAllows all defects.
err-xconAllows only erroneous CCM and cross-connect CCM defects.
mac-rem-err-xconAllows only MAC, not receiving CCM, erroneous CCM, and

cross-connect defects.
no-defectAllows no defects.
rem-err-xconAllows only not receiving CCM, erroneous CCM, and cross-connect CCM

defects.
xconAllows only cross-connect CCM defects.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Maintenance End Point Lowest Priority Defect

Copyright 2014, Juniper Networks, Inc.

693

Interfaces Fundamentals for Routing Devices

lsq-failure-options
Syntax

Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

lsq-failure-options {
no-termination-request;
[trigger-link-failure interface-name];
}
[edit interfaces lsq-fpc/pic/port]

Statement introduced in Junos OS Release 7.4.

For AS PIC or MultiServices PIC link services IQ (lsq) interfaces only, define the failure
recovery option settings.
The remaining statements are explained separately.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

mac
Syntax
Hierarchy Level
Release Information
Description

mac mac-address;
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Set the MAC address of the interface.
Use this statement at the [edit interfaces ... ps0] hierarchy level to configure the MAC
address for a pseudowire logical device that is used for subscriber interfaces over
point-to-point MPLS pseudowires.

Options

mac-addressMAC address. Specify the MAC address as six hexadecimal bytes in one

of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn. For example,

0011.2233.4455 or 00:11:22:33:44:55.
Required Privilege
Level
Related
Documentation

694

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the MAC Address on the Management Ethernet Interface

Configuring a Pseudowire Subscriber Logical Interface Device

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mac-address (Accept Source Mac)

Syntax

mac-address mac-address policer;

Hierarchy Level

[edit interfaces interface-name unit logical-unit-number accept-source-mac],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
accept-source-mac ]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For Gigabit Ethernet IQ and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), for Gigabit Ethernet
DPCs on MX Series routers, and 100-Gigabit Ethernet Type 5 PIC with CFP, specify a
remote MAC address on which to count incoming and outgoing packets.

Options

mac-addressMAC address. Specify the MAC address as six hexadecimal bytes in one

of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn. For example,

0011.2233.4455 or 00:11:22:33:44:55.
policerMAC policer. For more information, see policer (MAC).

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring MAC Address Filtering

mac-address (VLAN and Stacked VLAN Interfaces)

Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

mac-address;
[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include],

Statement introduced in Junos OS Release 10.0.

Specify that the client hardware address (chaddr) from the incoming DHCP discover
packet be concatenated with the username during the subscriber authentication process.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

Copyright 2014, Juniper Networks, Inc.

695

Interfaces Fundamentals for Routing Devices

mac-learn-enable
Syntax
Hierarchy Level
Release Information
Description

(mac-learn-enable | no-mac-learn-enable);
[edit interfaces interface-name gigether-options ethernet-switch-profile]

Statement introduced before Junos OS Release 7.4.

For Gigabit Ethernet IQ and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), for Gigabit Ethernet
DPCs on MX Series routers, and 100-Gigabit Ethernet Type 5 PIC with CFP configure
whether source and destination MAC addresses are dynamically learned:

mac-learn-enableAllow the interface to dynamically learn source and destination

MAC addresses.

no-mac-learn-enableProhibit the interface from dynamically learning source and

destination MAC addresses.

MAC address learning is based on source addresses. You can start accounting for traffic
after there has been traffic sent from the MAC address. Once the MAC address is learned,
the frames and bytes transmitted to or received from the MAC address can be tracked.

NOTE: When you gather interfaces into a bridge domain, the

no-mac-learn-enable statement at the [edit interfaces interface-name
gigether-options ethernet-switch-profile] hierarchy level is not supported. You
must use the no-mac-learning statement at the [edit bridge-domains
bridge-domain-name bridge-options interface interface-name] hierarchy level
to disable MAC learning on an interface in a bridge domain. For information
on disabling MAC learning for a bridge domain, see MX Series Layer 2
Configuration Guide.

Required Privilege
Level
Related
Documentation

696

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring MAC Address Filtering

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mac-validate
Syntax
Hierarchy Level
Release Information

mac-validate (loose | strict);

[edit interfaces interface-name unit logical-unit-number family family]

Statement introduced in Junos OS Release 9.3.

Description

Enable IP and MAC address validation for static Ethernet, IP demux interfaces, and VLAN
demux interfaces. Supported on MX Series routers only.

Options

looseForwards incoming packets when both the IP source address and the MAC source

address match one of the trusted address tuples. Drops packets when the IP source
address matches one of the trusted tuples, but the MAC address does not match
the MAC address of the tuple. Continues to forward incoming packets when the
source address of the incoming packet does not match any of the trusted IP
addresses.
strictForwards incoming packets when both the IP source address and the MAC source

address match one of the trusted address tuples. Drops packets when the MAC
address does not match the tuple's MAC source address, or when IP source address
of the incoming packet does not match any of the trusted IP addresses.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

MAC Address Validation on Static Ethernet Interfaces Overview

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Copyright 2014, Juniper Networks, Inc.

697

Interfaces Fundamentals for Routing Devices

maintenance-association
Syntax

Hierarchy Level

Release Information

Description
Options

maintenance-association ma-name {
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
continuity-check {
hold-interval minutes;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number;
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name]

Statement introduced in Junos OS Release 8.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers.
Configure the name of the maintenance association in IEEE-compliant format.
ma-nameThe name of the maintenance association within the maintenance domain.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

698

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Creating a Maintenance Association

Configuring a Maintenance Endpoint

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

maintenance-domain
Syntax

Hierarchy Level
Release Information

Description
Options

maintenance-domain domain-name {
bridge-domain name <vlan-id [ vlan-ids ]>;
instance vpls-instance-name;
level number;
maintenance-association ma-name {
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
continuity-check {
hold-interval minutes;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
mip-half-function(none | default | explicit);
name-format (character-string | none | dns | mac+2oct);
}
virtual-switch name {
bridge-domain name <vlan-id [ vlan-ids ]>;
}
}
[edit protocols oam ethernet connectivity-fault-management]

Statement introduced in Junos OS Release 8.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers.
Configure the name of the maintenance domain in IEEE-compliant format.
domain-nameName of the maintenance domain.

The remaining statements are explained separately.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

699

Interfaces Fundamentals for Routing Devices

Related
Documentation

Creating the Maintenance Domain

Configuring a Maintenance Endpoint

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

master-only
Syntax
Hierarchy Level

Release Information

Description
Required Privilege
Level
Related
Documentation

700

master-only;
[edit groups rex interfaces (fxp0 | em0) unit logical-unit-number family family address],
[edit groups rex logical-systems logical-system-name interfaces fxp0 unit logical-unit-number
family family address],
[edit interfaces (fxp0 | em0) unit logical-unit-number family family address],
[edit logical-systems logical-system-name interfaces fxp0 unit logical-unit-number family
family address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
Configure the IP address to be used when the Routing Engine is the current master.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring a Consistent Management IP Address

CLI User Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

maximum-contexts
Syntax
Hierarchy Level

Release Information
Description
Options

maximum-contexts number <force>;

[edit interfaces interface-name unit logical-unit-number compression rtp],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
compression rtp]

Statement introduced in Junos OS Release 7.5.

Specify the maximum number of RTP contexts to accept during negotiation.
numberMaximum number of contexts.
force(Optional) Requires the PIC to use the value specified for maximum RTP contexts,

regardless of the negotiated value. This option allows the software to interoperate
with Junos OS Releases that base the RTP context value on link speed.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

maximum-requests
Syntax
Hierarchy Level
Release Information
Description

Options

maximum-requests times;
[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Specify the maximum number of retransmission times of an EAPOL Request packet to
the client before it times out the authentication session.
timesSpecify the maximum number of retransmission times.

Range: 1 through 10 times

Default: 2 times
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

interface (IEEE 802.1x) on page 629

Copyright 2014, Juniper Networks, Inc.

701

Interfaces Fundamentals for Routing Devices

maximum-vcs
Syntax
Hierarchy Level
Release Information
Description

maximum-vcs maximum-vcs;
[edit interfaces at-fpc/pic/port atm-options vpi vpi-identifier]

Statement introduced before Junos OS Release 7.4.

For ATM1 interfaces, configure the maximum number of virtual circuits (VCs) allowed
on a virtual path (VP). When configuring ATM1 interfaces on the router, you must include
this statement.
For a configured virtual path identifier (VPI), valid virtual channel identifier (VCI) numbers
are from 0 through (maximum-vcs value 1). VCI numbers 0 through 31 are reserved by
the ATM Forum. It is recommended that you use a VCI number higher than 31 when
connecting to an ATM switch.

Options

maximum-vcsMaximum number of VCs on the VP.

Range: 1 through 4090

Required Privilege
Level
Related
Documentation

702

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Maximum Number of ATM1 VCs on a VP

multipoint-destination on page 724

promiscuous-mode on page 822

vci on page 964

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mc-ae
Syntax

Hierarchy Level

Release Information

Description

Options

mc-ae {
chassis-id chassis-id;
events {
iccp-peer-down {
force-icl-down;
prefer-status-control-active;
}
}
mc-ae-id mc-ae-id;
mode (active-active | active-standby);
redundancy-group group-id;
revert-time revert-time;
status-control (active | standby);
switchover-mode (non-revertive |revertive);
init-delay-time seconds;
}
[edit interfaces aeX aggregated-ether-options]
[edit logical-systems logical-system-name interfaces aeX aggregated-ether-options]

Statement introduced in Junos OS Release 9.6 for MX Series routers.

events statement introduced in Junos OS Release 11.4R4 for MX Series routers.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
prefer-status-control-active statement introduced in Junos OS Release 13.2R1 for EX
Series switches.
init-delay-time seconds statement introduced in Junos OS Release 13.2R3 for EX Series
switches.
switchover-mode and revert-time statements introduced in Junos OS Release 13.3.
Support for logical systems introduced in Junos OS Release 14.1.
Enable multichassis link aggregation groups (MC-LAG), which enables one device to
form a logical LAG interface with two or more other devices.
chassis-idSpecify the chassis ID for Link Aggregation Control Protocol (LACP) to

calculate the port number of MC-LAG physical member links.

Values: 0 or 1
eventsSpecify an action if a specific MC-LAG event occurs.
iccp-peer-downSpecify an action if the ICCP peer of this node goes down.
force-icl-downIf the nodes ICCP peer goes down, bring down the interchassis-link

logical interface.
prefer-status-control-activeSpecify that the node configured as status-control
active become the active node if the peer of this node goes down.

NOTE: The prefer-status-control-active statement can be

configured with the status-control standby configuration to prevent

Copyright 2014, Juniper Networks, Inc.

703

Interfaces Fundamentals for Routing Devices

the LACP MC-LAG system ID from reverting to the default LACP

system ID on ICCP failure. Use this configuration only if you can
ensure that ICCP will not go down unless the router or switch is down.
You must also configure the hold-time down value (at the [edit
interfaces interface-name] hierarchy level) for the interchassis link
with the status-control standby configuration to be higher than the
ICCP BFD timeout. This configuration prevents data traffic loss by
ensuring that when the router or switch with the status-control
active configuration goes down, the router or switch with the
status-control standby configuration does not go into standby mode.
To make the prefer-status-control-active configuration work with
the status-control standby configuration when an interchassis-link
logical interface is configured on aggregate Ethernet interface, you
must either configure the lacp periodic interval statement at the
[edit interface interface-name aggregated-ether-options] hierarchy
level as slow or configure the detection-time threshold statement
at the [edit protocols iccp peer liveness-detection] hierarchy level
as less than 3 seconds.

mc-ae-idSpecify the identification number of the MC-LAG device. The two MC-LAG

network devices that manage a given MC-LAG must have the same identification
number.
Range: 1 through 65,535
mode (active-active | active-standby)Specify whether the MC-LAG is in active-active

or active-standby mode.

NOTE: You can configure IPv4 (inet) and IPv6 (inet6) addresses on
mc-ae interfaces when the active-standy mode is configured.

redundancy-groupSpecify the redundancy group identification number. The Inter-Chassis

Control Protocol (ICCP) uses the redundancy group ID to associate multiple chassis
that perform similar redundancy functions.
Range: 1 through 4,294,967,294
revert-timeWait interval (in minutes) before the switchover to the preferred node is

performed when the switchover-mode is configured as revertive.

Range: 1 through 10

704

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

status-control (active | standby)Specify whether the chassis becomes active or remains

in standby when an interchassis link failure occurs.

switchover-mode (non-revertive | revertive)Specify whether Junos OS should trigger a

link switchover to the preferred node when the active node is available.

NOTE: For revertive mode to automatically switch over to the preferred

node, the status-control statement should be configured as active.

init-delay-time secondsTo minimize traffic loss, specify the number of seconds by which

to delay bringing the multichassis aggregated Ethernet (mc-ae) interface back to

the up state when you reboot an MC-LAG peer.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Active-Active Bridging and VRRP over IRB Functionality on MX Series Routers Overview

Configuring Multichassis Link Aggregation

Configuring Multichassis Link Aggregation

Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation
on MX Series Routers

Example: Configuring Multichassis Link Aggregation in an Active-Active Bridging Domain

Configuring Manual and Automatic Link Switchover for MC-LAG Interfaces

member-interface-speed
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

member-interface-speed speed;
[edit interfaces container-options member-interface-type]

Statement introduced in Junos OS Release 9.2.

Specify container-interface member-interface speed options.
speedSet interface speed to OC3, OC12, OC48, OC192, OC768, or mixed.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Displaying APS Using a Container Interface with ATM Encapsulation

Configuring Container Interfaces for APS on SONET Links

container-options on page 481

Copyright 2014, Juniper Networks, Inc.

705

Interfaces Fundamentals for Routing Devices

member-interface-type
Syntax

Hierarchy Level
Release Information
Description
Options

member-interface-type sonet {
member-interface-speed [ speed ];
}
[edit interfaces container-options]

Statement introduced in Junos OS Release 9.2.

Specify container-interface member-interface type as sonet and speed options.
sonetProtocol type of the container interface, specify sonet.
speedSet interface speed to OC3, OC12, OC48, OC192, OC768, or mixed.

Required Privilege
Level
Related
Documentation

706

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Displaying APS Using a Container Interface with ATM Encapsulation

Configuring Container Interfaces for APS on SONET Links

container-options on page 481

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mep
Syntax

Hierarchy Level

Release Information
Description

Options

mep mep-id {
action-profile action-profile-name
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name]

Statement introduced in Junos OS Release 8.4.

The numeric identifier of the maintenance association end point (MEP) within the
maintenance association.
mep-idSpecify the numeric identifier of the MEP.

Range: 1 through 8191

The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Alarm Indication Signal (ETH-AIS) Function Overview

Configuring ETH-AIS on a CFM MEP

Configuring a Maintenance Endpoint

Copyright 2014, Juniper Networks, Inc.

707

Interfaces Fundamentals for Routing Devices

minimum-links
Syntax
Hierarchy Level

Release Information

Description

Options

minimum-links number;
[edit interfaces aex aggregated-ether-options],
[edit interfaces aex aggregated-sonet-options],
[edit interfaces interface-name mlfr-uni-nni-bundle-options],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-range range aggregated-ether-options],
[edit interfaces interface-range range aggregated-sonet-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
For aggregated Ethernet, SONET/SDH, multilink, link services, and voice services interfaces
only, set the minimum number of links that must be up for the bundle to be labeled up.
numberNumber of links.

Range: On M120, M320, MX Series, T Series, and TX Matrix routers with Ethernet
interfaces, the valid range for minimum-links number is 1 through 64. When the
maximum value (16) is specified, all configured links of a bundle must be up for the
bundle to be labeled up.On all other routers and on EX Series switches, other than
EX8200 switches, the range of valid values for minimum-links number is 1 through
8. When the maximum value (8) is specified, all configured links of a bundle must
be up for the bundle to be labeled upOn EX8200 switches, the range of valid values
for minimum-links number is 1 through 12. When the maximum value (12) is specified,
all configured links of a bundle must be up for the bundle to be labeled up.
Default: 1
Required Privilege
Level
Related
Documentation

708

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Aggregated Ethernet Minimum Links

Configuring Aggregated SONET/SDH Interfaces

Configuring Aggregated Ethernet Links (CLI Procedure)

Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200

Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mip-half-function
Syntax
Hierarchy Level

Release Information
Description

mip-half-function (none | default | explicit);

[edit protocols oam ethernet connectivity-fault-managementmaintenance-domain
md-name],
[edit protocols oam ethernet connectivity-fault-managementmaintenance-association
ma-name]

Statement introduced in Junos OS Release 9.6.

Specify the OAM Ethernet CFM maintenance domain MIP half functions.

NOTE: Whenever a MIP is configured and a bridge domain is mapped to

multiple maintenance domains or maintenance associations, it is essential
that the mip-half-function value for all maintenance domains and
maintenance associations are the same.

Options

noneSpecify to not use the mip-half-function.

defaultSpecify to use the default mip-half-function.
explicitSpecify an explicit mip-half-function.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Creating the Maintenance Domain

maintenance-domain on page 699

Copyright 2014, Juniper Networks, Inc.

709

Interfaces Fundamentals for Routing Devices

mlfr-uni-nni-bundle-options
Syntax

Hierarchy Level
Release Information
Description

mlfr-uni-nni-bundle-options {
acknowledge-retries number;
acknowledge-timer milliseconds;
action-red-differential-delay (disable-tx | remove-link);
drop-timeout milliseconds;
fragment-threshold bytes;
hello-timer milliseconds;
link-layer-overhead percent;
lmi-type (ansi | itu | c-lmi);
minimum-links number;
mrru bytes;
n391 number;
n392 number;
n393 number;
red-differential-delay milliseconds;
t391 seconds;
t392 number;
yellow-differential-delay milliseconds;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Configure link services and voice services interface management properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

710

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Frame Relay Keepalives

lmi (Frame Relay) on page 674

lmi-type on page 677

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mode (Dynamic Profiles)

Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

mode loose;
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
(inet) rpf-check]

Statement introduced in Junos OS Release 9.6.

Check whether the packet has a source address with a corresponding prefix in the routing
table. If a corresponding prefix is not found, unicast reverse path forwarding (RPF) loose
mode does not accept the packet. Unlike strict mode, loose mode does not check whether
the interface expects to receive a packet with a specific source address prefix.
If you do not include this statement, unicast RPF is in strict mode.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Unicast RPF Strict Mode on page 227

mode (Interfaces)
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

mode loose;
[edit interfaces interface-name unit logical-unit-number family (inet | inet6) rpf-check],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family (inet | inet6) rpf-check]

Statement introduced before Junos OS Release 7.4.

Check whether the packet has a source address with a corresponding prefix in the routing
table. If a corresponding prefix is not found, unicast reverse path forwarding (RPF) loose
mode does not accept the packet. Unlike strict mode, loose mode does not check whether
the interface expects to receive a packet with a specific source address prefix.
If you do not include this statement, unicast RPF is in strict mode.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Unicast RPF Strict Mode on page 227

Copyright 2014, Juniper Networks, Inc.

711

Interfaces Fundamentals for Routing Devices

modem-options
Syntax

Hierarchy Level
Release Information
Description

modem-options {
dialin (console | routable);
init-command-string initialization-command-string;
}
[edit interfaces umd0]

Statement introduced in Junos OS Release 8.2.

For J Series Services Routers, configure a USB port to act as a USB modem.
The remaining statement is explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying a USB Modem Interface on J Series Routers on page 316

monitor-session
Syntax
Hierarchy Level
Release Information
Description

Default

Options

monitor-session (interface-name | all);

[edit protocols ppp]

Statement introduced in Junos OS Release 7.5.

Monitor PPP packet exchanges. When monitoring is enabled, packets exchanged during
a session are logged to the default log of /var/log/pppd.
If you do not include this statement, no PPPD-specific monitoring operations are
performed.
allMonitor PPP packet exchanges on all sessions.
interface-nameLogical interface name on which to enable session monitoring.

Required Privilege
Level
Related
Documentation

712

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Monitoring a PPP Session on page 136

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mpls (Interfaces)
Syntax

Hierarchy Level

Release Information
Description

mpls {
pop-all-labels {
required-depth number;
}
}
[edit interfaces interface-name atm-options],
[edit interfaces interface-name sonet-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]

Statement introduced before Junos OS Release 7.4.

For passive monitoring on ATM and SONET/SDH interfaces and 10-Gigabit Ethernet
interfaces in WAN PHY mode, process incoming IP packets that have MPLS labels.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Removing MPLS Labels from Incoming Packets

Enabling Packet Flow Monitoring on SONET/SDH Interfaces

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

713

Interfaces Fundamentals for Routing Devices

mrru
Syntax
Hierarchy Level

Release Information
Description

Options

mrru bytes;
[edit interfaces interface-name mlfr-uni-nni-bundle-options],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For multilink, link services, voice services, and J Series Services Routers ISDN interfaces
only, set the maximum received reconstructed unit (MRRU). The MRRU is similar to the
MTU, but is specific to multilink interfaces.
bytesMRRU size.

Range: 1500 through 4500 bytes

Default: 1500 bytes
Required Privilege
Level
Related
Documentation

714

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Logical Interface Properties

mtu on page 715

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mtu
Syntax

mtu bytes;

Hierarchy Level

[edit interfaces interface-name],

[edit interfaces interface-name unit logical-unit-number family family],
[edit interfaces interface-range name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family],
[edit logical-systems logical-system-name protocols l2circuit local-switching interface
interface-name backup-neighbor address],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name],
[edit logical-systems logical-system-name protocols l2circuit neighbor address interface
interface-name backup-neighbor address],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
l2vpn interface interface-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
vpls],
[edit protocols l2circuit local-switching interface interface-name backup-neighbor address],
[edit protocols l2circuit neighbor address interface interface-name]
[edit protocols l2circuit neighbor address interface interface-name backup-neighbor address],
[edit routing-instances routing-instance-name protocols l2vpn interface interface-name],
[edit routing-instances routing-instance-name protocols vpls]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for Layer 2 VPNs and VPLS introduced in Junos OS Release 10.4.
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 Universal Access Routers.
Support at the[set interfaces interface-name unit logical-unit-number family ccc] hierarchy
level introduced in Junos OS Release 12.3R3 for MX Series routers.

Description

Specify the maximum transmission unit (MTU) size for the media or protocol. The default
MTU size depends on the device type. Changing the media MTU or protocol MTU causes
an interface to be deleted and added again.
To route jumbo data packets on an integrated routing and bridging (IRB) interface or
routed VLAN interface (RVI) on EX Series switches, you must configure the jumbo MTU
size on the member physical interfaces of the VLAN that you have associated with the
IRB interface or RVI, as well as on the IRB interface or RVI itself (the interface named irb
or vlan, respectively).

CAUTION: For EX Series switches, setting or deleting the jumbo MTU size on
an IRB interface or RVI while the switch is transmitting packets might cause
packets to be dropped.

Copyright 2014, Juniper Networks, Inc.

715

Interfaces Fundamentals for Routing Devices

NOTE:
The MTU for an IRB interface is calculated by removing the Ethernet header
overhead [6(DMAC)+6(SMAC)+2(EtherType)]. Because, the MTU is the
lower value of the MTU configured on the IRB interface and the MTU
configured on the IRBs associated bridge domain IFDs or IFLs, the IRB MTU
is calculated as follows:

716

In case of Layer 2 IFL configured with the flexible-vlan-tagging statement,

the IRB MTU is calculated by including 8 bytes overhead (SVLAN+CVLAN).

In case of Layer 2 IFL configured with the vlan-tagging statement, the IRB
MTU is calculated by including a single VLAN 4 bytes overhead.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

NOTE:

If a packet whose size is larger than the configured MTU size is received on
the receiving interface, the packet is eventually dropped. The value
considered for MRU (maximum receive unit) size is also the same as the
MTU size configured on that interface.

Not all devices allow you to set an MTU value, and some devices have
restrictions on the range of allowable MTU values. You cannot configure
an MTU for management Ethernet interfaces (fxp0, em0, or me0) or for
loopback, multilink, and multicast tunnel devices.

On ACX Series routers, you can configure the protocol MTU by including
the mtu statement at the [edit interfaces interface-name unit
logical-unit-number family inet] or [edit interfaces interface-name unit
logical-unit-number family inet6] hierarchy level.

If you configure the protocol MTU at any of these hierarchy levels, the
configured value is applied to all families that are configured on the
logical interface.

If you are configuring the protocol MTU for both inet and inet6 families
on the same logical interface, you must configure the same value for
both the families. It is not recommended to configure different MTU size
values for inet and inet6 families that are configured on the same logical
interface.

For IRB interfaces, MTU is calculated by removing the Ethernet header

overhead (6(DMAC)+6(SMAC)+2(EtherType)), and the MTU is a minimum
of the two values:

Configured MTU

Associated bridge domain's physical or logical interface MTU

For Layer 2 logical interfaces configured with flexible-vlan-tagging, IRB

MTU is calculated by including 8 bytes overhead (SVLAN+CVLAN).

For Layer 2 logical interfaces configured with vlan-tagging, IRB MTU is

calculated by including single VLAN 4 bytes overhead.

NOTE: Changing the Layer 2 logical interface option from

vlan-tagging to flexible-vlan-tagging or vice versa adjusts the
logical interface MTU by 4 bytes with the existing MTU size.
As a result, the Layer 2 logical interface is deleted and
re-added, and the IRB MTU is re-computed appropriately.

Copyright 2014, Juniper Networks, Inc.

717

Interfaces Fundamentals for Routing Devices

For more information about configuring MTU for specific interfaces and router or switch
combinations, see Configuring the Media MTU on page 93.
Options

bytesMTU size.

Range: 256 through 9192 bytes, 256 through 9216 (EX Series switch interfaces), 256
through 9500 bytes (Junos OS 12.1X48R2 for PTX Series routers)
Default: 1500 bytes (INET, INET6, and ISO families), 1448 bytes (MPLS), 1514 bytes (EX
Series switch interfaces)
Required Privilege
Level
Related
Documentation

718

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Media MTU on page 93

Configuring the MTU for Layer 2 Interfaces

Setting the Protocol MTU on page 208

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

multi-chassis-protection
Syntax

Hierarchy Level
Release Information
Description

multi-chassis-protection {
peer a.b.c.d {
interface interface-name;
}
}
[edit interfaces interface-name]

Statement introduced in Junos OS Release 11.1.

For MX Series routers with multichassis aggregated Ethernet (MC-AE) interfaces, you
can use this statement under the physical interface level to reduce the configuration at
the logical interface level if the following assumption exists:
If there are n +1 logical interfaces under ae0, from ae0.0 through ae0.n, there will be n +
1 logical interfaces under ge-0/0/0 as well, from ge-0/0/0.0 through ge-0/0/0.n, and
each ge-0/0/0 logical interface will be a protection link for the ae0 logical interface.

NOTE: A bridge domain cannot have MC-AE logical interfaces which belong
to different redundancy groups.

If the Inter-Chassis Control Protocol (ICCP) connection is UP and the interchassis data
link (ICL) comes UP, the router configured as standby will bring up the MC-AE interfaces
shared with the peer.
The remaining statements are explained separately.
Options
Required Privilege
Level
Related
Documentation

interface interface-nameSpecify the interface: interface interface-name-fpc/pic/port

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Multichassis Link Aggregation

Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation
on MX Series Routers

Configuring Aggregated Ethernet Link Protection

Example: Configuring Aggregated Ethernet Link Protection

peer on page 788

Copyright 2014, Juniper Networks, Inc.

719

Interfaces Fundamentals for Routing Devices

multicast-dlci
Syntax
Hierarchy Level

Release Information
Description

Options

multicast-dlci dlci-identifier;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For point-to-multipoint Frame Relay, link services, and voice services interfaces only,
enable multicast support on the interface. You can configure multicast support on the
interface if the Frame Relay switch performs multicast replication.
dlci-identifierDLCI identifier, a number from 16 through 1022 that defines the Frame

Relay DLCI over which the switch expects to receive multicast packets for replication.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Multicast-Capable Frame Relay Connection

dlci on page 515

multipoint-destination on page 724

Junos OS Services Interfaces Library for Routing Devices

multicast-only
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

720

multicast-only;
[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]

Statement introduced before Junos OS Release 7.4.

Configure the unit and family so that it can transmit and receive multicast traffic only.
You can configure this property on the IP family only.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the Protocol Family on page 190

Junos OS Services Interfaces Library for Routing Devices

tunnel on page 942

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

multicast-statistics
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

multicast-statistics;
[edit interfaces interface-name]

Statement introduced before Junos OS Release 10.2.

For Ethernet, SONET, aggregated Ethernet, and aggregated SONET interfaces in T Series
or TX Matrix routers, specify support for multicast statistics on a physical interface to
enable multicast accounting for all the logical interfaces below the physical interface.
not enabledmust be configured to enable
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Multicast Statistics Collection on Aggregated Ethernet Interfaces

Configuring Multicast Statistics Collection on Aggregated SONET Interfaces

Configuring Multicast Statistics Collection on Ethernet Interfaces

Configuring Multicast Statistics Collection on SONET Interfaces

Copyright 2014, Juniper Networks, Inc.

721

Interfaces Fundamentals for Routing Devices

multicast-vci
Syntax
Hierarchy Level

Release Information
Description

Options

multicast-vci vpi-identifier.vci-identifier;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For ATM encapsulation only, and for point-to-multipoint ATM logical interfaces only,
enable the support of multicast on the interface. You can configure multicast support
on the interface if the ATM switch performs multicast replication.
vci-identifierATM virtual circuit identifier.

Range: 0 through 16,384

vpi-identifierATM virtual path identifier.

Range: 0 through 255

Default: 0
Required Privilege
Level
Related
Documentation

722

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Multicast-Capable ATM1 or ATM2 IQ Connection

multipoint-destination on page 724

vci on page 964

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

multilink-max-classes
Syntax
Hierarchy Level

Release Information
Description

Options

multilink-max-classes number;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For Adaptive Services (AS) PIC link services IQ interfaces (lsq) only, configure the number
of multilink classes to be negotiated when a link joins the bundle.
numberThe number of multilink classes to be negotiated when a link joins the bundle.

Range: 1 through 8
Default: None
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

multipoint on page 723

multipoint
Syntax
Hierarchy Level

Release Information
Description
Default
Required Privilege
Level
Related
Documentation

multipoint;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Configure the interface unit as a multipoint connection.
If you omit this statement, the interface unit is configured as a point-to-point connection.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring a Multipoint Connection on page 176

point-to-point on page 795

Copyright 2014, Juniper Networks, Inc.

723

Interfaces Fundamentals for Routing Devices

multipoint-destination
Syntax

multipoint-destination address dlci dlci-identifier;

multipoint-destination address {
epd-threshold cells;
inverse-arp;
oam-liveness {
down-count cells;
up-count cells;
}
oam-period (disable | seconds);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}

Hierarchy Level

[edit interfaces interface-name unit logical-unit-number family family address address],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address]

Release Information
Description

Options

Statement introduced before Junos OS Release 7.4.

For point-to-multipoint Frame Relay or ATM interfaces only, enable the support of
multicast on the interface. You can configure multicast support on the interface if the
Frame Relay or ATM switch performs multicast replication.
addressAddress of the remote side of the point-to-multipoint connection.
dlci-identifierFor Frame Relay interfaces, the data-link connection identifier.

Range: 0 through 0xFFFFFF (24 bits)

vci-identifierFor ATM interfaces, the virtual circuit identifier.

Range: 0 through 16,384

vpi-identifierFor ATM interfaces, the virtual path identifier.

Range: 0 through 255

Default: 0
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

724

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Point-to-Point ATM1 or ATM2 IQ Connection

Configuring a Point-to-Multipoint Frame Relay Connection

dlci on page 515

encapsulation (Logical Interface) on page 543

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

multiservice-options
Syntax

Hierarchy Level
Release Information
Description

multiservice-options {
(syslog | no-syslog);
(core-dump | no-core-dump);
(dump-on-flow-control);
flow-control-options {
down-on-flow-control;
dump-on-flow-control;
reset-on-flow-control;
}
}
[edit interfaces mo-fpc/pic/port]

Statement introduced before Junos OS Release 7.4.

For monitoring services interfaces only, configure multiservice-specific interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Multiservice Physical Interface Properties on page 153

Junos OS Services Interfaces Library for Routing Devices

passive-monitor-mode on page 782

Copyright 2014, Juniper Networks, Inc.

725

Interfaces Fundamentals for Routing Devices

n391
Syntax
Hierarchy Level
Release Information
Description

Options

n391 number;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voice services interfaces only, set the Frame Relay full status polling
interval.
numberPolling interval.

Range: 1 through 255

Default: 6
Required Privilege
Level
Related
Documentation

726

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

n392 on page 727

n393 on page 728

timeslots on page 920

t392 on page 912

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

n392
Syntax
Hierarchy Level
Release Information
Description

Options

n392 number;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voices interfaces only, set the Frame Relay error threshold, in number
of errors.
numberError threshold.

Range: 1 through 10
Default: 3
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

n391 on page 726

n393 on page 728

timeslots on page 920

t392 on page 912

Copyright 2014, Juniper Networks, Inc.

727

Interfaces Fundamentals for Routing Devices

n393
Syntax
Hierarchy Level
Release Information
Description
Options

n393 number;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voices interfaces only, set the Frame Relay monitored event count.
numberNumber of event count.

Range: 1 through 10
Default: 4
Required Privilege
Level
Related
Documentation

728

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

n391 on page 726

n392 on page 727

timeslots on page 920

t392 on page 912

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

name-format
Syntax
Hierarchy Level

Release Information

Description
Options

name-format (character-string | none | dns | mac+2oct);

[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name]

Statement introduced in Junos OS Release 8.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers.
Specify the format of the maintenance domain name.
character-stringThe name is an ASCII character string.
noneThe maintenance domain name is not used.
dnsThe name is in domain name service (DNS) format. For example: www.juniper.net.
mac+2octName is the MAC address plus a two-octet maintenance association identifier.

For example: 08:00:22:33:44:55.100.

Default: character-string
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Creating a Maintenance Association

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

Copyright 2014, Juniper Networks, Inc.

729

Interfaces Fundamentals for Routing Devices

native-vlan-id
Syntax
Hierarchy Level

Release Information

Description

native-vlan-id number;
[edit interfaces ge-fpc/pic/port],
[edit interfaces interface-name]

Statement introduced in Junos OS Release 8.3.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Statement introduced in Junos OS Release 13.2X51-D20 for the QFX Series.
Configure mixed tagging support for untagged packets on a port for the following:

M Series routers with Gigabit Ethernet IQ PICs with SFP and Gigabit Ethernet IQ2 PICs
with SFP configured for 802.1Q flexible VLAN tagging

MX Series routers with Gigabit Ethernet DPCs and MICs, Tri-Rate Ethernet DPCs and
MICs, and 10-Gigabit Ethernet DPCs and MICs and MPCs configured for 802.1Q flexible
VLAN tagging

T4000 routers with 100-Gigabit Ethernet Type 5 PIC with CFP

EX Series switches with Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet,

and aggregated Ethernet interfaces

When the native-vlan-id statement is included with the flexible-vlan-tagging statement,

untagged packets are accepted on the same mixed VLAN-tagged port.
The logical interface on which untagged packets are received must be configured with
the same VLAN ID as the native VLAN ID configured on the physical interface. To configure
the logical interface, include the vlan-id statement (matching the native-vlan-id statement
on the physical interface) at the [edit interfaces interface-name unit logical-unit-number]
hierarchy level.
When the native-vlan-id statement is included with the interface-mode statement,
untagged packets are accepted and forwarded within the bridge domain or VLAN that
is configured with the matching VLAN ID.
Options

numberVLAN ID number.

Range: (ACX Series routers and EX Series switches) 0 through 4094.

Required Privilege
Level
Related
Documentation

730

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Mixed Tagging Support for Untagged Packets

Configuring a Logical Interface for Access Mode

Configuring the Native VLAN Identifier (CLI Procedure)

Understanding Bridging and VLANs on EX Series Switches

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

flexible-vlan-tagging on page 577

Understanding Q-in-Q Tunneling on EX Series Switches

ncp-max-conf-req
Syntax
Hierarchy Level
Release Information

ncp-max-conf-req number
[edit interfaces so-fpc/pic/port unit number ppp-options]

Statement introduced in Junos OS Release 9.6.

Description

Set the maximum number of NCP Configure-Requests to be sent, after which the router
goes to NCP down state.

Options

numberRanges from 0 to 65535, where 0 means send infinite NCP Configure-Requests

and any other value specifies the maximum number NCP Configure-Requests to
send and then stop sending.
Default254

Range: 0 through 65,535

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the NCP Configure-Request Maximum Sent on page 177

ppp-options on page 812

Copyright 2014, Juniper Networks, Inc.

731

Interfaces Fundamentals for Routing Devices

ncp-restart-timer
Syntax
Hierarchy Level

Release Information

ncp-restart-timer milliseconds;
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options]

Statement introduced in Junos OS Release 8.1.

Description

For interfaces with PPP and PPP TCC encapsulations and on multilink PPP bundle
interfaces, configure a restart timer for the Network Control Protocol (NCP) component
of a PPP session.

Options

millisecondsThe time in milliseconds between successive NCP configuration requests.

Range: 500 through 10,000 milliseconds

Default: 3 seconds
Required Privilege
Level
Related
Documentation

732

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Restart Timers on page 176

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

nd6-stale-time
Syntax
Hierarchy Level
Release Information

Description

nd6-stale-time seconds;
[edit interfaces interface-name unit logical-unit-number family inet6]

Statement introduced in Junos OS Release 11.1.

Statement introduced in Junos OS Release 11.1 for EX Series switches.
Set the stale timer for IPv6 neighbor reachability confirmation. Reachability of the IPv6
neighbors is confirmed only after the stale timer has expired. For example, by setting the
stale timer to 180 seconds, users can specify that IPv6 neighbor reachability be confirmed
every 180 seconds.

NOTE: When the Routing Engine sends a control packet to an IPv6 neighbor,
the stale timer is the maximum interval in which neighbor reachability is
confirmed. In such cases, IPv6 neighbor reachability is confirmed before the
stale timer expires.

Default
Options

Default is 20 minutes (1200 seconds)

secondsDuration in seconds.

Range: 1 to 1200
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IPv6 Neighbor Discovery Overview

show ipv6 neighbors on page 1756

Copyright 2014, Juniper Networks, Inc.

733

Interfaces Fundamentals for Routing Devices

negotiate-address
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

negotiate-address;
[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]

Statement introduced before Junos OS Release 7.4.

For interfaces with PPP encapsulation, enable the interface to be assigned an IP address
by the remote end.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring IPCP Options on page 200

address on page 412

unnumbered-address (PPP) on page 958

Junos OS Administration Library for Routing Devices

negotiation-options
Syntax

Hierarchy Level
Release Information
Description

negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
[edit protocols oam link-fault-management interface interface-name]

Statement introduced in Junos OS Release 8.4.

Enable and disable IEEE 802.3ah Operation, Administration, and Management (OAM)
features for Ethernet interfaces.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

734

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.3ah OAM Link-Fault Management Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

neighbor (Automatic Protection Switching for SONET/SDH)

Syntax
Hierarchy Level
Release Information
Description

neighbor address;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

If you are configuring one router to be the working router and a second to be the protect
router, configure the address of the remote interface. You configure this on one or both
of the interfaces.
The address you specify for the neighbor must never be routed through the interface on
which APS is configured, or instability will result. We strongly recommend that you directly
connect the working and protect routers and that you configure the interface address of
this shared network as the neighbor address.

Options
Required Privilege
Level
Related
Documentation

addressNeighbors address.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Basic Automatic Protect Switching

no-allow-link-events
Syntax
Hierarchy Level

Release Information
Description
Required Privilege
Level
Related
Documentation

no-allow-link-events;
[edit protocols oam ethernet link-fault-management interface interface-name
negotiation-options]

Statement introduced in Junos OS Release 8.4.

Disable the sending of link event TLVs.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Disabling the Sending of Link Event TLVs

Copyright 2014, Juniper Networks, Inc.

735

Interfaces Fundamentals for Routing Devices

no-aggregate-delegate-processing
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

no-aggregate-delegate-processing;
[edit protocols oam ethernet connectivity-fault-management]

Statement introduced in Junos OS Release 14.1.

Disable distribution of connectivity fault management (CFM) sessions on aggregated
Ethernet interfaces.
CFM sessions on aggregated Ethernet interfaces are distributed by default.
ConfigureTo enter configuration mode.
ControlTo modify any configuration.

IEEE 802.1ag OAM Connectivity Fault Management Overview

asynchronous-notification
Syntax
Hierarchy Level

(asynchronous-notification | no-asynchronous-notification);
[edit interfaces ge-fpc/pic/port gigether-options ]

Release Information

Statement introduced in Junos OS Release 8.3.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For all 10-Gigabit Ethernet interfaces, M120, M320, and T Series routers, configure support
for notification of link down alarm generation and transfer.

asynchronous-notificationSupport notification of link down alarm generation and

transfer.

no-asynchronous-notificationProhibit notification of link down alarm generation and

transfer.
Default
Required Privilege
Level
Related
Documentation

736

Support for notification of link down alarm generation and transfer is not enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

10-Gigabit Ethernet Notification of Link Down Alarm Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

no-auto-mdix
Syntax
Hierarchy Level
Release Information

Description

no-auto-mdix;
[edit interface ge-fpc/port/pic gigether-options]

Statement introduced in Junos OS Release 9.5.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Disable the Auto MDI/MDIX feature.
MX Series routers with Gigabit Ethernet interfaces automatically detect MDI and MDIX
port connections. Use this statement to override the default setting. Remove this
statement to return to the default setting.

Default

Auto MDI/MDIX is enabled by default.

Options

There are no options for this statement.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Interfaces Overview

gigether-options on page 589.

Copyright 2014, Juniper Networks, Inc.

737

Interfaces Fundamentals for Routing Devices

auto-negotiation
Syntax

Hierarchy Level

Release Information

Description

(auto-negotiation | no-auto-negotiation) <remote-fault (local-interface-online |

local-interface-offline)>;
[edit interfaces interface-name ether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces ge-pim/0/0 switch-options switch-port port-number]

Statement introduced in Junos OS Release 7.6.

Statement introduced in Junos OS Release 8.4 for J Series Services Routers.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
For Gigabit Ethernet interfaces on M Series, MX Series, T Series, TX Matrix routers, and
ACX Series routers explicitly enable autonegotiation and remote fault. For EX Series
switches and J Series Services Routers, explicitly enable autonegotiation only.

auto-negotiationEnables autonegotiation. This is the default.

no-auto-negotiationDisable autonegotiation. When autonegotiation is disabled, you

must explicitly configure the link mode and speed.

When you configure Tri-Rate Ethernet copper interfaces to operate at 1 Gbps,
autonegotiation must be enabled.

NOTE: On EX Series switches, an interface configuration that disables

autonegotiation and manually sets the link speed to 1 Gbps is accepted when
you commit the configuration; however, if the interface you are configuring
is a Tri-Rate Ethernet copper interface, the configuration is ignored as invalid
and autonegotiation is enabled by default.
To correct the invalid configuration and disable autonegotiation:
1.

Delete the no-auto-negotiation statement and commit the configuration.

2. Set the link speed to 10 or 100 Mbps, set no-auto-negotiation, and commit

the configuration.

On J Series Services Routers with universal Physical Interface Modules (uPIMs) and on
EX Series switches, if the link speed and duplex mode are also configured, the interfaces
use the values configured as the desired values in the negotiation. If autonegotiation is
disabled, the link speed and link mode must be configured.

NOTE: On T4000 routers, the auto-negotiation command is ignored for

interfaces other than Gigabit Ethernet.

738

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Default

Options

Autonegotiation is automatically enabled. No explicit action is taken after the

autonegotiation is complete or if the negotiation fails.
remote-fault (local-interface-online | local-interface-offline)(Optional) For M Series,

MX Series, T Series, TX Matrix routers, and ACX Series routers only, manually configure
remote fault on an interface.
Default: local-interface-online
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Gigabit Ethernet Autonegotiation Overview

Configuring Gigabit Ethernet Interfaces on J Series Services Routers

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

auto-negotiation (J Series uPIM)

Syntax
Hierarchy Level
Release Information
Description

(auto-negotiation | no-auto-negotiation);
[edit interfaces ge-pim/0/0 switch-options switch-port port-number]

Statement introduced in Junos OS Release 8.4.

For universal Physical Interface Modules (uPIMs) on J Series Services Routers only,
explicitly enable autonegotiation. If the link speed and duplex are also configured, the
interfaces use the values configured as the desired values in the negotiation. Include the
no-auto-negotiation statement to disable autonegotiation.
If autonegotiation is disabled, the link speed and link mode must be configured.

Default
Options

Autonegotiation is enabled by default.

auto-negotiationEnables autonegotiation.
no-auto-negotiationDisables autonegotiation.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Interfaces on J Series Services Routers

Copyright 2014, Juniper Networks, Inc.

739

Interfaces Fundamentals for Routing Devices

cbit-parity
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(cbit-parity | no-cbit-parity);
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

For T3 interfaces only, enable or disable C-bit parity mode, which controls the type of
framing that is present on the transmitted T3 signal. When C-bit parity mode is enabled,
the C-bit positions are used for the far-end block error (FEBE), far-end alarm and control
(FEAC), terminal data link, path parity, and mode indicator bits, as defined in ANSI
T1.107a-1989. For ATM and ATM2 IQ2 and IQ2-E interfaces, M23 framing is used when
the no-cbit-parity statement is included. For all other interfaces, M13 framing is used
when the no-cbit-parity statement is included.
C-bit parity mode is enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring E3 and T3 Parameters on ATM Interfaces

Disabling T3 C-Bit Parity Mode

core-dump
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

740

(core-dump | no-core-dump);
[edit interfaces mo-fpc/pic/port multiservice-options]

Statement introduced before Junos OS Release 7.4.

For monitoring services interfaces only, a useful tool for isolating the cause of a problem.
Core dumping is enabled by default. The directory /var/tmp contains core files. The Junos
OS saves the current core file (0) and the four previous core files, which are numbered
1 through 4 (from newest to oldest):

core-dumpEnable the core dumping operation.

no-core-dumpDisable the core dumping operation.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Multiservice Physical Interface Properties on page 153

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

feac-loop-respond
Syntax
Hierarchy Level
Release Information
Description

(feac-loop-respond | no-feac-loop-respond);
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

For T3 interfaces only, configure the router so a remote CSU can place the local router
into loopback.
If you configure remote or local loopback with the T3 loopback statement, the router
does not respond to FEAC requests from the CSU even if you include the feac-loop-respond
statement in the configuration. For the router to respond, you must delete the loopback
statement from the configuration.
You must rollback the setting done on the remote CSU prior to deactivating the
feac-loop-respond statement. If the remote CSU cannot comply, clear the remote loop
through local configuration to achieve the cleanup. For example, configure remote
loopback on the interface and then delete the remote loopback.

Default
Required Privilege
Level
Related
Documentation

The router does not respond to FEAC requests.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the T3 FEAC Response

loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3) on page 686

remote-loopback-respond on page 843

Copyright 2014, Juniper Networks, Inc.

741

Interfaces Fundamentals for Routing Devices

flow-control
Syntax
Hierarchy Level

(flow-control | no-flow-control);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-name multiservice-options],
[edit interfaces interface-range name aggregated-ether-options],
[edit interfaces interface-range name ether-options]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 in EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces only, explicitly
enable flow control, which regulates the flow of packets from the router or switch to the
remote side of the connection. Enabling flow control is useful when the remote device
is a Gigabit Ethernet switch. Flow control is not supported on the 4-port Fast Ethernet
PIC.

NOTE: On the Type 5 FPC, to prioritize control packets in case of ingress

oversubscription, you must ensure that the neighboring peers support MAC
flow control. If the peers do not support MAC flow control, then you must
disable flow control.

Default
Required Privilege
Level
Related
Documentation

742

Flow control is enabled.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Flow Control

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

gratuitous-arp-reply
Syntax
Hierarchy Level

(gratuitous-arp-reply | no-gratuitous-arp-reply);
[edit interfaces interface-name]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 in EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For Ethernet interfaces, enable updating of the Address Resolution Protocol (ARP) cache
for gratuitous ARPs.

Default
Required Privilege
Level
Related
Documentation

Updating of the ARP cache is disabled on all Ethernet interfaces.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Gratuitous ARP

no-gratuitous-arp-request on page 743

no-gratuitous-arp-request
Syntax
Hierarchy Level
Release Information

Description

Default
Required Privilege
Level
Related
Documentation

no-gratuitous-arp-request;
[edit interfaces interface-name]

Statement introduced in Junos OS Release 9.6 for EX Series switches.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
For Ethernet interfaces and pseudowire logical interfaces, do not respond to gratuitous
ARP requests.
Gratuitous ARP responses are enabled on all Ethernet interfaces.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Gratuitous ARP

gratuitous-arp-reply on page 590

Copyright 2014, Juniper Networks, Inc.

743

Interfaces Fundamentals for Routing Devices

no-keepalives
Syntax
Hierarchy Level

Release Information
Description

no-keepalives;
[edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Disable the sending of keepalives on a physical interface configured with PPP, Frame
Relay, or Cisco HDLC encapsulation. The default keepalive interval is 10 seconds.
For ATM2 IQ interfaces only, you can disable keepalives on a logical interface unit if the
logical interface is configured with one of the following PPP over ATM encapsulation
types:

Required Privilege
Level
Related
Documentation

744

atm-ppp-llcPPP over AAL5 LLC encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Keepalives on page 124

Disabling the Sending of PPPoE Keepalive Messages

Configuring Frame Relay Keepalives

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

long-buildout
Syntax
Hierarchy Level
Release Information
Description

(long-buildout | no-long-buildout);
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Configure the T3 line buildout. A T3 interface has two settings for the T3 line buildout: a
short setting, which is less than 255 feet (68 meters), and a long setting, which is greater
than 255 feet and shorter than 450 feet (137 meters).
This statement applies to copper-cable-based T3 interfaces only. You cannot configure
a line buildout for a DS3 channel on a channelized OC12 interface, which runs over
fiber-optic cable.

Default

Required Privilege
Level
Related
Documentation

A T3 interface uses the short line buildout setting (no-long-buildout) for wires shorter
than 255 feet (68 meters).
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the T3 Line Buildout

Copyright 2014, Juniper Networks, Inc.

745

Interfaces Fundamentals for Routing Devices

loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet)

Syntax
Hierarchy Level

Release Information

Description

(loopback | no-loopback);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-range name ether-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
For aggregated Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet
interfaces, enable or disable loopback mode.

NOTE:

Required Privilege
Level
Related
Documentation

746

By default, local aggregated Ethernet, Fast Ethernet, Tri-Rate Ethernet

copper, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces connect to a
remote system.

IPv6 Neighbor Discovery Protocol (NDP) addresses are not supported on

Gigabit Ethernet interfaces when loopback mode is enabled on the
interface. That is, if the loopback statement is configured at the [edit
interfaces ge-fpc/pic/port gigether-options] hierarchy level, an NDP address
cannot be configured at the [edit interfaces ge-fpc/pic/port unit
logical-unit-number family inet6 address] hierarchy level.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Ethernet Loopback Capability

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

mac-learn-enable
Syntax
Hierarchy Level
Release Information
Description

(mac-learn-enable | no-mac-learn-enable);
[edit interfaces interface-name gigether-options ethernet-switch-profile]

Statement introduced before Junos OS Release 7.4.

For Gigabit Ethernet IQ and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), for Gigabit Ethernet
DPCs on MX Series routers, and 100-Gigabit Ethernet Type 5 PIC with CFP configure
whether source and destination MAC addresses are dynamically learned:

mac-learn-enableAllow the interface to dynamically learn source and destination

MAC addresses.

no-mac-learn-enableProhibit the interface from dynamically learning source and

destination MAC addresses.

MAC address learning is based on source addresses. You can start accounting for traffic
after there has been traffic sent from the MAC address. Once the MAC address is learned,
the frames and bytes transmitted to or received from the MAC address can be tracked.

NOTE: When you gather interfaces into a bridge domain, the

no-mac-learn-enable statement at the [edit interfaces interface-name
gigether-options ethernet-switch-profile] hierarchy level is not supported. You
must use the no-mac-learning statement at the [edit bridge-domains
bridge-domain-name bridge-options interface interface-name] hierarchy level
to disable MAC learning on an interface in a bridge domain. For information
on disabling MAC learning for a bridge domain, see MX Series Layer 2
Configuration Guide.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring MAC Address Filtering

Copyright 2014, Juniper Networks, Inc.

747

Interfaces Fundamentals for Routing Devices

no-partition
Syntax
Hierarchy Level

Release Information
Description

no-partition interface-type (e1 | (cau4 | so) | (ct3 | t3) | so | t3);

[edit interfaces ce1-fpc/pic/port],
[edit interfaces coc1-fpc/pic/port:channel],
[edit interfaces coc12-fpc/pic/port],
[edit interfaces cstm1-fpc/pic/port],
[edit interfaces ct3-fpc/pic/port]

Statement introduced before Junos OS Release 7.4.

For Channelized E1 IQ PICs only, configure the channelized E1 interface as an unpartitioned,
clear channel.
For Channelized OC12 PIC only, convert the channelized OC1 IQ interface into a channelized
T3 interface or a T3 interface. You perform this configuration task for C-bit parity and
M13-mapped configurations.
For Channelized OC12 IQ PICs only, configure the channelized OC12 interface as an
unpartitioned, clear channel.
For Channelized STM1 PIC only, convert the channelized STM1 IQ interface into a
channelized Administrative Unit 4 (AU-4) interface or a SONET/SDH STM1 interface.
For Channelized DS3 PIC only, configure the channelized T3 interface as an unpartitioned,
clear channel.

Default

If you do not include either this statement or the partition statement, the Channelized IQ
PIC is not partitioned, and no data channels are configured.

Options

The option used must correspond to the physical interface type:

e1E1 interface type.
coc12 soChannelized OC12 interface type, in SONET mode.
cau4Channelized AU-4 interface type.
cstm1SONET/SDH STM1 interface type, in SDH mode.
ct3Channelized T3 interface type.
t3T3 interface type.

Required Privilege
Level
Related
Documentation

748

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Channelized E1 IQ and IQE Interfaces Overview

Channelized OC12/STM4 IQ and IQE Interfaces Overview

Configuring an OC12/STM4 Interface

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Configuring Channelized STM1 IQ and IQE Interfaces

Configuring T3 IQ Interfaces

partition on page 780

no-partition

Copyright 2014, Juniper Networks, Inc.

749

Interfaces Fundamentals for Routing Devices

payload-scrambler
Syntax
Hierarchy Level

Release Information
Description

(payload-scrambler | no-payload-scrambler);
[edit interfaces interface-name e3-options],
[edit interfaces interface-name sonet-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Enable or disable HDLC scrambling on an E3, a SONET/SDH, or a T3 interface. This type
of scrambling provides better link stability. Both sides of a connection must either use or
not use scrambling.
If you commit a T3 interface configuration that has HDLC payload scrambling enabled,
the interface must also be configured to be compatible with the channel service unit
(CSU) at the remote end of the line.
Disable payload scrambling on an E3 interface if Digital Link compatibility mode is used.
On a channelized OC12 interface, the sonet payload-scrambler statement is ignored. To
configure scrambling on the DS3 channels on the interface, you can include the t3-options
payload-scrambler statement in the configuration for each DS3 channel.

NOTE: The payload-scrambler statement at the [edit interfaces interface-name

e3-options] hierarchy level is not valid for IQE PICs.

Default

Required Privilege
Level
Related
Documentation

750

Payload scrambling is disabled on all E3 and T3 interfaces; it is enabled by default on

E3/T3 over ATM interfaces and on SONET/SDH interfaces.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring E3 and T3 Parameters on ATM Interfaces

Configuring E3 HDLC Payload Scrambling

Configuring SONET/SDH HDLC Payload Scrambling for Link Stability

Configuring T3 HDLC Payload Scrambling

Examples: Configuring T3 Interfaces

compatibility-mode on page 474

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

no-pre-classifier
Syntax
Hierarchy Level
Release Information
Description

no-pre-classifier;
[edit chassis fpc n pic n]

Statement introduced in Junos OS Release 10.4.

Specify disabling the control queue for all ports on the 10-Gigabit Ethernet LAN/WAN
PIC. Deleting this configuration re-enables the control queue feature on all ports of the
10-Gigabit Ethernet LAN/WAN PIC.

NOTE: For the 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (model number
PD-5-10XGE-SFPP), the control queue has a rate limiter to limit the control
traffic to 2 Mbps (fixed, not user-configurable) per port. If the transit control
traffic crosses this limit, then it can cause drops on locally terminating control
traffic, causing flap of protocols such as BGP and OSPF. To avoid the control
traffic being dropped, configure the no-pre-classifier statement to disable
the control queue.

Default
Required Privilege
Level
Related
Documentation

The no-pre-classifier statement is not configured and the control queue is operational.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

10-port 10-Gigabit Ethernet LAN/WAN PIC Overview

Configuring Control Queue Disable on a 10-port 10-Gigabit Ethernet LAN/WAN PIC

Copyright 2014, Juniper Networks, Inc.

751

Interfaces Fundamentals for Routing Devices

no-redirects
Syntax
Hierarchy Level
Release Information

Description

no-redirects;
[edit interfaces interface-name unit logical-unit-number family family]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Do not send protocol redirect messages on the interface.
To disable the sending of protocol redirect messages for the entire router or switch,
include the no-redirects statement at the [edit system] hierarchy level.

Default
Required Privilege
Level
Related
Documentation

752

Interfaces send protocol redirect messages.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Disabling the Transmission of Redirect Messages on an Interface on page 210

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

source-filtering
Syntax
Hierarchy Level

Release Information

Description

(source-filtering | no-source-filtering);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Packet Transport Routers.
For aggregated Ethernet, Fast Ethernet, Gigabit Ethernet, and Gigabit Ethernet IQ
interfaces only, enable the filtering of MAC source addresses, which blocks all incoming
packets to that interface. To allow the interface to receive packets from specific MAC
addresses, include the source-address-filter statement.
If the remote Ethernet card is changed, the interface is no longer able to receive packets
from the new card because it has a different MAC address.

Default
Required Privilege
Level
Related
Documentation

Source address filtering is disabled.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling Ethernet MAC Address Filtering

Configuring MAC Address Filtering on PTX Series Packet Transport Routers

accept-source-mac on page 399

source-address-filter on page 887

Copyright 2014, Juniper Networks, Inc.

753

Interfaces Fundamentals for Routing Devices

syslog (Monitoring)
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

(syslog | no-syslog);
[edit interfaces mo-fpc/pic/port multiservice-options]

Statement introduced before Junos OS Release 7.4.

System logging is enabled by default. The system log information of the Monitoring
Services PIC is passed to the kernel for logging in the /var/log directory.

syslogEnable PIC system logging.

no-syslogDisable PIC system logging.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Multiservice Physical Interface Properties on page 153

Junos OS Services Interfaces Library for Routing Devices

no-termination-request
Syntax
Hierarchy Level

no-termination-request;
[edit interfaces interface-name ppp-options],
[edit interfaces lsq-fpc/pic/port lsq-failure-options]

Release Information

Statement introduced in Junos OS Release 7.4.

Support at the [edit interfaces interface-name ppp-options] hierarchy level added in Junos
OS Release 8.3.

Description

For LSQ PICs or link PICs in redundant LSQ configurations, you can inhibit the router from
sending PPP termination-request messages to the remote host if the PIC fails.

Required Privilege
Level
Related
Documentation

754

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Link PIC Failover on Channelized OC3 IQ and IQE Interfaces

Configuring Link PIC Failover on Channelized OC12/STM4 IQ and IQE Interfaces

Configuring Link PIC Failover on Channelized STM1 Interfaces

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

translate-discard-eligible
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(translate-discard-eligible | no-translate-discard-eligible);
[edit interfaces interface-name unit logical-unit-number family ccc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family ccc]

Statement introduced before Junos OS Release 7.4.

For interfaces with encapsulation type Frame Relay CCC, enable or disable translation
of Frame Relay discard eligible (DE) control bits.
DE bit translation is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Frame Relay Control Bit Translation

translate-fecn-and-becn
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(translate-fecn-and-becn | no-translate-fecn-and-becn);
[edit interfaces interface-name unit logical-unit-number family ccc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family ccc]

Statement introduced before Junos OS Release 7.4.

For interfaces with encapsulation type Frame Relay CCC, enable or disable translation
of Frame Relay forward explicit congestion notification (FECN) control bits and Frame
Relay backward explicit congestion notification (BECN) control bits.
FECN and BECN bit translation is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Frame Relay Control Bit Translation

Copyright 2014, Juniper Networks, Inc.

755

Interfaces Fundamentals for Routing Devices

unframed
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(unframed | no-unframed);
[edit interfaces interface-name e3-options]

Statement introduced before Junos OS Release 7.4.

For E3 IQ interfaces only, enable or disable unframed mode. In unframed mode, the E3
IQ interface do not detect yellow (ylw) or loss-of-frame (lof) alarms.
Unframed mode is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring E3 IQ and IQE Unframed Mode

z0-increment
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

756

(z0-increment | no-z0-increment);
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

Configure an incremental STM ID rather than a static one.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring an Incrementing STM ID to Interoperate with Older Equipment in SDH Mode

sonet-options on page 884

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

node-id
Syntax
Hierarchy Level
Release Information
Description

node-id mac-address;
[edit protocols protection-group ethernet-ring ring-name]

Statement introduced in Junos OS Release 9.4.

For EX Series switches and QFX Series switches, node-id is not configurable.
For MX Series routers, optionally specify the MAC address of a node in the protection
group. If this statement is not included, the router assigns the nodes MAC address.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

non-revertive (Interfaces)
Syntax
Hierarchy Level
Release Information

Description

Required Privilege
Level
Related
Documentation

non-revertive;
[edit interfaces aeX aggregated-ether-options lacp link-protection]

Statement introduced in Junos OS Release 9.3.

Statement introduced in Junos OS Release 11.4 for EX Series switches.
Disable the ability to switch to a better priority link (if one is available) once a link is
established as active and collection distribution is enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

link-protection on page 670

Configuring Aggregated Ethernet Link Protection

Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

757

Interfaces Fundamentals for Routing Devices

oam
Syntax

758

oam {
ethernet {
connectivity-fault-management {
action-profile profile-name {
default-actions {
interface-down;
}
}
performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
maintenance-domain domain-name {
level number;
name-format (character-string | none | dns | mac+2octet);
maintenance-association ma-name {
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number;
port-status-tlv;
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
}
}
}
link-fault-management {
action-profile profile-name {
action {
link-down;
send-critical-event;
syslog;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
interface interface-name {
apply-action-profile
link-discovery (active | passive);
loopback-tracking;
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
}
}
}
}

Hierarchy Level
Release Information

[edit protocols]

Statement introduced in Junos OS Release 8.2.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers.

Copyright 2014, Juniper Networks, Inc.

759

Interfaces Fundamentals for Routing Devices

Description

For Ethernet interfaces on M320, M120, MX Series, and T Series routers and PTX Series
Packet Transport Routers, provide IEEE 802.3ah Operation, Administration, and
Maitenance (OAM) support.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

760

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.3ah OAM Link-Fault Management Overview

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

oam-liveness
Syntax

Hierarchy Level

Release Information

Description

oam-liveness {
down-count cells;
up-count cells;
}
[edit interfaces interface-name atm-options vpi vpi-identifier],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number family family address address
multipoint-destination address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address multipoint-destination address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
For ATM encapsulation only, configure Operation, Administration, and Maintenance
(OAM) F5 loopback cell count thresholds. Not supported on ATM-over-SHDSL interfaces.
For ATM2 IQ PICs only, configure OAM F4 loopback cell count thresholds at the [edit
interfaces interface-name atm-options vpi vpi-identifier] hierarchy level.

Options

down-count cellsMinimum number of consecutive OAM F4 or F5 loopback cells lost

before a VC is declared down.

Range: 1 through 255
Default: 5 cells
up-count cellsMinimum number of consecutive OAM F4 or F5 loopback cells received

before a VC is declared up.

Range: 1 through 255
Default: 5 cells
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the ATM OAM F5 Loopback Cell Threshold

Copyright 2014, Juniper Networks, Inc.

761

Interfaces Fundamentals for Routing Devices

oam-period
Syntax
Hierarchy Level

Release Information

Description

oam-period (disable | seconds);

[edit interfaces interface-name atm-options vpi vpi-identifier],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number family family address address
multipoint-destination address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address multipoint-destination address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
For ATM encapsulation only, configure the OAM F5 loopback cell period. Not supported
on ATM-over-SHDSL interfaces.
For ATM2 IQ PICs only, configure the OAM F4 loopback cell period at the [edit interfaces
interface-name atm-options vpi vpi-identifier] hierarchy level.

Default

Options

If you omit this statement, OAM F5 loopback cells are not initiated, but the interface still
responds if it receives OAM F5 loopback cells.
disableDisable the OAM loopback cell transmit feature.
secondsOAM loopback cell period.

Range: 1 through 900 seconds

Required Privilege
Level
Related
Documentation

762

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Defining the ATM OAM F5 Loopback Cell Period

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

oc-slice
Syntax
Hierarchy Level
Release Information
Description
Default

Options

oc-slice oc-slice-range;
[edit interfaces interface-name partition partition-number]

Statement introduced before Junos OS Release 7.4.

For channelized OC12 IQ interfaces only, configure the range of SONET/SDH slices.
If you do not include either this statement or the no-partition statement, the Channelized
OC12 IQ PICs not partitioned, and no data channels are configured.
oc-slice-rangeRange of SONET/SDH slices. OC3 interfaces must occupy three

consecutive OC slices per interface, in the form 13, 46, 79, or 1012. The T3, T1,
and DS0 interface types each occupy one OC slice per interface.
Range: For OC3 interfaces,13, 46, 79, or 1012; for SONET/SDH and T3 interfaces,
112
The remaining statement is explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Channelized OC12/STM4 IQ and IQE Interfaces Overview

open-timeout
Syntax
Hierarchy Level
Release Information
Description
Options

open-timeout seconds;
[edit interfaces interface-name services-options]

Statement introduced before Junos OS Release 7.4.

Configure timeout period for Transmission Control Protocol (TCP) session establishment.
secondsTimeout period in seconds.

Range: 4 through 224 seconds

Default: 5 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

763

Interfaces Fundamentals for Routing Devices

operating-mode
Syntax
Hierarchy Level
Release Information
Description

Options

operating-mode mode;
[edit interfaces at-fpc/pic/port dsl-options]

Statement introduced before Junos OS Release 7.4.

For J Series Services Routers only, modify the operating mode of the digital subscriber
line for an ATM interface.
modeOperating mode for ATM-over-ADSL interfaces. The mode can be one of the

following:

adsl2plusSet the ADSL line to train in the ITU G.992.5 mode.

ansi-dmtSet the ADSL line to train in the ANSI T1.413 Issue 2 mode.

autoSet the ADSL line to autonegotiate the setting to match the setting of the DSL

access multiplexer (DSLAM) located at the central office. The ADSL line trains in the
ANSI T1.413 Issue 2 (ansi-dmt) or ITU G.992.1 (itu-dmt) mode.

etsiSet the ADSL line to train in the ETSI TS 101 388 V1.3.1 mode.

itu-annexb-ur2Set the ADSL line to train in the ITU G.992.1 UR-2 mode.

itu-annexb-non-ur2Set the ADSL line to train in the ITU G.992.1 non-UR-2 mode.

itu-dmtSet the ADSL line to train in the ITU G.992.1 mode.

itu-dmt-bisSet the ADSL line to train in the ITU G.992.3 mode.

Default: auto
Required Privilege
Level
Related
Documentation

764

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-ADSL Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

optics-options
Syntax

Hierarchy Level
Release Information

Description

Options
Required Privilege
Level
Related
Documentation

optics-options {
alarm low-light-alarm {
(link-down | syslog);
}
tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs number);
tx-power dbm;
warning low-light-warning {
(link-down | syslog);
}
wavelength nm;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

alarm option and warning options introduced in Junos OS Release 10.0.
Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement and tx-power option introduced in Junos OS Release 13.2 for PTX Series
routers.
tca option introduced in Junos OS Release 14.2 for PTX Series routers.
For 10-Gigabit Ethernet or 100-Gigabit Ethernet dense wavelength-division multiplexing
(DWDM) interfaces only, configure full C-band International Telecommunication Union
(ITU)-Grid tunable optics.
The remaining statements are explained separately.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Ethernet DWDM Interface Wavelength Overview

100-Gigabit Ethernet OTN Options Configuration Overview

Copyright 2014, Juniper Networks, Inc.

765

Interfaces Fundamentals for Routing Devices

option-82
Syntax
Hierarchy Level

Release Information

Description

option-82 <circuit-id> <remote-id>;

[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include]

Statement introduced in Junos OS Release 10.0.

Options circuit-id and remote-id introduced in Junos OS Release 11.4.
Specify that the option 82 information from the client PDU is concatenated with the
username during the subscriber authentication process.
For autosense VLANs, you can additionally specify Option 82 suboption information that
is concatenated with the username. You can specify either both or neither of the Agent
Circuit ID (suboption 1) and Agent Remote ID (suboption 1). If you specify both, the Agent
Circuit ID is supplied first, followed by a delimiter, and then the Agent Remote ID. If you
specify that neither suboption is supplied, the raw payload of Option 82 from the PDU
is concatenated to the username.

NOTE: The option 82 value used in creating the username is based on the
option 82 value that is encoded in the incoming DHCP discover packet. The
use of suboptions is supported for DHCPv4 only.

Options

noneUse the raw payload of Option 82 from the PDU.

circuit-id(Optional) Use the Agent Circuit ID suboption (suboption 1).
remote-id(Optional) Use the Agent Remote ID suboption (suboption 2).

Required Privilege
Level
Related
Documentation

766

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

Using DHCP Option 82 Suboptions in Authentication Usernames for Autosense VLANs

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

otn-options
Syntax

Hierarchy Level

Release Information

otn-options {
bytes (otn-options) transmit-payload-type value;
fec (efec | gfec | gfec-sdfec | none | ufec);
(is-ma | no-is-ma);
(laser-enable | no-laser-enable);
(line-loopback | no-line-loopback);
(local-loopback | no-local-loopback);
(odu-ttim-action-enable | no-odu-ttim-action-enable);
(otu-ttim-action-enable | no-otu-ttim-action-enable);
odu-delay-management {
(bypass | no-bypass);
(monitor-end-point | no-monitor-end-point);
number-of-frames value;
(no-start-measurement | start-measurement;
}
odu-signal-degrade {
ber-threshold-clear value;
ber-threshold-signal-degrade value;
interval value;
}
(prbs | no-prbs);
preemptive-fast-reroute {
(backward-frr-enable | no-backward-frr-enable);
(signal-degrade-monitor-enable | no-signal-degrade-monitor-enable);
odu-backward-frr-enable | no-odu-backward-frr-enable;
odu-signal-degrade-monitor-enable | no-odu-signal-degrade-monitor-enable;
}
rate {
(fixed-stuff-bytes | no-fixed-stuff-bytes);
oc192;
otu4;
(pass-through | no-pass-through);
}
signal-degrade {
ber-threshold-clear value;
ber-threshold-signal-degrade value;
interval value;
}
tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs number);
trigger trigger-identifier;
tti tti-identifier;
}
[edit interfaces ge-fpc/pic/port]
[edit interfaces xe-fpc/pic/port]
[edit interfaces et-fpc/pic/port]

Statement introduced in Junos OS Release 9.4.

bytes, is-ma, local-loopback, no-is-ma, no-local-loopback, no-odu-ttim-action-enable,
no-otu-ttim-action-enable, no-prbs, odu-delay-management, odu-ttim-action-enable,

Copyright 2014, Juniper Networks, Inc.

767

Interfaces Fundamentals for Routing Devices

otu-ttim-action-enable, prbs, preemptive-fast-reroute, and signal-degrade statements

introduced in Junos OS Release 13.2 for PTX Series routers.

oc192 statement introduced in Junos OS Release 13.3R3 for MX Series routers.
odu-signal-degrade, odu-backward-frr-enable | no-odu-backward-frr-enable,
odu-signal-degrade-monitor-enable | no-odu-signal-degrade-monitor-enable statements
introduced in Junos OS Release 14.1R2 and 14.2 for P2-100GE-OTN PIC in PTX5000
routers.
tca option introduced in Junos OS Release 14.2 for PTX Series routers.
Description
Options
Required Privilege
Level
Related
Documentation

Specify the Ethernet optical transport network (OTN) interface and options.
The remaining statements are explained separately.
interfacesTo view this statement in the configuration.
interfaces-controlTo add this statement to the configuration.

10-Gigabit Ethernet OTN Options Configuration Overview

100-Gigabit Ethernet OTN Options Configuration Overview

Configuring 100-Gigabit Ethernet OTN Optics

output
Syntax

Hierarchy Level

Release Information
Description
Options
Required Privilege
Level
Related
Documentation

768

output {
service-set service-set-name <service-filter filter-name>;
}
[edit interfaces interface-name unit logical-unit-number family inet service],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service]

Statement introduced before Junos OS Release 7.4.

Define one or more output service sets and filters to be applied to traffic.
The remaining statements are explained separately.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

output-list
Syntax
Hierarchy Level

Release Information

output-list [ filter-names ];
[edit interfaces interface-name unit logical-unit-number family family filter],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family filter]

Statement introduced in Junos OS Release 7.6.

Description

Apply a group of filters to evaluate when packets are transmitted on an interface.

Options

[ filter-names ]Name of a filter to evaluate when packets are transmitted on the

interface. Up to 16 filters can be included in a filter input list.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying a Filter to an Interface on page 219

input-list on page 622

Routing Policies, Firewall Filters, and Traffic Policers Feature Guide for Routing Devices

Junos OS Services Interfaces Library for Routing Devices

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

769

Interfaces Fundamentals for Routing Devices

output-policer
Syntax
Hierarchy Level

Release Information

Description

Options

output-policer policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]

Statement introduced in Junos OS Release 8.2.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Apply a single-rate two-color policer to the Layer 2 output traffic at the logical interface.
The output-policer and output-three-color statements are mutually exclusive.
policer-nameName of the single-rate two-color policer that you define at the [edit
firewall] hierarchy level.

Required Privilege
Level
Related
Documentation

770

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Two-Color and Three-Color Policers at Layer 2

Applying Layer 2 Policers to Gigabit Ethernet Interfaces

Configuring a Gigabit Ethernet Policer

input-policer on page 623

input-three-color on page 625

layer2-policer on page 657

logical-interface-policer on page 683

output-three-color on page 772

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

output-priority-map
Syntax

Hierarchy Level

Release Information

Description

output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile]
[edit interfaces interface-name ether-options ethernet-switch-profile
ethernet-policer-profile]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 13.2 for the QFX Series.
For Gigabit Ethernet IQ and 10-Gigabit Ethernet interfaces only, define the output policer
priority map to be applied to outgoing frames on this interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying an Output Priority Map

input-priority-map on page 624

Copyright 2014, Juniper Networks, Inc.

771

Interfaces Fundamentals for Routing Devices

output-three-color
Syntax
Hierarchy Level

Release Information

Description

Options
Required Privilege
Level
Related
Documentation

772

output-three-color policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]

Statement introduced in Junos OS Release 8.2.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Apply a single-rate or two-rate three-color policer to the Layer 2 output traffic at the
logical interface. The output-three-color and output-policer statements are mutually
exclusive.
policer-nameName of the single-rate or two-rate three-color policer.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Two-Color and Three-Color Policers at Layer 2

Applying Layer 2 Policers to Gigabit Ethernet Interfaces

Configuring a Gigabit Ethernet Policer

input-three-color on page 625

input-policer on page 623

layer2-policer on page 657

logical-interface-policer on page 683

output-policer on page 770

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

output-vlan-map (Aggregated Ethernet)

Syntax

Hierarchy Level

Release Information
Description

output-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 8.2.

For aggregated Ethernet interfaces using Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ2
and IQ2-E interfaces, and 100-Gigabit Ethernet Type 5 PIC with CFP only, define the
rewrite profile to be applied to outgoing frames on this logical interface.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Stacking and Rewriting Gigabit Ethernet VLAN Tags

input-vlan-map (Aggregated Ethernet) on page 626

Copyright 2014, Juniper Networks, Inc.

773

Interfaces Fundamentals for Routing Devices

output-vlan-map
Syntax

output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}

Hierarchy Level

[edit interfaces interface-name unit logical-unit-number],

[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Release Information

Statement introduced before Junos OS Release 7.4.

pop-pop, pop-swap, push-push, swap-push, and swap-swap statements added in Junos
OS Release 8.1.
Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Statement introduced in Junos OS Release 13.2X51-D20 for the QFX Series.

Description

For Gigabit Ethernet IQ, 10-Port 10-Gigabit Ethernet SFPP interfaces, 100-Gigabit Ethernet
Type 5 PIC with CFP only, Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet,
and aggregated Ethernet interfaces, define the rewrite operation to be applied to outgoing
frames on this logical interface.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

774

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Stacking and Rewriting Gigabit Ethernet VLAN Tags

input-vlan-map on page 627

Configuring Q-in-Q Tunneling (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

overflow (Receive Bucket)

Syntax
Hierarchy Level
Release Information
Description
Options

overflow (discard | tag);

[edit interfaces interface-name receive-bucket]

Statement introduced before Junos OS Release 7.4.

Specify how to handle packets that exceed the threshold for the receive leaky bucket.
tagTag, count, and process received packets that exceed the threshold.
discardDiscard received packets that exceed the threshold. No counting is done.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

overflow (Transmit Bucket)

Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

overflow discard;
[edit interfaces interface-name transmit-bucket]

Statement introduced before Junos OS Release 7.4.

Discard packets that exceed the threshold for the transmit leaky bucket.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

Copyright 2014, Juniper Networks, Inc.

775

Interfaces Fundamentals for Routing Devices

override
Syntax
Hierarchy Level

Release Information
Description

Options

override tag vlan-tag dynamic-profile profile name;

[edit interfaces interface-name auto-configure vlan-ranges],
[edit interfaces interface-name auto-configure stacked-vlan-ranges]

Statement introduced in Junos OS Release 11.2.

Override dynamic profile assignment to individual VLANs that are already part of a
previously defined VLAN range and dynamic profile.
vlan-tagVLAN tag that you want to override.
profile-nameName of the dynamic profile that you want to use when overriding the

specified VLAN tag.

Required Privilege
Level
Related
Documentation

776

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Overriding the Dynamic Profile Used for an Individual VLAN

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

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

pado-advertise
Syntax
Hierarchy Level
Release Information
Description

pado-advertise;
[edit protocols pppoe]

Statement introduced in Junos OS Release 10.2.

Enable named services configured in PPPoE service name tables to be advertised in
PPPoE Active Discovery Offer (PADO) control packets. By default, advertisement of
named services in PADO packets is disabled.

NOTE: If you enable advertisement of named services in PADO packets,

make sure the number and length of of all advertised service entries does
not exceed the maximum transmission unit (MTU) size of the PPPoE
underlying interface.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Enabling Advertisement of Named Services in PADO Control Packets

paired-group
Syntax
Hierarchy Level
Release Information
Description
Options

paired-group group-name;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Configure load sharing between two working protect circuit pairs.
group-nameCircuits group name, as configured with the protect-circuit or working-circuit

statement.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring APS Load Sharing

working-circuit on page 991

Copyright 2014, Juniper Networks, Inc.

777

Interfaces Fundamentals for Routing Devices

pap
Syntax

Hierarchy Level

Release Information
Description

pap {
access-profile name;
default-pap-password password;
local-name name;
local-password password;
passive;
}
[edit interfaces interface-name ppp-options],
[edit interfaces interface-name unit logical-unit-number ppp-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options]

Statement introduced in Junos OS Release 8.3.

Configure the Password Authentication Protocol (PAP). Use PAP authentication as a
means to provide a simple method for the peer to establish its identity using a two-way
handshake. This is done only upon initial link establishment.
After the link is established, an ID and password pair is repeatedly sent by the peer to the
authenticator until authentication is acknowledged or the connection is terminated.

BEST PRACTICE: On inline service (si) interfaces for L2TP, only the pap
statement itself is typically used for subscriber management. We recommend
that you leave the subordinate statements at their default values.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

778

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Challenge Handshake Authentication Protocol on page 126

Configuring PPP PAP Authentication on page 178

Tracing Operations of the pppd Process on page 137

traceoptions (PPP Process) on page 928

Example: Configuring PAP for an L2TP Profile

Applying PPP Attributes to L2TP LNS Subscribers Per Inline Service Interface

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

pap-password
Syntax
Hierarchy Level
Release Information

Description

pap-password password;
[edit access profile profile-name client client-name]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Configure the Password Authentication Protocol (PAP) password.

NOTE: This statement is not supported for L2TP LNS on MX Series routers.

Options
Required Privilege
Level
Related
Documentation

passwordPAP password.

adminTo view this statement in the configuration.

admin-controlTo add this statement to the configuration.

Configuring the PAP Password for an L2TP Profile

Copyright 2014, Juniper Networks, Inc.

779

Interfaces Fundamentals for Routing Devices

partition
Syntax

Hierarchy Level
Release Information
Description

Default

Options

partition partition-number oc-slice oc-slice-range interface-type type timeslots

time-slot-range;
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

For IQ interfaces and J Series interfaces on the Dual-Port Channelized E1 and T1PIM,
configure the channelized interface partition. The partition number is correlated with the
channel number. Partition and channel numbering on IQ interfaces begins with :1, not :0.
If you omit this statement, the channelized PIC or PIM is not partitioned, and no data
channels are configured.
partition-numberSublevel interface partition index.

Range:

1 through 4 for an OC3 interface on a channelized OC12 IQ interface.

1 through 12 for a T3 interface on a channelized OC12 IQ interface.

1 through 4 for a T3 interface on a channelized T3 IQ interface.

1 through 28 for a T1 IQ interface on a channelized OC12 IQ or channelized T3 IQ interface.

1 through 10 for an E1 interface on a channelized E1 IQ interface.

1 through 30 on a channelized E1 interface.

1 through 23 on a channelized T1 interface.

1 through 24 for NxDS0 interfaces on either channelized OC12 IQ or channelized DS3

IQ interfaces.

0 through 31(with 0 reserved for framing) for NxDS0 interfaces on channelized E1 IQ

interfaces.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

780

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Channelized E1 IQ and IQE Interfaces Overview

Channelized OC12/STM4 IQ and IQE Interfaces Overview

Configuring Channelized T3 IQ Interfaces

no-partition on page 748

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

passive (CHAP)
Syntax
Hierarchy Level

Release Information
Description

passive;
[edit interfaces interface-name ppp-options chap],
[edit interfaces interface-name unit logical-unit-number ppp-options chap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options chap]

Statement introduced before Junos OS Release 7.4.

Do not challenge the peer, but respond if challenged. If you omit this statement from the
configuration, the interface always challenges its peer.
For ATM2 IQ interfaces only, you can configure CHAP on the logical interface unit if the
logical interface is configured with one of the following PPP over ATM encapsulation
types:

Required Privilege
Level
Related
Documentation

atm-ppp-llcPPP over AAL5 LLC encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Passive Mode on page 128

Junos OS Administration Library for Routing Devices

passive (PAP)
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

passive;
[edit interfaces interface-name ppp-options pap],
[edit interfaces interface-name unit logical-unit-number ppp-options pap],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options pap]

Statement introduced in Junos OS Release 8.3.

Initiate an authentication request when the PAP option is received from a peer. If you
omit this statement from the configuration, the interface requires the peer to initiate an
authentication request.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Passive Mode on page 131

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

781

Interfaces Fundamentals for Routing Devices

passive-monitor-mode
Syntax
Hierarchy Level

Release Information
Description

passive-monitor-mode;
[edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Monitor packet flows from another router. If you include this statement in the
configuration, the interface does not send keepalives or alarms, and does not participate
actively on the network.
This statement is supported on ATM, Ethernet, and SONET/SDH interfaces. For more
information, see ATM Interfaces Feature Guide for Routing Devices.
For ATM and Ethernet interfaces, you can include this statement on the physical interface
only.
For SONET/SDH interfaces, you can include this statement on the logical interface only.

Required Privilege
Level
Related
Documentation

782

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Enabling Passive Monitoring on ATM Interfaces

Passive Monitoring on Ethernet Interfaces Overview

Enabling Packet Flow Monitoring on SONET/SDH Interfaces

multiservice-options on page 725

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

password (Interfaces)
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

password password-string;
[edit interfaces interface-name auto-configure vlan-ranges authentication],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication]

Statement introduced in Junos OS Release 10.0.

Configure the password that is sent to the external AAA authentication server for
subscriber VLAN or stacked VLAN interface authentication.
password-stringAuthentication password.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an Authentication Password for VLAN or Stacked VLAN Ranges

path-database-size
Syntax
Hierarchy Level
Release Information
Description
Options

path-database-size path-database-size;
[edit protocols oam ethernet connectivity-fault-management linktrace]

Statement introduced in Junos OS Release 8.5.

Number of linktrace reply entries to be stored per linktrace request.
path-database-sizeDatabase size.

Range: 1 through 255

Default: 64
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Linktrace Protocol in CFM

Copyright 2014, Juniper Networks, Inc.

783

Interfaces Fundamentals for Routing Devices

path-trace
Syntax
Hierarchy Level
Release Information
Description

path-trace trace-string;
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

For SONET/SDH interfaces and 10-Gigabit Ethernet interfaces in WAN PHY mode,
configure a path trace identifier, which is a text string that identifies the circuit.
On SONET/SDH OC48 interfaces that are configured for channelized (multiplexed)
mode (by including the no-concatenate statement at the [edit chassis fpc slot-number
pic pic-number] hierarchy level), the bytes e1-quiet and bytes f1 options have no effect.
The bytes f2, bytes z3, bytes z4, and path-trace options work correctly on channel 0 and
work in the transmit direction only on channels 1, 2, and 3.
For DS3 channels on a channelized OC12 interface, you can configure a unique path trace
for each of the 12 channels. Each path trace can be up to 16 bytes. For channels on a
channelized OC12 IQ interface, each path trace can be up to 64 bytes.

Options

trace-stringText string that identifies the circuit. If the string contains spaces, enclose

it in quotation marks. A common convention is to use the circuit identifier as the path
trace identifier. If you do not configure an identifier, the Junos OS uses the system
and interface names to construct the default trace-string. For all nonchannelized
SONET/SDH interfaces, the default trace-string is system-name interface-name. For
channelized SONET/SDH interfaces and 10Gigabit Ethernet WAN-PHY interfaces,
the default trace-string is interface-name.
Required Privilege
Level
Related
Documentation

784

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the SONET/SDH Path Trace Identifier for a Circuit

sonet-options on page 884

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

payload-scrambler
Syntax
Hierarchy Level

Release Information
Description

(payload-scrambler | no-payload-scrambler);
[edit interfaces interface-name e3-options],
[edit interfaces interface-name sonet-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Enable or disable HDLC scrambling on an E3, a SONET/SDH, or a T3 interface. This type
of scrambling provides better link stability. Both sides of a connection must either use or
not use scrambling.
If you commit a T3 interface configuration that has HDLC payload scrambling enabled,
the interface must also be configured to be compatible with the channel service unit
(CSU) at the remote end of the line.
Disable payload scrambling on an E3 interface if Digital Link compatibility mode is used.
On a channelized OC12 interface, the sonet payload-scrambler statement is ignored. To
configure scrambling on the DS3 channels on the interface, you can include the t3-options
payload-scrambler statement in the configuration for each DS3 channel.

NOTE: The payload-scrambler statement at the [edit interfaces interface-name

e3-options] hierarchy level is not valid for IQE PICs.

Default

Required Privilege
Level
Related
Documentation

Payload scrambling is disabled on all E3 and T3 interfaces; it is enabled by default on

E3/T3 over ATM interfaces and on SONET/SDH interfaces.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring E3 and T3 Parameters on ATM Interfaces

Configuring E3 HDLC Payload Scrambling

Configuring SONET/SDH HDLC Payload Scrambling for Link Stability

Configuring T3 HDLC Payload Scrambling

Examples: Configuring T3 Interfaces

compatibility-mode on page 474

Copyright 2014, Juniper Networks, Inc.

785

Interfaces Fundamentals for Routing Devices

payload-size
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

payload-size bytes ;
[edit interfaces interface-name satop-options]

Option introduced in Junos OS Release 9.3.

Specify the satop-options payload-size in integer number of bytes.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

ATM Support on Circuit Emulation PICs Overview

satop-options on page 861

pdu-interval
Syntax
Hierarchy Level
Release Information
Description

Options

pdu-interval interval;
[edit protocols oam ethernet link-fault-management interface interface-name]

Statement introduced in Junos OS Release 8.2.

For Ethernet interfaces on EX Series switches and M320, M120, MX Series, and T Series
routers, specify the periodic OAM PDU sending interval for fault detection. Used for IEEE
802.3ah Operation, Administration, and Management (OAM) support.
intervalPeriodic OAM PDU sending interval.

Range: 100 through 1000 milliseconds

Default: 1000 milliseconds
Required Privilege
Level
Related
Documentation

786

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the OAM PDU Interval

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

pdu-threshold
Syntax
Hierarchy Level
Release Information
Description

Options

pdu-threshold threshold-value;
[edit protocols oam ethernet link-fault-management interface interface-name]

Statement introduced in Junos OS Release 8.2.

For Ethernet interfaces on EX Series switches and M320, M120, MX Series, and T Series
routers, specify the number of OAM PDUs to miss before an error is logged. Used for IEEE
802.3ah Operation, Administration, and Management (OAM) support.
threshold-valueThe number of PDUs missed before declaring the peer lost.

Range: 3 through 10 PDUs

Default: 3 PDUs
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the OAM PDU Threshold

Copyright 2014, Juniper Networks, Inc.

787

Interfaces Fundamentals for Routing Devices

peer
Syntax

Hierarchy Level
Release Information
Description

Options

peer a.b.c.d {
interface interface-name;
}
[edit interfaces interface-name multi-chassis-protection]

Statement introduced in Junos OS Release 11.1.

For MX Series routers with multichassis aggregated Ethernet (MC-AE) interfaces, use
the multi-chassis-protection statement under the physical interface level to reduce the
configuration at the logical interface level. If the interchassis control protocol connection
(ICCP) is UP and the interchassis data link (ICL) comes UP, the router configured as
standby will bring up the MC-AE interfaces shared with the peer active-active node
specified by the peer statement. You must also specify the peers physical interface.
a.b.c.dSpecify the IP address of the peer.
interface interface-nameSpecify the peers physical interface: interface

interface-name-fpc/pic/port
Required Privilege
Level
Related
Documentation

788

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Multichassis Link Aggregation

Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation
on MX Series Routers

Configuring Aggregated Ethernet Link Protection

Example: Configuring Aggregated Ethernet Link Protection

multi-chassis-protection on page 719

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

peer-unit
Syntax
Hierarchy Level

Release Information
Description
Options
Required Privilege
Level
Related
Documentation

peer-unit unit-number;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Configure a peer relationship between two logical systems.
unit-numberPeering logical system unit number.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

789

Interfaces Fundamentals for Routing Devices

per-unit-scheduler
Syntax
Hierarchy Level

per-unit-scheduler;
[edit interfaces interface-name]

Release Information

Statement introduced before Junos OS Release 7.4.

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.

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 map names 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: Per-unit scheduling is not supported on T1 interfaces configured on

the Channelized OC12 IQ PIC.

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.
Required Privilege
Level
Related
Documentation

790

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs

vlan-tagging on page 976

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

flexible-vlan-tagging on page 577

Applying Scheduling and Shaping to VLANs

Configuring Virtual LAN Queuing and Shaping on PTX Series Routers

performance-monitoring
Syntax

Hierarchy Level
Release Information
Description

performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
[edit protocols oam ethernet connectivity-fault-management]

Statement introduced in Junos OS Release 9.5.

Specify performance monitoring support for Ethernet frame delay measurement.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

Ethernet Frame Delay Measurements Overview

Guidelines for Configuring Routers to Support an ETH-DM Session

Enabling the Hardware-Assisted Timestamping Option

Copyright 2014, Juniper Networks, Inc.

791

Interfaces Fundamentals for Routing Devices

periodic
Syntax
Hierarchy Level

Release Information

Description

Options

periodic interval;
[edit interfaces aex aggregated-ether-options lacp],
[edit interfaces interface-range name aggregated-ether-options lacp]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
For aggregated Ethernet interfaces only, configure the interval for periodic transmission
of LACP packets.
intervalInterval for periodic transmission of LACP packets.

fastTransmit packets every second.

slowTransmit packets every 30 seconds.

Default: fast
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring LACP for Aggregated Ethernet Interfaces

Configuring Aggregated Ethernet LACP (CLI Procedure)

Example: Configuring Aggregated Ethernet High-Speed Uplinks Between an EX4200

Virtual Chassis Access Switch and an EX4200 Virtual Chassis Distribution Switch

pfc
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

792

pfc;
[edit interfaces interface-name ppp-options compression],
[edit interfaces interface-name unit logical-unit-number ppp-options compression],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
ppp-options compression]

Statement introduced before Junos OS Release 7.4.

For interfaces with PPP encapsulation, configure the router to compress the protocol
field to one byte.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the PPP Protocol Field Compression on page 135

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

pic-type
Syntax
Hierarchy Level
Release Information
Description
Options

pic-type (atm1 | atm2);

[edit interfaces at-fpc/pic/port atm-options]

Statement introduced before Junos OS Release 7.4.

For ATM interfaces, configure the type of ATM PIC installed in your router.
atm1ATM1 PIC.
atm2ATM2 IQ PIC.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the ATM PIC Type

plp-to-clp
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

plp-to-clp;
[edit interfaces at-fpc/pic/port atm-options],
[edit interfaces at-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces at--fpc/pic/port unit
logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, enable the PLP setting to be copied to the cell-loss priority
(CLP) bit.
If you omit this statement, the Junos OS does not copy the PLP setting to the CLP bit.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling the PLP Setting to Be Copied to the CLP Bit

Copying the PLP Setting to the CLP Bit on ATM Interfaces

Copyright 2014, Juniper Networks, Inc.

793

Interfaces Fundamentals for Routing Devices

plp1
Syntax
Hierarchy Level

Release Information

Description

Default
Options

plp1 cells;
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number address address family family
multipoint-destination address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
address address family family multipoint-destination address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for QFX Series switches.
For ATM2 IQ interfaces only, define the EPD threshold on a VC. The EPD threshold is a
limit on the number of transmit packets that can be queued. Packets that exceed the
limit are discarded. This threshold applies to packets that have a PLP of 1.
EPD threshold is unregulated.
cellsMaximum number of cells.

Range: For 1-port and 2-port OC12 interfaces, 1 through 425,984 cellsFor 1-port OC48
interfaces, 1 through 425,984 cellsFor 2-port OC3, DS3, and E3 interfaces, 1 through
212,992 cellsFor 4-port DS3 and E3 interfaces, 1 through 106,496 cells
Required Privilege
Level
Related
Documentation

794

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Two EPD Thresholds per Queue

Configuring an ATM Scheduler Map

linear-red-profile on page 662

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

point-to-point
Syntax
Hierarchy Level

Release Information

point-to-point;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Description

For all interfaces except aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet,
configure the interface unit as a point-to-point connection. This is the default connection
type.

Default

If you omit this statement, the interface unit is configured as a point-to-point connection.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Point-to-Point Connection on page 175

multipoint on page 723

policer (CFM Firewall)

Syntax

Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

policer cfm-policer {
if-exceeding {
bandwidth-limit 8k;
burst-size-limit 2k;
}
then discard;
}
[edit firewall]

Statement introduced in Junos OS Release 10.0.

Attach an explicit policer to CFM sessions.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Rate Limiting of Ethernet OAM Messages

policer (CFM Global) on page 796

policer (CFM Session) on page 797

Copyright 2014, Juniper Networks, Inc.

795

Interfaces Fundamentals for Routing Devices

policer (CFM Global)

Syntax

Hierarchy Level
Release Information
Description
Options

policer {
all cfm-policer-name;
continuity-check cfm-policer-name;
other cfm-policer-name;
}
}
[edit protocols oam ethernet connectivity-fault-management]

Statement introduced in Junos OS Release 10.0.

Specify a policer at the global level to police the CFM traffic belonging to all sessions.
continuity-check cfm-policer-namePolice all continuity check packets with the policer

specified.
other cfm-policer-namePolice all non-continuity check packets with the policer specified.
all cfm-policer-namePolice all CFM packets with policer specified. If the all option is

used, then you cannot specify above two options.

Required Privilege
Level
Related
Documentation

796

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Rate Limiting of Ethernet OAM Messages

policer (CFM Session) on page 797

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

policer (CFM Session)

Syntax

Hierarchy Level

Release Information
Description
Options

policer {
all cfm-policer-name;
continuity-check cfm-policer-name;
other cfm-policer-name;
}
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain name
level number maintenance-association name]

Statement introduced in Junos OS Release 10.0.

Specify a separate policer to rate-limit packets specific to that session.

continuity-check cfm-policer-namePolice continuity check packets belonging to this

session.
other cfm-policer-namePolice all non-continuity check packets belonging to this

session.
all cfm-policer-namePolice all CFM packets belonging to this session. If the all option

is used, then you cannot specify the above two options.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Rate Limiting of Ethernet OAM Messages

policer (CFM Global) on page 796

Copyright 2014, Juniper Networks, Inc.

797

Interfaces Fundamentals for Routing Devices

policer (CoS)
Syntax

Hierarchy Level

Release Information

policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile]

Statement introduced before Junos OS Release 7.4.

Description

For Gigabit Ethernet IQ , Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), and 100-Gigabit
Ethernet Type 5 PIC with CFP, define a CoS policer template to specify the premium
bandwidth and burst-size limits, and the aggregate bandwidth and burst-size limits. The
premium policer is not supported on MX Series routers or for Gigabit Ethernet interfaces
with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port
on the M7i router).

Options

cos-policer-nameName of one policer to specify the premium bandwidth and burst-size

limits, and the aggregate bandwidth and burst-size limits.

The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

798

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Policers

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

policer (Interface)
Syntax

policer {
arp policer-template-name;
disable-arp-policer
input policer-template-name;
output policer-template-name;
}

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

Statement introduced before Junos OS Release 7.4.

disable-arp-policer option added in Junos OS Release 14.1 for MX Series routers with MPCs
(Trio-based FPCs).

Description

Apply a policer to an interface. To prevent the processing of ARP policers on the arriving
ARP packets, include the disable-arp-policer statement. You can configure this statement
only for interfaces with inet address families and on MX Series routers with MPCs. When
you disable ARP policers per interface, the packets are continued to be policed by the
distributed DoS (DDoS) ARP policer. The maximum rate of is 10000 pps per FPC.

Options

arp policer-template-nameFor inet family only, name of one policer to evaluate when

ARP packets are received on the interface.

disable-arp-policerConfigure the router to disable the processing of the specified ARP

policers on the received ARP packets. Disabling ARP policers can cause
denial-of-service (DoS) attacks on the system. Due to this possibility, we recommend
that you exercise caution while disabling ARP policers.
input policer-template-nameName of one policer to evaluate when packets are received

on the interface.
output policer-template-nameName of one policer to evaluate when packets are

transmitted on the interface.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying Policers on page 210

Configuring Firewall Filters and Policers for VPLS

Routing Policies, Firewall Filters, and Traffic Policers Feature Guide for Routing Devices

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

799

Interfaces Fundamentals for Routing Devices

policer (MAC)
Syntax

Hierarchy Level

Release Information

Description

policer {
input cos-policer-name;
output cos-policer-name;
}
[edit interfaces interface-name unit logical-unit-number accept-source-mac
mac-address mac-address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
accept-source-mac mac-address mac-address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
For Gigabit Ethernet IQ and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), and 100-Gigabit
Ethernet Type 5 PIC with CFP, configure MAC policing.

NOTE:
On MX Series routers with Gigabit Ethernet or Fast Ethernet PICs, the following
considerations apply:

Options

Interface counters do not count the 7-byte preamble and 1-byte frame
delimiter in Ethernet frames.

In MAC statistics, the frame size includes MAC header and CRC before any
VLAN rewrite/imposition rules are applied.

In traffic statistics, the frame size encompasses the L2 header without CRC
after any VLAN rewrite/imposition rule.

input cos-policer-nameName of one policer to specify the premium bandwidth and

aggregate bandwidth.
output cos-policer-nameName of one policer to specify the premium bandwidth and

aggregate bandwidth.
Required Privilege
Level
Related
Documentation

800

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring MAC Address Filtering

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

policy-statement
Syntax

Hierarchy Level

Release Information

Description

policy-statement policy-name {
term term-name {
from {
family family-name;
match-conditions;
policy subroutine-policy-name;
prefix-list prefix-list-name;
prefix-list-filter prefix-list-name match-type <actions>;
protocol protocol-name
route-filter destination-prefix match-type <actions>;
source-address-filter source-prefix match-type <actions>;
traffic-engineering;
}
to {
match-conditions;
policy subroutine-policy-name;
}
then actions;
}
}
[edit dynamic policy-options],
[edit logical-systems logical-system-name policy-options],
[edit policy-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5.
Support for configuration in the dynamic database introduced in Junos OS Release 9.5
for EX Series switches.
inet-mdt option introduced in Junos OS Release 10.0R2.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
route-target option introduced in Junos OS Release 12.2.
protocol option introduced in Junos OS Release 14.2.
traffic-engineering option introduced in Junos OS Release 14.2.
Define a routing policy, including subroutine policies.
A term is a named structure in which match conditions and actions are defined. Routing
policies are made up of one or more terms. Each routing policy term is identified by a
term name. The name can contain letters, numbers, and hyphens (-) and can be up to
255 characters long. To include spaces in the name, enclose the entire name in double
quotation marks.
Each term contains a set of match conditions and a set of actions:

Match conditions are criteria that a route must match before the actions can be applied.
If a route matches all criteria, one or more actions are applied to the route.

Actions specify whether to accept or reject the route, control how a series of policies
are evaluated, and manipulate the characteristics associated with a route.

Copyright 2014, Juniper Networks, Inc.

801

Interfaces Fundamentals for Routing Devices

Generally, a router compares a route against the match conditions of each term in a
routing policy, starting with the first and moving through the terms in the order in which
they are defined, until a match is made and an explicitly configured or default action of
accept or reject is taken. If none of the terms in the policy match the route, the router
compares the route against the next policy, and so on, until either an action is taken or
the default policy is evaluated.
If none of the match conditions of each term evaluates to true, the final action is executed.
The final action is defined in an unnamed term. Additionally, you can define a default
action (either accept or reject) that overrides any action intrinsic to the protocol.
The order of match conditions in a term is not relevant, because a route must match all
match conditions in a term for an action to be taken.
To list the routing policies under the [edit policy-options] hierarchy level by
policy-statement policy-name in alphabetical order, enter the show policy-options
configuration command.

802

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Options

actions(Optional) One or more actions to take if the conditions match. The actions are

described in Configuring Flow Control Actions.

family family-name(Optional) Specify an address family protocol. Specify inet for IPv4.

Specify inet6 for 128-bit IPv6, and to enable interpretation of IPv6 router filter
addresses. For IS-IS traffic, specify iso. For IPv4 multicast VPN traffic, specify
inet-mvpn. For IPv6 multicast VPN traffic, specify inet6-mvpn. For
multicast-distribution-tree (MDT) IPv4 traffic, specify inet-mdt. For BGP route target
VPN traffic, specifyroute-target For traffic-engineering, specify traffic-engineering.

NOTE: When family is not specified, the routing device or routing instance
uses the address family or families carried by BGP. If multiprotocol BGP
(MP-BGP) is enabled, the policy defaults to the protocol family or families
carried in the network layer reachability information (NLRI) as configured in
the family statement for BGP. If MP-BGP is not enabled, the policy uses the
default BGP address family unicast IPv4.

from(Optional) Match a route based on its source address.

match-conditions(Optional in from statement; required in to statement) One or more

conditions to use to make a match. The qualifiers are described in Routing Policy
Match Conditions.
policy subroutine-policy-nameUse another policy as a match condition within this policy.

The name identifying the subroutine policy 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 ( ). Policy names cannot take the form __.*-internal__, as this
form is reserved. For information about how to configure subroutines, see
Understanding Policy Subroutines in Routing Policy Match Conditions.
policy-nameName that identifies the policy. 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 ( ).
prefix-list prefix-list-nameName of a list of IPv4 or IPv6 prefixes.
prefix-list-filter prefix-list-nameName of a prefix list to evaluate using qualifiers;
match-type is the type of match (see Configuring Prefix List Filters), and actions is the

action to take if the prefixes match.

protocol protocol-nameName of the protocol used to control traffic engineering database

import at the originating point.

route-filter destination-prefix match-type <actions>(Optional) List of routes on which

to perform an immediate match; destination-prefix is the IPv4 or IPv6 route prefix to

match, match-type is the type of match (see Configuring Route Lists), and actions is
the action to take if the destination-prefix matches.

Copyright 2014, Juniper Networks, Inc.

803

Interfaces Fundamentals for Routing Devices

source-address-filter source-prefix match-type <actions>(Optional) Unicast source

addresses in multiprotocol BGP (MBGP) and Multicast Source Discovery Protocol

(MSDP) environments on which to perform an immediate match. source-prefix is
the IPv4 or IPv6 route prefix to match, match-type is the type of match (see
Configuring Route Lists), and actions is the action to take if the source-prefix matches.
term term-nameName that identifies the term. The term name must be unique in the

policy. It can contain letters, numbers, and hyphens (-) and can be up to 64 characters
long. To include spaces in the name, enclose the entire name in quotation marks
( ). A policy statement can include multiple terms. We recommend that you name
all terms. However, you do have the option to include an unnamed term which must
be the final term in the policy. To configure an unnamed term, omit the term
statement when defining match conditions and actions.
to(Optional) Match a route based on its destination address or the protocols into which

the route is being advertised.

then(Optional) Actions to take on matching routes. The actions are described in

Configuring Flow Control Actions and Configuring Actions That Manipulate Route
Characteristics.
Required Privilege
Level
Related
Documentation

804

routingTo view this statement in the configuration.

routing-controlTo add this statement to the configuration.

dynamic-db

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

pool
Syntax
Hierarchy Level

Release Information
Description

Options

pool pool-name <priority priority>;

[edit interfaces br-pim/0/port dialer-options],
[edit interfaces umd0 dialer-options],
[edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers, for logical and physical ISDN interfaces, specify the dial
pool. The dial pool allows logical (dialer) and physical (br-pim/0/port) interfaces to be
bound together dynamically on a per-call basis. On a dialer interface, pool directs the
dialer interface which dial pool to use. On br-pim/0/port interface, pool defines the pool
to which the interface belongs.
pool-namePool identifier.
priority priority(Physical br-pim/0/port interfaces only) Specify a priority value of 0

(lowest) to 255 (highest) for the interface within the pool.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

805

Interfaces Fundamentals for Routing Devices

pop
Syntax
Hierarchy Level

Release Information

pop;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Statement introduced in Junos OS Release 13.2X51-D20 for the QFX Series.

Description

NOTE: On EX4300 switches, pop is not supported at the [edit interfaces

interface-name unit logical-unit-number input-vlan-map] hierarchy level.

For Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ2, and IQ2-E interfaces; 10-Gigabit Ethernet
LAN/WAN PIC; aggregated Ethernet interfaces using Gigabit Ethernet IQ interfaces;
100-Gigabit Ethernet Type 5 PIC with CFP; and Gigabit Ethernet, 10-Gigabit Ethernet,
40-Gigabit Ethernet, and aggregated Ethernet interfaces, specify the VLAN rewrite
operation to remove a VLAN tag from the top of the VLAN tag stack. The outer VLAN tag
of the frame is removed.
Required Privilege
Level
Related
Documentation

806

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Removing a VLAN Tag

Configuring Q-in-Q Tunneling (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

pop-all-labels
Syntax

Hierarchy Level

pop-all-labels {
required-depth number;
}
[edit interfaces interface-name atm-options mpls],
[edit interfaces interface-name sonet-options mpls],
[edit interfaces interface-name fastether-options mpls],
[edit interfaces interface-name gigether-options mpls]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

For passive monitoring on ATM, SONET/SDH, Fast Ethernet, and Gigabit Ethernet
interfaces only, removes up to two MPLS labels from incoming IP packets. For passive
monitoring on T Series devices, removes up to five MPLS labels from incoming IP packets.
This statement has no effect on IP packets with more than two MPLS labels, or IP packets
with more than five MPLS labels on T Series devices. Packets with MPLS labels cannot
be processed by the Monitoring Services PIC; if packets with MPLS labels are forwarded
to the Monitoring Services PIC, they are discarded.
The remaining statement is explained separately.

Default

Required Privilege
Level
Related
Documentation

If you omit this statement, the MPLS labels are not removed, and the packet is not
processed by the Monitoring Services PIC.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Removing MPLS Labels from Incoming Packets

Enabling Packet Flow Monitoring on SONET/SDH Interfaces

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

807

Interfaces Fundamentals for Routing Devices

pop-pop
Syntax
Hierarchy Level

Release Information

Description

Required Privilege
Level
Related
Documentation

808

pop-pop;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
For Gigabit Ethernet IQ, IQ2 and IQ2-E interfaces, 10-Gigabit Ethernet LAN/WAN PIC, for
aggregated Ethernet interfaces using Gigabit Ethernet IQ2 and IQ2-E or 10-Gigabit Ethernet
PICs on MX Series routers, and 100-Gigabit Ethernet Type 5 PIC with CFP, and for
10-Gigabit Ethernet SFP interfaces on EX Series switches, specify the VLAN rewrite
operation to remove both the outer and inner VLAN tags of the frame.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Removing the Outer and Inner VLAN Tags

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

pop-swap
Syntax
Hierarchy Level

Release Information

Description

pop-swap;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Specify the VLAN rewrite operation to remove the outer VLAN tag of the frame, and
replace the inner VLAN tag of the frame with a user-specified VLAN tag value. The inner
tag becomes the outer tag in the final frame.
You can use this statement on Gigabit Ethernet IQ, IQ2, IQ2-E interfaces, 10-Gigabit
Ethernet LAN/WAN PIC, on aggregated Ethernet interfaces using Gigabit Ethernet IQ2
and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers, and 100-Gigabit Ethernet
Type 5 PIC with CFP.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Removing the Outer VLAN Tag and Rewriting the Inner VLAN Tag

Copyright 2014, Juniper Networks, Inc.

809

Interfaces Fundamentals for Routing Devices

port
Syntax

Hierarchy Level
Release Information
Description

Options

port {
minimum port-number;
maximum port-number;
}
[edit interfaces vsp-fpc/pic/port unit logical-unit-number compression rtp]

Statement introduced before Junos OS Release 7.4.

For voice services interfaces only, assign User Datagram Protocol (UDP) destination port
numbers reserved for Real-Time Transport Protocol (RTP) traffic.
minimum port-numberSpecify minimum port number.

Range: 0 through 65,535

maximum port-numberSpecify maximum port number.

Range: 0 through 65,535

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

port-priority
Syntax
Hierarchy Level
Release Information

Description
Options

port-priority priority;
[edit interfaces interface-name gigether-options 802.3ad lacp]

Statement introduced in Junos OS Release 9.3.

Statement introduced in Junos OS Release 11.4 for EX Series switches.
Define LACP port priority at the interface level.
priorityPriority for being elected to be the active port and both collect and distribute

traffic. A smaller value indicates a higher priority for being elected.

Range: 1 through 255
Default: 127
Required Privilege
Level
Related
Documentation

810

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure)

Configuring Aggregated Ethernet LACP

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

port-status-tlv
Syntax
Hierarchy Level
Release Information

port-status-tlv blocked;
[edit protocols oam ethernet connectivity-fault-management action-profile tlv-action event]

Statement introduced in Junos OS Release 9.6.

Description

Define an action-profile consisting of various events and the action. Based on values of
port-status-tlv in the received CCM packets, specific action such as interface-down can
be taken using action-profile options.

Options

blockedWhen the incoming CCM packet contains port status TLV with value blocked,

the action will be triggered for this action-profile.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Connectivity Fault Management Action Profile

Configuring Remote MEP Action Profile Support

post-service-filter
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

post-service-filter filter-name;
[edit interfaces interface-name unit logical-unit-number family inet service input],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service input]

Statement introduced before Junos OS Release 7.4.

Define the filter to be applied to traffic after service processing. The filter is applied only
if a service set is configured and selected.
filter-nameIdentifier for postservice filter.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

811

Interfaces Fundamentals for Routing Devices

ppp-options
Syntax

Hierarchy Level

Release Information
Description

ppp-options {
authentication [ authentication-protocols ];
chap {
access-profile name;
challenge-length minimum minimum-length maximum maximum-length;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
dynamic-profile profile-name;
initiate-ncp (ip | ipv6 | dual-stack-passive)
lcp-max-conf-req number
lcp-restart-timer milliseconds;
loopback-clear-timer seconds;
ncp-max-conf-req number
ncp-restart-timer milliseconds;
on-demand-ip-address
pap {
access-profile name;
default-pap-password password;
local-name name;
local-password password;
passive;
}
}
[edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

On interfaces with PPP encapsulation, configure PPP-specific interface properties.
For ATM2 IQ interfaces only, you can configure CHAP on the logical interface unit if the
logical interface is configured with one of the following PPP over ATM encapsulation
types:

atm-ppp-llcPPP over AAL5 LLC encapsulation.

atm-ppp-vc-muxPPP over AAL5 multiplex encapsulation.

BEST PRACTICE: On inline service (si) interfaces for L2TP, only the chap and
pap statements are typically used for subscriber management. We
recommend that you leave the other statements subordinate to

812

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

ppp-optionsincluding those subordinate to chap and papat their default

values.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPP Challenge Handshake Authentication Protocol on page 126

Applying PPP Attributes to L2TP LNS Subscribers Per Inline Service Interface

pppoe-options
Syntax

Hierarchy Level

Release Information

Description

pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
}
[edit interfaces pp0 unit logical-unit-number],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

client Statement introduced in Junos OS Release 8.5.
server Statement introduced in Junos OS Release 8.5.
For J Series Services Routers, M120 Multiservice Edge Routers, M320 Multiservice Edge
Service Routers, and MX Series Universal Edge Routers with PPP over Ethernet interfaces,
configure PPP over Ethernet-specific interface properties.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a PPPoE Interface

Copyright 2014, Juniper Networks, Inc.

813

Interfaces Fundamentals for Routing Devices

pppoe-underlying-options (Static and Dynamic Subscribers)

Syntax

Hierarchy Level

Release Information
Description

pppoe-underlying-options {
access-concentrator name;
dynamic-profile profile-name;
direct-connect
duplicate-protection;
max-sessions number;
max-sessions-vsa-ignore;
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds> <lockout-time-max
maximum-seconds> <filter [aci]>;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 10.0.

Configure PPPoE-specific interface properties for the underlying interface on which the
router creates a static or dynamic PPPoE logical interface. The underlying interface must
be configured with PPPoE (ppp-over-ether) encapsulation.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

814

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE (for static interfaces)

Configuring an Underlying Interface for Dynamic PPPoE Subscriber Interfaces

Assigning a Service Name Table to a PPPoE Underlying Interface

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

preferred
Syntax
Hierarchy Level

Release Information

Description

preferred;
[edit interfaces interface-name unit logical-unit-number family family address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Configure this address to be the preferred address on the interface. If you configure more
than one address on the same subnet, the preferred source address is chosen by default
as the source address when you initiate frame transfers to destinations on the subnet.

NOTE: The edit logical-systems hierarchy is not available on QFabric systems.

Default
Required Privilege
Level
Related
Documentation

The lowest-numbered address on the subnet is the preferred address.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the Interface Address on page 192

Copyright 2014, Juniper Networks, Inc.

815

Interfaces Fundamentals for Routing Devices

preferred-source-address
Syntax
Hierarchy Level

Release Information
Description

preferred-source-address address;
[edit interfaces interface-name unit logical-unit-number family family unnumbered-address
interface-name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family unnumbered-address interface-name]

Statement introduced in Junos OS Release 9.0.

For unnumbered Ethernet interfaces configured with a loopback interface as the donor
interface, specify one of the loopback interfaces secondary addresses as the preferred
source address for the unnumbered Ethernet 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.
Configuration of a preferred source address for unnumbered Ethernet interfaces is
supported for the IPv4 and IPv6 address families.

Options
Required Privilege
Level
Related
Documentation

816

addressSecondary IP address of the donor loopback interface.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Preferred Source Address for Unnumbered Ethernet or Demux Interfaces

on page 205

address on page 412

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

premium (Hierarchical Policer)

Syntax

Hierarchy Level

Release Information

Description

Options
Required Privilege
Level
Related
Documentation

premium {
if-exceeding {
bandwidth-limit bandwidth;
burst-size-limit burst;
}
then {
discard;
}
}
[edit dynamic-profiles profile-name firewall hierarchical-policer],
[edit firewall hierarchical-policer]

Statement introduced in Junos OS Release 9.5.

Support at the [edit dynamic-profiles ... hierarchical-policer name] hierarchy level
introduced in Junos OS Release 11.4.
On M40e, M120, and M320 edge routers with FPC input as FFPC and FPC output as SFPC,
and on MX Series, T320, T640, and T1600 edge routers with Enhanced Intelligent Queuing
(IQE) PICs, T4000 routers with Type 5 FPC and Enhanced Scaling Type 4 FPC, specify
a premium level for a hierarchical policer.
Options are described separately.
firewallTo view this statement in the configuration.
firewall-controlTo add this statement to the configuration.

Applying Policers on page 210

Guidelines for Applying Traffic Policers

Hierarchical Policer Configuration Overview

Hierarchical Policers

aggregate (Hierarchical Policer)

bandwidth-limit (Hierarchical Policer) on page 440

burst-size-limit (Hierarchical Policer) on page 453

hierarchical-policer

if-exceeding (Hierarchical Policer)

Copyright 2014, Juniper Networks, Inc.

817

Interfaces Fundamentals for Routing Devices

premium (Output Priority Map)

Syntax

Hierarchy Level

Release Information
Description

premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map classifier]

Statement introduced before Junos OS Release 7.4.

For Gigabit Ethernet IQ interfaces only, define the classifier for egress premium traffic.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Specifying an Output Priority Map

input-priority-map on page 624

premium (Policer)
Syntax

Hierarchy Level

Release Information
Description

premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name]

Statement introduced before Junos OS Release 7.4.

Define a policer to apply to nonpremium traffic.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

818

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Policers

aggregate (Gigabit Ethernet CoS Policer) on page 416

ieee802.1p on page 605

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

preserve-interface
Syntax
Hierarchy Level
Release Information
Description

preserve-interface;
[edit interfaces interface-name sonet-options aps]

Statement introduced in Junos OS Release 7.6.

Provide link PIC replication, providing MLPPP link redundancy at the port level. This feature
is supported with SONET APS and the following link PICs:

Channelized OC3 IQ PIC

Channelized OC12 IQ PIC

Channelized STM1 IQ PIC

Link PIC replication provides the ability to add two sets of links, one from the active
SONET PIC and the other from the standby SONET PIC, to the same bundle. If the active
SONET PIC fails, links from the standby PIC are used without triggering link renegotiation.
All the negotiated state is replicated from the active links to the standby links to prevent
link renegotiation.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Link PIC Redundancy

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

819

Interfaces Fundamentals for Routing Devices

primary (Address on Interface)

Syntax
Hierarchy Level

Release Information

Description

primary;
[edit interfaces interface-name unit logical-unit-number family family address address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
Configure this address to be the primary address of the protocol on the interface. If the
logical unit has more than one address, the primary address is used by default as the
source address when packet transfer originates from the interface and the destination
address does not indicate the subnet.

NOTE: The edit logical-systems hierarchy is not available on QFabric systems.

Default

Required Privilege
Level
Related
Documentation

For unicast traffic, the primary address is the lowest non-127 (in other words,
non-loopback) preferred address on the unit.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the Interface Address on page 192

primary (AS PIC or Multiservices PIC Interfaces)

Syntax
Hierarchy Level
Release Information
Description
Options

primary interface-name;
[edit interfaces (rsp0 | rsp1) redundancy-options]

Statement introduced before Junos OS Release 7.4.

Specify the primary AS PIC or MultiServices PIC interface.
interface-nameThe identifier for the AS PIC interface or MultiServices PIC interface,

which must be of the form sp-fpc/pic/port.

Required Privilege
Level
Related
Documentation

820

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

priority (OAM Connectivity-Fault Management)

Syntax
Hierarchy Level

priority number;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id]

For EX Series Switches:

[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id]

Release Information
Description
Options

Statement introduced in Junos OS Release 8.4.

IEEE 802.1p priority bits used by the continuity check messages.
numberConfigure the IEEE 802.1p priority bits to be used in the VLAN header of the CFM

packets.
Range: 0 through 7
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Maintenance Endpoint

priority (Schedulers)
Syntax
Hierarchy Level

Release Information
Description
Options

priority (high | low);

[edit interfaces at-fpc/pic/port atm-options scheduler-maps map-name forwarding-class
class-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, assign queuing priority to a forwarding class.
lowForwarding class has low priority.
highForwarding class has high priority.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

Copyright 2014, Juniper Networks, Inc.

821

Interfaces Fundamentals for Routing Devices

promiscuous-mode
Syntax

Hierarchy Level
Release Information

Description

promiscuous-mode {
vpi vpi-identifier;
}
[edit interfaces interface-name atm-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
For ATM interfaces with atm-ccc-cell-relay encapsulation, map all incoming cells from
either an interface port or a VP to a single label-switched path (LSP) without restricting
the VCI number. Promiscuous mode allows you to map traffic from all 65,535 VCIs to a
single LSP, or from all 256 VPIs to a single LSP.

NOTE: In ACX Series routers, the statement supports only Inverse Multiplexing
for ATM (IMA).

Options

vpi-identifierOpen this VPI in promiscuous mode.

Range: 0 through 255

Required Privilege
Level
Related
Documentation

822

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM Cell-Relay Promiscuous Mode

vpi (ATM CCC Cell-Relay Promiscuous Mode) on page 981

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

protect-circuit
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

protect-circuit group-name;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Configure the protect router in an APS circuit pair. When the working interface fails, APS
brings up the protection circuit and the traffic is moved to the protection circuit.
group-nameCircuits group name.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Basic Automatic Protect Switching

working-circuit on page 991

Copyright 2014, Juniper Networks, Inc.

823

Interfaces Fundamentals for Routing Devices

protection-group
Syntax

824

protection-group {
ethernet-ring ring-name {
data-channel {
vlan number
}
east-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
}
guard-interval number;
node-id mac-address;
restore-interval number;
ring-protection-link-owner;
non-revertive;
wait-to-block-interval number;
major-ring-name name;
propagate-tc;
compatibility-version (1|2);
ring-id number;
non-vc-mode;
dot1p-priority number;
west-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
virtual-control-channel {
west-interface name;
east-interface name;
}
}
}
control-vlan (vlan-id | vlan-name);
east-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
}
}
control-channel channel-name {
vlan number;
interface name interface-name
}
}
data-channel {
vlan number

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

}
guard-interval number;
node-id mac-address;
restore-interval number;
ring-protection-link-owner;
west-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
}
control-channel channel-name {
vlan number;
interface name interface-name
}
}
}
guard-interval number;
restore-interval number;
traceoptions {
file filename <no-stamp> <world-readable | no-world-readable> <replace> <size size>;
flag flag;
}
}

Hierarchy Level
Release Information

Description

[edit protocols]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Configure Ethernet ring protection switching.
The statements are explained separately. All statements apply to MX Series routers. EX
Series switches do not assign node-id and use control-vlan instead of control-channel.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Ethernet Ring Protection Using Ring Instances for Load Balancing

Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series
Routers

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

825

Interfaces Fundamentals for Routing Devices

protocol-down
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

protocol-down;
[edit protocols oam ethernet link-fault-management action-profile event]

Statement introduced in Junos OS Release 8.5.

Upper layer indication of protocol down event. When the protocol-down statement is
included, the protocol down event triggers the action specified under the action statement.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring an OAM Action Profile

protocols
Syntax
Hierarchy Level
Release Information
Description

protocols [inet iso mpls];

[edit interfaces interface-name unit logical-unit-number family tcc]

Statement introduced in Junos OS Release 8.3.

For Layer 2.5 VPNs on T Series, MX Series, M120, and M320 routers support, configure
IS-IS (ISO traffic) or MPLS traffic to traverse a TCC interface. By default, IPv4 (inet)
traffic runs on T Series, MX, Series, M120, and M320 routers and over TCC interfaces. You
must configure the same traffic type on both ends of the Layer 2.5 VPN.

NOTE: Some platform and FPC combinations can not pass TCC encapsulated
ISO traffic. See Platforms/FPCs That Cannot Forward TCC Encapsulated ISO
Traffic for details.

Required Privilege
Level
Related
Documentation

826

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring IS-IS or MPLS Traffic for TCC Interfaces on page 261

Platforms/FPCs That Cannot Forward TCC Encapsulated ISO Traffic

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

proxy
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

proxy inet-address address;

[edit interfaces interface-name unit logical-unit-number family tcc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family tcc]

Statement introduced before Junos OS Release 7.4.

For Layer 2.5 VPNs using an Ethernet interface as the TCC router, configure the IP address
for which the TCC router is proxying. Ethernet TCC is supported on interfaces that carry
IPv4 traffic only. Ethernet TCC encapsulation is supported on 1-port Gigabit Ethernet,
2-port Gigabit Ethernet, 4-port Gigabit Ethernet, and 4-port Fast Ethernet PICs only.
Ethernet TCC is not supported on the T640 router.
inet-addressConfigure the IP address of the neighbor to the TCC router.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Ethernet TCC

Example: Configuring an Ethernet TCC or Extended VLAN TCC

remote on page 842

Junos OS VPNs Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

827

Interfaces Fundamentals for Routing Devices

proxy-arp
Syntax
Hierarchy Level

Release Information

Description

proxy-arp (restricted | unrestricted);

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.6 for EX Series switches.
restricted added in Junos OS Release 10.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for the QFX Series.
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 requests target address.

NOTE: You must configure the IP address and the inet family for the interface
when you enable proxy ARP.

Default

Options

Proxy ARP is not enabled. The router or switch responds to an ARP request only if the
destination IP address is its own.

noneThe 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
Required Privilege
Level
Related
Documentation

828

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Restricted and Unrestricted Proxy ARP

Configuring Proxy ARP (CLI Procedure)

Configuring Gratuitous ARP

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

push
Syntax
Hierarchy Level

Release Information

push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Statement introduced in Junos OS Release 13.2X51-D20 for the QFX Series.

Description

NOTE: On EX4300 switches, push is not supported at the [edit interfaces

interface-name unit logical-unit-number output-vlan-map] hierarchy level.

Specify the VLAN rewrite operation to add a new VLAN tag to the top of the VLAN stack.
An outer VLAN tag is pushed in front of the existing VLAN tag.
You can use this statement on Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E
interfaces; 10-Gigabit Ethernet LAN/WAN PIC; aggregated Ethernet interfaces using
Gigabit Ethernet IQ interfaces; 100-Gigabit Ethernet Type 5 PIC with CFP; and Gigabit
Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet, and aggregated Ethernet interfaces.
If you include the push statement in the configuration, you must also include the pop
statement at the [edit interfaces interface-name unit logical-unit-number output-vlan-map]
hierarchy level.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Stacking a VLAN Tag

Configuring Q-in-Q Tunneling (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

829

Interfaces Fundamentals for Routing Devices

push-push
Syntax
Hierarchy Level

Release Information

Description

push-push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Specify the VLAN rewrite operation to push two VLAN tags in front of the frame.
You can use this statement on Gigabit Ethernet IQ, IQ2 and IQ2-E interfaces, 10-Gigabit
Ethernet LAN/WAN PIC, on aggregated Ethernet interfaces using Gigabit Ethernet IQ2
and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers, and 100-Gigabit Ethernet
Type 5 PIC with CFP.

Required Privilege
Level
Related
Documentation

830

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Stacking Two VLAN Tags

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

queue-depth
Syntax
Hierarchy Level
Release Information
Description

Default
Options

queue-depth cells;
[edit interfaces interface-name atm-options linear-red-profiles profile-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define maximum queue depth in the CoS VC drop profile.
Packets are always dropped beyond the defined maximum. This statement is mandatory;
there is no default configuration.
Buffer usage is unregulated.
cellsMaximum number of cells the queue can contain.

Range: 1 through 64,000 cells

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

Configuring Linear RED Profiles on ATM Interfaces

high-plp-threshold on page 593

low-plp-threshold on page 692

Copyright 2014, Juniper Networks, Inc.

831

Interfaces Fundamentals for Routing Devices

queue-length
Syntax
Hierarchy Level

Release Information

Description

Default
Options

queue-length number;
[edit interfaces interface-name unit logical-unit-number address address family family
multipoint-destination address shaping ],
[edit interfaces interface-name unit logical-unit-number shaping ],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
address address family family multipoint-destination address shaping ],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
shaping ]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
For ATM1 interfaces only, define the maximum queue length in the traffic-shaping profile.
For ATM1 PICs, each VC has its own independent shaping parameters.
Buffer usage is unregulated.
numberMaximum number of packets the queue can contain.

Range: 1 through 16,383 packets

Default: 16,383 packets
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the ATM1 Queue Length

queues
Syntax
Hierarchy Level
Release Information
Description
Options

queues [ queue-numbers ];
[edit interfaces vsp-fpc/pic/port unit logical-unit-number compression rtp]

Statement introduced before Junos OS Release 7.4.

For voice services interfaces only, assign queue numbers for RTP traffic.
queues queue-numbersAssign one or more of the following queues: q0, q1, q2, q3. For

VRRP services, specify the q3 option instead of q0.

Required Privilege
Level
Related
Documentation

832

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

quiet-period
Syntax
Hierarchy Level
Release Information
Description

Options

quiet-period seconds;
[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Specify the number of seconds the port remains in the wait state following a failed
authentication exchange with the client, before reattempting authentication.
secondsSpecify the number of seconds the port remains in the wait state following a

failed authentication exchange with the client, before reattempting authentication.

Range: 0 through 65,535 seconds
Default: 60 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

interface (IEEE 802.1x) on page 629

radius-realm
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

radius-realm radius-realm-string;
[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include]

Statement introduced in Junos OS Release 10.0.

Specify that the user-defined RADIUS realm string is appended as a last piece to the
username and used by RADIUS to direct the authentication request to a profile that does
not allocates addresses.
radius-realm-stringA string to describe the RADIUS realm.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

Copyright 2014, Juniper Networks, Inc.

833

Interfaces Fundamentals for Routing Devices

ranges (Dynamic Stacked VLAN)

Syntax
Hierarchy Level

Release Information
Description
Options

ranges (any | low-taghigh-tag),(any | low-taghigh-tag);

[edit interfaces interface-name auto-configure stacked-vlan-ranges dynamic-profile
profile-name]

Statement introduced in Junos OS Release 9.5.

Configure VLAN ranges for dynamic, auto-sensed stacked VLANs.
anyThe entire VLAN range.
low-tagThe lower limit of the VLAN range.
high-tagThe upper limit of the VLAN range.

Range: 1 through 4094

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs

ranges (Dynamic VLAN)

Syntax
Hierarchy Level
Release Information
Description
Options

ranges (any | low-tag)-(any | high-tag);

[edit interfaces interface-name auto-configure vlan-ranges dynamic-profile profile-name]

Statement introduced in Junos OS Release 9.5.

Configure VLAN ranges for dynamic, auto-sensed VLANs.
anyThe entire VLAN range.
low-tagThe lower limit of the VLAN range.
high-tagThe upper limit of the VLAN range.

Range: 1 through 4094

Required Privilege
Level
Related
Documentation

834

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag

VLANs

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

rate
Syntax
Hierarchy Level

Release Information
Description
Options

rate percentage;
[edit interfaces interface-name receive-bucket],
[edit interfaces interface-name transmit-bucket]

Statement introduced before Junos OS Release 7.4.

Specify percentage of the interface line rate that is available to receive or transmit packets.
percentagePercentage of the interface line rate that is available to receive or transmit

packets.
Range: 0 through 100
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

rate
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level

rate new-sessions-per-second;
[edit interfaces interface-name services-options session-limit]

Statement introduced in Junos OS Release 9.6.

Specify the maximum number of new sessions allowed per second.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

835

Interfaces Fundamentals for Routing Devices

rdi
Syntax
Hierarchy Level
Release Information
Description

rdi;
[edit protocols oam ethernet connectivity-fault-management action-profile tlv-action event]

Statement introduced in Junos OS Release 10.1.

Define a new event rdi. The remote defect indication (rdi) event is triggered whenever
CCM packets are received from a remote location with the rdi bit set.
This event is cleared and action is reverted when none of the remote MEPs send the CCM
packets with the RDI bit.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Connectivity Fault Management Action Profile

reassemble-packets
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

836

reassemble-packets;
[edit interfaces gr-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces gr-fpc/pic/port unit logical-unit-number]

Statement introduced in Junos OS Release 9.2.

Enable reassembly of fragmented tunnel packets on generic routing encapsulation (GRE)
tunnel interfaces.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Configuring Packet Reassembly

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

reauthentication
Syntax
Hierarchy Level
Release Information
Description
Options

reauthentication (disable | interval seconds);

[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Set or disable the periodic reauthentication of the client.

disableDisable the periodic reauthentication of the client.

interval secondsSpecify the periodic reauthentication time interval.

Range: 1 through 65,535 seconds

Default: 3600 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

dot1x on page 517

interface (IEEE 802.1x) on page 629

quiet-period on page 833

Copyright 2014, Juniper Networks, Inc.

837

Interfaces Fundamentals for Routing Devices

receive-bucket
Syntax

Hierarchy Level
Release Information
Description

receive-bucket {
overflow (discard | tag);
rate percentage;
threshold bytes;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Set parameters for the receive leaky bucket, which specifies what percentage of the
interfaces total capacity can be used to receive packets.
For each DS3 channel on a channelized OC12 interface, you can configure a unique receive
bucket.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

transmit-bucket on page 935

receive-options-packets
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

838

receive-options-packets;
[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]

Statement introduced before Junos OS Release 7.4.

For a Monitoring Services PIC and an ATM or SONET/SDH PIC installed in an M160, M40e,
or T Series router, guarantee conformity with cflowd records structure. This statement
is required when you enable passive monitoring.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling Passive Monitoring on ATM Interfaces

Enabling Packet Flow Monitoring on SONET/SDH Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

receive-ttl-exceeded
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

receive-ttl-exceeded;
[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]

Statement introduced before Junos OS Release 7.4.

For Monitoring Services PIC and an ATM or SONET/SDH PIC installed in an M160, M40e,
or T Series router, guarantee conformity with cflowd records structure. This statement
is required when you enable passive monitoring.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling Passive Monitoring on ATM Interfaces

Enabling Packet Flow Monitoring on SONET/SDH Interfaces

red-differential-delay
Syntax
Hierarchy Level
Release Information
Description

Options

red-differential-delay milliseconds;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voice services interfaces only, configure the red differential delay
among bundle links to give warning when a link has a differential delay that exceeds the
configured threshold.
millisecondsRed differential delay threshold.

Range: 1 through 2000 milliseconds

Default: 10 milliseconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

action-red-differential-delay on page 410

yellow-differential-delay on page 991

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

839

Interfaces Fundamentals for Routing Devices

redial-delay
Syntax
Hierarchy Level

Release Information
Description

redial-delay time;
[edit interfaces dln unit logical-unit-number dialer-options],
[edit logical-systems logical-system-name interfaces dln unit logical-unit-number
dialer-options]

Statement introduced in Junos OS Release 7.5.

On J Series Services Routers with interfaces configured for ISDN with dialout, specify the
delay (in seconds) between two successive calls made by the dialer. To configure callback
mode, include the callback statement at the [edit interfaces dln unit logical-unit-number
dialer-options] hierarchy level.
If the callback statement is configured, you cannot use the caller caller-id statement at
the [edit interfaces dln unit logical-unit-number dialer-options] hierarchy level.

Options

timeDelay (in seconds) between two successive calls.

Range: 2 through 255 seconds

Default: 3 seconds
Required Privilege
Level
Related
Documentation

840

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ISDN Interfaces Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

redundancy-options
Syntax

Hierarchy Level

Release Information

redundancy-options {
primary interface-name;
secondary interface-name;
hot-standby;
}
[edit interfaces (rsp0 | rsp1)],
[edit interfaces rlsqnumber]
[edit interfaces rspnumber]
[edit interfaces rmsnumber]

Statement introduced before Junos OS Release 7.4.

Description

Specify the primary and secondary (backup) AS PIC interfaces or MultiServices PIC
interfaces.

Options

primary interface-nameThe identifier for the primary LSQ AS, rsp, or rms interface.
secondary interface-nameThe identifier for the secondary (backup) LSQ AS, rsp, or

rmsinterface.
hot-standbyFor one-to-one AS, rsp, or rms redundancy configurations, specify that the

failure detection and recovery must take place in less than 5 seconds.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

841

Interfaces Fundamentals for Routing Devices

remote
Syntax

Hierarchy Level

Release Information
Description

Options

remote {
(inet-address address | mac-address address);
}
[edit interfaces interface-name unit logical-unit-number family tcc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family tcc]

Statement introduced before Junos OS Release 7.4.

For Layer 2.5 VPNs using an Ethernet interface as the TCC router, configure the location
of the remote router. Ethernet TCC is supported on interfaces that carry IPv4 traffic only.
Ethernet TCC encapsulation is supported on 1-port Gigabit Ethernet, 2-port Gigabit
Ethernet, 4-port Gigabit Ethernet, and 4-port Fast Ethernet PICs only.
mac-addressConfigure the MAC address of the remote site.
inet-addressConfigure the IP address of the remote site.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Ethernet TCC

Example: Configuring an Ethernet TCC or Extended VLAN TCC

proxy on page 827

Junos OS VPNs Library for Routing Devices

remote-loopback
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

842

remote-loopback;
[edit protocols oam link-fault-management interface interface-name]

Statement introduced in Junos OS Release 8.2.

For Ethernet interfaces on EX Series switches and M320, M120, MX Series, and T Series
routers, set the remote DTE into loopback mode. Remove the statement from the
configuration to take the remote DTE out of loopback mode. Used for IEEE 802.3ah
Operation, Administration, and Management (OAM) support.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Setting a Remote Interface into Loopback Mode

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

remote-loopback-respond
Syntax
Hierarchy Level

remote-loopback-respond;
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name t1-options]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.

Description

For T1 interfaces only, configure the router to respond to remote loopback requests.
Remote loopback requests can be from the facilities data link or inband.

NOTE: When configuring CT1 interfaces on the 10-port Channelized E1/T1

IQE PIC, the remote-loopback-respond statement must be included at the
[edit interfaces ct1-fpc/pic/port] hierarchy level.

Default
Required Privilege
Level
Related
Documentation

The router does not respond to remote loop requests.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the T1 Remote Loopback Response

feac-loop-respond on page 574

loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3) on page 686

Copyright 2014, Juniper Networks, Inc.

843

Interfaces Fundamentals for Routing Devices

remote-mep
Syntax

Hierarchy Level

Release Information
Description

Options

remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
detect-loc;
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id]

Statement introduced in Junos OS Release 8.4.

Configure the numeric identifier of the remote maintenance association end point (MEP)
within the maintenance association.
mep-idNumeric identifier of the MEP.

Range: 1 through 8191

The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

Configuring a Maintenance Endpoint

detect-loc

remove-when-no-subscribers
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

844

remove-when-no-subscribers;
[edit interfaces interface-name auto-configure]

Statement introduced in Junos OS Release 11.4.

Remove subscriber VLANs automatically when no client sessions (for example, DHCP
or PPPoE) exist on the VLAN.
routingTo view this statement in the configuration.
routingcontrolTo add this statement to the configuration.

Automatically Removing VLANs with No Subscribers

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

request
Syntax
Hierarchy Level
Release Information
Description

Options

request (protect | working);

[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Perform a manual switch between the protect and working circuits. This statement is
honored only if there are no higher-priority reasons to switch.
protectRequest that the circuit become the protect circuit.
workingRequest that the circuit become the working circuit.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Switching Between the Working and Protect Circuits

force on page 579

Copyright 2014, Juniper Networks, Inc.

845

Interfaces Fundamentals for Routing Devices

required-depth
Syntax
Hierarchy Level

Release Information

Description

required-depth number;
[edit interfaces interface-name atm-options mpls pop-all-labels],
[edit interfaces interface-name sonet-options mpls pop-all-labels],
[edit interfaces interface-name fastether-options mpls pop-all-labels],
[edit interfaces interface-name gigether-options mpls pop-all-labels]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
For passive monitoring on ATM and SONET/SDH interfaces only, specify the number of
MPLS labels an incoming packet must have for the pop-all-labels statement to take
effect.
If you include the required-depth 1 statement, the pop-all-labels statement takes effect
for incoming packets with one label only. If you include the required-depth 2 statement,
the pop-all-labels statement takes effect for incoming packets with two labels only.

Options

numberNumber of MPLS labels on incoming IP packets.

Range: 1 or 2 labels
Default: If you omit this statement, the pop-all-labels statement takes effect for incoming
packets with one or two labels. The default is equivalent to including the
required-depth [ 1 2 ] statement.
Required Privilege
Level
Related
Documentation

846

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Removing MPLS Labels from Incoming Packets

Enabling Packet Flow Monitoring on SONET/SDH Interfaces

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

restore-interval
Syntax
Hierarchy Level
Release Information

Description

Options

restore-interval number;
[edit protocols protection-group ethernet-ring ring-name]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.
Configures the number of minutes that the node does not process any Ethernet ring
protection (ERP) protocol data units (PDUs).. This configuration is a global configuration
and applies to all Ethernet rings if the Ethernet ring does not have a more specific
configuration for this value. If no parameter is configured at the protection group level,
the global configuration of this parameter uses the default value.
numberSpecify the restore interval.
Range: 5 through 12 minutes

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

847

Interfaces Fundamentals for Routing Devices

retries
Syntax
Hierarchy Level
Release Information
Description

Options

retries integer;
[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Set a limit on the number of failed authentication attempts between a port and a client.
When the limit is exceeded, the port waits to reattempt authentication for the number
of seconds set by the quiet-period statement configured at the same hierarchy level.
integerSpecify the number of retries.

Range: 1 through 10
Default: 3 retries
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

dot1x on page 517

interface (IEEE 802.1x) on page 629

quiet-period on page 833

revert-time (Interfaces)
Syntax
Hierarchy Level
Release Information
Description
Default
Options

revert-time seconds;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Configure APS revertive mode.
APS operates in nonrevertive mode.
secondsAmount of time to wait after the working circuit has again become functional

before making the working circuit active again.

Range: 1 through 65,535 seconds
Default: None (APS operates in nonrevertive mode)
Required Privilege
Level
Related
Documentation

848

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Revertive Mode

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

revertive
Syntax
Hierarchy Level

revertive;
[edit interfaces aeX aggregated-ether-options lacp link-protection]

Release Information

Statement introduced in Junos OS Release 9.3.

Statement introduced in Junos OS Release 12.3 for EX Series switches.

Description

Enable the ability to switch to a better priority link (if one is available).

NOTE: By default, LACP link protection is revertive. However, you can use
this statement to define a specific aggregated Ethernet interface as revertive
to override a global non-revertive statement specified at the [edit chassis]
hierarchy level.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

non-revertive (Chassis)

Configuring LACP Link Protection of Aggregated Ethernet Interfaces (CLI Procedure)

rfc-2615
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation

rfc-2615;
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

Include this statement to enable features described in RFC 2615, PPP over SONET/SDH.
Settings required by RFC 1619, PPP over SONET/SDH.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring PPP Support on SONET/SDH Interfaces

Copyright 2014, Juniper Networks, Inc.

849

Interfaces Fundamentals for Routing Devices

ring-protection-link-end
Syntax
Hierarchy Level
Release Information

Description

Required Privilege
Level
Related
Documentation

ring-protection-link-end;
[edit protocols protection-group ethernet-ring ring-name (east-interface | west-interface)]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Specify that the port is one side of a ring protection link (RPL) by setting the RPL end
flag.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

ring-protection-link-owner
Syntax
Hierarchy Level
Release Information

Description

Required Privilege
Level
Related
Documentation

850

ring-protection-link-owner;
[edit protocols protection-group ethernet-ring ring-name]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.
Specify the ring protection link (RPL) owner flag in the Ethernet protection ring. Include
this statement only once for each ring (only one node can function as the RPL owner).
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

routing-instance
Syntax

Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

routing-instance {
destination routing-instance-name;
}
[edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel]

Statement introduced before Junos OS Release 7.4.

To configure interfaces and logical-systems, specify the destination routing instance that
points to the routing table containing the tunnel destination address.
The default Internet routing table is inet.0.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

851

Interfaces Fundamentals for Routing Devices

routing-instance (PPPoE Service Name Tables)

Syntax
Hierarchy Level

Release Information
Description

routing-instance routing-instance-name;
[edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]

Statement introduced in Junos OS Release 10.2.

Use in conjunction with the dynamic-profile statement at the same hierarchy levels to
specify the routing instance in which to instantiate a dynamic PPPoE interface. You can
associate a routing instance with a named service entry, empty service entry, or any service
entry configured in a PPPoE service name table, or with an agent circuit identifier/agent
remote identifier (ACI/ARI) pair defined for these services.
The routing instance associated with a service entry in a PPPoE service name table
overrides the routing instance associated with the PPPoE underlying interface on which
the dynamic PPPoE interface is created.
If you include the routing-instance statement at the [edit protocols pppoe
service-name-tables table-name service service-name agent-specifier aci circuit-id-string
ari remote-id-string] hierarchy level, you cannot also include the static-interface statement

at this level. The routing-instance and static-interface statements are mutually exclusive
for ACI/ARI pair configurations.
Options

routing-instance-nameName of the routing instance in which the router instantiates the

dynamic PPPoE interface.

Required Privilege
Level
Related
Documentation

852

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for
Dynamic PPPoE Interface Creation

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

rpf-check (Dynamic Profiles)

Syntax

Hierarchy Level

Release Information
Description

rpf-check {
fail-filter filter-name;
mode loose;
}
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
family]

Statement introduced in Junos OS Release 9.6.

Check whether traffic is arriving on an expected path. You can include this statement
with the inet protocol family only.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Unicast RPF Strict Mode on page 227

Configuring Unicast RPF and Fail Filters in Dynamic Profiles for Subscriber Interfaces

Copyright 2014, Juniper Networks, Inc.

853

Interfaces Fundamentals for Routing Devices

rpf-check (interfaces)
Syntax

Hierarchy Level

Release Information
Description

rpf-check {
fail-filter filter-name;
mode loose;
}
[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]

Statement introduced before Junos OS Release 7.4.

Check whether traffic is arriving on an expected path. You can include this statement
with the inet or inet6 protocol family only.
The mode statement is explained separately.

Options

fail-filterA filter to evaluate when packets are received on the interface. If the RPF check

fails, this optional filter is evaluated. If the fail filter is not configured, the default
action is to silently discard the packet.
Required Privilege
Level
Related
Documentation

854

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Unicast RPF Strict Mode on page 227

Configuring Unicast RPF Loose Mode on page 229

Example: Configuring Unicast Reverse-Path-Forwarding Check on page 234

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

rpf-loose-mode-discard
Syntax

rpf-loose-mode-discard {
family {
inet;
inet6;
}
}

Hierarchy Level

[edit forwarding-options]

Release Information

Description

Options

Statement introduced in Junos OS Release 12.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Configure unicast reverse path forwarding (unicast RPF) loose mode with the ability to
discard packets with the source address pointing to the discard next hop.
inetIPv4 address family.
inet6IPv6 address family.

Required Privilege
Level
Related
Documentation

interface-controlTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Unicast RPF on page 224

rtp
Syntax

Hierarchy Level
Release Information
Description

rtp {
f-max-period number;
queues [ queue-numbers ];
port {
minimum port-number;
maximum port-number;
}
}
[edit interfaces interface-name unit logical-unit-number compression]

Statement introduced before Junos OS Release 7.4.

Configure the real-time transport protocol (RTP) properties for voice services traffic.
The remaining statements are described separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

855

Interfaces Fundamentals for Routing Devices

rts
Syntax
Hierarchy Level

Release Information
Description
Options

rts (assert | de-assert | normal);

[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 and V.35 interfaces only, configure the to-DCE signal, request to send (RTS).
assertThe to-DCE signal must be asserted.
de-assertThe to-DCE signal must be deasserted.
normalNormal RTS signal handling, as defined by the TIA/EIA Standard 530.

Default: normal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

rts-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

rts-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure RTS signal polarity.
negativeNegative signal polarity.
positivePositive signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

856

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

rtvbr
Syntax
Hierarchy Level

Release Information
Description

rtvbr peak rate sustained rate burst length;

[edit interfaces interface-name atm-options vpi vpi-identifier shaping ],
[edit interfaces interface-name unit logical-unit-number address address family family
multipoint-destination address shaping ],
[edit interfaces interface-name unit logical-unit-number shaping ],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
shaping ],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
address address family family multipoint-destination address shaping ]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ PICs only, define the real-time variable bandwidth utilization in the
traffic-shaping profile.
When you configure the real-time bandwidth utilization, you must specify all three options
(burst, peak, and sustained). You can specify the rate 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 the rate 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 using the formula 1 cps = 384 bps.

Default
Options

If the rtvbr statement is not included, bandwidth utilization is unlimited.

burst lengthBurst length, in cells. If you set the length to 1, the peak traffic rate is used.

Range: 1 through 4000 cells

peak ratePeak rate, in bits per second or cells per second.

Range: For ATM2 IQ OC3 and OC12 interfaces, 33 Kbps through 542,526,792 bps. For
ATM2 IQ OC48 interfaces, 33 Kbps through 2,170,107,168 bps. For ATM2 IQ DS3 and
E3 interfaces, 33 Kbps through the maximum rate, which depends on the ATM
encapsulation and framing you configure..
sustained rateSustained rate, in bps or cps.

Range: For ATM2 IQ OC3 and OC12 interfaces, 33 Kbps through 542,526,792 bps. For
ATM2 IQ OC48 interfaces, 33 Kbps through 2,170,107,168 bps. For ATM2 IQ DS3 and
E3 interfaces, from 33 Kbps through the maximum rate, which depends on the ATM
encapsulation and framing you configure.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM CBR

Configuring ATM2 IQ Real-Time VBR

Applying Scheduler Maps to Logical ATM Interfaces

Copyright 2014, Juniper Networks, Inc.

857

Interfaces Fundamentals for Routing Devices

858

cbr on page 462

vbr on page 962

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

sa-multicast (100-Gigabit Ethernet)

Syntax
Hierarchy Level
Release Information
Description

sa-multicast;
[edit chassis fpc slot pic slot forwarding-mode]

Statement introduced in Junos OS Release 10.4.

Configure the 100-Gigabit Ethernet PIC or MIC to interoperate with other Juniper Networks
100-Gigabit Ethernet PICs.

NOTE: The default packet steering mode for PD-1CE-CFP-FPC4 is SA

multicast bit mode. No SA multicast configuration is required to enable this
mode.

sa-multicast supports interoperability between the following PICs and MICs:

Required Privilege
Level
Related
Documentation

100-Gigabit Ethernet Type 5 PIC with CFP (PF-1CGE-CFP) and the 100-Gigabit Ethernet
Type 4 PIC with CFP (PD-1CE-CFP-FPC4) .

100-Gigabit Ethernet MICs and the 100-Gigabit Ethernet Type 4 PIC with CFP
(PD-1CE-CFP-FPC4).

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Interoperability Between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4 and

PF-1CGE-CFP

Configuring the Interoperability Between the 100-Gigabit Ethernet PICs PF-1CGE-CFP

and PD-1CE-CFP-FPC4

Configuring 100-Gigabit Ethernet MICs to Interoperate with Type 4 100-Gigabit Ethernet

PICs (PD-1CE-CFP-FPC4)Using SA Multicast Mode

Interoperability Between MPC4E (MPC4E-3D-2CGE-8XGE) and 100-Gigabit Ethernet

PICs on Type 4 FPC

Configuring MPC4E (MPC4E-3D-2CGE-8XGE) to Interoperate with 100-Gigabit Ethernet

PICs on Type 4 FPC Using SA Multicast Mode

Interoperability Between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4 and

P1-PTX-2-100GE-CFP

Configuring the Interoperability Between the 100-Gigabit Ethernet PICs

P1-PTX-2-100GE-CFP and PD-1CE-CFP-FPC4

forwarding-mode (100-Gigabit Ethernet)

sa-multicast (PTX Series Packet Transport Routers)

vlan-steering (100-Gigabit Ethernet Type 4 PIC with CFP) on page 975

Copyright 2014, Juniper Networks, Inc.

859

Interfaces Fundamentals for Routing Devices

Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP

sampling (Interfaces)
Syntax
Hierarchy Level

Release Information
Description
Options

sampling direction;
[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]

Statement introduced before Junos OS Release 7.4.

Configure the direction of traffic to be sampled.
direction can be one of the following:
inputConfigure at least one expected ingress point.
outputConfigure at least one expected egress point.
input outputOn a single interface, configure at least one expected ingress point and

one expect egress point.

Required Privilege
Level
Related
Documentation

860

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Configuring Flow Monitoring

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

satop-options
Syntax

Hierarchy Level
Release Information

Description

satop-options {
excessive-packet-loss-rate {
apply-groups group-name
apply-groups-except group-name
groups group-name
sample-period milliseconds
threshold percentile
)
idle-pattern pattern
jitter-buffer-auto-adjust
jitter-buffer-latency milliseconds
jitter-buffer-packets packets
payload-size bytes;
}
[edit interfaces interface-name]

Statement introduced in Junos OS Release 9.3.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Set Structure-Agnostic TDM over Packet (SAToP) protocol options.
On ACX Series routers, the following statements are not supported:
apply-groups group-name
apply-groups-except group-name
groups group-name
jitter-buffer-auto-adjust

Options

excessive-packet-loss-rate optionsSet packet loss options.

apply-groups group-nameGroups from which to inherit configuration data.

apply-groups-except group-nameDon't inherit configuration data from these groups.

groups group-nameSpecify groups.

sample-period millisecondsNumber of milliseconds over which excessive packet loss

rate is calculated.

threshold percentilePercentile designating the threshold of excessive packet loss rate

(from 1 to 100).
idle-pattern patternAn 8bit hexadecimal pattern to replace TDM data in a lost packet

(from 0 to 255).
jitter-buffer-auto-adjustAutomatically adjust the jitter buffer.

NOTE: This option is not applicable on MX Series routers.

Copyright 2014, Juniper Networks, Inc.

861

Interfaces Fundamentals for Routing Devices

jitter-buffer-latency millisecondsNumber of milliseconds delay in jitter buffer (from 1 to

1000 milliseconds).
jitter-buffer-packets packetsNumber of packets in jitter buffer (from 1 to 64).
payload-size bytesPayload size in integer number of bytes.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring SAToP on 4-Port Channelized OC3/STM1 Circuit Emulation PICs

Configuring SAToP Emulation on T1/E1 Interfaces on 12-port Channelized T1/E1 Circuit

Emulation PICs

ATM Support on Circuit Emulation PICs Overview

shared-interface
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

862

shared-interface;
[edit interfaces ge-fpc/pic/slot],
[edit interfaces so-fpc/pic/slot],
[edit interfaces xe-fpc/pic/slot]

Statement introduced in Junos OS Release 9.3.

Configure a physical interface to be a shared interface. Logical interfaces configured
under the shared physical interface can be assigned to different Protected System
Domains (PSDs).
This statement has no options.
view-levelTo view this statement in the configuration.
control-levelTo add this statement to the configuration.

interface-shared-with on page 636

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

scheduler-maps (For ATM2 IQ Interfaces)

Syntax

Hierarchy Level
Release Information
Description
Options

scheduler-maps map-name {
forwarding-class (class-name | assured-forwarding | best-effort | expedited-forwarding
| network-control);
vc-cos-mode (alternate | strict);
}
[edit at-fpc/pic/port interface-name atm-options]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, define CoS parameters assigned to forwarding classes.
map-nameName of the scheduler map.

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

Configuring Scheduler Maps on ATM Interfaces

atm-scheduler-map on page 429

schedulers
Syntax
Hierarchy Level
Release Information
Description
Default

Options

schedulers number;
[edit interfaces interface-name]

Statement introduced in Junos OS Release 8.2.

Specify the number of schedulers for Ethernet IQ2 and IQ2-E PIC port interfaces.
If you omit this statement, the 1024 schedulers are distributed equally over all ports in
multiples of 4.
numberNumber of schedulers to configure on the port.

Range: 1 through 1024

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Class of Service Feature Guide for Routing Devices

Copyright 2014, Juniper Networks, Inc.

863

Interfaces Fundamentals for Routing Devices

secondary
Syntax
Hierarchy Level
Release Information
Description
Options

secondary interface-name;
[edit interfaces (rsp0 | rsp1) redundancy-options]

Statement introduced before Junos OS Release 7.4.

Specify the secondary (backup) AS PIC interface or MultiServices PIC interface.
interface-nameThe identifier for the AS PIC interface or MultiServices PIC interface,

which must be of the form sp-fpc/pic/port.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

send-critical-event
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

864

send-critical-event;
[edit protocols oam ethernet link-fault-management action-profile action]

Statement introduced in Junos OS Release 8.5.

Send OAM PDUs with the critical event bit set.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Specifying the Actions to Be Taken for Link-Fault Management Events

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

serial-options
Syntax

Hierarchy Level
Release Information
Description

serial-options {
clock-rate rate;
clocking-mode (dce | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm (ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopback (dce-local | dce-remote | local | remote);
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
[edit interfaces se-pim/0/port]

Statement introduced prior to Junos OS Release 7.4.

Configure serial-specific interface properties.
The statements are explained separately.

Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

865

Interfaces Fundamentals for Routing Devices

Related
Documentation

Serial Interfaces Overview on page 301

no-concatenate

server
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

server;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options]

Statement introduced in Junos OS Release 8.5.

Configure the router to operate in the PPPoE server mode. Supported on M120 and M320
Multiservice Edge Routers and MX Series Universal Edge Routers operating as access
concentrators.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring the PPPoE Server Mode

server-timeout
Syntax
Hierarchy Level
Release Information
Description

Options

server-timeout seconds;
[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Sets the number of seconds the port waits for a reply when relaying a response from the
client to the authentication server before timing out and invoking the server-fail action.
secondsThe number of seconds the port waits for a response when relaying a request

from the authentication server to the client before resending the request.
Range: 1 through 60 seconds
Default: 30 seconds
Required Privilege
Level
Related
Documentation

866

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

interface (IEEE 802.1x) on page 629

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

service (Logical Interfaces)

Syntax

Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

service {
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
[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]

Statement introduced before Junos OS Release 7.4.

Define one or more service sets and filters, and one postservice filter to be applied to an
interface.
The remaining statements are explained separately.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

867

Interfaces Fundamentals for Routing Devices

service (PPPoE)
Syntax

Hierarchy Level
Release Information

Description

Default
Options

service service-name {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
max-sessions number;
agent-specifier {
aci circuit-id-string ari remote-id-string {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
static-interface interface-name;
}
}
}
[edit protocols pppoe service-name-tables table-name]

Statement introduced in Junos OS Release 10.0.

any, dynamic-profile, routing-instance, max-sessions, and static-interface options
introduced in Junos OS Release 10.2.
Specify the action taken by the interface on receipt of a PPPoE Active Discovery Initiation
(PADI) control packet for the specified named service, empty service, or any service in a
PPPoE service name table. You can also specify the dynamic profile and routing instance
that the router uses to instantiate a dynamic PPPoE interface, and the maximum number
of active PPPoE sessions that the router can establish with the specified service.
The default action is terminate.
service-nameService entry in the PPPoE service name table:

service-nameNamed service entry of up to 32 characters; for example, premiumService.

You can configure a maximum of 512 named service entries across all PPPoE service
name tables on the router.

emptyService entry of zero length that represents an unspecified service. Each PPPoE

service name table includes one empty service entry by default.

anyDefault service for non-empty service entries that do not match the named or
empty service entries configured in the PPPoE service name table. Each PPPoE service

name table includes one any service entry by default.

The remaining statements are explained separately.
Required Privilege
Level

868

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Related
Documentation

Configuring PPPoE Service Name Tables

Assigning a Service to a Service Name Table and Configuring the Action Taken When the
Client Request Includes a Non-zero Service Name Tag

Configuring the Action Taken When the Client Request Includes an Empty Service Name
Tag

Configuring the Action Taken for the Any Service

service-domain
Syntax
Hierarchy Level

Release Information
Description

Options

service-domain (inside | outside);

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For adaptive services interfaces, specify a service interface domain. If you specify this
interface using the next-hop-service statement at the [edit services service-set
service-set-name] hierarchy level, the interface domain must match that used with the
inside-service-interface and outside-service-interface statements.
insideInterface used within the network.
outsideInterface used outside the network.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

869

Interfaces Fundamentals for Routing Devices

service-filter (Interfaces)
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

service-filter filter-name;
[edit interfaces interface-name unit logical-unit-number family inet service (input | output)
service-set service-set-name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service (input | output) service-set service-set-name]

Statement introduced before Junos OS Release 7.4.

Define the filter to be applied to traffic before it is accepted for service processing.
Configuration of a service filter is optional; if you include the service-set statement without
a service-filter definition, Junos OS assumes the match condition is true and selects the
service set for processing automatically.
filter-nameIdentifies the filter to be applied in service processing.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Applying Filters and Services to Interfaces

Junos OS Services Interfaces Library for Routing Devices

service-name
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

870

service-name name;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options]

Statement introduced before Junos OS Release 7.4.

For J Series Services Routers with PPP over Ethernet interfaces, configure the service to
be requested from the PPP over Ethernet server; that is, the access concentrator. For
example, you can use this statement to indicate an Internet service provider (ISP) name
or a class of service.
nameService to be requested from the PPP over Ethernet server.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the PPPoE Service Name

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

service-name-table
Syntax
Hierarchy Level

Release Information

Description

service-name-table table-name;
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family
pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit interfaces interface-name unit logical-unit-number family pppoe],
[edit interfaces interface-name unit logical-unit-number pppoe-underlying-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family pppoe],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
pppoe-underlying-options]

Statement introduced in Junos OS Release 10.0.

Support at the [edit ... family pppoe] hierarchies introduced in Junos OS Release 11.2.
Specify the PPPoE service name table assigned to a PPPoE underlying interface. This
underlying interface is configured with either the encapsulation ppp-over-ether statement
or the family pppoe statement; the two statements are mutually exclusive.

NOTE: The [edit ... family pppoe] hierarchies are supported only on MX Series
routers with MPCs.

Options

table-nameName of the PPPoE service name table, a string of up to 32 alphanumeric

characters.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Assigning a Service Name Table to a PPPoE Underlying Interface

Configuring the PPPoE Family for an Underlying Interface

Copyright 2014, Juniper Networks, Inc.

871

Interfaces Fundamentals for Routing Devices

service-name-tables
Syntax

Hierarchy Level

service-name-tables table-name {
service service-name {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
max-sessions number;
agent-specifier {
aci circuit-id-string ari remote-id-string {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
static-interface interface-name;
}
}
}
}
[edit protocols pppoe]

Release Information

Statement introduced in Junos OS Release 10.0.

dynamic-profile, routing-instance, max-sessions, and static-interface options introduced
in Junos OS Release 10.2.

Description

Create and configure a PPPoE service name table. Specify the action taken for each
service and remote access concentrator on receipt of a PPPoE Active Discovery Initiation
(PADI) packet. You can also specify the dynamic profile and routing instance that the
router uses to instantiate a dynamic PPPoE interface, and the maximum number of active
PPPoE sessions that the router can establish with the specified service. A maximum of
32 PPPoE service name tables is supported per router.

Options

table-nameName of the PPPoE service name table, a string of up to 32 alphanumeric

characters.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

872

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Creating a Service Name Table

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

service-set
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

service-set service-set-name;
[edit interfaces interface-name unit logical-unit-number family inet service (input | output)
service-set service-set-name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet service (input | output) service-set service-set-name]

Statement introduced before Junos OS Release 7.4.

Define one or more service sets to be applied to an interface. If you define multiple service
sets, the Junos OS evaluates the filters in the order in which they appear in the
configuration.
service-set-nameIdentifies the service set.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

873

Interfaces Fundamentals for Routing Devices

services (Priority Level)

Syntax
Hierarchy Level
Release Information
Description
Options

Required Privilege
Level
Related
Documentation

874

services priority-level;
[edit interfaces interface-name services-options sysloghost hostname]

Statement introduced before Junos OS Release 7.4.

Specify system logging priority level.
priority-levelAssigns a priority level to the facility. Valid entries are as follows:

alertConditions that should be corrected immediately.

anyMatches any level.

emergencyPanic conditions.

criticalCritical conditions.

errorError conditions.

infoInformational messages.

noticeConditions that require special handling.

warningWarning messages.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

services-options
Syntax

Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

services-options {
inactivity-timeout seconds;
open-timeout seconds;
session-limit {
maximum number;
rate new-sessions-per-second;
}
syslog {
host hostname {
facility-override facility-name;
log-prefix prefix-number;
services priority-level;
}
}
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Define the service options to be applied on an interface.
The remaining statements are explained separately.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

875

Interfaces Fundamentals for Routing Devices

shaping
Syntax

Hierarchy Level

Release Information
Description

shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
[edit interfaces interface-name atm-options vpi vpi-identifier],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-name unit logical-unit-number address address family family
multipoint-destination address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
address address family family multipoint-destination address]

Statement introduced before Junos OS Release 7.4.

For ATM encapsulation only, define the traffic-shaping profile.
For Circuit Emulation PICs, specify traffic shaping in the ingress and egress directions.
For ATM2 IQ interfaces, changing or deleting VP tunnel traffic shaping causes all logical
interfaces on a VP to be deleted and then re-added.
VP tunnels are not supported on multipoint interfaces.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

876

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Defining Virtual Path Tunnels

Defining the ATM Traffic-Shaping Profile

Configuring ATM QoS or Shaping

Applying Scheduler Maps to Logical ATM Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

shdsl-options
Syntax

Hierarchy Level

Release Information
Description

shdsl-options {
annex (annex-a | annex-b);
line-rate line-rate;
loopback (local | remote | payload);
snr-margin {
current margin;
snext margin;
}
}
[edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name

Statement introduced in Junos OS Release 7.4.

For J Series Services Routers only, configure symmetric DSL (SHDSL) options.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-SHDSL Overview

Copyright 2014, Juniper Networks, Inc.

877

Interfaces Fundamentals for Routing Devices

short-name-format
Syntax
Hierarchy Level

Release Information

Description
Options

short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);

[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name]

Statement introduced in Junos OS Release 8.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers.
Specify the name format of the maintenance association name.
character-stringThe name is an ASCII character string.
vlanThe primary VLAN identifier.
2octetA number in the range 0 through 65,535.
rfc-2685-vpn-idA VPN identifier that complies with RFC 2685.

Default: character-string

NOTE: The PTX Series Packet Transport Routers support the vlan and 2octet
options only.

Required Privilege
Level
Related
Documentation

878

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Creating a Maintenance Association

Configuring Ethernet 802.1ag OAM on PTX Series Packet Transport Routers

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

short-sequence
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

short-sequence;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For multilink interfaces only, set the length of the packet sequence identification number
to 12 bits.
If you omit this statement from the configuration, the length is set to 24 bits.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

879

Interfaces Fundamentals for Routing Devices

sla-iterator-profile
Syntax

Hierarchy Level

Release Information
Description
Options

sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id]

Statement introduced in Junos OS Release 11.1.

Configure a remote MEP with an iterator profile and specify the options.
profile-nameName of the iterator profile configured for a remote MEP. For more

information about configuring a remote MEP with an iterator profile, see Configuring
a Remote MEP with an Iterator Profile.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

880

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

Configuring an Iterator Profile

Configuring a Remote MEP with an Iterator Profile

Verifying the Configuration of an Iterator Profile

Managing Iterator Statistics

sla-iterator-profiles on page 881

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

sla-iterator-profiles
Syntax

Hierarchy Level
Release Information
Description
Options

sla-iterator-profiles {
profile-name {
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period iteration-period-value;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
[edit protocols oam ethernet connectivity-fault-management performance-monitoring]

Statement introduced in Junos OS Release 11.1.

Configure an iterator application and specify the iterator profile options.
profile-nameName of the iterator profile. For more information about configuring the

iterator profile, see Configuring an Iterator Profile.

The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

ConfigureTo enter configuration mode.

ControlTo modify any configuration.

Configuring an Iterator Profile

Configuring a Remote MEP with an Iterator Profile

Verifying the Configuration of an Iterator Profile

Managing Iterator Statistics

Copyright 2014, Juniper Networks, Inc.

881

Interfaces Fundamentals for Routing Devices

snext
Syntax
Hierarchy Level

Release Information

snext margin;
[edit interfaces interface-name shdsl-options snr-margin],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options
snr-margin]

Statement introduced in Junos OS Release 7.4.

Description

For J Series Services Routers only, configure self-near-end crosstalk (SNEXT)

signal-to-noise ratio (SNR) margin for a SHDSL line. When configured, the line trains at
higher than SNEXT threshold. The SNR margin is the difference between the desired SNR
and the actual SNR.

Options

marginDesired SNEXT margin. Possible values are disabled or a margin between 10dB

and 10 dB.
Default: disabled
Required Privilege
Level
Related
Documentation

882

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-SHDSL Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

snr-margin
Syntax

Hierarchy Level

Release Information
Description

snr-margin {
current margin;
snext margin;
}
[edit interfaces interface-name shdsl-options],
[edit logical-systems logical-system-name interfaces interface-name shdsl-options]

Statement introduced in Junos OS Release 7.4.

For J Series Services Routers only, configure the SHDSL signal-to-noise ratio (SNR)
margin. The SNR margin is the difference between the desired SNR and the actual SNR.
Configuring the SNR creates a more stable SHDSL connection by making the line train
at a SNR margin higher than the threshold. If any external noise below the threshold is
applied to the line, the line remains stable.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ATM-over-SHDSL Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

883

Interfaces Fundamentals for Routing Devices

sonet-options
Syntax

Hierarchy Level
Release Information
Description

884

sonet-options {
aps {
advertise-interval milliseconds;
annex-b
authentication-key key;
(break-before-make | no-break-before-make);
fast-aps-switch;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
bytes {
c2 value;
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
fcs (16 | 32);
loopback (local | remote);
mpls {
pop-all-labels {
required-depth number;
}
}
path-trace trace-string;
(payload-scrambler | no-payload-scrambler);
rfc-2615;
trigger {
defect ignore;
defect hold-time up milliseconds down milliseconds;
}
}
vtmapping (itu-t | klm);
(z0-increment | no-z0-increment);
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Configure SONET/SDH-specific interface properties.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

On SONET/SDH OC48 interfaces that you configure for channelized (multiplexed) mode
(by including the no-concatenate statement at the [edit chassis fpc slot-number pic
pic-number] hierarchy level), the bytes e1-quiet and bytes f1 options have no effect. The
bytes f2, bytes z3, bytes z4, and path-trace options work correctly on channel 0 and work
in the transmit direction only on channels 1, 2, and 3.
On a channelized OC12 interface, the bytes e1-quiet, bytes f1, bytes f2, bytes z3, and bytes
z4 options are not supported. The fcs and payload-scrambler statements are also not
supported; you must configure these for each DS3 channel using the t3-options fcs and
t3-options payload-scrambler statements. The aps and loopback statements are supported
only on channel 0 and are ignored if included in the configurations for channels 1 through
11. You can configure loopbacks for each DS3 channel with the t3-options loopback
statement. The path-trace statement can be included in the configuration for each DS3
channel, thereby configuring a unique path trace for each channel.
To configure loopback on channelized IQ and IQE PICs, SONET/SDH level, use the
loopback statement local and remote options at the controller interface (coc48, cstm16,
coc12, cstm4, coc3, and cstm1). It is ignored for path-level interfaces so-fpc/pic/port or
so-fpc/pic/port:channel.
If you are running Intermediate System-to-Intermediate System (IS-IS) over SONET/SDH
interfaces, use PPP if you are running Cisco IOS Release 12.0 or later. If you need to run
HDLC, configure an ISO family MTU of 4469 on the router.
The statements are explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring SONET/SDH Parameters on ATM Interfaces

Channelized OC12/STM4 IQ and IQE Interfaces Overview

Channelized STM1 Interfaces Overview

SONET/SDH Interfaces Overview

no-concatenate

Copyright 2014, Juniper Networks, Inc.

885

Interfaces Fundamentals for Routing Devices

source
Syntax
Hierarchy Level

Release Information
Description

source source-address;
[edit interfaces interface-name unit logical-unit-number tunnel address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel address]

Statement introduced before Junos OS Release 7.4.

Specify the source address of the tunnel.

Default

If you do not specify a source address, the tunnel uses the units primary address as the
source address of the tunnel.

Options

source-addressAddress of the local side of the tunnel. This is the address that is placed

in the outer IP headers source field.

Required Privilege
Level
Related
Documentation

886

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

multicast-only on page 720

primary (Address on Interface) on page 820

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

source-address-filter
Syntax

Hierarchy Level

Release Information

source-address-filter {
mac-address;
}
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Packet Transport Routers.

Description

For aggregated Ethernet, Fast Ethernet, Gigabit Ethernet, Gigabit Ethernet IQ interfaces,
and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i router), specify the MAC addresses from which
the interface can receive packets. For this statement to have any effect, you must include
the source-filtering statement in the configuration to enable source address filtering. This
statement is not supported on the J Series Services Routers.

Options

mac-addressMAC address filter. You can specify the MAC address as nn:nn:nn:nn:nn:nn

or nnnn.nnnn.nnnn, where n is a decimal digit. To specify more than one address,

include multiple mac-address options in the source-address-filter statement.
If you enable the VRRP on a Fast Ethernet or Gigabit Ethernet interface, as described in
VRRP and VRRP for IPv6 Overview, and if you enable MAC source address filtering
on the interface, you must include the virtual MAC address in the list of source MAC
addresses that you specify in the source-address-filter statement. MAC addresses
ranging from 00:00:5e:00:01:00 through 00:00:5e:00:01:ff are reserved for VRRP,
as defined in RFC 3768, Virtual Router Redundancy Protocol. When you configure the
VRRP group, the group number must be the decimal equivalent of the last
hexadecimal byte of the virtual MAC address.
On untagged Gigabit Ethernet interfaces, you should not configure the source-address-filter
statement and the accept-source-mac statement simultaneously. On tagged Gigabit
Ethernet interfaces, you should not configure the source-address-filter statement
and the accept-source-mac statement with an identical MAC address specified in
both filters.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Enabling Ethernet MAC Address Filtering

Configuring MAC Address Filtering on PTX Series Packet Transport Routers

source-filtering on page 753

Copyright 2014, Juniper Networks, Inc.

887

Interfaces Fundamentals for Routing Devices

source-class-usage
Syntax

Hierarchy Level

Release Information

Description

Options

source-class-usage {
direction;
}
[edit interfaces interface-name unit logical-unit-number family inet accounting],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family inet accounting],
[edit routing-instances routing-instance-name vrf-table-label]

Statement introduced before Junos OS Release 7.4.

Support for the vrf-table-label statement added in Junos OS Release 9.3.
Enable packet counters on an interface that count packets that arrive from specific
prefixes on the provider core router and are destined for specific prefixes on the customer
edge router.
direction can be one of the following:
inputConfigure at least one expected ingress point.
outputConfigure at least one expected egress point.
input outputOn a single interface, configure at least one expected ingress point and

one expect egress point.

Required Privilege
Level
Related
Documentation

888

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Enabling Source Class and Destination Class Usage on page 242

accounting on page 403

destination-class-usage on page 508

Junos OS Services Interfaces Library for Routing Devices

vrf-table-label

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

source-filtering
Syntax
Hierarchy Level

Release Information

Description

(source-filtering | no-source-filtering);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Packet Transport Routers.
For aggregated Ethernet, Fast Ethernet, Gigabit Ethernet, and Gigabit Ethernet IQ
interfaces only, enable the filtering of MAC source addresses, which blocks all incoming
packets to that interface. To allow the interface to receive packets from specific MAC
addresses, include the source-address-filter statement.
If the remote Ethernet card is changed, the interface is no longer able to receive packets
from the new card because it has a different MAC address.

Default
Required Privilege
Level
Related
Documentation

Source address filtering is disabled.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling Ethernet MAC Address Filtering

Configuring MAC Address Filtering on PTX Series Packet Transport Routers

accept-source-mac on page 399

source-address-filter on page 887

Copyright 2014, Juniper Networks, Inc.

889

Interfaces Fundamentals for Routing Devices

speed (Ethernet)
Syntax
Hierarchy Level

speed (10m | 100m | 1g | auto | auto-10m-100m);

[edit interfaces interface-name],
[edit interfaces ge-pim/0/0 switch-options switch-port port-number]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Statement introduced in Junos OS Release 13.2X50-D10 for EX Series switches.

Description

Configure the interface speed. This statement applies to the management Ethernet
interface (fxp0 or em0), Fast Ethernet 12-port and 48-port PICs, the built-in Fast Ethernet
port on the FIC (M7i router), the built-in Ethernet interfaces on J Series Services Routers,
Combo Line Rate DPCs and Tri-Rate Ethernet Copper interfaces on MX Series routers,
Gigabit Ethernet ports on J Series Services Routers with uPIMs installed and configured
for access switching mode, and Gigabit Ethernet interfaces on EX Series switches.
When you configure the Tri-Rate Ethernet copper interface to operate at 1 Gbps,
autonegotiation must be enabled. When you configure 100BASE-FX SFP, you must set
the port speed at 100 Mbps.

Options

You can specify the speed as either 10m (10 Mbps), 100m (100 Mbps), or on J Series
routers with uPIMs installed and on MX Series routers, 1g (1 Gbps). You can also
specify the auto option on MX Series routers.
For Gigabit Ethernet interfaces on EX Series switches, you can specify one of the following
options:

10m10 Mbps

100m100 Mbps

1g1 Gbps

autoAutomatically negotiate the speed (10 Mbps, 100 Mbps, or 1 Gbps) based on

the speed of the other end of the link.

auto-10m-100mAutomatically negotiate the speed (10 Mbps or 100 Mbps) based

on the speed of the other end of the link.

Required Privilege
Level
Related
Documentation

890

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Interface Speed on page 106

Configuring the Interface Speed on Ethernet Interfaces

Configuring Gigabit Ethernet Autonegotiation

Configuring Gigabit Ethernet Interfaces on J Series Services Routers

Configuring Gigabit Ethernet Interfaces (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

speed (MX Series DPC)

Syntax
Hierarchy Level
Release Information
Description

speed (auto | 1Gbps | 100Mbps | 10Mbps);

[edit interfaces ge-fpc/pic/port]

Statement introduced in Junos OS Release 9.5.

On MX Series routers with Combo Line Rate DPCs and Tri-Rate Copper SFPs you can
set auto negotiation of speed. To specify the auto negotiation speed, use the speed (auto
| 1Gbps | 100Mbps | 10Mbps) statement under the [edit interface ge-/fpc/pic/port] hierarchy
level. The auto option will attempt to automatically match the rate of the connected
interface. To set port speed negotiation to a specific rate, set the port speed to 1Gbps,
100Mbps, or 10Mbps.

NOTE: If the negotiated speed and the interface speed do not match, the
link will not be brought up. Half duplex mode is not supported.

Options

Required Privilege
Level
Related
Documentation

You can specify the speed as either auto (autonegotiate), 10Mbps (10 Mbps), 100Mbps
(100 Mbps), or 1Gbps (1 Gbps).
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Autonegotiation

no-auto-mdix on page 737

Copyright 2014, Juniper Networks, Inc.

891

Interfaces Fundamentals for Routing Devices

speed (SONET/SDH)
Syntax
Hierarchy Level

Release Information
Description

Options

speed (oc3 | oc12 | oc48);

[edit interfaces so-fpc/pic/port],
[edit interfaces so-fpc/pic/port:channel]

Statement introduced in Junos OS Release 8.3.

Configure the interface speed. This statement applies to SONET/SDH interfaces on
next-generation SONET/SDH Type 1 and Type 2 PICs with SFP. Available speeds depend
on whether the PIC is in concatenated mode or nonconcatenated mode. Include the
channel in the interface name when configuring nonconcatenated interfaces.
oc3 | oc12 | oc48Speed when the PIC is in concatenated mode. For example, you can

configure each port of a 4-port OC12 PIC to have a speed of oc3.

You can configure port 0 of a 4-port OC12 PIC to have a speed of oc12.
oc3 | oc12Speed when the PIC is in nonconcatenated mode.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring SONET/SDH Interface Speed

spid1
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

892

spid1 spid1-string;
[edit interfaces br-pim/0/port isdn-options]

Statement introduced before Junos OS Release 7.4.

Configure the Service Profile Identifier (SPID).
spid1-stringNumeric SPID.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

spid2
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

spid2 spid2-string;
[edit interfaces br-pim/0/port isdn-options]

Statement introduced before Junos OS Release 7.4.

Configure an additional SPID.
spid2-stringNumeric SPID.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

J Series Services Router Configuration Guide

Copyright 2014, Juniper Networks, Inc.

893

Interfaces Fundamentals for Routing Devices

stacked-vlan-ranges
Syntax

Hierarchy Level
Release Information
Description

stacked-vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
password password-string;
username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-18
option-37
option-82;
radius-realm radius-realm-string;
user-prefix user-prefix-string;
}
}
dynamic-profile profile-name {
accept (any | dhcp-v4 | inet);
ranges (any | low-taghigh-tag),(any | low-taghigh-tag);
}
override;
}
[edit interfaces interface-name auto-configure]

Statement introduced in Junos OS Release 9.5.

Configure multiple VLANs. Each VLAN is assigned a VLAN ID number from the range.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

894

routingTo view this statement in the configuration.

routingcontrolTo add this statement to the configuration.

Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs

Configuring Interfaces to Support Both Single and Stacked VLANs

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

stacked-vlan-tagging
Syntax
Hierarchy Level

stacked-vlan-tagging;
[edit interfaces interface-name]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access 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.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview

vlan-tags (Stacked VLAN Tags) on page 979

Copyright 2014, Juniper Networks, Inc.

895

Interfaces Fundamentals for Routing Devices

start-end-flag
Syntax
Hierarchy Level

Release Information

Description

start-end-flag (filler | shared);

[edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
For DS0, E1, E3, T1, and T3 interfaces, configure the interface to share the transmission
of start and end flags.

NOTE: When configuring E1 or T1 interfaces on the 10-port Channelized E1/T1

IQE PIC, the start-end-flag statement must be included at the [edit interfaces
e1-fpc/pic/port] or [edit interfaces t1-fpc/pic/port] hierarchy level as
appropriate.

Options

fillerWait two idle cycles between the start and end flags.
sharedShare the transmission of the start and end flags. This is the default.

Required Privilege
Level
Related
Documentation

896

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring E1 Start and End Flags

Configuring the E3 Start and End Flags

Configuring T1 Start and End Flags

Configuring T3 Start and End Flags

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

static-interface
Syntax
Hierarchy Level

Release Information
Description

static-interface interface-name;
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]

Statement introduced in Junos OS Release 10.2.

Reserve the specified static PPPoE interface for use only by the PPPoE client with
matching agent circuit identifier (ACI) and agent remote identifier (ARI) information. You
can specify only one static interface per ACI/ARI pair configured for a named service
entry, empty service entry, or any service entry in the PPPoE service name table.
The static interface associated with an ACI/ARI pair takes precedence over the general
pool of static interfaces associated with the PPPoE underlying interface.
If you include the static-interface statement in the configuration, you cannot also include
either the dynamic-profile statement or the routing-instance statement. The
dynamic-profile, routing-instance, and static-interface statements are mutually exclusive
for ACI/ARI pair configurations.

Options

interface-nameName of the static PPPoE interface reserved for use by the PPPoE client

with matching ACI/ARI information. Specify the interface in the format pp0.logical,
where logical is a logical unit number from 0 through 16385 for static interfaces.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Reserving a Static PPPoE Interface for Exclusive Use by a PPPoE Client

Copyright 2014, Juniper Networks, Inc.

897

Interfaces Fundamentals for Routing Devices

static-tei-val
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

static-tei-val value;
[edit interfaces br-pim/0/port isdn-options]

Statement introduced before Junos OS Release 7.4.

For J Series Services Routers only. Statically configure the Terminal Endpoint Identifier
(TEI) value. The TEI value represents any ISDN-capable device attached to an ISDN
network that is the terminal endpoint. TEIs are used to distinguish between several
different devices using the same ISDN links.
valueValue between 0 through 63.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

supplicant
Syntax
Hierarchy Level
Release Information
Description

supplicant single;
[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Specify the supplicant mode. Only single mode is supported.
This option will authenticate only the first client that connects to a port. All other clients
that connect later (802.1x compliant or non-compliant) will be allowed free access on
that port without any further authentication. If the first authenticated client logs out, all
other users are locked out until a client authenticates again.

Options
Required Privilege
Level
Related
Documentation

898

singleSets single mode.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

interface (IEEE 802.1x) on page 629

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

supplicant-timeout
Syntax
Hierarchy Level
Release Information
Description

Options

supplicant-timeout seconds;
[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Specify the number of seconds the port waits for a response when relaying a request
from the authentication server to the client before resending the request.
secondsSpecify the number of seconds the port waits for the supplicant timeout.

Range: 1 through 60 seconds

Default: 30 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

interface (IEEE 802.1x) on page 629

Copyright 2014, Juniper Networks, Inc.

899

Interfaces Fundamentals for Routing Devices

swap
Syntax
Hierarchy Level

Release Information

Description

swap;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Statement introduced in Junos OS Release 13.2X51-D20 for the QFX Series.
Specify the VLAN rewrite operation to replace a VLAN tag. The outer VLAN tag of the
frame is overwritten with the user-specified VLAN tag information.
On MX Series routers, you can enter this statement on Gigabit Ethernet IQ and 10-Gigabit
Ethernet IQ2 and IQ2-E interfaces, 10-Gigabit Ethernet LAN/WAN PIC, aggregated Ethernet
using Gigabit Ethernet IQ interfaces, and 100-Gigabit Ethernet Type 5 PIC with CFP. On
EX Series switches, you can enter this statement on Gigabit Ethernet, 10-Gigabit Ethernet,
40-Gigabit Ethernet, and aggregated Ethernet interfaces.

Required Privilege
Level
Related
Documentation

900

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Rewriting the VLAN Tag on Tagged Frames

Configuring Q-in-Q Tunneling (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

swap-push
Syntax
Hierarchy Level

Release Information

Description

swap-push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Specify the VLAN rewrite operation to replace the outer VLAN tag of the frame with 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.
You can use this statement on Gigabit Ethernet IQ, IQ2 and IQ2-E interfaces, 10-Gigabit
Ethernet LAN/WAN PIC, and for aggregated Ethernet interfaces using Gigabit Ethernet
IQ2 and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers, and 100-Gigabit Ethernet
Type 5 PIC with CFP.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Rewriting a VLAN Tag and Adding a New Tag

Copyright 2014, Juniper Networks, Inc.

901

Interfaces Fundamentals for Routing Devices

swap-swap
Syntax
Hierarchy Level

Release Information

Description

swap-swap;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced in Junos OS Release 8.1.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Specify the VLAN rewrite operation to replace both the inner and the outer VLAN tags
of the frame with a user-specified VLAN tag value.
You can use this statement on Gigabit Ethernet IQ, IQ2 and IQ2-E interfaces, 10-Gigabit
Ethernet LAN/WAN PIC, for aggregated Ethernet interfaces using Gigabit Ethernet IQ2
and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers, and for 100-Gigabit Ethernet
Type 5 PIC with CFP.

Required Privilege
Level
Related
Documentation

902

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Rewriting the Inner and Outer VLAN Tags

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

switch-options
Syntax

Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

switch-options {
switch-port port-number {
(auto-negotiation | no-auto-negotiation);
speed (10m | 100m | 1g);
link-mode (full-duplex | half-duplex);
}
}
[edit interfaces ge-pim/0/0]

Statement introduced in Junos OS Release 8.4.

On a J Series Services Router with multiport Gigabit Ethernet uPIMs installed and operating
in access switching mode, only one physical interface is configured for the entire multiport
Gigabit Ethernet uPIM. Configuration of the physical port characteristics is done under
the single physical interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Interfaces on J Series Services Routers

Copyright 2014, Juniper Networks, Inc.

903

Interfaces Fundamentals for Routing Devices

switch-port
Syntax

Hierarchy Level
Release Information
Description

switch-port port-number {
(auto-negotiation | no-auto-negotiation);
speed (10m | 100m | 1g);
link-mode (full-duplex | half-duplex);
}
[edit interfaces ge-pim/0/0 switch-options]

Statement introduced in Junos OS Release 8.4.

On a J Series Services Router with Ethernet uPIMs installed and operating in access
switching mode, configuration of the physical port characteristics, done under the single
physical interface.

Default

Autonegotiation is enabled by default. If the link speed and duplex are also configured,
the interfaces use the values configured as the desired values in the negotiation.

Options

port-numberPorts are numbered 0 through 5 on the 6-port Gigabit Ethernet uPIM, 0

through 7 on the 8-port Gigabit Ethernet uPIM, and 0 through 15 on the 16-port Gigabit
Ethernet uPIM.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

904

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Gigabit Ethernet Interfaces on J Series Services Routers

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

switch-type
Syntax
Hierarchy Level
Release Information
Description
Options

switch-type (att5e | etsi | ni1 | ntdms-100)

[edit interfaces br-pim/0/port isdn-options]

Statement introduced before Junos OS Release 7.4.

For J Series Services Routers only. Configure the ISDN variant supported.
att5eAT&T switch variant.
etsiEuropean Telecommunications Standards Institute switch variant.
ni1National ISDN 1 switch variant.
ntdms-100Northern Telecom DMS-100.
nttNTT Group switch for Japan.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

ISDN Interfaces Overview

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

905

Interfaces Fundamentals for Routing Devices

switching-mode
Syntax
Hierarchy Level
Release Information
Description

Default

Options

switching-mode (bidirectional | unidirectional);

[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

For unchannelized OC3, OC12, and OC48 SONET/SDH interfaces on T Series routers
only, configure the interface to interoperate with SONET/SDH line-terminating equipment
(LTE) that is provisioned for unidirectional linear APS in 1+1 architecture.
If the switching-mode statement is not configured, the mode is bidirectional, and the
interface does not interoperate with a unidirectional SONET/SDH LTE.
bidirectionalSupport bidirectional mode only.
unidirectionalInteroperate with a SONET/SDH LTE provisioned for unidirectional mode.

Required Privilege
Level
Related
Documentation

906

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Switching Mode

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

symbol-period
Syntax
Hierarchy Level

Release Information
Description

symbol-period count;
[edit protocols oam ethernet link-fault-management action-profile event, link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]

Statement introduced in Junos OS Release 8.4.

Configure the threshold for sending symbol period events or taking the action specified
in the action profile.
A symbol error is any symbol code error on the underlying physical layer. The symbol
period threshold is reached when the number of symbol errors reaches the configured
value within the period window. The default period window is the number of symbols
that can be transmitted on the underlying physical layer in 1 second. The window is not
configurable.

Options

countThreshold count for symbol period events.

Range: 1 through 100

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Threshold Values for Local Fault Events on an Interface

Configuring Threshold Values for Fault Events in an Action Profile

Copyright 2014, Juniper Networks, Inc.

907

Interfaces Fundamentals for Routing Devices

syslog (Interfaces)
Syntax

Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

syslog {
host hostname {
facility-override facility-name;
log-prefix prefix-number;
services priority-level;
}
}
[edit interfaces interface-name services-options]

Statement introduced before Junos OS Release 7.4.

For adaptive services interfaces, configure generation of system log messages for the
service set. System log information is passed to the kernel for logging in the /var/log
directory. Any values configured in the service set definition override these values.
The remaining statements are explained separately.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

syslog (Monitoring)
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

908

(syslog | no-syslog);
[edit interfaces mo-fpc/pic/port multiservice-options]

Statement introduced before Junos OS Release 7.4.

System logging is enabled by default. The system log information of the Monitoring
Services PIC is passed to the kernel for logging in the /var/log directory.

syslogEnable PIC system logging.

no-syslogDisable PIC system logging.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Multiservice Physical Interface Properties on page 153

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

syslog (OAM Action)

Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

syslog;
[edit protocols oam ethernet link-fault-management action-profile action]

Statement introduced in Junos OS Release 8.5.

Generate a syslog message for the Ethernet Operation, Administration, and Management
(OAM) event.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Specifying the Actions to Be Taken for Link-Fault Management Events

system-priority
Syntax
Hierarchy Level
Release Information

Description

system-priority priority;
[edit interfaces aeX aggregated-ether-options lacp]

Statement introduced in Junos OS Release 9.3.

Statement introduced in Junos OS Release 11.4 for EX Series switches.
Define LACP system priority at the aggregated Ethernet interface level. This system
priority value takes precedence over a system priority value configured at the global [edit
chassis] hierarchy level.
The device with the lower system priority value determines which links between LACP
partner devices are active and which are in standby for each LACP group. The device on
the controlling end of the link uses port priorities to determine which ports are bundled
into the aggregated bundle and which ports are put in standby mode. Port priorities on
the other device (the noncontrolling end of the link) are ignored. In priority comparisons,
numerically lower values have higher priority. Therefore, the system with the numerically
lower value (higher priority value) for LACP system priority becomes the controlling
system. If both devices have the same LACP system priority (for example, they are both
configured with the default setting of 127), the device MAC address determines which
switch is in control.

Options

priorityPriority for the aggregated Ethernet system. A smaller value indicates a higher

priority.
Range: 0 through 65535
Default: 127
Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

909

Interfaces Fundamentals for Routing Devices

t1-options
Syntax

Hierarchy Level
Release Information

Description

t1-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout value;
byte-encoding (nx56 | nx64);
crc-major-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5);
crc-minor-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5 | 5e-6 | 1e-6);
fcs (16 | 32);
framing (esf | sf);
idle-cycle-flag (flags | ones);
invert-data;
line-encoding (ami | b8zs);
loopback (local | payload | remote);
remote-loopback-respond;
start-end-flag (filler | shared);
timeslots time-slot-range;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Configure T1-specific physical interface properties.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

910

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

T1 Interfaces Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

t310
Syntax
Hierarchy Level
Release Information
Description

Options

t310-value seconds;
[edit interfaces br-pim/0/port isdn-options]

Statement introduced before Junos OS Release 7.4.

For ISDN interfaces, configure the Q.931-specific timer for T310, in seconds. The Q.931
protocol is involved in the setup and termination of connections.
secondsTimer value, in seconds.

Range: 1 through 65,536 seconds

Default: 10 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

t391
Syntax
Hierarchy Level
Release Information
Description
Options

t391 seconds;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voices interfaces only, set Frame Relay link integrity polling interval.
secondsLink integrity polling interval.

Range: 5 through 30 seconds

Default: 10 seconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

n391 on page 726

n392 on page 727

n393 on page 728

t392 on page 912

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

911

Interfaces Fundamentals for Routing Devices

t392
Syntax
Hierarchy Level
Release Information
Description
Options

t392 seconds;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voices interfaces only, set Frame Relay polling verification interval.
secondsPolling verification interval.

Range: 5 through 30 seconds

Default: 15 seconds
Required Privilege
Level
Related
Documentation

912

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

n391 on page 726

n392 on page 727

n393 on page 728

t391 on page 911

timeslots on page 920

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

t3-options
Syntax

Hierarchy Level
Release Information
Description

t3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
(cbit-parity | no-cbit-parity);
compatibility-mode (digital-link | kentrox | larscom) <subrate value>;
fcs (16 | 32);
(feac-loop-respond | no-feac-loop-respond);
idle-cycle-flag value;
(long-buildout | no-long-buildout);
(loop-timing | no-loop-timing);
loopback (local | payload | remote);
start-end-flag value;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Configure T3-specific physical interface properties, including the properties of DS3
channels on a channelized OC12 interface. The long-buildout statement is not supported
for DS3 channels on a channelized OC12 interface.
On T3 interfaces, the default encapsulation is PPP.
For ATM1 interfaces, you can configure a subset of E3 options statements.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

T3 Interfaces Overview

Copyright 2014, Juniper Networks, Inc.

913

Interfaces Fundamentals for Routing Devices

tag-protocol-id (TPIDs Expected to Be Sent or Received)

Syntax
Hierarchy Level

tag-protocol-id [tpids];
[edit interfaces interface-name gigether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile],
[edit interfaces interface-name ether-options ethernet-switch-profile]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Statement introduced in Junos OS Release 13.2X50-D15 for EX Series switches.

Description

For Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces, aggregated
Ethernet with Gigabit Ethernet IQ interfaces, and Gigabit Ethernet PICs with SFPs (except
the 10-port Gigabit Ethernet PIC, and the built-in Gigabit Ethernet port on the M7i router),
define the TPIDs expected to be sent or received on a particular VLAN. For each Gigabit
Ethernet port, you can configure up to eight TPIDs using the tag-protocol-id statement;
but only the first four TPIDs are supported on IQ2 and IQ2-E interfaces.
For 10-Gigabit Ethernet LAN/WAN PIC interfaces on T Series routers only the default
TPID value (0x8100) is supported.
For Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet, and aggregated Ethernet
interfaces on EX Series switches, define the TPIDs expected to be sent or received on a
particular VLAN. The default TPID value is 0x8100. Other supported values are 0x88a8,
0x9100, and 0x9200.

Options
Required Privilege
Level
Related
Documentation

914

tpidsTPIDs to be accepted on the VLAN. Specify TPIDs in hexadecimal.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames

Configuring Q-in-Q Tunneling (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

tag-protocol-id (TPID to Rewrite)

Syntax
Hierarchy Level

Release Information

Description

tag-protocol-id tpid;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
For Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces only, configure
the outer TPID value. All TPIDs you include in input and output VLAN maps must be
among those you specify at the [edit interfaces interface-name gigether-options
ethernet-switch-profile tag-protocol-id [ tpids ]] hierarchy level.
For 10-Gigabit Ethernet LAN/WAN PIC interfaces on T Series routers the default TPID
value (0x8100) is supported.

Default
Required Privilege
Level
Related
Documentation

If the tag-protocol-id statement is not configured, the TPID value is 0x8100.

interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Inner and Outer TPIDs and VLAN IDs

Copyright 2014, Juniper Networks, Inc.

915

Interfaces Fundamentals for Routing Devices

targeted-broadcast
Syntax

Hierarchy Level

Release Information
Description

targeted-broadcast {
forward-and-send-to-re;
forward-only;
}
[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]

Statement introduced in Junos OS Release 10.2.

Specify the IP packets destined for a Layer 3 broadcast address to be forwarded to both
an egress interface and the Routing Engine, or to an egress interface only. The packets
are broadcast only if the egress interface is a LAN interface.
The statements are explained separately.

Default

Required Privilege
Level
Related
Documentation

916

When this statement is not included, broadcast packets are sent to the Routing Engine
only.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Targeted Broadcast on page 251

Understanding Targeted Broadcast on page 250

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

targeted-distribution (Static Interfaces over Aggregated Ethernet)

Syntax
Hierarchy Level

Release Information

Description

Required Privilege
Level
Related
Documentation

targeted-distribution;
[edit interfaces demux0 unit logical-unit-number],
[edit interfaces pp0 unit logical-unit-number]

Statement introduced in Junos OS Release 11.2.

Statement introduced in Junos OS Release 13.2R2 for EX Series switches.
Configure egress data for a logical interface to be sent across a single member link in an
aggregated Ethernet bundle. A backup link is provisioned with CoS scheduling resources
in the event that the primary assigned link goes down. The aggregated Ethernet interface
must be configured without link protection.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

CoS for PPPoE Subscriber Interfaces Overview

Configuring the Distribution Type for PPPoE Subscribers on Aggregated Ethernet Interfaces

Verifying the Distribution of PPPoE Subscribers in an Aggregated Ethernet Interface

Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis

Configuring Module Redundancy for a Virtual Chassis

Configuring Chassis Redundancy for a Virtual Chassis

tei-option
Syntax
Hierarchy Level
Release Information
Description

Options

tei-option (first-call | power-up);

[edit interfaces br-pim/0/port isdn-options]

Statement introduced before Junos OS Release 7.4.

For ISDN interfaces, configure when the Terminal Endpoint Identifier (TEI) negotiates
with the ISDN provider.
first-callActivation does not occur until the call setup is sent.
power-upActivation occurs when the Services Router is powered on.

Default: power-up
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ISDN Physical Interface Properties

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

917

Interfaces Fundamentals for Routing Devices

terminate (PPPoE Service Name Tables)

Syntax

terminate;

Hierarchy Level

[edit protocols pppoe service-name-tables table-name service service-name],

[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]

Release Information

Statement introduced in Junos OS Release 10.0.

Support at [edit protocols pppoe service-name-tables table-name service service-name
agent-specifier aci circuit-id-string ari remote-id-string] hierarchy level introduced in Junos
OS Release 10.2.

Description

Direct the router to immediately respond to a PPPoE Active Discovery Initiation (PADI)
control packet received from a PPPoE client by sending the client a PPPoE Active
Discovery Offer (PADO) packet. The PADO packet contains the name of the access
concentrator (router) that can service the client request. The terminate action is the
default action for a named service entry, empty service entry, any service entry, or agent
circuit identifier/agent remote identifier (ACI/ARI) pair in a PPPoE service name table.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

then
Syntax

Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

918

then {
discard;
}
[edit firewall hierarchical-policer aggregate],
[edit firewall hierarchical-policer premium]

Statement introduced in Junos OS Release 9.5.

On M40e, M120, and M320 (with FFPC and SFPC) edge routers and T320, T640, and
T1600 core routers with Enhanced Intelligent Queuing (IQE) PICs, discard packets when
a specified bandwidth or burst limits for an aggregate level of a hierarchical policer is
reached.
discardDiscard packets if condition is met.

firewallTo view this statement in the configuration.

firewall-controlTo add this statement to the configuration.

Applying Policers on page 210

Class of Service Feature Guide for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

threshold
Syntax
Hierarchy Level
Release Information

threshold bytes;
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Description

Specify the bucket threshold, which controls the burstiness of the leaky bucket
mechanism. The larger the value, the more bursty the traffic, which means that over a
very short amount of time, the interface can receive or transmit close to line rate, but the
average over a longer time is at the configured bucket rate.

Options

bytesMaximum size, in bytes, for traffic bursts. For ease of entry, you can enter number

either as a complete decimal number or as a decimal number followed by the

abbreviation k (1000). For example, the entry threshold 2k corresponds to a threshold
of 2000 bytes.
Range: 0 through 65,535 bytes
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

Copyright 2014, Juniper Networks, Inc.

919

Interfaces Fundamentals for Routing Devices

timeslots
Syntax
Hierarchy Level

Release Information
Description

timeslots time-slot-range;
[edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name partition partition-number],
[edit interfaces interface-name t1-options]

Statement introduced before Junos OS Release 7.4.

For E1 and T1interfaces, allocate the specific time slots by number.

NOTE: When configuring E1 or T1 interfaces on the 10-port Channelized E1/T1

IQE PIC, the timeslots statement must be included at the [edit interfaces
e1-fpc/pic/port] or [edit interfaces t1-fpc/pic/port] hierarchy level as
appropriate.

Options

time-slot-rangeActual time slot numbers allocated:

Range: Ranges vary by interface type and configuration option as follows:

1 through 24 for T1 interfaces (0 is reserved)

1 through 31 for 4-port E1 PICs (0 is reserved)

1 through 31 for NxDS0 interfaces (0 is reserved)

2 through 32 for 10-port Channelized E1 and 10-port Channelized E1 IQ PICs (1 is

reserved)

2 through 32 for the setting under e1-options with IQE PICs (1 is reserved) (when creating
fractional E1)

1 through 31 for the setting under partition with IQE PICs (0 is reserved) (when creating
NxDS0)

NOTE: When creating fractional E1 interfaces only, if you connect a 4-port

E1 PIC interface to a device that uses time slot numbering from 2 through 32,
you must subtract 1 from the configured number of time slots.

Required Privilege
Level
Related
Documentation

920

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Fractional E1 IQ and IQE Interfaces

Configuring Fractional T1 IQ and IQE Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Configuring Fractional E1 Time Slots

Configuring Fractional T1 Time Slots

Configuring a Channelized T1/E1 Interface to Drop and Insert Time Slots

tm
Syntax
Hierarchy Level

Release Information
Description
Options

tm (ignore | normal | require);

[edit interfaces interface-name serial-options dce-options],
[edit interfaces interface-name serial-options dte-options]

Statement introduced before Junos OS Release 7.4.

For EIA-530 interfaces only, configure the from-DCE signal, test-mode (TM).
ignoreThe from-DCE signal is ignored.
normalNormal TM signal handling as defined by the TIA/EIA Standard 530.
requireThe from-DCE signal must be asserted.

Default: normal
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Signal Handling on page 310

tm-polarity
Syntax
Hierarchy Level
Release Information
Description
Options

tm-polarity (negative | positive);

[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure TM signal polarity.
negativeNegative signal polarity.
positivePositive signal polarity.

Default: positive
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Serial Signal Polarities on page 313

Copyright 2014, Juniper Networks, Inc.

921

Interfaces Fundamentals for Routing Devices

traceoptions (Individual Interfaces)

Syntax

Hierarchy Level
Release Information

Description

traceoptions {
file filename <files name> <size size> <world-readable | no-world-readable>;
flag flag;
match;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Define tracing operations for individual interfaces.
To specify more than one tracing operation, include multiple flag statements.
The interfaces traceoptions statement does not support a trace file. The logging is done
by the kernel, so the tracing information is placed in the system syslog file in the directory
/var/log/dcd.

Default
Options

If you do not include this statement, no interface-specific tracing operations are performed.
file nameName of the file to receive the output of the tracing operation. Enclose the

name within quotation marks. All files are placed in the directory /var/log/dcd. By
default, interface process tracing output is placed in the file files number(Optional)
Maximum number of trace files. When a trace file named trace-file reaches its
maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the
maximum number of trace files is reached. Then the oldest trace file is overwritten.
match(Optional) Regular expression for lines to be traced.
no-world-readable(Optional) Prevent any user from reading the log file.
world-readable(Optional) Allow any user to read the log file.
size size(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB),

or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is
renamed trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme
continues until the maximum number of trace files is reached. Then, the oldest trace
file is overwritten.
flagTracing operation to perform. To specify more than one tracing operation, include

multiple flag statements. The following are the interface-specific tracing options.

922

allAll interface tracing operations

eventInterface events

ipcInterface interprocess communication (IPC) messages

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Required Privilege
Level
Related
Documentation

mediaInterface media changes

q921Trace ISDN Q.921 frames

q931Trace ISDN Q.931 frames

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Tracing Operations of an Individual Router Interface on page 321

Copyright 2014, Juniper Networks, Inc.

923

Interfaces Fundamentals for Routing Devices

traceoptions (Interface Process)

Syntax

Hierarchy Level
Release Information

Description
Default
Options

traceoptions {
file <filename> <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
flag flag <disable>;
no-remote-trace;
}
[edit interfaces]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Define tracing operations for the interface process (dcd).
If you do not include this statement, no interface-specific tracing operations are performed.
disable(Optional) Disable the tracing operation. You can use this option to disable a

single operation when you have defined a broad group of tracing operations, such
as all.
filenameName of the file to receive the output of the tracing operation. Enclose the

name within quotation marks. All files are placed in the directory /var/log. By default,
interface process tracing output is placed in the file dcd.
files number(Optional) Maximum number of trace files. When a trace file named
trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and

so on, until the maximum number of trace files is reached. Then the oldest trace file
is overwritten.
If you specify a maximum number of files, you also must specify a maximum file size with
the size option.
Range: 2 through 1000
Default: 3 files
flagTracing operation to perform. To specify more than one tracing operation, include

multiple flag statements. You can include the following flags:

all

change-eventsLog changes that produce configuration events

config-statesLog the configuration state machine changes

kernelLog configuration IPC messages to kernel

kernel-detailLog details of configuration messages to kernel

no-world-readable(Optional) Disallow any user to read the log file.

924

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

size size(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB),

or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed
trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues
until the maximum number of trace files is reached. Then, the oldest trace file is
overwritten.
If you specify a maximum file size, you also must specify a maximum number of trace
files with the files option.
Syntax: xk to specify kilobytes, xm to specify megabytes, or xg to specify gigabytes
Range: 10 KB through the maximum file size supported on your router
Default: 1 MB
world-readable(Optional) Allow any user to read the log file.
match regex(Optional) Refine the output to include only those lines that match the

given regular expression.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Tracing Operations of the Interface Process on page 322

Copyright 2014, Juniper Networks, Inc.

925

Interfaces Fundamentals for Routing Devices

traceoptions (LACP)
Syntax

Hierarchy Level
Release Information
Description
Default
Options

traceoptions {
file <filename> <files number> <size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
fast-hello-issu
[edit protocols lacp]

Statement introduced in Junos OS Release 7.6.

Define tracing operations for the LACP protocol.
If you do not include this statement, no LACP protocol tracing operations are performed.
disable(Optional) Disable the tracing operation. You can use this option to disable a

single operation when you have defined a broad group of tracing operations, such
as all.
filenameName of the file to receive the output of the tracing operation. Enclose the

name within quotation marks. All files are placed in the directory /var/log. By default,
interface process tracing output is placed in the file lacpd.
files number(Optional) Maximum number of trace files. When a trace file named
trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and

so on, until the maximum number of trace files is reached. Then the oldest trace file
is overwritten.
If you specify a maximum number of files, you also must specify a maximum file size with
the size option.
Range: 2 through 1000
Default: 3 files
flagTracing operation to perform. To specify more than one tracing operation, include

multiple flag statements. You can include the following flags:

allAll LACP tracing operations

configurationConfiguration code

packetPackets sent and received

processLACP process events

protocolLACP protocol state machine

routing-socketRouting socket events

startupProcess startup events

no-world-readable(Optional) Prevent any user from reading the log file.

926

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

size size(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB),

or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed
trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues
until the maximum number of trace files is reached. Then the oldest trace file is
overwritten.
If you specify a maximum file size, you also must specify a maximum number of trace
files with the files option:
Syntax: xk to specify kilobytes, xm to specify megabytes, or xg to specify gigabytes
Range: 10 KB through the maximum file size supported on your router
Default: 1 MB
world-readable(Optional) Allow any user to read the log file.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Tracing LACP Operations

Copyright 2014, Juniper Networks, Inc.

927

Interfaces Fundamentals for Routing Devices

traceoptions (PPP Process)

Syntax

Hierarchy Level

traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
flag flag;
level severity-level;
no-remote-trace;
}
[edit protocols ppp]

Release Information

Statement introduced in Junos OS Release 7.5.

Description

Define tracing operations for the PPP process.

To specify more than one tracing operation, include multiple flag statements.
You cannot specify a separate trace tile. Tracing information is placed in the system
syslog file in the directory /var/log/pppd.

Default
Options

If you do not include this statement, no PPPD-specific tracing operations are performed.
filenameName of the file to receive the output of the tracing operation. Enclose the

name within quotation marks. All files are placed in the directory /var/log. By default,
commit script process tracing output is placed in the file ppd. If you include the file
statement, you must specify a filename. To retain the default, you can specify eventd
as the filename.
files number(Optional) Maximum number of trace files. When a trace file named
trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and

so on, until the maximum number of trace files is reached. Then the oldest trace file
is overwritten.
If you specify a maximum number of files, you also must specify a maximum file size with
the size option and a filename.
Range: 2 through 1000
Default: 3 files
disable(Optional) Disable the tracing operation. You can use this option to disable a

single operation when you have defined a broad group of tracing operations, such
as all.
flagTracing operation to perform. To specify more than one tracing operation, include

multiple flag statements. The following are the PPPD-specific tracing options.

928

accessAccess code

address-poolAddress pool code

allAll areas of code

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

authAuthentication code

chapChallenge Handshake Authentication Protocol (CHAP) code

configConfiguration code

ifdbInterface database code

lcpLCP state machine code

memoryMemory management code

messageMessage processing code

mlpppTrace MLPPP code

ncpNCP state machine code

papPassword Authentication Protocol (PAP) code

pppPPP protocol processing code

radiusRADIUS processing code

rtsockRouting socket code

sessionSession management code

signalSignal handling code

timerTimer code

uiUser interface code

match regex(Optional) Refine the output to include only those lines that match the

given regular expression.

size size(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB),

or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed
trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues
until the maximum number of trace files is reached. Then the oldest trace file is
overwritten.
If you specify a maximum file size, you also must specify a maximum number of trace
files with the files option and filename.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through 1 GB
Default: 128 KB
world-readable(Optional) Enable unrestricted file access.
non-world-readable(Optional) By default, log files can be accessed only by the user

who configures the tracing operation. Specify non-world-readable to reset the default.
Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

929

Interfaces Fundamentals for Routing Devices

Related
Documentation

930

Tracing Operations of the pppd Process on page 137

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

traceoptions (PPPoE)
Syntax

Hierarchy Level
Release Information

Description
Options

traceoptions {
file <filename> <files number> <match regular-expression > <size maximum-file-size>
<world-readable | no-world-readable>;
filter {
aci regular-expression;
ari regular-expresion;
service-name regular-expresion;
underlying-interface interface-name;
}
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
}
[edit protocols pppoe]

Statement introduced in Junos OS Release 9.6.

Option filter introduced in Junos OS Release 12.3
Define tracing operations for PPPoE processes.
file filenameName of the file to receive the output of the tracing operation. Enclose the

name within quotation marks. All files are placed in the directory /var/log.
files number(Optional) Maximum number of trace files to create before overwriting the

oldest one. If you specify a maximum number of files, you also must specify a
maximum file size with the size option.
Range: 2 through 1000
Default: 3 files
disableDisable this trace flag.
filterAdditional filter to refine the output to display particular subscribers. Filtering

based on the following subscriber identifiers simplifies troubleshooting in a scaled

environment.

BEST PRACTICE: Due to the complexity of agent circuit identifiers and agent
remote identifiers, we recommend that you do not try an exact match when
filtering on these options. For service names, searching on the exact name is
appropriate, but you can also use a regular expression with that option.

aci regular-expressionRegular expression to match the agent circuit identifier provided

by PPPoE client.

ari regular-expressionRegular expression to match the agent remote identifier provided

by PPPoE client.

Copyright 2014, Juniper Networks, Inc.

931

Interfaces Fundamentals for Routing Devices

service regular-expressionRegular expression to match the name of PPPoE service.

underlying-interface interface-nameName of a PPPoE underlying interface. You cannot

use a regular expression for this filter option.

flag flagTracing operation to perform. To specify more than one tracing operation,

include multiple flag statements. You can include the following flags:

allTrace all operations.

configTrace configuration events.

eventsTrace events.

gresTrace GRES events.

initTrace initialization events.

interface-dbTrace interface database operations.

memoryTrace memory processing events.

protocolTrace protocol events.

rtsockTrace routing socket events.

session-dbTrace connection events and flow.

signalTrace signal operations.

stateTrace state handling events.

timerTrace timer processing.

uiTrace user interface processing.

levelLevel of tracing to perform. You can specify any of the following levels:

allMatch all levels.

errorMatch error conditions.

infoMatch informational messages.

noticeMatch notice messages about conditions requiring special handling.

verboseMatch verbose messages.

warningMatch warning messages.

Default: error
match regular-expression(Optional) Refine the output to include lines that contain the

regular expression.
no-remote-traceDisable remote tracing.
no-world-readable(Optional) Disable unrestricted file access.

932

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

size maximum-file-size(Optional) Maximum size of each trace file. By default, the number

entered is treated as bytes. Alternatively, you can include a suffix to the number to
indicate kilobytes (KB), megabytes (MB), or gigabytes (GB). If you specify a maximum
file size, you also must specify a maximum number of trace files with the files option.
Syntax: sizek to specify KB, sizem to specify MB, or sizeg to specify GB
Range: 10240 through 1073741824
Default: 128 KB
world-readable(Optional) Enable unrestricted file access.

Required Privilege
Level
Related
Documentation

traceTo view this statement in the configuration.

trace-controlTo add this statement to the configuration.

Configuring PPPoE Service Name Tables

Tracing PPPoE Operations

translate-discard-eligible
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(translate-discard-eligible | no-translate-discard-eligible);
[edit interfaces interface-name unit logical-unit-number family ccc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family ccc]

Statement introduced before Junos OS Release 7.4.

For interfaces with encapsulation type Frame Relay CCC, enable or disable translation
of Frame Relay discard eligible (DE) control bits.
DE bit translation is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Frame Relay Control Bit Translation

Copyright 2014, Juniper Networks, Inc.

933

Interfaces Fundamentals for Routing Devices

translate-fecn-and-becn
Syntax
Hierarchy Level

Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(translate-fecn-and-becn | no-translate-fecn-and-becn);
[edit interfaces interface-name unit logical-unit-number family ccc],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family ccc]

Statement introduced before Junos OS Release 7.4.

For interfaces with encapsulation type Frame Relay CCC, enable or disable translation
of Frame Relay forward explicit congestion notification (FECN) control bits and Frame
Relay backward explicit congestion notification (BECN) control bits.
FECN and BECN bit translation is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Frame Relay Control Bit Translation

translate-plp-control-word-de
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

934

translate-plp-control-word-de
[edit interfaces interface-name unit logical-unit-number family ccc]

Statement introduced before Junos OS Release 11.1.

For the interfaces with encapsulation type Frame Relay CCC, classify and rewrite the
control word discard eligibility (DE) bit based on the packet loss priority (PLP).
PLP bit translation is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring Frame Relay Control Bit Translation

frame-relay-de

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

transmit-bucket
Syntax

Hierarchy Level
Release Information
Description

transmit-bucket {
overflow discard;
rate percentage;
threshold bytes;
}
[edit interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Set parameters for the transmit leaky bucket, which specifies what percentage of the
interfaces total capacity can be used to transmit packets.
For each DS3 channel in a channelized OC12 interface, you can configure a unique transmit
bucket.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Receive and Transmit Leaky Bucket Properties to Reduce Network

Congestion on page 139

receive-bucket on page 838

transmit-clock
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

transmit-clock invert;
[edit interfaces interface-name serial-options]

Statement introduced before Junos OS Release 7.4.

Configure the transmit clock signal.
invertShift the clock phase 180 degrees.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Serial Clocking Mode on page 307

Copyright 2014, Juniper Networks, Inc.

935

Interfaces Fundamentals for Routing Devices

transmit-period
Syntax
Hierarchy Level
Release Information

transmit-period seconds;
[edit protocols dot1x authenticator interface interface-id]

Statement introduced in Junos OS Release 9.3.

Description

Set the number of seconds the port waits before retransmitting the initial EAPOL PDUs
to the client.

Options

secondsThe number of seconds the port waits before retransmitting the initial EAPOL

PDUs to the client.

Range: 1 through 65,535 seconds
Default: 30 seconds
Required Privilege
Level
Related
Documentation

936

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

IEEE 802.1x Port-Based Network Access Control Overview

authenticator on page 432

dot1x on page 517

interface (IEEE 802.1x) on page 629

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

transmit-weight (ATM2 IQ CoS Forwarding Class)

Syntax
Hierarchy Level

Release Information
Description
Default
Options

transmit-weight (cells number | percent number);

[edit interfaces interface-name atm-options scheduler-maps map-name forwarding-class
class-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, assign a transmission weight to a forwarding class.
95 percent for queue 0, 5 percent for queue 3.
percent percentTransmission weight of the forwarding class as a percentage of the

total bandwidth.
Range: 5 through 100
cells numberTransmission weight of the forwarding class as a number of cells.

Range: 0 through 32,000

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

Copyright 2014, Juniper Networks, Inc.

937

Interfaces Fundamentals for Routing Devices

transmit-weight (ATM2 IQ Virtual Circuit)

Syntax
Hierarchy Level

Release Information
Description

transmit-weight number;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ PICs only, configure the transmission weight.
Each VC is serviced in weighted round robin (WRR) mode. When VCs have data to send,
they send the number of cells equal to their weight before passing control to the next
active VC. This allows proportional bandwidth sharing between multiple VCs within a
rate-shaped VP tunnel. VP tunnels are not supported on multipoint interfaces.

Options

numberNumber of cells a VC sends before passing control to the next active VC within

a VP tunnel.
Range: 1 through 32,767
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the ATM2 IQ Transmission Weight

traps
Syntax

(traps | no-traps);

Hierarchy Level

[edit interfaces interface-name],

[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-range name],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Release Information

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.

Description

Required Privilege
Level
Related
Documentation

938

Enable or disable the sending of Simple Network Management Protocol (SNMP)

notifications when the state of the connection changes.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Enabling or Disabling SNMP Notifications on Physical Interfaces on page 154

Enabling or Disabling SNMP Notifications on Logical Interfaces on page 183

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

trigger
Syntax

Hierarchy Level
Release Information
Description

Default
Options

trigger {
defect ignore;
defect hold-time up milliseconds down milliseconds;
}
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

For ATM over SONET/SDH, SONET/SDH interfaces, and 10-Gigabit Ethernet interfaces
in WAN PHY mode, configure SONET/SDH defect triggers to be ignored.
If you do not include this statement, all SONET/SDH defect triggers are honored.
defectDefect to ignore or hold. It can be one of the following:

ais-lLine alarm indication signal

ais-pPath alarm indication signal

ber-sdBit error rate signal degrade

ber-sfBit error rate signal fault

locd (ATM only)Loss of cell delineation

lofLoss of frame

lolPHY loss of light

lop-pPath loss of pointer

losLoss of signal

pllPHY phase-locked loop out of lock

plm-pPath payload (signal) label mismatch

rfi-lLine remote failure indication

rfi-pPath remote failure indication

uneq-pPath unequipped

The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring SONET/SDH Defect Triggers

Copyright 2014, Juniper Networks, Inc.

939

Interfaces Fundamentals for Routing Devices

trigger-link-failure
Syntax
Hierarchy Level
Release Information
Description

Options
Required Privilege
Level
Related
Documentation

[trigger-link-failure interface-name];
[edit interfaces lsq-fpc/pic/port lsq-failure-options]

Statement introduced in Junos OS Release 7.4.

List of SONET interfaces connected to the LSQ interface that can implement Automatic
Protection Switching (APS) if the LSQ PIC fails.
interface-nameName of SONET interface.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

trunk-bandwidth
Syntax
Hierarchy Level

Release Information
Description

trunk-bandwidth rate;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces configured to use Layer 2 circuit trunk mode, configure a scheduler
so that unused bandwidth from any inactive trunk is proportionally shared among the
active trunks.
During congestion, each trunk receives a proportional share of the leftover bandwidth,
thus minimizing the latency on each trunk.

Options

ratePeak 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.
Range: 1,000,000 through 542,526,792 bps
Required Privilege
Level
Related
Documentation

940

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Layer 2 Circuit Trunk Mode Scheduling

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

trunk-id
Syntax
Hierarchy Level

Release Information
Description

trunk-id number;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces with ATM CCC cell-relay encapsulation, configure the trunk
identification number.
When you associate a trunk ID number with a logical interface, you are in effect specifying
the interfaces that are allowed to send ATM traffic over an LSP.

Options

numberA valid trunk identifier.

Range: For UNI mode, 0 through 7. For NNI mode, 0 through 31.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Layer 2 Circuit Transport Mode on ATM2 IQ Interfaces

ttl
Syntax
Hierarchy Level
Release Information
Description
Options

ttl value;
[edit interfaces interface-name unit number tunnel]

Statement introduced before Junos OS Release 7.4

Set the time-to-live value bit in the header of the outer IP packet.
valueTime-to-live value.

Range: 0 through 255

Default: 64
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

941

Interfaces Fundamentals for Routing Devices

tunnel
Syntax

Hierarchy Level

Release Information
Description

tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Configure a tunnel. You can use the tunnel for unicast and multicast traffic or just for
multicast traffic. You can also use tunnels for encrypted traffic or VPNs.
The statements are explained separately.

Required Privilege
Level
Related
Documentation

942

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

Junos OS VPNs Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

underlying-interface
Syntax
Hierarchy Level

Release Information

Description

underlying-interface interface-name;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit interfaces demux0 unit logical-unit-number demux-options],
[edit logical-systems logical-system-name interfaces demux0 unit logical-unit-number
demux-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
demux0 unit logical-unit-number demux-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
pp0 unit logical-unit-number pppoe-options]

Statement introduced before Junos OS Release 7.4.

Support for aggregated Ethernet added in Junos OS Release 9.4.
For J Series Services Routers, M120 and M320 Multiservice Edge routers, and MX Series
Universal Edge Routers with PPP over Ethernet interfaces, configure the interface on
which PPP over Ethernet is running.
For demux interfaces, configure the underlying interface on which the demultiplexing
(demux) interface is running.

Options

interface-nameName of the interface on which PPP over Ethernet or demux is running.

For example, at-0/0/1.0 (ATM VC), fe-1/0/1.0 (Fast Ethernet interface), ge-2/0/0.0
(Gigabit Ethernet interface), ae1.0 (for IP demux on an aggregated Ethernet interface),
or ae1 (for VLAN demux on an aggregated Ethernet interface).

NOTE: Demux interfaces are currently supported on Gigabit Ethernet, Fast

Ethernet, 10-Gigabit Ethernet interfaces, or aggregated Ethernet devices.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an IP Demultiplexing Interface on page 284

Configuring a VLAN Demultiplexing Interface on page 288

Configuring the PPPoE Underlying Interface

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

943

Interfaces Fundamentals for Routing Devices

unframed
Syntax
Hierarchy Level
Release Information
Description

Default
Required Privilege
Level
Related
Documentation

(unframed | no-unframed);
[edit interfaces interface-name e3-options]

Statement introduced before Junos OS Release 7.4.

For E3 IQ interfaces only, enable or disable unframed mode. In unframed mode, the E3
IQ interface do not detect yellow (ylw) or loss-of-frame (lof) alarms.
Unframed mode is disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring E3 IQ and IQE Unframed Mode

unidirectional
Syntax
Hierarchy Level

Release Information

Description

unidirectional;
[edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name]

Statement introduced in Junos OS Release 8.5.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Create two new, unidirectional (transmit-only and receive-only) physical interfaces
subordinate to the original parent interface. Unidirectional links are currently supported
only on 10-Gigabit Ethernet interfaces on the following hardware:

NOTE: Which interfaces and pic for EX9200?

Default
Required Privilege
Level
Related
Documentation

944

4-port 10-Gigabit Ethernet DPC on the MX960 router

10Gigabit Ethernet IQ2 PIC and 10Gigabit Ethernet IQ2E PIC on the T Series router

Disabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Understanding Unidirectional Traffic Flow on Physical Interfaces on page 141

Enabling Unidirectional Traffic Flow on Physical Interfaces on page 142

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

unit (Dynamic Profiles Standard Interface)

Syntax

unit logical-unit-number {
auto-configure {
agent-circuit-identifier {
dynamic-profile profile-name;
}
}
dial-options {
ipsec-interface-id name;
l2tp-interface-id name;
(shared | dedicated);
}
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 {
access-concentrator name;
address address;
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
adf {
counter;
input-precedence precedence;
not-mandatory;
output-precedence precedence;
rule rule-value;
}
input filter-name (
precedence precedence;
}
output filter-name {
precedence precedence;
}
}
max-sessions number;
max-sessions-vsa-ignore;
rpf-check {
fail-filter filter-name;
mode loose;
}
service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-service-filter filter-name;
}

Copyright 2014, Juniper Networks, Inc.

945

Interfaces Fundamentals for Routing Devices

input-vlan-map {
inner-tag-protocol-id tpid;
inner-vlan-id number;
(push | swap);
tag-protocol-id tpid;
vlan-id number;
}
output {
service-set service-set-name {
service-filter filter-name;
}
}
output-vlan-map {
inner-tag-protocol-id tpid;
inner-vlan-id number;
(pop | swap);
tag-protocol-id tpid;
vlan-id number;
}
}
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;
}
keepalives {
interval seconds;
}
ppp-options {
chap;
pap;
}
vlan-id number;
vlan-tags outer [tpid].vlan-id [inner [tpid].vlan-id];
}
}

Hierarchy Level
Release Information
Description

946

[edit dynamic-profiles profile-name interfaces interface-name]

Statement introduced in Junos OS Release 9.2.

Configure a logical interface on the physical device. You must configure a logical interface
to be able to use the physical device.

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

Options

logical-unit-numberThe specific unit number of the interface you want to assign to the
dynamic profile, or one of the following Junos OS predefined variables:

$junos-underlying-interface-unitFor static VLANs, the unit number variable. The static

unit number variable is dynamically replaced with the client unit number when the
client session begins. The client unit number is specified by the DHCP when it accesses
the subscriber network.

$junos-interface-unitThe unit number variable on a dynamic underlying VLAN interface

for which you want to enable the creation of dynamic VLAN subscriber interfaces based
on agent circuit identifier information.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dynamic Underlying VLAN Interfaces to Use Agent Circuit Identifier Information

Configuring Static Underlying VLAN Interfaces to Use Agent Circuit Identifier Information

Agent Circuit Identifier-Based Dynamic VLANs Components Overview

Copyright 2014, Juniper Networks, Inc.

947

Interfaces Fundamentals for Routing Devices

unit
Syntax

948

unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
accounting-profile name;
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
allow-any-vci;
atm-scheduler-map (map-name | default);
backup-options {
interface interface-name;
}
bandwidth rate;
cell-bundle-size cells;
clear-dont-fragment-bit;
compression {
rtp {
maximum-contexts number <force>;
f-max-period number;
queues [queue-numbers];
port {
minimum port-number;
maximum port-number;
}
}
}
compression-device interface-name;
copy-tos-to-outer-ip-header;
demux-destination family;
demux-source family;
demux-options {
underlying-interface interface-name;
}
description text;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
callback;
callback-wait-period time;
deactivation-delay seconds;
dial-string [dial-string-numbers];
idle-timeout seconds;

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

incoming-map {
caller caller-id) | accept-all;
initial-route-check seconds;
load-interval seconds;
load-threshold percent;
pool pool-name;
redial-delay time;
watch-list {
[routes];
}
}
}
disable;
disable-mlppp-inner-ppp-pfc;
dlci dlci-identifier;
drop-timeout milliseconds;
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
encapsulation type;
epd-threshold cells plp1 cells;
family family-name {
... the family subhierarchy appears after the main [edit interfaces interface-name unit
logical-unit-number] hierarchy ...
}
fragment-threshold bytes;
inner-vlan-id-range start start-id end end-id;
input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap |
swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
link-layer-overhead percent;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);

Copyright 2014, Juniper Networks, Inc.

949

Interfaces Fundamentals for Routing Devices

output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap |
swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
passive-monitor-mode;
peer-unit unit-number;
plp-to-clp;
point-to-point;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
dynamic-profile profile-name;
lcp-restart-timer milliseconds;
loopback-clear-timer seconds;
ncp-restart-timer milliseconds;
pap {
access-profile name;
default-pap-password password;
local-name name;
local-password password;
passive;
}
}
pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
}
pppoe-underlying-options {
access-concentrator name;
direct-connect;
dynamic-profile profile-name;
max-sessions number;
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
short-sequence;

950

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

targeted-distribution;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
vci-range start start-vci end end-vci;
vpi vpi-identifier;
vlan-id number;
vlan-id-range number-number;
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
family family {
accounting {
destination-class-usage;
source-class-usage {
(input | output | input output);
}
}
access-concentrator name;
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;
duplicate-protection;
dynamic-profile profile-name;
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);
max-sessions number;

Copyright 2014, Juniper Networks, Inc.

951

Interfaces Fundamentals for Routing Devices

mtu bytes;
multicast-only;
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 {
post-service-filter filter-name;
service-set service-set-name <service-filter filter-name>;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
service-name-table table-name
(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];
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;
epd-threshold cells <plp1 cells>;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
shaping {

952

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

(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-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority number;
track {
interface interface-name {
bandwidth-threshold bits-per-second priority-cost number;
}
priority-hold-time seconds;
route ip-address/prefix-length routing-instance instance-name priority-cost cost;
}
virtual-address [addresses];
virtual-link-local-address ipv6address;
vrrp-inherit-from {
active-interface interface-name;
active-group group-number;
}
}
}
}
}

Hierarchy Level

Release Information
Description

Options

[edit interfaces interface-name],

[edit logical-systems logical-system-name interfaces interface-name],
[edit interfaces interface-set interface-set-name interface interface-name]

Statement introduced before Junos OS Release 7.4.

Configure a logical interface on the physical device. You must configure a logical interface
to be able to use the physical device.
logical-unit-numberNumber of the logical unit.

Range: 0 through 1,073,741,823 for demux and PPPoE static interfaces. 0 through 16,385
for all other static interface types.
The remaining statements are explained separately.
Required Privilege
Level

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Copyright 2014, Juniper Networks, Inc.

953

Interfaces Fundamentals for Routing Devices

unnumbered-address (Demux)
Syntax
Hierarchy Level

Release Information

Description

Options

unnumbered-address interface-name <preferred-source-address address>;

[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]

Statement introduced in Junos OS Release 8.2.

preferred-source-address option introduced in Junos OS Release 9.0.
IP demultiplexing interfaces supported in Junos OS Release 9.2.
For IP demultiplexing interfaces, enable the local address to be derived from the specified
interface. Configuring an unnumbered interface enables IP processing on the interface
without assigning an explicit IP address to the interface.
interface-nameName 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.
Required Privilege
Level
Related
Documentation

954

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an Unnumbered Interface on page 203

address on page 412

Junos System Basics Configuration Guide

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

unnumbered-address (Dynamic Profiles)

Syntax
Hierarchy Level

Release Information

Description

unnumbered-address interface-name <preferred-source-address address>;

[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]

Statement introduced in Junos OS Release 9.2.

$junos-preferred-source-address variable support added in Junos OS Release 9.6.
Support for the $junos-loopback-interface predefined variable introduced in Junos OS
Release 9.6.
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-nameName 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 dynamic 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 valid, static routing instance
value. In addition, whatever static unnumbered interface you specify must belong to
that routing instance.

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.

When defining the unnumbered-address statement using the $junos-loopback-interface

dynamic variable, keep the following in mind:

To use the $junos-loopback-interface dynamic variable, the dynamic profile must also
contain the routing-instance statement configured with the $junos-routing-instance
dynamic variable at the [edit dynamic-profiles] hierarchy level.

The applied loopback interface is based on the dynamically obtained routing instance
of the subscriber.

Copyright 2014, Juniper Networks, Inc.

955

Interfaces Fundamentals for Routing Devices

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 dynamic variable for the
inet family, or $junos-preferred-source-ipv6-address dynamic 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 $junos-preferred-source-ipv6-address dynamic
variables, keep the following in mind:

Required Privilege
Level
Related
Documentation

956

You must configure the unnumbered-address statement using the

$junos-loopback-interface dynamic variable.

You must configure the routing-instance statement using the $junos-routing-instance

dynamic 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.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Dynamic Profiles Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

unnumbered-address (Ethernet)
Syntax
Hierarchy Level

Release Information

Description

Options

unnumbered-address interface-name <preferred-source-address address>;

[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]

Statement introduced in Junos OS Release 8.2.

preferred-source-address option introduced in Junos OS Release 9.0.
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.
interface-nameName 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.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring an Unnumbered Interface on page 203

address on page 412

Junos System Basics Configuration Guide

Copyright 2014, Juniper Networks, Inc.

957

Interfaces Fundamentals for Routing Devices

unnumbered-address (PPP)
Syntax

unnumbered-address interface-name destination address destination-profile profile-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

Options

Statement introduced before Junos OS Release 7.4.

For interfaces with PPP encapsulation, enable the local address to be derived from the
specified interface.
interface-nameInterface from which the local address is derived. The interface name

must include a logical unit number and must have a configured address.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

958

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring IPCP Options on page 200

address on page 412

negotiate-address on page 734

Junos OS Administration Library for Routing Devices

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

up-count
Syntax
Hierarchy Level

Release Information
Description

up-count cells;
[edit interfaces interface-name atm-options vpi vpi-identifier oam-liveness],
[edit interfaces interface-name unit logical-unit-number oam-liveness],
[edit interfaces interface-name unit logical-unit-number family family address address
multipoint-destination address oam-liveness],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
oam-liveness],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family family address address multipoint-destination address oam-liveness]

Statement introduced before Junos OS Release 7.4.

For ATM encapsulation only, configure Operation, Administration, and Maintenance
(OAM) F5 loopback cell count thresholds. Not supported on ATM-over-SHDSL interfaces.
For ATM2 IQ PICs only, configure OAM F4 loopback cell count thresholds at the [edit
interfaces interface-name atm-options vpi vpi-identifier] hierarchy level.

Options

cellsMinimum number of consecutive OAM F4 or F5 loopback cells received before a

VC is declared up.
Range: 1 through 255
Default: 5 cells
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the ATM OAM F5 Loopback Cell Threshold

Copyright 2014, Juniper Networks, Inc.

959

Interfaces Fundamentals for Routing Devices

user-prefix
Syntax
Hierarchy Level

Release Information
Description

Options
Required Privilege
Level
Related
Documentation

960

user-prefix user-prefix-string;
[edit interfaces interface-name auto-configure vlan-ranges authentication username-include],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication
username-include]

Statement introduced in Junos OS Release 10.0.

Specify the user prefix that is concatenated with the username during the subscriber
authentication process.
user-prefix-stringThe user prefix string.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

username-include
Syntax

Hierarchy Level

Release Information
Description

username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-18;
option-37;
option-82 <circuit-id> <remote-id>;
radius-realm radius-realm-string;
user-prefix user-prefix-string;
}
[edit interfaces interface-name auto-configure vlan-ranges authentication],
[edit interfaces interface-name auto-configure stacked-vlan-ranges authentication]

Statement introduced in Junos OS Release 10.0.

Configure the username that the router passes to the external AAA server. You must
include at least one of the optional statements for the username to be valid. If you do
not configure a username, the router accesses the local authentication service only and
does not use external authentication services, such as RADIUS.
The username takes the format user-prefix mac-address circuit-type option82
interface-name domain-name radius-realm with each component separated by whatever
delimiter you choose.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Interface Username Information for AAA Authentication

Using DHCP Option 82 Suboptions in Authentication Usernames for Autosense VLANs

Using DHCP Option 18 and Option 37 in Authentication Usernames for DHCPv6 Autosense
VLANs

Copyright 2014, Juniper Networks, Inc.

961

Interfaces Fundamentals for Routing Devices

vbr
Syntax
Hierarchy Level

Release Information
Description

vbr peak rate sustained rate burst length;

[edit interfaces interface-name atm-options vpi vpi-identifier shaping],
[edit interfaces interface-name unit logical-unit-number address address family family
multipoint-destination address shaping ],
[edit interfaces interface-name unit logical-unit-number shaping ],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
address address family family multipoint-destination address shaping ],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
shaping ]

Statement introduced before Junos OS Release 7.4.

For ATM encapsulation only, define the variable bandwidth utilization in the traffic-shaping
profile.
When you configure the variable bandwidth utilization, you must specify all three options
(burst, peak, and sustained). You can specify the rate 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 the rate 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.

Default
Options

If the vbr statement is not specified, bandwidth utilization is unlimited.

burst lengthBurst length, in cells. If you set the length to 1, the peak traffic rate is used.

Range: 1 through 4000 cells

peak ratePeak rate, in bits per second or cells per second.

Range: For ATM1 interfaces, 33 Kbps through 135.6 Mbps (ATM OC3); 33 Kbps through
276 Mbps (ATM OC12). For ATM2 IQ OC3 and OC12 interfaces, 33 Kbps through
542,526,792 bps. For ATM2 IQ OC48 interfaces, 33 Kbps through 2,170,107,168 bps.
For ATM2 IQ DS3 and E3 interfaces, from 33 Kbps through the maximum rate, which
depends on the ATM encapsulation and framing you configure.
sustained rateSustained rate, in bits per second or cells per second.

Range: For ATM1 interfaces, 33 Kbps through 135.6 Mbps (ATM OC3); 33 Kbps through
276 Mbps (ATM OC12). For ATM2 IQ OC3 and OC12 interfaces, 33 Kbps through
542,526,792 bps. For ATM2 IQ OC48 interfaces, 33 Kbps through 2,170,107,168 bps.
For ATM2 IQ DS3 and E3 interfaces, from 33 Kbps through the maximum rate, which
depends on the ATM encapsulation and framing you configure.
Required Privilege
Level
Related
Documentation

962

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM CBR

Applying Scheduler Maps to Logical ATM Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

cbr on page 462

rtvbr on page 857

shaping on page 876

vc-cos-mode
Syntax
Hierarchy Level
Release Information
Description

Options

vc-cos-mode (alternate | strict);

[edit interfaces interface-name atm-options scheduler-maps map-name]

Statement introduced before Junos OS Release 7.4.

For ATM2 IQ interfaces only, specify packet-scheduling priority value for ATM2 IQ VC
tunnels.
alternateVC CoS queue has high priority. The scheduling of the queues alternates

between the high-priority queue and the remaining queues, so every other scheduled
packet is from the high-priority queue.
strictVC CoS queue has strictly high priority. A queue with strict high priority is always

scheduled before the remaining queues. The remaining queues are scheduled in
round-robin fashion.
Default: alternate
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM2 IQ VC Tunnel CoS Components

Configuring Scheduler Maps on ATM Interfaces

Copyright 2014, Juniper Networks, Inc.

963

Interfaces Fundamentals for Routing Devices

vci
Syntax
Hierarchy Level

Release Information

Description

vci vpi-identifier.vci-identifier;
[edit interfaces at-fpc/pic/port unit logical-unit-number],
[edit interfaces at-fpc/pic/port unit logical-unit-number family family address address
multipoint-destination address],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number
family family address address multipoint-destination address]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.1 for the QFX Series.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
routers.
For ATM point-to-point logical interfaces only, configure the virtual circuit identifier (VCI)
and virtual path identifier (VPI).
To configure a VPI for a point-to-multipoint interface, specify the VPI in the
multipoint-destination statement.
VCIs 0 through 31 are reserved for specific ATM values designated by the ATM Forum.

Options

vci-identifierATM virtual circuit identifier. Unless you configure the interface to use

promiscuous mode, this value cannot exceed the highest-numbered VC configured

for the interface with the maximum-vcs option of the vpi statement.
Range: 0 through 4089 or 0 through 65,535 with promiscuous mode, with VCIs
0 through 31 reserved.
vpi-identifierATM virtual path identifier.

Range: 0 through 255

Default: 0
Required Privilege
Level
Related
Documentation

964

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Point-to-Point ATM1 or ATM2 IQ Connection

Applying Scheduler Maps to Logical ATM Interfaces

multipoint-destination on page 724

promiscuous-mode on page 822

vpi (ATM CCC Cell-Relay Promiscuous Mode) on page 981

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vci-range
Syntax
Hierarchy Level

Release Information
Description

Options

vci-range start start-vci end end-vci;

[edit interfaces at-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number]

Statement introduced in Junos OS Release 9.0.

Range of VCI values used in ATM-to-Ethernet interworking cross-connects. VCI 0 through
31 are reserved. VCI 0 through 31 should not be used.
start-vciLowest number VCI in the range.
end-vciHighest number VCI in the range.

Range: 0 through 255

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM-to-Ethernet Interworking on page 262

virtual-switch
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

virtual-switch name bridge-domain name vlan-id [vlan-ids ];

[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name default-x]

Statement introduced in Junos OS Release 9.6.

Specify the routing-instance type as a virtual switch, under which bridge-domain MIPs
must be enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring MIP for Bridge Domains of a Virtual Switch

Copyright 2014, Juniper Networks, Inc.

965

Interfaces Fundamentals for Routing Devices

vlan-id (Logical Port in Bridge Domain)

Syntax
Hierarchy Level

Release Information
Description

Options

vlan-id number;
[edit interfaces interface-name unit logical-unit-number family bridge],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family bridge]

Statement introduced in Junos OS Release 9.2.

The VLAN ID configured on the logical port. Received packets with no VLAN tags are
forwarded within the bridge domain with the matching VLAN ID.
numberThe VLAN ID.

Range: 1 through 4095

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Logical Interface for Access Mode

vlan-id (Outer VLAN ID)

Syntax
Hierarchy Level

Release Information
Description

Options

vlan-id outer-vlan-id;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 9.0.

The outer VLAN ID to be used in ATM-to-Ethernet interworking cross-connects. Outer
VLAN IDs are converted to the ATM VPI. The outer VLAN ID must match the VPI value
configured. The allowable VPI range is 0 to 255. Do not configure the outer VLAN ID to
be greater than 255.
outer-vlan-idOuter VLAN ID number.

Range: 0 through 4094

Required Privilege
Level
Related
Documentation

966

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM-to-Ethernet Interworking on page 262

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vlan-id (VLAN ID to Be Bound to a Logical Interface)

Syntax
Hierarchy Level

Release Information
Description

Options

vlan-id number;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

For Fast Ethernet, Gigabit Ethernet, and Aggregated Ethernet interfaces only, bind a
802.1Q VLAN tag ID to a logical interface.
numberA 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.
For 48-port Fast Ethernet and Gigabit Ethernet PICs, 1 through 4094.
VLAN ID 0 is reserved for tagging the priority of frames.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Mixed Tagging

Copyright 2014, Juniper Networks, Inc.

967

Interfaces Fundamentals for Routing Devices

vlan-id (VLAN ID to Rewrite)

Syntax
Hierarchy Level

Release Information

Description

vlan-id number;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
input-vlan-map],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
output-vlan-map]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
For Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2, 10-Gigabit Ethernet LAN/WAN PIC,
and IQ2-E interfaces and aggregated Ethernet using Gigabit Ethernet IQ interfaces, specify
the line VLAN identifiers to be rewritten at the input or output interface.
You cannot include the vlan-id statement with the swap statement, swap-push statement,
push-push statement, or push-swap statement at the [edit interfaces interface-name unit
logical-unit-number output-vlan-map] hierarchy level. If you include any of those
statements in the output VLAN map, the VLAN ID in the outgoing frame is rewritten to
the vlan-id statement that you include at the [edit interfaces interface-name unit
logical-unit-number] hierarchy level.

Required Privilege
Level
Related
Documentation

968

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Rewriting the VLAN Tag on Tagged Frames

Binding VLAN IDs to Logical Interfaces

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vlan-id-list (Ethernet VLAN Circuit)

Syntax
Hierarchy Level

Release Information
Description

vlan-id-list [vlan-id vlan-idvlan-id];

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 9.5.

Binds a single-tag logical interface to a list of VLAN IDs. Configures a logical interface to
receive and forward any tag frame whose VLAN ID tag matches the list of VLAN IDs you
specify.

NOTE:
When you create a circuit cross-connect (CCC) using VLAN-bundled
single-tag logical interfaces on Layer 2 VPN routing instances, the circuit
automatically uses ethernet encapsulation. For Layer 2 VPN, you need to
include the encapsulation-type statement and specify the value ethernet at
either of the following hierarchy levels:

[edit routing-instances routing-instance-name protocols l2vpn]

[edit logical-systems logical-system-name routing-instances

routing-instance-name protocols l2vpn]

For more information about the encapsulation-type configuration statement

and the Layer 2 encapsulation types ethernet and ethernet-vlan, see the Junos
OS VPNs Library for Routing Devices.

Options

[vlan-id vlan-idvlan-id]A list of valid VLAN ID numbers. Specify the VLAN IDs individually

by using a space to separate each ID, as an inclusive list by separating the starting
VLAN ID and ending VLAN ID with a hyphen, or as a combination of both.
Range: 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.

NOTE: Configuring vlan-id-list with the entire vlan-id range is an unnecessary

waste of system resources and is not best practice. It should be used only
when a subset of VLAN IDs (not the entire range) needs to be associated
with a logical interface. If you specify the entire range (1-4094), it has the
same result as not specifying a range; however, it consumes PFE resources
such as VLAN lookup tables entries, and so on.
The following examples illustrate this further:
[edit interfaces interface-name]
vlan-tagging;
unit number {

Copyright 2014, Juniper Networks, Inc.

969

Interfaces Fundamentals for Routing Devices

vlan-id-range 1-4094;
}
[edit interfaces interface-name]
unit 0;

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Binding VLAN IDs to Logical Interfaces

encapsulation (Logical Interface) on page 543

encapsulation (Physical Interface) on page 547

encapsulation-type (Layer 2 VPN routing instance), see the Junos OS VPNs Library for
Routing Devices

flexible-vlan-tagging on page 577

vlan-tagging on page 976

vlan-tags (Dual-Tagged Logical Interface) on page 977

vlan-id-list (Interface in Bridge Domain)

Syntax
Hierarchy Level

Release Information
Description

Options

vlan-id-list [ number number-number ];

[edit interfaces interface-name unit logical-unit-number family bridge],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family bridge]

Statement introduced in Junos OS Release 9.2.

Configure a logical interface to forward packets and learn MAC addresses within each
bridge domain configured with a VLAN ID that matches a VLAN ID specified in the list.
VLAN IDs can be entered individually using a space to separate each ID, entered as an
inclusive list separating the starting VLAN ID and ending VLAN ID with a hyphen, or a
combination of both.
number numberIndividual VLAN IDs separated by a space.
number-numberStarting VLAN ID and ending VLAN ID in an inclusive range.

Range: 1 through 4095

Required Privilege
Level
Related
Documentation

970

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring a Logical Interface for Trunk Mode

Configuring the VLAN ID List for a Trunk Interface

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vlan-id-range
Syntax
Hierarchy Level

Release Information

Description
Options

vlan-id-range vlan-idvlan-id
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 8.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Bind a range of VLAN IDs to a logical interface.
numberThe first number is the lowest VLAN ID in the range the second number is the

highest VLAN ID in the range.

Range: 1 through 4094

NOTE: Configuring vlan-id-range with the entire vlan-id range is an

unnecessary waste of system resources and is not best practice. It should be
used only when a subset of VLAN IDs (not the entire range) needs to be
associated with a logical interface. If you specify the entire range (1-4094),
it has the same result as not specifying a range; however, it consumes PFE
resources such as VLAN lookup tables entries, and so on.
The following examples illustrate this further:
[edit interfaces interface-name]
vlan-tagging;
unit number {
vlan-id-range 1-4094;
}
[edit interfaces interface-name]
unit 0;

VLAN ID 0 is reserved for tagging the priority of frames.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Binding a Range of VLAN IDs to a Logical Interface

Copyright 2014, Juniper Networks, Inc.

971

Interfaces Fundamentals for Routing Devices

vlan-ranges
Syntax

Hierarchy Level
Release Information
Description

vlan-ranges {
access-profile profile-name;
authentication {
packet-types [packet-types];
password password-string;
username-include {
circuit-type;
delimiter delimiter-character;
domain-name domain-name-string;
interface-name;
mac-address;
option-82 <circuit-id> <remote-id>;
radius-realm radius-realm-string;
user-prefix user-prefix-string;
}
}
dynamic-profile profile-name {
accept (any | dhcp-v4 | inet);
ranges (any | low-tag)(any | high-tag);
}
override;
}
[edit interfaces interface-name auto-configure]

Statement introduced in Junos OS Release 9.5.

Configure multiple VLANs. Each VLAN is assigned a VLAN ID number from the range.
The remaining statements are explained separately.

Required Privilege
Level
Related
Documentation

972

routingTo view this statement in the configuration.

routingcontrolTo add this statement to the configuration.

Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag

VLANs

Configuring Interfaces to Support Both Single and Stacked VLANs

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vlan-rewrite
Syntax
Hierarchy Level

Release Information

Description

Options

vlan-rewrite translate (200 500 | 201 501)

[edit interfaces interface-name unit number family bridge interface-mode trunk]
[edit interfaces interface-name unit number family ethernet-switching interface-mode trunk]

Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 12.3R2 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for the QFX Series.
Translates an incoming VLAN to a bridge-domain VLAN, corresponding counter translation
at egress. Supports translation of VLAN 200 to VLAN 500 and VLAN 201 to VLAN 501.
Other valid VLANs pass through without translation.
translate 200 500Translates incoming packets with VLAN 200 to 500.
translate 201 501Translates incoming packets with VLAN 201 to 501.
translate 202 502Translates incoming packets with VLAN 202 to 502.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Rewriting a VLAN Tag and Adding a New Tag

Copyright 2014, Juniper Networks, Inc.

973

Interfaces Fundamentals for Routing Devices

vlan-rule (100-Gigabit Ethernet Type 4 PIC with CFP)

Syntax
Hierarchy Level
Release Information
Description

vlan-rule (high-low | odd-even);

[edit chassis fpc slot pic slot forwarding-mode vlan-steering]

Statement introduced in Junos OS Release 10.4.

Configure the interoperation mode of the 100-Gigabit Ethernet Type 4 PIC with CFP
(PD-1CE-CFP-FPC4) when interoperating with 100 gigabit Ethernet interfaces from other
vendors.
If no VLAN rule is configured, all tagged packets are distributed to PFE0.

Options

high-lowVLAN IDs 1 through 2047 are distributed to PFE0 and VLAN IDs 2048 through

4096 are distributed to PFE1.

odd-evenOdd number VLAN IDs are distributed to PFE1 and even number VLAN IDs are

distributed to PFE0.
Required Privilege
Level
Related
Documentation

974

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP

forwarding-mode (100-Gigabit Ethernet)

vlan-steering (100-Gigabit Ethernet Type 4 PIC with CFP) on page 975

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vlan-steering (100-Gigabit Ethernet Type 4 PIC with CFP)

Syntax

Hierarchy Level
Release Information
Description

vlan-steering {
vlan-rule (high-low | odd-even);
}
[edit chassis fpc slot pic slot forwarding-mode]

Statement introduced in Junos OS Release 9.4.

Configure the 100-Gigabit Ethernet Type 4 PIC with CFP (PD-1CE-CFP-FPC4) to
interoperate with 100 gigabit Ethernet interfaces from other vendors.
The other statement is explained separately.

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP

forwarding-mode (100-Gigabit Ethernet)

sa-multicast (100-Gigabit Ethernet) on page 859

vlan-rule (100-Gigabit Ethernet Type 4 PIC with CFP) on page 974

Copyright 2014, Juniper Networks, Inc.

975

Interfaces Fundamentals for Routing Devices

vlan-tagging
Syntax
Hierarchy Level

Release Information

Description

Required Privilege
Level
Related
Documentation

976

vlan-tagging;
[edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Statement introduced in Junos OS Release 13.2 for PTX Series Routers.
Statement introduced in Junos OS Release 14.1X53-D10 for the QFX Series.
For Fast Ethernet and Gigabit Ethernet interfaces, aggregated Ethernet interfaces
configured for VPLS, and pseudowire subscriber interfaces, enable the reception and
transmission of 802.1Q VLAN-tagged frames on the interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Example: Configuring BGP Autodiscovery for LDP VPLS

Configuring Tagged Aggregated Ethernet Interfaces

Configuring Interfaces for VPLS Routing

Enabling VLAN Tagging

802.1Q VLANs Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vlan-tags (Dual-Tagged Logical Interface)

Syntax
Hierarchy Level

Release Information
Description

vlan-tags inner-list [vlan-id vlan-idvlan-id ] outer <tpid.>vlan-id;

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced in Junos OS Release 9.5.

(MX Series routers only) Binds a dual-tag logical interface to a list of VLAN IDs. Configures
the logical interface to receive and forward any dual-tag frame whose inner VLAN ID tag
matches the list of VLAN IDs you specify.

NOTE:
To create a circuit cross-connect (CCC) using VLAN-bundled dual-tag logical
interfaces on Layer 2 VPN routing instances, you must include the
encapsulation-type statement and specify the value ethernet-vlan at the one
of the following hierarchy levels:

[edit routing-instances routing-instance-name protocols l2vpn]

[edit logical-systems logical-system-name routing-instances

routing-instance-name protocols l2vpn]

For more information about the encapsulation-type configuration statement

and the Layer 2 encapsulation types ethernet and ethernet-vlan, see the Junos
OS VPNs Library for Routing Devices.

Options

inner-list [vlan-id vlan-id vlan-id-vlan-id]A list of valid VLAN ID numbers. Specify the

VLAN IDs individually by using a space to separate each ID, as an inclusive list by
separating the starting VLAN ID and ending VLAN ID with a hyphen, or as a
combination of both.
Range: 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
outer <tpid.>vlan-idAn optional Tag Protocol ID (TPID) and a valid VLAN ID.

Range: For TPID, specify a hexadecimal value in the format 0xnnnn.

Range: For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of
frames.

NOTE: Configuring inner-list with the entire vlan-id range is an unnecessary

waste of system resources and is not best practice. It should 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
PFE resources such as VLAN lookup tables entries, and so on.

Copyright 2014, Juniper Networks, Inc.

977

Interfaces Fundamentals for Routing Devices

The following examples illustrate this further:

[edit interfaces interface-name]
vlan-tagging;
unit number {
vlan-tags outer vid inner-list 1-4094;
}
[edit interfaces interface-name]
vlan-tagging;
unit number {
vlan-id vid;
}

Required Privilege
Level
Related
Documentation

978

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Binding VLAN IDs to Logical Interfaces

encapsulation (Logical Interface) on page 543

encapsulation (Physical Interface) on page 547

encapsulation-type (Layer 2 VPN routing instance), see the Junos OS VPNs Library for
Routing Devices.

flexible-vlan-tagging on page 577

vlan-id-list (Ethernet VLAN Circuit) on page 969

vlan-tagging on page 976

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vlan-tags (Stacked VLAN Tags)

Syntax
Hierarchy Level

Release Information

Description

vlan-tags inner tpid.vlan-id inner-range vid1vid2 outer tpid.vlan-id;

[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1X48 for PTX Series Packet Transport
Routers.
For Gigabit Ethernet IQ and IQE interfaces only, bind TPIDs and 802.1Q VLAN tag IDs to
a logical interface.

NOTE: The inner-range vid1vid2 option is supported on MX Series with IQE

PICs only.

Options

inner tpid.vlan-idA TPID and a valid VLAN identifier.

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-range vid1vid2For MX Series routers with Enhanced IQ (IQE) PICs only; specify

a range of VLAN IDs where vid1 is the start of the range and vid2 is the end of the
range.
Range: For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of
frames.
outer tpid.vlan-idA TPID and a valid VLAN identifier.

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. It should 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 (14094), 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:
[edit interfaces interface-name]
stacked-vlan-tagging;
unit number {
vlan-tags outer vid inner-range 1-4094;
}

Copyright 2014, Juniper Networks, Inc.

979

Interfaces Fundamentals for Routing Devices

[edit interfaces interface-name]

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

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dual VLAN Tags

Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers

stacked-vlan-tagging on page 895

vlan-tags-outer
Syntax
Hierarchy Level
Release Information
Description

Required Privilege
Level
Related
Documentation

vlan-tags-outer vlan-tag;
[edit interfaces interface-set interface-set-name interface interface-name]

Statement introduced in Junos OS Release 8.5.

The S-VLAN outer tag that belongs to a set of interfaces used to configure hierarchical
CoS schedulers.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Class of Service Feature Guide for Routing Devices

vlan-vci-tagging
Syntax
Hierarchy Level

Release Information
Description

Required Privilege
Level
Related
Documentation

980

vlan-vci-tagging;
[edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name]

Statement introduced in Junos OS Release 9.0.

Enable the ATM-to-Ethernet interworking cross-connect function on a Gigabit Ethernet,
10-Gigabit Ethernet, or aggregated Ethernet interface.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring ATM-to-Ethernet Interworking on page 262

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vpi (ATM CCC Cell-Relay Promiscuous Mode)

Syntax
Hierarchy Level
Release Information

Description

vpi vpi-identifier;
[edit interfaces at-fpc/pic/port atm-options promiscuous-mode]

Statement introduced before Junos OS Release 7.4.

Junos OS Release 12.2 for the ACX Series Universal Access routers.
For ATM interfaces, allow all VCIs in this VPI to open in ATM CCC cell-relay mode.
When you include vpi statements at the [edit interfaces interface-name atm-options
promiscuous-mode] hierarchy level, the specified VPIs open in promiscuous mode.

Options

vpi-identifierATM virtual path identifier. This is one of the VPIs that you define in the vci

statement. (For a list of hierarchy levels at which you can include the vci statement,
see vci.)
Range: 0 through 255
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM Cell-Relay Promiscuous Mode

Copyright 2014, Juniper Networks, Inc.

981

Interfaces Fundamentals for Routing Devices

vpi (Define Virtual Path)

Syntax

Hierarchy Level

vpi vpi-identifier {
maximum-vcs maximum-vcs;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
}
[edit interfaces at-fpc/pic/port atm-options]

Release Information

Statement introduced before Junos OS Release 7.4.

Description

For ATM interfaces, configure the virtual path (VP).

NOTE: Certain options apply only to specific platforms.

Options

vpi-identifierATM virtual path identifier. This is one of the VPIs that you define in the vci

statement. (For a list of hierarchy levels at which you can include the vci statement,
see vci.)
Range: 0 through 255
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation

982

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring the Maximum Number of ATM1 VCs on a VP

multipoint-destination on page 724

promiscuous-mode on page 822

vci on page 964

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

vpi (Logical Interface and Interworking)

Syntax
Hierarchy Level

Release Information

Description
Options

vpi virtual-path-identifier;
[edit interfaces at-fpc/pic/port unit logical-unit-number],
[edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number]

Statement introduced in Junos OS Release 9.0.

Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
routers.
VPI used in an ATM-to-Ethernet interworking cross-connect.
virtual-path-identifierVPI to be used.

Range: 0 through 255

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring ATM-to-Ethernet Interworking on page 262

Configuring ATM Cell-Relay Promiscuous Mode

vtmapping
Syntax
Hierarchy Level

Release Information
Description

vtmapping (itu-t | klm);

[edit interfaces interface-name sonet-options];
[edit chassis fpc number pic number]

Statement introduced before Junos OS Release 7.4.

For the Channelized STM1 IQ PIC or Channelized STM1 PIC, configure virtual tributary
mapping.
For the Channelized STM1 PIC, you configure virtual tributary mapping at the [edit chassis
fpc number pic number] hierarchy level.

Options

itu-tInternational Telephony Union standard.

klmKLM standard.

Default: klm
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Virtual Tributary Mapping of Channelized STM1 Interfaces

Configuring the Junos OS to Support Channelized STM1 Interface Virtual Tributary Mapping

Copyright 2014, Juniper Networks, Inc.

983

Interfaces Fundamentals for Routing Devices

warning
Syntax

Hierarchy Level
Release Information

Description

Options

warning low-light-warning {
(link-down | syslog);
}
[edit interfaces interface-name optics-options]

Statement introduced in Junos OS Release 10.0.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for PTX Series routers.
Specifies the action to take if the receiving optics signal is below the optics low-light
warning threshold.
link-downDrop the 10-Gigabit Ethernet link and marks link as down.
syslogWrite the optics information to the system log.

Required Privilege
Level
Related
Documentation

984

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or
Warning

optics-options on page 765

100-Gigabit Ethernet OTN Options Configuration Overview

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

watch-list
Syntax

Hierarchy Level
Release Information
Description

Options

watch-list {
[ routes ];
}
[edit interfaces dln unit logical-unit-number dialer-options]

Statement introduced before Junos OS Release 7.4.

On J Series Services Routers with ISDN interfaces, configure an ISDN list of routes to
watch. Used only for dialer watch.
routesIP prefix of a route. Specify one or more. The primary interface is considered up

if there is at least one valid route for any of the addresses in the watch list to an
interface other than the backup interface.
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Dialer Watch

Junos OS Interfaces and Routing Configuration Guide

Copyright 2014, Juniper Networks, Inc.

985

Interfaces Fundamentals for Routing Devices

wavelength
Syntax
Hierarchy Level
Release Information

Description

Options

wavelength nm;
[edit interfaces interface-name optics-options]

Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 13.2 for PTX Series routers.
For 10-Gigabit or 100-Gigabit Ethernet DWDM interfaces only, configure full C-band
ITU-Grid tunable optics.
nmWavelength value. It can be one of the following:

NOTE: All values are displayed. However, if you configure a value that is not
supported by the device, an error message is displayed and the device is not
tuned to the specified wavelength.

986

1528.381528.38 nanometers (nm), corresponds to a 50-GHz grid

1528.771528.77 nm, corresponds to 50-GHz and 100-GHz grids

1529.161529.16 nm, corresponds to a 50-GHz grid

1529.551529.55 nm, corresponds to 50-GHz and 100-GHz grids

1529.941529.94 nm, corresponds to a 50-GHz grid

1530.331530.33 nm, corresponds to 50-GHz and 100-GHz grids

1530.721530.72 nm, corresponds to a 50-GHz grid

1531.121531.12 nm, corresponds to 50-GHz and 100-GHz grids

1531.511531.51 nm, corresponds to a 50-GHz grid

1531.901531.90 nm, corresponds to 50-GHz and 100-GHz grids

1532.291532.29 nm, corresponds to a 50-GHz grid

1532.681532.68 nm, corresponds to 50-GHz and 100-GHz grids

1533.071533.07 nm, corresponds to a 50-GHz grid

1533.471533.47 nm, corresponds to 50-GHz and 100-GHz grids

1533.861533.86 nm, corresponds to a 50-GHz grid

1534.251534.25 nm, corresponds to 50-GHz and 100-GHz grids

1534.641534.64 nm, corresponds to a 50-GHz grid

1535.041535.04 nm, corresponds to 50-GHz and 100-GHz grids

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

1535.431535.43 nm, corresponds to a 50-GHz grid

1535.821535.82 nm, corresponds to 50-GHz and 100-GHz grids

1536.221536.22 nm, corresponds to a 50-GHz grid

1536.611536.61 nm, corresponds to 50-GHz and 100-GHz grids

1537.001537.00 nm, corresponds to a 50-GHz grid

1537.401537.40 nm, corresponds to 50-GHz and 100-GHz grids

1537.791537.79 nm, corresponds to a 50-GHz grid

1538.191538.19 nm, corresponds to 50-GHz and 100-GHz grids

1538.581538.58 nm, corresponds to a 50-GHz grid

1538.981538.98 nm, corresponds to 50-GHz and 100-GHz grids

1539.371539.37 nm, corresponds to a 50-GHz grid

1539.771539.77 nm, corresponds to 50-GHz and 100-GHz grids

1540.161540.16 nm, corresponds to a 50-GHz grid

1540.561540.56 nm, corresponds to 50-GHz and 100-GHz grids

1540.951540.95 nm, corresponds to a 50-GHz grid

1541.351541.35 nm, corresponds to 50-GHz and 100-GHz grids

1541.751541.75 nm, corresponds to a 50-GHz grid

1542.141542.14 nm, corresponds to 50-GHz and 100-GHz grids

1542.541542.54 nm, corresponds to a 50-GHz grid

1542.941542.94 nm, corresponds to 50-GHz and 100-GHz grids

1543.331543.33 nm, corresponds to a 50-GHz grid

1543.731543.73 nm, corresponds to 50-GHz and 100-GHz grids

1544.131544.13 nm, corresponds to a 50-GHz grid

1544.531544.53 nm, corresponds to 50-GHz and 100-GHz grids

1544.921544.92 nm, corresponds to a 50-GHz grid

1545.321545.32 nm, corresponds to 50-GHz and 100-GHz grids

1545.721545.72 nm, corresponds to a 50-GHz grid

1546.121546.12 nm, corresponds to 50-GHz and 100-GHz grids

1546.521546.52 nm, corresponds to a 50-GHz grid

1546.921546.92 nm, corresponds to 50-GHz and 100-GHz grids

1547.321547.32 nm, corresponds to a 50-GHz grid

1547.721547.72 nm, corresponds to 50-GHz and 100-GHz grids

1548.111548.11 nm, corresponds to a 50-GHz grid

Copyright 2014, Juniper Networks, Inc.

987

Interfaces Fundamentals for Routing Devices

988

1548.511548.51 nm, corresponds to 50-GHz and 100-GHz grids

1548.911548.91 nm, corresponds to a 50-GHz grid

1549.321549.32 nm, corresponds to 50-GHz and 100-GHz grids

1549.721549.72 nm, corresponds to a 50-GHz grid

1550.121550.12 nm, corresponds to 50-GHz and 100-GHz grids

1550.521550.52 nm, corresponds to a 50-GHz grid

1550.921550.92 nm, corresponds to 50-GHz and 100-GHz grids

1551.321551.32 nm, corresponds to a 50-GHz grid

1551.721551.72 nm, corresponds to 50-GHz and 100-GHz grids

1552.121552.12 nm, corresponds to a 50-GHz grid

1552.521552.52 nm, corresponds to 50-GHz and 100-GHz grids

1552.931552.93 nm, corresponds to a 50-GHz grid

1553.331554.33 nm, corresponds to 50-GHz and 100-GHz grids

1553.731554.73 nm, corresponds to a 50-GHz grid

1554.131554.13 nm, corresponds to 50-GHz and 100-GHz grids

1554.541554.54 nm, corresponds to a 50-GHz grid

1554.941554.94 nm, corresponds to 50-GHz and 100-GHz grids

1555.341555.34 nm, corresponds to a 50-GHz grid

1555.751555.75 nm, corresponds to 50-GHz and 100-GHz grids

1556.151556.15 nm, corresponds to a 50-GHz grid

1556.551556.55 nm, corresponds to 50-GHz and 100-GHz grids

1556.961556.96 nm, corresponds to a 50-GHz grid

1557.361557.36 nm, corresponds to 50-GHz and 100-GHz grids

1557.771557.77 nm, corresponds to a 50-GHz grid

1558.171558.17 nm, corresponds to 50-GHz and 100-GHz grids

1558.581558.58 nm, corresponds to a 50-GHz grid

1558.981558.98 nm, corresponds to 50-GHz and 100-GHz grids

1559.391559.39 nm, corresponds to a 50-GHz grid

1559.791559.79 nm, corresponds to 50-GHz and 100-GHz grids

1560.201560.20 nm, corresponds to a 50-GHz grid

1560.611560.61 nm, corresponds to 50-GHz and 100-GHz grids

1561.011561.01 nm, corresponds to a 50-GHz grid

1561.421561.42 nm, corresponds to 50-GHz and 100-GHz grids

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

1561.831561.83 nm, corresponds to a 50-GHz grid

1562.231562.23 nm, corresponds to 50-GHz and 100-GHz grids

1562.641562.64 nm, corresponds to a 50-GHz grid

1563.051563.05 nm, corresponds to 50-GHz and 100-GHz grids

1563.451563.45 nm, corresponds to a 50-GHz grid

1563.861563.86 nm, corresponds to 50-GHz and 100-GHz grids

1564.271564.27 nm, corresponds to a 50-GHz grid

1564.681564.68 nm, corresponds to 50-GHz and 100-GHz grids

1565.091565.09 nm, corresponds to a 50-GHz grid

1565.501565.50 nm, corresponds to 50-GHz and 100-GHz grids

1565.901565.90 nm, corresponds to a 50-GHz grid

1566.311566.31 nm, corresponds to 50-GHz and 100-GHz grids

1566.721566.72 nm, corresponds to a 50-GHz grid

1567.131567.13 nm, corresponds to 50-GHz and 100-GHz grids

1567.541567.54 nm, corresponds to a 50-GHz grid

1567.951567.95 nm, corresponds to 50-GHz and 100-GHz grids

1568.361568.36 nm, corresponds to a 50-GHz grid

1568.771568.77 nm, corresponds to 50-GHz and 100-GHz grids

Default: 1550.121550.12 nm, corresponds to 50-GHz and 100-GHz grids

Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet DWDM Interface Wavelength Overview

Configuring the 10-Gigabit or 100-Gigabit Ethernet DWDM Interface Wavelength

show interfaces diagnostics optics (Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit

Ethernet, and 100-Gigabit Ethernet)

Copyright 2014, Juniper Networks, Inc.

989

Interfaces Fundamentals for Routing Devices

west-interface
Syntax

Hierarchy Level
Release Information

Description

west-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
virtual-control-channel {
west-interface name;
east-interface name;
}
}
[edit protocols protection-group ethernet-ring ring-name]

Statement introduced in Junos OS Release 9.5.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Statement introduced in Junos OS Release 14.153-D10 for QFX Series switches.
Define one of the two interface ports for Ethernet ring protection, the other being defined
by the east-interface statement at the same hierarchy level. The interface must use the
control channel's logical interface name. The control channel is a dedicated VLAN channel
for the ring port.

NOTE: Always configure this port second, after configuring the east-interface
statement.

The statements are explained separately.

Required Privilege
Level
Related
Documentation

990

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Ethernet Ring Protection Switching Overview

Ethernet Ring Protection Using Ring Instances for Load Balancing

east-interface on page 540

ethernet-ring on page 558

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches

Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches

Configuring Ethernet Ring Protection Switching (CLI Procedure)

Copyright 2014, Juniper Networks, Inc.

Chapter 13: Configuration Statements

working-circuit
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

working-circuit group-name;
[edit interfaces interface-name sonet-options aps]

Statement introduced before Junos OS Release 7.4.

Configure the working router in an APS circuit pair.
group-nameCircuits group name.

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Configuring Basic Automatic Protect Switching

protect-circuit on page 823

yellow-differential-delay
Syntax
Hierarchy Level
Release Information
Description

Options

yellow-differential-delay milliseconds;
[edit interfaces interface-name mlfr-uni-nni-bundle-options]

Statement introduced before Junos OS Release 7.4.

For link services and voices interfaces only, configure the yellow differential delay among
bundle links to give warning when a link has a differential delay that exceeds the
configured threshold.
millisecondsYellow differential delay threshold.

Range: 1 through 2000 milliseconds

Default: 6 milliseconds
Required Privilege
Level
Related
Documentation

interfaceTo view this statement in the configuration.

interface-controlTo add this statement to the configuration.

Junos OS Services Interfaces Library for Routing Devices

action-red-differential-delay on page 410

remote on page 842

Copyright 2014, Juniper Networks, Inc.

991

Interfaces Fundamentals for Routing Devices

z0-increment
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation

992

(z0-increment | no-z0-increment);
[edit interfaces interface-name sonet-options]

Statement introduced before Junos OS Release 7.4.

Configure an incremental STM ID rather than a static one.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.

Configuring an Incrementing STM ID to Interoperate with Older Equipment in SDH Mode

sonet-options on page 884

Copyright 2014, Juniper Networks, Inc.

CHAPTER 14

Interface Operational Commands

Common Output Fields Description on page 994

Improvements to Interface Transmit Statistics Reporting on page 1001

show interfaces (10-Gigabit Ethernet)

show interfaces (ATM)

show interfaces (ATM-over-ADSL)

show interfaces (ATM-over-SHDSL)

show interfaces (Channelized DS3-to-DS0)

show interfaces (Channelized DS3-to-DS1)

show interfaces (Channelized E1 IQ)

show interfaces (Channelized E1)

show interfaces (Channelized OC12 IQ and IQE)

show interfaces (Channelized OC12)

show interfaces (Channelized OC3 IQ and IQE)

show interfaces (Channelized STM1 IQ)

show interfaces (Channelized STM1)

show interfaces (Channelized T1 IQ)

show interfaces (Channelized T3 IQ)

show interfaces (Discard)

show interfaces (Fast Ethernet)

show interfaces (Gigabit Ethernet)

show interfaces (ISDN B-Channel)

show interfaces (ISDN BRI)

show interfaces (ISDN D-channel)

show interfaces (ISDN Dialer)

show interfaces (M Series, MX Series and T Series Routers, and PTX Series Packet
Transport Routers Management and Internal Ethernet)

show interfaces (PPPoE)

show interfaces (PTX Series Packet Transport Routers)

Copyright 2014, Juniper Networks, Inc.

993

Interfaces Fundamentals for Routing Devices

show interfaces (SONET/SDH)

show interfaces (Serial)

show interfaces (T1, E1, or DS)

show interfaces (T3 or E3)

show interfaces demux0 (Demux Interfaces)

show interfaces extensive

show interfaces lsi (Label-Switched Interface)

show interfaces media

show interfaces terse

Common Output Fields Description

This chapter explains the content of the output fields, which appear in the output of most
show interfaces commands.

Damping Field
For the physical interface, the Damping field shows the setting of the following damping
parameters:

half-lifeDecay half-life. The number of seconds after which the accumulated interface

penalty counter is reduced by half if the interface remains stable.

max-suppressMaximum hold-down time. The maximum number of seconds that an

interface can be suppressed irrespective of how unstable the interface has been.

reuseReuse threshold. When the accumulated interface penalty counter falls below

this number, the interface is no longer suppressed.

suppressCutoff (suppression) threshold. When the accumulated interface penalty

counter exceeds this number, the interface is suppressed.

stateInterface damping state. If damping is enabled on an interface, it is suppressed

during interface flaps that match the configured damping parameters.

Destination Class Field

For the logical interface, the Destination class field provides the names of destination
class usage (DCU) counters per family and per class for a particular interface. The counters
display packets and bytes arriving from designated user-selected prefixes. For example:

Destination class

Packets
(packet-per-second)

gold
(
bronze
(
silver
(

994

Bytes
(bits-per-second)

1928095
889)
0
0)
0
0)

161959980
(
597762)
0
(
0)
0
(
0)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Enabled Field
For the physical interface, the Enabled field provides information about the state of the
interface, displaying one or more of the following values:

Administratively down, Physical link is DownThe interface is turned off, and the physical

link is inoperable and cannot pass packets even when it is enabled.To change the
interface state to Enabled, use the following command:
user@host# set interfaces interface enable

Manually verify the connections to bring the physical link up.

Administratively down, Physical link is UpThe interface is turned off, but the physical

link is operational and can pass packets when it is enabled.To change the interface
state to Enabled, use the following command:
user@host# set interfaces interface enable

Enabled, Physical link is DownThe interface is turned on, but the physical link is

inoperable and cannot pass packets. Manually verify the connections to bring the
physical link up.

Enabled, Physical link is UpThe interface is turned on, and the physical link is

operational and can pass packets.

Filters Field
For the logical interface, the Filters field provides the name of the firewall filters to be
evaluated when packets are received or transmitted on the interface. The format is Filters:
Input: filter-name and Filters: Output: filter-name. For example:
Filters: Input: sample-all
Filters: Output: cp-ftp

Flags Fields
The following sections provide information about flags that are specific to interfaces:

Addresses, Flags Field on page 996

Device Flags Field on page 996

Family Flags Field on page 997

Interface Flags Field on page 997

Link Flags Field on page 998

Logical Interface Flags Field on page 999

Copyright 2014, Juniper Networks, Inc.

995

Interfaces Fundamentals for Routing Devices

Addresses, Flags Field

The Addresses, Flags field provides information about the addresses configured for the
protocol family on the logical interface and displays one or more of the following values:

Dest-route-downThe routing process detected that the link was not operational and

changed the interface routes to nonforwarding status

Is-DefaultThe default address of the router used as the source address by SNMP,

ping, traceroute, and other network utilities.

Is-PreferredThe default local address for packets originating from the local router

and sent to destinations on the subnet.

Is-PrimaryThe default local address for broadcast and multicast packets originated

locally and sent out the interface.

PreferredThis address is a candidate to become the preferred address.

PrimaryThis address is a candidate to become the primary address.

Device Flags Field

The Device flags field provides information about the physical device and displays one
or more of the following values:

DownDevice has been administratively disabled.

Hear-Own-XmitDevice receives its own transmissions.

Link-Layer-DownThe link-layer protocol has failed to connect with the remote

endpoint.

LoopbackDevice is in physical loopback.

Loop-DetectedThe link layer has received frames that it sent, thereby detecting a

physical loopback.

No-CarrierOn media that support carrier recognition, no carrier is currently detected.

No-MulticastDevice does not support multicast traffic.

PresentDevice is physically present and recognized.

PromiscuousDevice is in promiscuous mode and recognizes frames addressed to all

physical addresses on the media.

QuenchTransmission on the device is quenched because the output buffer is

overflowing

Recv-All-MulticastsDevice is in multicast promiscuous mode and therefore provides

no multicast filtering.

996

RunningDevice is active and enabled.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Family Flags Field

The Family flags field provides information about the protocol family on the logical
interface and displays one or more of the following values:

DCUDestination class usage is enabled.

Dest-route-downThe software detected that the link is down and has stopped

forwarding the link's interface routes.

DownProtocol is inactive.

Is-PrimaryInterface is the primary one for the protocol.

Mac-Validate-LooseInterface is enabled with loose MAC address validation.

Mac-Validate-StrictInterface is enabled with strict MAC address validation.

Maximum labelsMaximum number of MPLS labels configured for the MPLS protocol

family on the logical interface.

MTU-Protocol-AdjustedThe effective MTU is not the configured value in the software.

No-RedirectsProtocol redirects are disabled.

PrimaryInterface can be considered for selection as the primary family address.

Protocol-DownProtocol failed to negotiate correctly.

SCU-inInterface is configured for source class usage input.

SCU-outInterface is configured for source class usage output.

send-bcast-packet-to-reInterface is configured to forward IPv4 broadcast packets

to the Routing Engine.

targeted-broadcastInterface is configured to forward IPv4 broadcast packets to the

LAN interface and the Routing Engine.

UnnumberedProtocol family is configured for unnumbered Ethernet. An unnumbered

Ethernet interface borrows an IPv4 address from another interface, which is referred
to as the donor interface.

UpProtocol is configured and operational.

uRPFUnicast Reverse Path Forwarding is enabled.

Interface Flags Field

The Interface flags field provides information about the physical interface and displays
one or more of the following values:

Admin-TestInterface is in test mode and some sanity checking, such as loop detection,

is disabled.

DisabledInterface is administratively disabled.

DownA hardware failure has occurred.

Copyright 2014, Juniper Networks, Inc.

997

Interfaces Fundamentals for Routing Devices

Hardware-DownInterface is nonfunctional or incorrectly connected.

Link-Layer-DownInterface keepalives have indicated that the link is incomplete.

No-MulticastInterface does not support multicast traffic.

No-receive No-transmitPassive monitor mode is configured on the interface.

OAM-On-SVLAN(MX Series routers with MPC/MIC interfaces only) Interface is

configured to propagate the Ethernet OAM state of a static, single-tagged service

VLAN (S-VLAN) on a Gigabit Ethernet, 10-Gigabit Ethernet, or aggregated Ethernet
interface to a dynamic or static double-tagged customer VLAN (C-VLAN) that has the
same S-VLAN (outer) tag as the S-VLAN.

Point-To-PointInterface is point-to-point.

Pop all MPLS labels from packets of depthMPLS 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:

1Takes effect for incoming packets with one label only.

2Takes effect for incoming packets with two labels only.

[ 1 2 ]Takes effect for incoming packets with either one or two labels.

PromiscuousInterface is in promiscuous mode and recognizes frames addressed to

all physical addresses.

Recv-All-MulticastsInterface is in multicast promiscuous mode and provides no

multicast filtering.

SNMP-TrapsSNMP trap notifications are enabled.

UpInterface is enabled and operational.

Link Flags Field

The Link flags field provides information about the physical link and displays one or more
of the following values:

ACFCAddress control field compression is configured. The Point-to-Point Protocol

(PPP) session negotiates the ACFC option.

Give-UpLink protocol does not continue connection attempts after repeated failures.

Loose-LCPPPP does not use the Link Control Protocol (LCP) to indicate whether the

link protocol is operational.

Loose-LMIFrame Relay does not use the Local Management Interface (LMI) to indicate

whether the link protocol is operational.

Loose-NCPPPP does not use the Network Control Protocol (NCP) to indicate whether

the device is operational.

No-KeepalivesLink protocol keepalives are disabled.

PFCProtocol field compression is configured. The PPP session negotiates the PFC

option.

998

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Logical Interface Flags Field

The Logical interface flags field provides information about the logical interface and
displays one or more of the following values:

ACFC EncapsulationAddress control field Compression (ACFC) encapsulation is

enabled (negotiated successfully with a peer).

Device-downDevice has been administratively disabled.

DisabledInterface is administratively disabled.

DownA hardware failure has occurred.

Clear-DF-BitGRE tunnel or IPsec tunnel is configured to clear the Don't Fragment

(DF) bit.

Hardware-DownInterface protocol initialization failed to complete successfully.

PFCProtocol field compression is enabled for the PPP session.

Point-To-PointInterface is point-to-point.

SNMP-TrapsSNMP trap notifications are enabled.

UpInterface is enabled and operational.

Label-Switched Interface Traffic Statistics Field

When you use the vrf-table-label statement to configure a VRF routing table, a
label-switched interface (LSI) logical interface label is created and mapped to the VRF
routing table.
Any routes present in a VRF routing table and configured with the vrf-table-label statement
are advertised with the LSI logical interface label allocated for the VRF routing table.
When packets for this VPN arrive on a core-facing interface, they are treated as if the
enclosed IP packet arrived on the LSI interface and are then forwarded and filtered based
on the correct table. For more information on the vrf-table-label statement, including a
list of supported interfaces, see the Junos VPNs Configuration Guide.
If you configure the family mpls statement at the [edit interfaces interface-name unit
logical-unit-number] hierarchy level and you also configure the vrf-table-label statement
at the [edit routing-instances routing-instance-name] hierarchy level, the output for the
show interface interface-name extensive command includes the following output fields
about the LSI traffic statistics:

Input bytesNumber of bytes entering the LSI and the current throughput rate in bits

per second (bps).

Input packetsNumber of packets entering the LSI and the current throughput rate in

packets per second (pps).

Copyright 2014, Juniper Networks, Inc.

999

Interfaces Fundamentals for Routing Devices

NOTE: If LSI interfaces are used with VPLS when no-tunnel-services is

configured or L3VPN when vrf-table-label configuration is applied inside the
routing-instance, the Input packets field associated with the core-facing
interfaces may not display the correct value. Only the Input counter is affected
because the LSI is used to receive traffic from the remote PEs. Traffic that
arrives on an LSI interface might not be counted at both the Traffic Statistics
and the Label-switched interface (LSI) traffic statistics levels.
This note applies to the following platforms:

M Series routers with -E3 FPC model numbers or configured with an

Enhanced CFEB (CFEB-E), and M120 routers

MX Series routers with DPC or ADPC only

The following example shows the LSI traffic statistics that you might see as part of the
output of the show interface interface-name extensive command:
Label-switched interface (LSI) traffic statistics:
Input bytes:
0
0 bps
Input packets:
0
0 pps

Policer Field
For the logical interface, the Policer field provides the policers that are to be evaluated
when packets are received or transmitted on the interface. The format is Policer: Input:
type-fpc/picport-in-policer, Output: type-fpc/pic/port-out-policer. For example:
Policer: Input: at-1/2/0-in-policer, Output: at-2/4/0-out-policer

Protocol Field
For the logical interface, the Protocol field indicates the protocol family or families that
are configured on the interface, displaying one or more of the following values:

aenetAggregated Ethernet. Displayed on Fast Ethernet interfaces that are part of an

aggregated Ethernet bundle.

cccCircuit cross-connect (CCC). Configured on the logical interface of CCC physical

interfaces.

inetIP version 4 (IPv4). Configured on the logical interface for IPv4 protocol traffic,

including Open Shortest Path First (OSPF), Border Gateway Protocol (BGP), Internet
Control Message Protocol (ICMP), and Internet Protocol Control Protocol (IPCP).

inet6IP version 6 (IPv6). Configured on the logical interface for IPv6 protocol traffic,

including Routing Information Protocol for IPv6 (RIPng), Intermediate

System-to-Intermediate System (IS-IS), and BGP.

isoInternational Organization for Standardization (ISO). Configured on the logical

interface for IS-IS traffic.

1000

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

mlfr-uni-nniMultilink Frame Relay (MLFR) FRF.16 user-to-network network-to-network

(UNI NNI). Configured on the logical interface for link services bundling.

mlfr-end-to-endMultilink Frame Relay end-to-end. Configured on the logical interface

for multilink bundling.

mlpppMultilink Point-to-Point Protocol (MLPPP). Configured on the logical interface

for multilink bundling.

mplsMultiprotocol Label Switching (MPLS). Configured on the logical interface for

participation in an MPLS path.

pppoe Point-to-Point Protocol over Ethernet (PPPoE). Configured on Ethernet

interfaces enabled to support multiple protocol families.

tccTranslational cross-connect (TCC). Configured on the logical interface of TCC

physical interfaces.

tnpTrivial Network Protocol (TNP). Used to communicate between the Routing Engine

and the routers packet forwarding components. The Junos OS automatically configures
this protocol family on the routers internal interfaces only.

vplsVirtual private LAN service (VPLS). Configured on the logical interface on which

you configure VPLS.

RPF Failures Field

For the logical interface, the RPF Failures field provides information about the amount
of incoming traffic (in packets and bytes) that failed a unicast reverse path forwarding
(RPF) check on a particular interface. The format is RPF Failures: Packets: xx,Bytes: yy.
For example:
RPF Failures: Packets: 0, Bytes:0

Source Class Field

For the logical interface, the Source class field provides the names of source class usage
(SCU) counters per family and per class for a particular interface. The counters display
packets and bytes arriving from designated user-selected prefixes. For example:
Packets
(packet-per-second)

Source class
gold
(
bronze
(
silver
(

1928095
889)
0
0)
0
0)

(
(
(

Bytes
(bits-per-second)
161959980
597762)
0
0)
0
0)

Improvements to Interface Transmit Statistics Reporting

The offered load on an interface can be defined as the amount of data the interface is
capable of transmitting during a given time period. The actual traffic that goes out of the
interface is the transmitted load. However, when outgoing interfaces are oversubscribed,

Copyright 2014, Juniper Networks, Inc.

1001

Interfaces Fundamentals for Routing Devices

there could be traffic drops in the schedulers attached to the outgoing interfaces. Hence,
the offered load is not always the same as the actual transmitted load because the
offered load calculation does not take into account possible packet drop or traffic loss.
On MX Series routers, the logical interface-level statistics show the offered load, which
is often different from the actual transmitted load. To address this limitation, Junos OS
introduces a new configuration option in Release 11.4 R3 and later. The new configuration
option, interface-transmit-statistics,at the [edit interface interface-name] hierarchy level,
enables you to configure Junos OS to accurately capture and report the transmitted load
on interfaces.
When the interface-transmit-statistics statement is included at the [edit interface
interface-name] hierarchy level, the following operational mode commands report the
actual transmitted load:

show interface interface-name <detail | extensive>

monitor interface interface-name

show snmp mib get objectID.ifIndex

NOTE: The interface-transmit-statistics statement is supported only on

Enhanced Queuing Dense Port Concentrators (DPCs) (Bellini) and Enhanced
IQ (IQE) (Agave) PICs of MX Series routers.

The show interface interface-name command also shows whether the

interface-transmit-statistics configuration is enabled or disabled on the interface.
Related
Documentation

1002

interface-transmit-statistics on page 635

show interfaces (Gigabit Ethernet) on page 1189

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (10-Gigabit Ethernet)

Syntax

Release Information
Description

Options

show interfaces xe-fpc/pic/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced in Junos OS Release 8.0.

(M320, M120, MX Series, and T Series routers and EX Series switches only) Display status
information about the specified 10-Gigabit Ethernet interface.
xe-fpc/pic/portDisplay standard information about the specified 10-Gigabit Ethernet

interface.
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.

Required Privilege
Level

view

List of Sample Output

show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, IQ2) on page 1018
show interfaces extensive (10-Gigabit Ethernet, WAN PHY Mode) on page 1021
show interfaces extensive (10-Gigabit Ethernet, DWDM OTN PIC) on page 1023
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional
Mode) on page 1025
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode,
Transmit-Only) on page 1025
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode,
Receive-Only) on page 1026

Output Fields

See Table 49 on page 1004 for the output fields for the show interfaces (10Gigabit Ethernet)
command.

Copyright 2014, Juniper Networks, Inc.

1003

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

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

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 loopback:

Local or Remote.

All levels

Source filtering

Source filtering status: Enabled or Disabled.

All levels

LAN-PHY mode

10-Gigabit Ethernet interface operating in Local Area Network Physical Layer

Device (LAN PHY) mode. LAN PHY allows 10-Gigabit Ethernet wide area links
to use existing Ethernet applications.

All levels

WAN-PHY mode

10-Gigabit Ethernet interface operating in Wide Area Network Physical 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.

All levels

Unidirectional

Unidirectional link mode status for 10-Gigabit Ethernet interface: Enabled or

Disabled for parent interface; Rx-only or Tx-only for child interfaces.

All levels

Flow control

Flow control status: Enabled or Disabled.

All levels

Auto-negotiation

(Gigabit Ethernet interfaces) Autonegotiation status: Enabled or Disabled.

All levels

Remote-fault

(Gigabit Ethernet interfaces) Remote fault status:

All levels

Physical Interface

OnlineAutonegotiation is manually configured as online.

OfflineAutonegotiation is manually configured as offline.

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

1004

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Link flags

Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description on page 994.

All levels

Wavelength

(10-Gigabit Ethernet dense wavelength-division multiplexing [DWDM]

interfaces) Displays the configured wavelength, in nanometers (nm).

All levels

Frequency

(10-Gigabit Ethernet DWDM interfaces only) Displays the frequency associated

with the configured wavelength, in terahertz (THz).

All levels

CoS queues

Number of CoS queues configured.

detail extensive none

Schedulers

(Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces only) Number of CoS

schedulers configured.

extensive

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

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 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).

detail extensive none

Input Rate

Input rate in bits per second (bps) and packets per second (pps). 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.

None specified

Output Rate

Output rate in bps and pps. 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.

None specified

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Egress account
overhead

Layer 2 overhead in bytes that is accounted in the interface statistics for egress
traffic.

detail extensive

Ingress account
overhead

Layer 2 overhead in bytes that is accounted in the interface statistics for ingress
traffic.

detail extensive

Copyright 2014, Juniper Networks, Inc.

detail
extensive

1005

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytesNumber 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 bytesNumber 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.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

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 49 on page 1004.
Input errors

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

Policed discardsNumber 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 incompletesNumber 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 errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

FIFO errorsNumber 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.

1006

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

CollisionsNumber 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 packetsNumber 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 errorsNumber 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 errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

Egress queues

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

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
(Egress)

CoS queue number and its associated user-configured forwarding class name.

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Copyright 2014, Juniper Networks, Inc.

detail extensive

1007

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Ingress queues

Total number of ingress queues supported on the specified interface. Displayed

on IQ2 interfaces.

extensive

Queue counters
(Ingress)

CoS queue number and its associated user-configured forwarding class name.
Displayed on IQ2 interfaces.

extensive

Active alarms and

Active defects

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Ethernet-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain amount of time, it is promoted to an alarm.
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.

NoneThere are no active defects or alarms.

LinkInterface has lost its link state, which usually means that the cable is

detail extensive none

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

OTN defects

OTN defects received on the interface.

detail extensive

OTN FEC Mode

The FECmode configured on the interface.

detail extensive

efecEnhanced forward error correction (EFEC) is configured to defect and

correct bit errors.

gfecG.709 Forward error correction (GFEC) mode is configured to detect

and correct bit errors.

OTN Rate

noneFEC mode is not configured.

OTN mode.

fixed-stuff-bytesFixed stuff bytes 11.0957 Gbps.

no-fixed-stuff-bytesNo fixed stuff bytes 11.0491 Gbps.

pass-throughEnable OTN passthrough mode.

no-pass-throughDo not enable OTN passthrough mode.

detail extensive

OTN Line Loopback

Status of the line loopback, if configured for the DWDM OTN PIC. Its value can
be: enabled or disabled.

detail extensive

OTN FEC statistics

The forward error correction (FEC) counters for the DWDM OTN PIC.

detail extensive

Corrected ErrorsThe count of corrected errors in the last second.

Corrected Error RatioThe corrected error ratio in the last 25 seconds. For

example, 1e-7 is 1 error per 10 million bits.

1008

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

OTN FEC alarms

OTN FEC excessive or degraded error alarms triggered on the interface.

detail extensive

OTN OC

OTN OTU

FEC DegradeOTU FEC Degrade defect.

FEC ExcessiveOTU FEC Excessive Error defect.

OTN OC defects triggered on the interface.

LOSOC Loss of Signal defect.

LOFOC Loss of Frame defect.

LOMOC Loss of Multiframe defect.

Wavelength LockOC Wavelength Lock defect.

OTN OTU defects detected on the interface

AISOTN AIS alarm.

BDIOTN OTU BDI alarm.

IAEOTN OTU IAE alarm.

TTIMOTN OTU TTIM alarm.

SFOTN ODU bit error rate fault alarm.

SDOTN ODU bit error rate defect alarm.

TCA-ESOTN ODU ES threshold alarm.

TCA-SESOTN ODU SES threshold alarm.

TCA-UASOTN ODU UAS threshold alarm.

TCA-BBEOTN ODU BBE threshold alarm.

BIPOTN ODU BIP threshold alarm.

BBEOTN OTU BBE threshold alarm.

ESOTN OTU ES threshold alarm.

SESOTN OTU SES threshold alarm.

UASOTN OTU UAS threshold alarm.

detail extensive

detail extensive

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

conditions from the WAN PHY or the LAN PHY device.

detail extensive

Bit errorsThe number of seconds during which at least one bit error rate

(BER) occurred while the PCS receiver is operating in normal mode.

Errored blocksThe number of seconds when at least one errored block

occurred while the PCS receiver is operating in normal mode.

Copyright 2014, Juniper Networks, Inc.

1009

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

MAC statistics

Receive and Transmit statistics reported by the PIC's MAC subsystem, including

extensive

the following:

Total octets and total packetsTotal number of octets and packets. For

Gigabit Ethernet IQ PICs, the received octets count varies by interface type.
For more information, see Table 50 on page 1018

Unicast packets, Broadcast packets, and Multicast packetsNumber of unicast,

broadcast, and multicast packets.

CRC/Align errorsTotal 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 errorNumber 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 framesNumber of MAC control frames.

MAC pause framesNumber of MAC control frames with pause operational

code.

Oversized framesNumber of frames that exceed 1518 octets.

Jabber framesNumber 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 framesTotal 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 framesNumber 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 violationsNumber of times an event caused the PHY to indicate Data

reception error or invalid data symbol error.

OTN Received
Overhead Bytes

APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58 Payload

Type: 0x08

extensive

OTN Transmitted
Overhead Bytes

APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00

Payload Type: 0x08

extensive

1010

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

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 should enter the system or be rejected.

Input packet countNumber of packets received from the MAC hardware

that the filter processed.

Input packet rejectsNumber of packets that the filter rejected because of

either the source MAC address or the destination MAC address.

Input DA rejectsNumber 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 rejectsNumber 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 countNumber of packets that the filter has given to the MAC

hardware.

Output packet pad countNumber 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 countNumber 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 filtersNumber 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:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

extensive

Subfields are:

PHY LockPhase-locked loop

PHY LightLoss of optical signal

Copyright 2014, Juniper Networks, Inc.

1011

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

WIS section

(10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information:

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

Subfields are:

WIS line

BIP-B1Bit interleaved parity for SONET section overhead

SEFSeverely errored framing

LOLLoss of light

LOFLoss of frame

ES-SErrored seconds (section)

SES-SSeverely errored seconds (section)

SEFS-SSeverely errored framing seconds (section)

(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

1012

BIP-B2Bit interleaved parity for SONET line overhead

REI-LRemote error indication (near-end line)

RDI-LRemote defect indication (near-end line)

AIS-LAlarm indication signal (near-end line)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

ES-LErrored seconds (near-end line)

SES-LSeverely errored seconds (near-end line)

UAS-LUnavailable seconds (near-end line)

ES-LFEErrored seconds (far-end line)

SES-LFESeverely errored seconds (far-end line)

UAS-LFEUnavailable seconds (far-end line)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

WIS path

(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

Subfields are:

BIP-B3Bit interleaved parity for SONET section overhead

REI-PRemote error indication

LOP-PLoss of pointer (path)

AIS-PPath alarm indication signal

RDI-PPath remote defect indication

UNEQ-PPath unequipped

PLM-PPath payload label mismatch

ES-PErrored seconds (near-end STS path)

SES-PSeverely errored seconds (near-end STS path)

UAS-PUnavailable seconds (near-end STS path)

SES-PFESeverely errored seconds (far-end STS path)

UAS-PFEUnavailable seconds (far-end STS path)

Copyright 2014, Juniper Networks, Inc.

1013

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Autonegotiation
information

Information about link autonegotiation.

extensive

Negotiation status:

IncompleteEthernet interface has the speed or link mode configured.

No autonegotiationRemote Ethernet interface has the speed or link mode

configured, or does not perform autonegotiation.

CompleteEthernet interface is connected to a device that performs

autonegotiation and the autonegotiation process is successful.

Link partner statusOK when Ethernet interface is connected to a device that

performs autonegotiation and the autonegotiation process is successful.

Link partner:

Link modeDepending on the capability of the attached Ethernet device,

either Full-duplex or Half-duplex.

Flow controlTypes 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 faultRemote fault information from the link partnerFailure

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 resolutionInformation from the link partner:

Flow controlTypes 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 faultRemote fault information. Link OK (no error detected on

receive), Offline (local interface is offline), and Link Failure (link error

detected on receive).
Received path
trace, Transmitted
path trace

(10-Gigabit Ethernet interfaces, WAN PHY mode) 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
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.

extensive

Packet Forwarding
Engine
configuration

Information about the configuration of the Packet Forwarding Engine:

extensive

1014

Destination slotFPC slot number.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Copyright 2014, Juniper Networks, Inc.

1015

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

VLAN-Tag

Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN
tag or for both the outer and inner (In) VLAN tags.

brief detail extensive

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

popThe outer VLAN tag of the incoming frame is removed.

swapThe outer VLAN tag of the incoming frame is overwritten with the user

none

specified VLAN tag information.

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

push-pushTwo VLAN tags are pushed in from the incoming frame.

swap-pushThe 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-swapBoth the inner and the outer VLAN tags of the incoming frame

are replaced by the user specified VLAN tag value.

pop-swapThe 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-popBoth 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

demux underlying interface. The output is one of the following:

Source Family Inet

Destination Family Inet

detail extensive none

Encapsulation

Encapsulation on the logical interface.

All levels

Protocol

Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description on page 994.

detail 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
the logical interface.

detail extensive none

Traffic statistics

Number and rate of bytes and packets received and transmitted on the specified
interface set.

detail extensive

Input bytes, Output bytesNumber 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 packetsNumber of packets received and transmitted

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.

extensive

Local statistics

Number and rate of bytes and packets destined to the routing device.

extensive

1016

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

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.
Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route Table

Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive none

Flags

Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description on page 994.

detail extensive

Donor interface

(Unnumbered Ethernet) Interface from which an unnumbered Ethernet interface

borrows an IPv4 address.

detail extensive none

Preferred source
address

(Unnumbered Ethernet) Secondary IPv4 address of the donor loopback interface

that acts as the preferred source address for the unnumbered Ethernet interface.

detail extensive none

Input Filters

Names of any input filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.

detail extensive

Output Filters

Names of any output filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.

detail extensive

Mac-Validate
Failures

Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail extensive none

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.

brief

Flags

Information about address flag (possible values are described in the Addresses
Flags section under Common Output Fields Description on page 994.

detail 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

Copyright 2014, Juniper Networks, Inc.

1017

Interfaces Fundamentals for Routing Devices

Table 49: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

For Gigabit Ethernet IQ PICs, traffic and MAC statistics output varies. Table 50 on page 1018
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). In Table 50 on page 1018, 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).

Table 50: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type
Interface Type

Sample Command

Byte and Octet Counts Include

Comments

Inbound physical
interface

show interfaces
ge-0/3/0 extensive

Traffic statistics:

The additional 4 bytes are

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
ge-0/3/0.50 extensive

Traffic statistics:
Input bytes: 478 bytes per packet, representing
the Layer 3 packet

Outbound physical
interface

show interfaces
ge-0/0/0 extensive

Traffic statistics:
Input bytes: 490 bytes per packet, representing
the Layer 3 packet + 12 bytes
MAC statistics:
Received octets: 478 bytes per packet,
representing the Layer 3 packet

Outbound logical
interface

show interfaces
ge-0/0/0.50 extensive

For input bytes, the

additional 12 bytes
includes 6 bytes for the
destination MAC address
+ 4 bytes for VLAN + 2
bytes for the Ethernet
type.

Traffic statistics:
Input bytes: 478 bytes per packet, representing
the Layer 3 packet

Sample Output
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, IQ2)
user@host> show interfaces xe-5/0/0 extensive
Physical interface: xe-5/0/0, Enabled, Physical link is Up
Interface index: 177, SNMP ifIndex: 99, Generation: 178
Link-level type: Ethernet, MTU: 1518, LAN-PHY mode, Speed: 10Gbps, Loopback:

1018

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

None, Source filtering: Enabled,

Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 4 maximum usable queues
Schedulers
: 1024
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:14:f6:b9:f1:f6, Hardware address: 00:14:f6:b9:f1:f6
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
6970332384
0 bps
Output bytes :
0
0 bps
Input packets:
81050506
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Ingress traffic statistics at Packet Forwarding Engine:
Input bytes :
6970299398
0 bps
Input packets:
81049992
0 pps
Drop
bytes :
0
0 bps
Drop
packets:
0
0 pps
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:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0,
MTU errors: 0, Resource errors: 0
Ingress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

81049992

81049992

1 expedited-fo

2 assured-forw

3 network-cont

Egress queues: 4 supported, 4 in use

Queue counters:
Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Active alarms : None

Active defects : None
PCS statistics
Bit errors
Errored blocks

Copyright 2014, Juniper Networks, Inc.

Seconds
0
0

1019

Interfaces Fundamentals for Routing Devices

MAC statistics:
Receive
Total octets
6970332384
Total packets
81050506
Unicast packets
81050000
Broadcast packets
506
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
81050506
Input packet rejects
506
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 5
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
%
bps
%
0 best-effort
95
950000000
95
3 network-control
5
50000000
5
Direction : Input
CoS transmit queue
0 best-effort
3 network-control

%
95
5

Bandwidth
bps
950000000
50000000

%
95
5

Transmit
0
0
0
0
0
0
0
0
0

0
0
0

Buffer Priority
usec
0
low
0
low

Limit

Buffer Priority
usec
0
low
0
low

Limit

none
none

none
none

Logical interface xe-5/0/0.0 (Index 71) (SNMP ifIndex 95) (Generation 195)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.100 ] Encapsulation: ENET2
Egress account overhead: 100
Ingress account overhead: 90
Traffic statistics:
Input bytes :
0
Output bytes :
46
Input packets:
0
Output packets:
1
IPv6 transit statistics:
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
0 bps
Output bytes :
0
0 bps

1020

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 253, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.1.1/24, Local: 192.1.1.1, Broadcast: 192.1.1.255,
Generation: 265
Protocol multiservice, MTU: Unlimited, Generation: 254, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__

show interfaces extensive (10-Gigabit Ethernet, WAN PHY Mode)

user@host> show interfaces xe-1/0/0 extensive
Physical interface: xe-1/0/0, Enabled, Physical link is Up
Interface index: 141, SNMP ifIndex: 34, Generation: 47
Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Loopback: Disabled
WAN-PHY mode
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps 16384
Link flags
: None
CoS queues
: 4 supported
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:a2:10:9d, Hardware address: 00:05:85:a2:10:9d
Last flapped
: 2005-07-07 11:22:34 PDT (3d 12:28 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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,
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
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
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
MAC statistics:
Receive
Transmit
Total octets
0
0
Total packets
0
0
Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0

Copyright 2014, Juniper Networks, Inc.

1021

Interfaces Fundamentals for Routing Devices

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
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 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
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.
Packet Forwarding Engine configuration:

1022

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Destination slot: 1
CoS information:
CoS transmit queue
0 best-effort
3 network-control

%
95
5

Bandwidth
bps
950000000
50000000

%
95
5

Buffer
bytes
0
0

Priority
low
low

Limit
none
none

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
Interface index: 143, SNMP ifIndex: 508, Generation: 208
Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, BPDU Error: None,
MAC-REWRITE 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
Wavelength
: 1550.12 nm, Frequency: 193.40 THz
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:70:2b:72, Hardware address: 00:05:85:70:2b:72
Last flapped
: 2011-04-20 15:48:54 PDT (18:39:49 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit 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:
Carrier transitions: 2, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont
Queue number:
0
1
2
3
Active alarms : LINK
Active defects : LINK
MAC statistics:
Total octets
Total packets

Copyright 2014, Juniper Networks, Inc.

Mapped forwarding classes

best-effort
expedited-forwarding
assured-forwarding
network-control

Receive
0
0

Transmit
0
0

1023

Interfaces Fundamentals for Routing Devices

Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0
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 octets
0
0
Total packets
0
0
Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0
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
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
Received DAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
Received SAPI:

1024

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

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:
APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00
Payload Type: 0x03
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 7
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Buffer Priority
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)
user@host> show interfaces xe-7/0/0 extensive
Physical interface: xe-7/0/0, Enabled, Physical link is Up
Interface index: 173, SNMP ifIndex: 212, Generation: 174
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps,
Unidirectional: Enabled,
Loopback: None, Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
...

show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode, Transmit-Only)
user@host> show interfaces xe-7/0/0tx extensive
Physical interface: xe-7/0/0-tx, Enabled, Physical link is Up
Interface index: 176, SNMP ifIndex: 137, Generation: 177
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps,
Unidirectional: Tx-Only
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:73:e4:83, Hardware address: 00:05:85:73:e4:83
Last flapped
: 2007-06-01 09:08:19 PDT (3d 02:31 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps

Copyright 2014, Juniper Networks, Inc.

1025

Interfaces Fundamentals for Routing Devices

Output bytes :
Input packets:
Output packets:

322891152287160
0
328809727380

9627472888 bps
0 pps
1225492 pps

...
Filter statistics:
Output packet count
Output packet pad count
Output packet error count
...

328810554250
0
0

Logical interface xe-7/0/0-tx.0 (Index 73) (SNMP ifIndex 138) (Generation 139)
Flags: SNMP-Traps Encapsulation: ENET2
Egress account overhead: 100
Ingress account overhead: 90
Traffic statistics:
Input bytes :
0
Output bytes :
322891152287160
Input packets:
0
Output packets:
328809727380
IPv6 transit 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 bytes :
0
0 bps
Output bytes :
322891152287160
9627472888 bps
Input packets:
0
0 pps
Output packets:
328809727380
1225492 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 147, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.11.12/24, Local: 10.11.12.13, Broadcast: 10.11.12.255,
Generation: 141
Protocol multiservice, MTU: Unlimited, Generation: 148, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__

show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode, Receive-Only)
user@host> show interfaces xe-7/0/0rx extensive
Physical interface: xe-7/0/0-rx, Enabled, Physical link is Up
Interface index: 174, SNMP ifIndex: 118, Generation: 175
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps,
Unidirectional: Rx-Only
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues

1026

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:73:e4:83, Hardware address: 00:05:85:73:e4:83
Last flapped
: 2007-06-01 09:08:22 PDT (3d 02:31 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
322857456303482
9627496104 bps
Output bytes :
0
0 bps
Input packets:
328775413751
1225495 pps
Output packets:
0
0 pps
...
Filter statistics:
Input packet count
Input packet rejects
Input DA rejects

328775015056
1
0

...
Logical interface xe-7/0/0-rx.0 (Index 72) (SNMP ifIndex 120) (Generation 138)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
322857456303482
Output bytes :
0
Input packets:
328775413751
Output packets:
0
IPv6 transit 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 bytes :
322857456303482
9627496104 bps
Output bytes :
0
0 bps
Input packets:
328775413751
1225495 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 145, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.1.1/24, Local: 192.1.1.1, Broadcast: 192.1.1.255,
Generation: 139
Protocol multiservice, MTU: Unlimited, Generation: 146, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__

Copyright 2014, Juniper Networks, Inc.

1027

Interfaces Fundamentals for Routing Devices

show interfaces (ATM)

Syntax

Release Information
Description

Options

show interfaces at-fpc/pic/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified ATM
interface.
at-fpc/pic/portDisplay standard information about the specified ATM interface.
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 the SNMP index of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (ATM, IMA Group) on page 1043

show interfaces extensive (ATM IMA Group) on page 1044
show interfaces (ATM1, SONET Mode) on page 1045
show interfaces brief (ATM1, SONET Mode) on page 1046
show interfaces detail (ATM1, SONET Mode) on page 1046
show interfaces extensive (ATM1, SONET Mode) on page 1047
show interfaces (ATM2, SDH Mode) on page 1049
show interfaces brief (ATM2, SDH Mode) on page 1050
show interfaces detail (ATM2, SDH Mode) on page 1051
show interfaces extensive (ATM2, SDH Mode) on page 1052
show interfaces (ATM2, SONET Mode) on page 1055
show interfaces brief (ATM2, SONET Mode) on page 1056
show interfaces detail (ATM2, SONET Mode) on page 1057
show interfaces extensive (ATM2, SONET Mode) on page 1059
Table 51 on page 1028 lists the output fields for the show interfaces (ATM) command.
Output fields are listed in the approximate order in which they appear.

Table 51: ATM show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical Interface

1028

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Description

Configured interface description.

All levels

Interface index

Physical interface's index number, 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

Link-level type

Encapsulation being used on the physical interface:

All levels

ATM-CCC-CELL-RELAYATM cell relay for CCC.

ATM-CCC-VC-MUXATM virtual circuit (VC) for CCC.

ATM-CISCO-NLPIDCisco-compatible ATM NLPID encapsulation.

ATM-MIPP-LLCATM MLPPP over ATM Adaptation Layer 5 (AAL5)/logical

link control (LLC).

ATM-NLPIDATM NLPID encapsulation.

ATM-PPP-LLCATM PPP over AAL5/LLC.

ATM-PPP-VC-MUXATM PPP over raw AAL5.

ATM-PVCATM permanent virtual circuits.

ATM-SNAPATM LLC/SNAP encapsulation.

ATM-TCC-SNAPATM LLC/SNAP for translational cross-connection.

ATM-TCC-VC-MUXATM VC for translational cross-connection.

ATM-VC-MUXATM VC multiplexing.

ETHER-OVER-ATM-LLCEthernet over ATM (LLC/SNAP) encapsulation.

ETHER-VPLS-OVER-ATM-LLCEthernet VPLS over ATM (bridging)

encapsulation.
MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source: Internal or External.

All levels

framing Mode

Framing mode: SONET or SDH.

All levels

Speed

Speed at which the interface is running as represented by the interface type

(for example, OC3, ADSL2+, and SHDSL(2-wire).

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

Payload scrambler

Whether payload scrambling is enabled.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Copyright 2014, Juniper Networks, Inc.

1029

Interfaces Fundamentals for Routing Devices

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

CoS queues

Number of CoS queues configured.

detail extensive none

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Current address

Ethernet MAC address for this interface for Ethernet over ATM encapsulation.

detail extensive none

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).

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Statistics for traffic on the interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface

Output packetsNumber of packets transmitted on the interface.

Input errors on the interface whose definitions are as follows:

extensive

ErrorsSum of the incoming frame aborts and frame check sequence (FCS)

errors.

DropsNumber 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 random early detection (RED)
mechanism.

Invalid VCsNumber of cells that arrived for a nonexistent VC.

Framing errorsSum of AAL5 packets that have FCS errors, reassembly

timeout errors, and length errors.

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

1030

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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,
increasing only when the cable is unplugged, the far-end system is powered
down and then up, or another problem occurs. If it increments quickly (perhaps
once every 10 seconds), the cable, the far-end system, or the PIC or PIM is
malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber of packets that remained so long in shared packet

SDRAM 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.

MTU errorsNumber of packets larger than the MTU threshold.

Resource errorsSum of transmit drops.

Egress queues

Total number of egress queues supported on the specified interface.

detail extensive

Queue counters

CoS queue number and its associated user-configured forwarding class name.

detail extensive

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

NOTE: Physical interface queue counters of ATM2 PICs displayed by the show
interfaces at-fpc/pic/port detail command show the packet forwarding stream
statistics associated with the ATM2 ports. Since multiple ports of the ATM2
PICs (except for the ATM2 dual-port OC12) share one packet forwarding stream,
the physical interface queue counters reflect the aggregate of ATM2 port
statistics.
SONET alarms
SONET defects

SONET media-specific 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 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.

Copyright 2014, Juniper Networks, Inc.

detail extensive none

1031

Interfaces Fundamentals for Routing Devices

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SONET PHY

Counts of specific SONET errors with detailed information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SONET section

PLL LockPhase-locked loop

PHY LightLoss of optical signal

Counts of specific SONET errors with detailed information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SONET line

BIP-B1Bit interleaved parity for SONET section overhead

SEFSeverely errored framing

LOLLoss of light

LOFLoss of frame

ES-SErrored seconds (section)

SES-SSeverely errored seconds (section)

SEFS-SSeverely errored framing seconds (section)

Active alarms and defects, plus counts of specific SONET errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

1032

BIP-B2Bit interleaved parity for SONET line overhead

REI-LRemote error indication (near-end line)

RDI-LRemote defect indication (near-end line)

AIS-LAlarm indication signal (near-end line)

BERR-SFBit error rate fault signal failure

BERR-SDBit error rate defect signal degradation

ES-LErrored seconds (near-end line)

SES-LSeverely errored seconds (near-end line)

UAS-LUnavailable seconds (near-end line)

ES-LFEErrored seconds (far-end line)

SES-LFESeverely errored seconds (far-end line)

UAS-LFEUnavailable seconds (far-end line)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SONET path

Active alarms and defects, plus counts of specific SONET errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

Received SONET
overhead

BIP-B3Bit interleaved parity for SONET section overhead

REI-PRemote error indication

LOP-PLoss of pointer (path)

AIS-PPath alarm indication signal

RDI-PPath remote defect indication

UNEQ-PPath unequipped

PLM-PPath payload (signal) label mismatch

ES-PErrored seconds (near-end STS path)

SES-PSeverely errored seconds (near-end STS path)

UAS-PUnavailable seconds (near-end STS path)

ES-PFEErrored seconds (far-end STS path)

SES-PFESeverely errored seconds (far-end STS path)

UAS-PFEUnavailable seconds (far-end STS path)

Values of the received and transmitted SONET overhead:

Transmitted
SONET overhead

extensive

C2Signal label. Allocated to identify the construction and content of the

STS-level SPE and for PDI-P.

F1Section user channel byte. This byte is set aside for the purposes of users.

K1 and K2These bytes are allocated for APS signaling for the protection of

the multiplex section.

J0Section 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.

S1Synchronization status. The S1 byte is located in the first STS-1 of an

STS-N.

SDH alarms
SDH defects

Z3 and Z4Allocated for future use.

SDH media-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain period, 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 light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.

Copyright 2014, Juniper Networks, Inc.

All levels

1033

Interfaces Fundamentals for Routing Devices

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SDH PHY

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SDH regenerator
section

PLL LockPhase-locked loop

PHY LightLoss of optical signal

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

SDH multiplex
section

RS-BIP824-bit BIP for multiplex section overhead (B2 bytes)

OOFOut of frame

LOSLoss of signal

LOFLoss of frame

RS-ESErrored seconds (near-end regenerator section)

RS-SESSeverely errored seconds (near-end regenerator section)

RS-SEFSSeverely errored framing seconds (regenerator section)

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

1034

MS-BIP248-bit BIP for high-order path overhead (B3 byte)

MS-FEBEFar-end block error (multiplex section)

MS-FERFFar-end remote fail (multiplex section)

MS-AISAlarm indication signal (multiplex section)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

MS-ESErrored seconds (near-end multiplex section)

MS-SESSeverely errored seconds (near-end multiplex section)

MS-UASUnavailable seconds (near-end multiplex section)

MS-ES-FEErrored seconds (far-end multiplex section)

MS-SES-FESeverely errored seconds (far-end multiplex section)

MS-UAS-FEUnavailable seconds (far-end multiplex section)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SDH path

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

Received SDH
overhead

HP-BIP88-bit BIP for regenerator section overhead (B1 byte)

HP-FEBEFar-end block error (high-order path)

HP-LOPLoss of pointer (high-order path)

HP-AISHigh-order-path alarm indication signal

HP-FERFFar-end remote fail (high-order path)

HP-UNEQUnequipped (high-order path)

HP-PLMPayload label mismatch (high-order path)

HP-ESErrored seconds (near-end high-order path)

HP-SESSeverely errored seconds (near-end high-order path)

HP-UASUnavailable seconds (near-end high-order path)

HP-ES-FEErrored seconds (far-end high-order path)

HP-SES-FESeverely errored seconds (far-end high-order path)

HP-UAS-FEUnavailable seconds (far-end high-order path)

Values of the received and transmitted SONET overhead:

Transmitted SDH
overhead

extensive

C2Signal label. This byte is allocated to identify the construction and content

of the STS-level SPE and for PDI-P.

F1Section user channel byte. This byte is set aside for the purposes of users.

K1 and K2These bytes are allocated for APS signaling for the protection of

the multiplex section.

J0Section trace. This byte is defined for STS-1 number 1 of an STS-N signal.

This bye is 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.

S1Synchronization status. The S1 byte is located in the first STS-1 of an

STS-N.

Received path trace

Transmitted path
trace

Z3 and Z4These bytes are allocated for future use.

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 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.

Copyright 2014, Juniper Networks, Inc.

extensive

1035

Interfaces Fundamentals for Routing Devices

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

ATM Status

ATM state information:

extensive

HCS StateStatus of the header check sequence. ATM uses the HCS field in

the cell header in the cell delineation process to frame ATM cell boundaries.
The HCS is an FCS-8 calculation over the first four octets of the ATM cell
header.

LOCCurrent loss of cell (LOC) delineation state. OK means that no LOC is

currently asserted.

1036

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

ATM Statistics

ATM statistics for the interface:

extensive

Uncorrectable HCS errorsNumber of cells dropped because the cell

delineation failed. These errors most likely indicate that a SONET/SDH layer
problem has occurred.

Correctable HCS errorsNumber of correctable HCS errors that occurred. The

cell delineation process can recover from these errors and locate the ATM
cell boundary, although the framing process is not quite stable. The ATM cell
is not dropped. This counter increases when the cell delineation process
changes its state from present to sync (for example, when a cable is plugged
into the interface).
The following error statistics are from the framer:

Tx cell FIFO overrunsNumber of overruns in the transmit FIFO.

Rx cell FIFO overrunsNumber of overruns in the receive FIFO.

Rx cell FIFO underrunsNumber of underruns in the receive FIFO.

Input cell countNumber of ATM cells received by the interface (not including

idle cells).

Output cell countNumber of ATM cells transmitted by the interface (including

idle cells).

Output idle cell countNumber of idle cells sent by the port. When ATM has

nothing to send, it sends idle cells to fill the time slot.

Output VC queue dropsNumber of packets dropped by a port on the PIC.

Packets are dropped because of queue limits on the VCs.

The following error statistics are from the SAR:

Input no buffersNumber of AAL5 packets dropped because no channel

blocks or buffers were available to handle them.

Input length errorsNumber of AAL5 packets dropped because their length

was incorrect. Usually, these errors occur because a cell has been corrupted
or lost, or because the length field was corrupted. They can also mean the
AAL5 length field was zero.

Input timeoutsNumber of AAL5 packets dropped because of a reassembly

timeout.

Input invalid VCsNumber of AAL5 packets dropped because the header

was unrecognized (because the VC was not correct or not configured).

Input bad CRCsNumber of AAL5 packets dropped because of frame check

sequence errors.

Input OAM cell no buffersNumber of received OAM cells or raw cells dropped

because no buffers were available to handle them.

L2 circuit out-of-sequence packets(Layer 2 AAL5 mode) Number of AAL5

packets that are out of sequential order.

Denied packets countThe number of packets dropped due to VLAN priority

deny packets or due to an error forwarding configuration that might cause a

negative frame length, that is, the stripping size is larger than the packet size.
Packet Forwarding
Engine
configuration

Information about the configuration of the Packet Forwarding Engine:

extensive

Destination slotFPC slot number.

Copyright 2014, Juniper Networks, Inc.

1037

Interfaces Fundamentals for Routing Devices

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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.

1038

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

VPI

(ATM2) Virtual path identifier information:

detail extensive none

FlagsVPI flags can be one or more of the following:

Active (virtual path is up)

OAM (operation and maintenance is enabled)

Shaping (shaping is configured)

CBR, Peak

OAM, PeriodInterval at which OAM F4 loopback cells are sent.

Up countNumber of F4 OAM cells required to consider the virtual path up;

the range is 1 through 255.

Down countNumber of F4 OAM cells required to consider the virtual path

down; the range is 1 through 255.

Total down timeTotal number of seconds the VPI has been down since it
was opened, using the format Total down time: hh:mm:ss or Never.

Last downTime of last Down transition, using the format Last down: hh:mm:ss
ago or Never.

OAM F4 cell statistics(Nonpromiscuous mode) OAM F4 statistics:

Total receivedNumber of OAM F4 cells received.

Total sentNumber of OAM F4 cells sent.

Loopback receivedNumber of OAM F4 loopback cells received.

Loopback sentNumber of OAM F4 loopback cells sent.

Last receivedTime at which the last OAM F4 cell was received.

Last sentTime at which the last OAM F4 cell was sent.

RDI receivedNumber of OAM F4 cells received with the remote defect

indication bit set.

RDI sentNumber of OAM F4 cells sent with the RDI bit set.

AIS receivedNumber of OAM F4 cells received with the alarm indication

signal bit set.

AIS sentNumber of OAM F4 cells sent with the AIS bit set.

Traffic statistics:

Input bytesNumber of bytes received on the VPI.

Output bytesNumber of bytes transmitted on the VPI.

Input packetsNumber of packets received on the VPI.

Output packetsNumber of packets transmitted on the VPI.

Logical Interface
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1039

Interfaces Fundamentals for Routing Devices

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Input packets

Number of packets received on the logical interface.

None specified

Output packets

Number of packets transmitted on the logical interface.

None specified

Encapsulation

Encapsulation on the logical interface.

All levels

Traffic statistics

Total number of bytes and packets received and transmitted on the logical
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. It takes a while (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Local statistics

Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. It takes a while (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Transit statistics

Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. It
takes a while (generally, less than 1 second) for this counter to stabilize.

detail extensive

Input packets

Number of packets received on the logical interface.

None specified

Output packets

Number of packets transmitted on the logical interface.

None specified

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.

brief

Protocol

Protocol family configured on the logical interface.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail extensive none

Destination

IP address of the remote side of the connection.

detail extensive none

1040

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Local

IP address of the logical interface.

detail extensive none

Broadcast

Broadcast address.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

VCI

Virtual circuit identifier number and information:

All levels

FlagsVCI flags:

ActiveVCI is up and in working condition.

CCC downVCI CCC is not in working condition.

ClosedVCI is closed because the user disabled the logical or physical

interface from the CLI.

ConfiguredVCI is configured.

DownVCI is not in working condition. The VCI might have alarms, defects,

F5 AIS/RDI, or no response to OAM loopback cells.

ILMIVCI is up and in working condition.

OAMOAM loopback is enabled.

MulticastVCI is a multicast VCI or DLCI.

Multipoint destinationVCI is configured as a multipoint destination.

NoneNo VCI flags.

Passive-OAMPassive OAM is enabled.

ShapingShaping is enabled.

SustainedShaping rate is set to Sustained.

UnconfiguredVCI is not configured.

Total down timeTotal number of seconds the VCI has been down, using the
format Total down time: hh:mm:ss orNever.

Last downTime of last Down transition, using the format Last down: hh:mm:ss.

EPD threshold(ATM2 only) Threshold at which a packet is dropped when

the queue size (in number of cells) exceeds the early packet-discard (EPD)
value.

Copyright 2014, Juniper Networks, Inc.

1041

Interfaces Fundamentals for Routing Devices

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

VCI (continued)

All levels

Transmit weight cells(ATM2 only) Amount of bandwidth assigned to this

queue.

ATM per-VC transmit statistics:

Tail queue packet dropsNumber of packets dropped because of bandwidth

constraints. This value indicates that packets are queued to send out at a
rate faster than allowed.

OAM F4 cell statistics(Nonpromiscuous mode) OAM F4 statistics:

Total receivedNumber of OAM F4 cells received.

Total sentNumber of OAM F4 cells sent.

Loopback receivedNumber of OAM F4 loopback cells received.

Loopback sentNumber of OAM F4 loopback cells sent.

Last receivedTime at which the last OAM F4 cell was received.

Last sentTime at which the last OAM F4 cell was sent.

RDI receivedNumber of OAM F4 cells received with the remote defect

indication bit set.

RDI sentNumber of OAM F4 cells sent with the RDI bit set.

AIS receivedNumber of OAM F4 cells received with the alarm indication

signal bit set.

AIS sentNumber of OAM F4 cells sent with the AIS bit set.

Traffic statisticsNumber and rate of bytes and packets received and

transmitted on the physical interface.

IMA group
properties

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface

Output packetsNumber of packets transmitted on the interface.

VersionThe specified IMA specification version, either IMA 1.0 or IMA 1.1.

Frame lengthThe specified frame size, which can be 32, 64, 128, or 256.

Differential delayMaximum differential delay among links in milliseconds.

SymmetryEither Common Transmit Clock or Independent Transmit Clock

detail extensive none

timing mode.

Transmit clockThe specified IMA clock mode, either common or independent.

Minimum linksThe number of minimum active links specified in both transmit

and receive directions.

TransmitThe per-PIC limit on the number of minimum active links in the

transmit direction.

ReceiveThe per-PIC limit on the number of minimum active links in the

receive direction.

Frame synchronizationThe specified IMA frame synchronization state

transition variables (Alpha, Beta, and Gamma) and their specified values.

1042

AlphaThe number of consecutive invalid ICP cells for IFSM.

BetaThe number of consecutive errored ICP cells for IFSM.

GammaThe number of consecutive valid ICP cells for IFSM.

LinksThe number of IMA links assigned to the IMA group.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 51: ATM show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

IMA group alarms

Start-up-FEFar-end group alarm status

detail extensive none

Config-AbortedNear-end configuration aborted group alarm status

Config-Aborted-FEFar-end configuration aborted group alarm status

Insufficient-LinksNear-end insufficient links group alarm status

Insufficient-Links-FEFar-end insufficient links group alarm status

Blocked-FEFar-end blocked group alarm status

GR-Timing-MismatchGroup timing mismatch alarm status

Start-up-FEFar-end group defect status

Config-AbortedNear-end configuration aborted group defect status

Config-Aborted-FEFar-end configuration aborted group defect status

Insufficient-LinksNear-end insufficient links group defect status

Insufficient-Links-FEFar-end insufficient links group defect status

Blocked-FEFar-end blocked group defect status

GR-Timing-MismatchGroup timing mismatch defect status

IMA group defects

detail extensive none

IMA Group state

Near-end and far-end group status

detail extensive none

IMA group media

IMA group media status, including seconds, count and state for the following
media parameters:

detail extensive none

FC

FC-FE

Addr-Mismatch

Running

UAS

Sample Output
show interfaces (ATM, IMA Group)
user@host> show interfaces at-1/0/0
Physical interface: at-1/0/0, Enabled, Physical link is Up
IMA group properties:
Version
: 1.1
Frame length
: 128
Differential delay
: 25 milliseconds
Symmetry
: Symmetrical Configuration and Operation
Transmit clock
: Common
Minimum links
: Transmit: 1, Receive: 1
Frame synchronization: Alpha: 2, Beta: 2, Gamma: 1
Links
: None
IMA group alarms : Start-up-FE Config-Aborted Config-Aborted-FE
Insufficient-Links Insufficient-Links-FE Blocked-FE GR-Timing-Mismatch
IMA group defects : Start-up-FE Config-Aborted Config-Aborted-FE
Insufficient-Links Insufficient-Links-FE Blocked-FE GR-Timing-Mismatch
IMA Group state:
Near end : Start up
Far end : Start up
IMA group media:
Seconds
Count State

Copyright 2014, Juniper Networks, Inc.

1043

Interfaces Fundamentals for Routing Devices

FC
FC-FE
Addr-Mismatch
Running
UAS

0
0
0
0
0

show interfaces extensive (ATM IMA Group)

user@host> show interfaces at-0/0/10 extensive
Physical interface: at-0/0/10, Enabled, Physical link is Up
Interface index: 178, SNMP ifIndex: 540, Generation: 531
Link-level type: ATM-PVC, MTU: 2048, Speed: Unspecified, Loopback: None, Payload
scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 8 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 84:18:88:c0:33:0a
Last flapped
: 2012-03-16 16:49:15 PDT (2d 07:12 ago)
Statistics last cleared: 2012-03-16 16:56:58 PDT (2d 07:05 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards:
0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors:
0, Resource errors: 0
IMA group properties:
Version
: 1.1
Frame length
: 128
Differential delay
: 25 milliseconds
Symmetry
: Symmetrical Configuration and Operation
Transmit clock
: Common
Minimum links
: Transmit: 1, Receive: 1
Frame synchronization: Alpha: 2, Beta: 2, Gamma: 1
Link #1
: t1-0/0/4
up
IMA Group alarms
: None
IMA Group defects : None
IMA Group state:
Near end : Operational
Far end : Operational
IMA group media:
Seconds
FC
FC-FE
Addr-Mismatch
Running
198306
UAS
0
ATM status:
HCS state:
Sync
LOC
:
OK

1044

Count
0
0
0

State

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0, Tx cell FIFO overruns:
0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0, Output
idle cell count: 0,
Output VC queue drops: 0, Input no buffers: 0, Input length errors: 0, Input
timeouts: 0, Input invalid VCs: 0,
Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 0
VPI 2
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/0/10.602 (Index 71) (SNMP ifIndex 1057) (Generation
17226)
Flags: Point-To-Point SNMP-Traps CCC-Down 0x0 Encapsulation:
ATM-CCC-Cell-Relay
L2 circuit cell bundle size: 1, bundle timeout: 125 usec, timeout count: 0
L2 circuit out-of-sequence count: 0, denied packets count: 0

show interfaces (ATM1, SONET Mode)

user@host> show interfaces at-1/0/0
Physical interface: at-1/0/0, Enabled, Physical link is Up
Interface index: 300, SNMP ifIndex: 194
Description: to allspice at-1/0/0
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Current address: 00:05:85:02:38:7e
Last flapped
: 2006-02-24 14:28:12 PST (6d 01:51 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SONET alarms
: None
SONET defects : None
Logical interface at-1/0/0.0 (Index 64) (SNMP ifIndex 204)
Flags: Point-To-Point SNMP-Traps Encapsulation: ATM-SNAP
Input packets : 0
Output packets: 0
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.220.24/30, Local: 192.168.220.26,
Broadcast: 192.168.220.27
Protocol iso, MTU: 4470
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0

Copyright 2014, Juniper Networks, Inc.

1045

Interfaces Fundamentals for Routing Devices

show interfaces brief (ATM1, SONET Mode)

user@host> show interfaces at-1/0/0 brief
Physical interface: at-1/0/0, Enabled, Physical link is Up
Description: to allspice at-1/0/0
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
Logical interface at-1/0/0.0
Flags: Point-To-Point SNMP-Traps Encapsulation: ATM-SNAP
inet 192.168.220.26/30
iso
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never

show interfaces detail (ATM1, SONET Mode)

user@host> show interfaces at-1/0/0 detail
Physical interface: at-1/0/0, Enabled, Physical link is Up
Interface index: 300, SNMP ifIndex: 194, Generation: 183
Description: to allspice at-1/0/0
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:02:38:7e
Last flapped
: 2006-02-24 14:28:12 PST (6d 01:55 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

SONET alarms
SONET defects

: None
: None

Logical interface at-1/0/0.0 (Index 64) (SNMP ifIndex 204) (Generation 5)

Flags: Point-To-Point SNMP-Traps Encapsulation: ATM-SNAP
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0

1046

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Output bytes :
0
Input packets:
0
Output packets:
0
Transit statistics:
Input bytes :
0
0
Output bytes :
0
0
Input packets:
0
0
Output packets:
0
0
Protocol inet, MTU: 4470, Generation: 13, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.220.24/30, Local: 192.168.220.26,
Broadcast: 192.168.220.27, Generation: 14
Protocol iso, MTU: 4470, Generation: 14, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

bps
bps
pps
pps

show interfaces extensive (ATM1, SONET Mode)

user@host> show interfaces at-1/0/0 extensive
Physical interface: at-1/0/0, Enabled, Physical link is Up
Interface index: 300, SNMP ifIndex: 194, Generation: 183
Description: to allspice at-1/0/0
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:02:38:7e
Last flapped
: 2006-02-24 14:28:12 PST (6d 01:56 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

Copyright 2014, Juniper Networks, Inc.

1047

Interfaces Fundamentals for Routing Devices

2 assured-forw

3 network-cont

SONET alarms
: None
SONET defects : None
SONET PHY:
Seconds
Count State
PLL Lock
0
0 OK
PHY Light
0
0 OK
SONET section:
BIP-B1
0
0
SEF
0
0 OK
LOS
0
0 OK
LOF
0
0 OK
ES-S
0
SES-S
0
SEFS-S
0
SONET line:
BIP-B2
0
0
REI-L
0
0
RDI-L
0
0 OK
AIS-L
0
0 OK
BERR-SF
0
0 OK
BERR-SD
0
0 OK
ES-L
0
SES-L
0
UAS-L
0
ES-LFE
0
SES-LFE
0
UAS-LFE
0
SONET path:
BIP-B3
0
0
REI-P
0
0
LOP-P
0
0 OK
AIS-P
0
0 OK
RDI-P
0
0 OK
UNEQ-P
1
1 OK
PLM-P
0
0 OK
ES-P
1
SES-P
1
UAS-P
0
ES-PFE
0
SES-PFE
0
UAS-PFE
0
Received SONET overhead:
F1
: 0x00, J0
: 0x00, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x13, C2(cmp) : 0x13, F2
: 0x00
Z3
: 0x00, Z4
: 0x00, S1(cmp) : 0x00
Transmitted SONET overhead:
F1
: 0x00, J0
: 0x01, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x13, F2
: 0x00, Z3
: 0x00
Z4
: 0x00
ATM status:
HCS state:
Sync
LOC
:
OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,
Tx cell FIFO overruns: 0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0,
Output idle cell count: 0, Output VC queue drops: 0, Input no buffers: 0,

1048

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input length errors: 0, Input timeouts: 0, Input invalid VCs: 0,

Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 1
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
%
bps
%
usec
0 best-effort
95
147744000
95
0
low
3 network-control
5
7776000
5
0
low

Limit
none
none

Logical interface at-1/0/0.0 (Index 64) (SNMP ifIndex 204) (Generation 5)

Flags: Point-To-Point SNMP-Traps Encapsulation: ATM-SNAP
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 13, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.220.24/30, Local: 192.168.220.26,
Broadcast: 192.168.220.27, Generation: 14
Protocol iso, MTU: 4470, Generation: 14, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

show interfaces (ATM2, SDH Mode)

user@host> show interfaces at-0/2/1
Physical interface: at-0/2/1, Enabled, Physical link is Up
Interface index: 154, SNMP ifIndex: 42
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Current address: 00:05:85:8f:30:3f
Last flapped
: 2006-03-24 13:29:58 PST (00:04:48 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SDH
alarms
: None

Copyright 2014, Juniper Networks, Inc.

1049

Interfaces Fundamentals for Routing Devices

SDH
defects : None
VPI 0
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input packets:
0
Output packets:
0
Logical interface at-0/2/1.0 (Index 75) (SNMP ifIndex 51)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-SNAP
Input packets : 0
Output packets: 0
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.6, Local: 10.0.12.5
Protocol iso, MTU: 4470
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
Input packets : 0
Output packets: 0
Logical interface at-0/2/1.32767 (Index 76) (SNMP ifIndex 50)
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
Input packets : 0
Output packets: 0

show interfaces brief (ATM2, SDH Mode)

user@host> show interfaces at-0/2/1 brief
Physical interface: at-0/2/1, Enabled, Physical link is Up
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SDH mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
Logical interface at-0/2/1.0
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-SNAP
inet 10.0.12.5
--> 10.0.12.6
iso
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
Logical interface at-0/2/1.32767
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0

1050

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces detail (ATM2, SDH Mode)

user@host> show interfaces at-0/2/1 detail
Physical interface: at-0/2/1, Enabled, Physical link is Up
Interface index: 154, SNMP ifIndex: 42, Generation: 40
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:8f:30:3f
Last flapped
: 2006-03-24 13:29:58 PST (00:05:10 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0
Output bytes :
0
0
Input packets:
0
0
Output packets:
0
0
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets

bps
bps
pps
pps
Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

SDH
alarms
: None
SDH
defects : None
VPI 0
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/2/1.0 (Index 75) (SNMP ifIndex 51) (Generation 25)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-SNAP
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 62, Route table: 0
Flags: None

Copyright 2014, Juniper Networks, Inc.

1051

Interfaces Fundamentals for Routing Devices

Addresses, Flags: Is-Preferred Is-Primary

Destination: 10.0.12.6, Local: 10.0.12.5, Broadcast: Unspecified,
Generation: 58
Protocol iso, MTU: 4470, Generation: 63, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/2/1.32767 (Index 76) (SNMP ifIndex 50) (Generation 26)
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
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
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

show interfaces extensive (ATM2, SDH Mode)

user@host> show interfaces at-0/2/1 extensive
Physical interface: at-0/2/1, Enabled, Physical link is Up
Interface index: 154, SNMP ifIndex: 42, Generation: 40
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:8f:30:3f
Last flapped
: 2006-03-24 13:29:58 PST (00:06:49 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

1052

0
0
0
0

bps
bps
pps
pps

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

SDH
alarms
: None
SDH
defects : None
SDH PHY:
Seconds
PLL Lock
0
PHY Light
1
SDH regenerator section:
RS-BIP8
2
OOF
2
LOS
2
LOF
2
RS-ES
4
RS-SES
3
RS-SEFS
2
SDH multiplex section:
MS-BIP24
2
MS-FEBE
1
MS-FERF
2
MS-AIS
2
BERR-SF
0
BERR-SD
0
MS-ES
4
MS-SES
2
MS-UAS
0
MS-ES-FE
3
MS-SES-FE
2
MS-UAS-FE
0
SDH path:
HP-BIP8
1
HP-FEBE
1
HP-LOP
0
HP-AIS
2
HP-FERF
3
HP-UNEQ
1
HP-PLM
2
HP-ES
4
HP-SES
3
HP-UAS
0
HP-ES-FE
3
HP-SES-FE
3
HP-UAS-FE
0
Received SDH overhead:

Copyright 2014, Juniper Networks, Inc.

Count
0
1

State
OK
OK

8828
2
1
1

OK
OK
OK

771
17476
1
1
0
0

OK
OK
OK
OK

6
251
0
1
2
1
1

OK
OK
OK
OK
OK

1053

Interfaces Fundamentals for Routing Devices

F1
: 0x00, J0
: 0x00, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x13, C2(cmp) : 0x13, F2
: 0x00
Z3
: 0x00, Z4
: 0x00, S1(cmp) : 0x00
Transmitted SDH overhead:
F1
: 0x00, J0
: 0x01, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x13, F2
: 0x00, Z3
: 0x00
Z4
: 0x00
ATM status:
HCS state:
Sync
LOC
:
OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,
Tx cell FIFO overruns: 0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0,
Output idle cell count: 0, Output VC queue drops: 0, Input no buffers: 0,
Input length errors: 0, Input timeouts: 0, Input invalid VCs: 0,
Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 0
VPI 0
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/2/1.0 (Index 75) (SNMP ifIndex 51) (Generation 25)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-SNAP
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 62, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.6, Local: 10.0.12.5, Broadcast: Unspecified,
Generation: 58
Protocol iso, MTU: 4470, Generation: 63, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0

1054

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input packets:
0
Output packets:
0
Logical interface at-0/2/1.32767 (Index 76) (SNMP ifIndex 50) (Generation 26)
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
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
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

show interfaces (ATM2, SONET Mode)

user@host> show interfaces at-0/3/1
Physical interface: at-0/3/1, Enabled, Physical link is Up
Interface index: 139, SNMP ifIndex: 67
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Current address: 00:14:f6:22:58:5e
Last flapped
: 2006-03-13 17:46:36 PST (16:01:12 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SONET alarms
: None
SONET defects : None
VPI 0
Flags: Active, OAM, Shaping
CBR, Peak: 50kbps
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
OAM F4 cell statistics:
Total received: 4, Total sent: 4
Loopback received: 4, Loopback sent: 4
RDI received: 0, RDI sent: 0
AIS received: 0
Traffic statistics:
Input packets:
4
Output packets:
30
VPI 10
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input packets:
0

Copyright 2014, Juniper Networks, Inc.

1055

Interfaces Fundamentals for Routing Devices

Output packets:
0
Logical interface at-0/3/1.0 (Index 78) (SNMP ifIndex 77)
Flags: Point-To-Point Copy-PLP-To-CLP SNMP-Traps 0x4000
Encapsulation: ATM-SNAP
Input packets : 0
Output packets: 0
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.59.5, Local: 10.0.59.6
Protocol iso, MTU: 4470
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 10
Input packets : 0
Output packets: 0
Logical interface at-0/3/1.32767 (Index 79) (SNMP ifIndex 76)
Flags: Point-To-Multipoint Copy-PLP-To-CLP No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Input packets : 4
Output packets: 30
VCI 0.16
Flags: Active, ILMI
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
Input packets : 0
Output packets: 26
VCI 0.4
Flags: Active, OAM
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
Input packets : 4
Output packets: 4
OAM F4 cell statistics:
Total received: 4, Total sent: 4
Loopback received: 4, Loopback sent: 4
RDI received: 0, RDI sent: 0
AIS received: 0, AIS sent: 0

show interfaces brief (ATM2, SONET Mode)

user@host> show interfaces at-0/3/1 brief
Physical interface: at-0/3/1, Enabled, Physical link is Up
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
Logical interface at-0/3/1.0
Flags: Point-To-Point Copy-PLP-To-CLP SNMP-Traps 0x4000
Encapsulation: ATM-SNAP
inet 10.0.59.6
--> 10.0.59.5
iso
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 10

1056

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Logical interface at-0/3/1.32767

Flags: Point-To-Multipoint Copy-PLP-To-CLP No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
VCI 0.16
Flags: Active, ILMI
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
VCI 0.4
Flags: Active, OAM
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0

show interfaces detail (ATM2, SONET Mode)

user@host> show interfaces at-0/3/1 detail
Physical interface: at-0/3/1, Enabled, Physical link is Up
Interface index: 139, SNMP ifIndex: 67, Generation: 22
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:14:f6:22:58:5e
Last flapped
: 2006-03-13 17:46:36 PST (16:02:39 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
312
0 bps
Output bytes :
2952
0 bps
Input packets:
6
0 pps
Output packets:
50
0 pps
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

44

44

1 expedited-fo

2 assured-forw

3 network-cont

SONET alarms
: None
SONET defects : None
VPI 0
Flags: Active, OAM, Shaping
CBR, Peak: 50kbps
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
OAM F4 cell statistics:
Total received: 6, Total sent: 6
Loopback received: 6, Loopback sent: 6
Last received: 00:00:29, Last sent: 00:00:29
RDI received: 0, RDI sent: 0
AIS received: 0
Traffic statistics:
Input bytes :
312
Output bytes :
2952
Input packets:
6
Output packets:
50

Copyright 2014, Juniper Networks, Inc.

1057

Interfaces Fundamentals for Routing Devices

VPI 10
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/3/1.0 (Index 78) (SNMP ifIndex 77) (Generation 20)
Flags: Point-To-Point Copy-PLP-To-CLP SNMP-Traps 0x4000
Encapsulation: ATM-SNAP
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 38, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.59.5, Local: 10.0.59.6, Broadcast: Unspecified,
Generation: 44
Protocol iso, MTU: 4470, Generation: 39, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 10
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/3/1.32767 (Index 79) (SNMP ifIndex 76) (Generation 21)
Flags: Point-To-Multipoint Copy-PLP-To-CLP No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Traffic statistics:
Input bytes :
360
Output bytes :
3302
Input packets:
6
Output packets:
50
Local statistics:
Input bytes :
360
Output bytes :
3302
Input packets:
6
Output packets:
50
VCI 0.16
Flags: Active, ILMI
Total down time: 0 sec, Last down: Never

1058

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

EPD threshold: 0, Transmit weight cells: 0

ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
2640
Input packets:
0
Output packets:
44
VCI 0.4
Flags: Active, OAM
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
312
Output bytes :
312
Input packets:
6
Output packets:
6
OAM F4 cell statistics:
Total received: 6, Total sent: 6
Loopback received: 6, Loopback sent: 6
Last received: 00:00:29, Last sent: 00:00:29
RDI received: 0, RDI sent: 0
AIS received: 0, AIS sent: 0

show interfaces extensive (ATM2, SONET Mode)

user@host> show interfaces at-0/3/1 extensive
Physical interface: at-0/3/1, Enabled, Physical link is Up
Interface index: 139, SNMP ifIndex: 67, Generation: 22
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:14:f6:22:58:5e
Last flapped
: 2006-03-13 17:46:36 PST (16:04:12 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
520
0 bps
Output bytes :
4240
0 bps
Input packets:
10
0 pps
Output packets:
72
0 pps
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets
0 best-effort
1 expedited-fo

Copyright 2014, Juniper Networks, Inc.

Transmitted packets

Dropped packets

62

62

1059

Interfaces Fundamentals for Routing Devices

2 assured-forw

3 network-cont

10

10

SONET alarms
: None
SONET defects : None
SONET PHY:
Seconds
Count State
PLL Lock
0
0 OK
PHY Light
0
0 OK
SONET section:
BIP-B1
0
0
SEF
0
0 OK
LOS
0
0 OK
LOF
0
0 OK
ES-S
0
SES-S
0
SEFS-S
0
SONET line:
BIP-B2
0
0
REI-L
0
0
RDI-L
0
0 OK
AIS-L
0
0 OK
BERR-SF
0
0 OK
BERR-SD
0
0 OK
ES-L
0
SES-L
0
UAS-L
0
ES-LFE
0
SES-LFE
0
UAS-LFE
0
SONET path:
BIP-B3
0
0
REI-P
0
0
LOP-P
0
0 OK
AIS-P
0
0 OK
RDI-P
0
0 OK
UNEQ-P
1
1 OK
PLM-P
0
0 OK
ES-P
1
SES-P
1
UAS-P
0
ES-PFE
0
SES-PFE
0
UAS-PFE
0
Received SONET overhead:
F1
: 0x00, J0
: 0x00, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x13, C2(cmp) : 0x13, F2
: 0x00
Z3
: 0x00, Z4
: 0x00, S1(cmp) : 0x00
Transmitted SONET overhead:
F1
: 0x00, J0
: 0x01, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x13, F2
: 0x00, Z3
: 0x00
Z4
: 0x00
ATM status:
HCS state:
Sync
LOC
:
OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,
Tx cell FIFO overruns: 0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0,
Output idle cell count: 0, Output VC queue drops: 0, Input no buffers: 0,

1060

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input length errors: 0, Input timeouts: 0, Input invalid VCs: 0,

Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 0
VPI 0
Flags: Active, OAM, Shaping
CBR, Peak: 50kbps
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
OAM F4 cell statistics:
Total received: 10, Total sent: 10
Loopback received: 10, Loopback sent: 10
Last received: 00:00:02, Last sent: 00:00:02
RDI received: 0, RDI sent: 0
AIS received: 0
Traffic statistics:
Input bytes :
520
Output bytes :
4240
Input packets:
10
Output packets:
72
VPI 10
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/3/1.0 (Index 78) (SNMP ifIndex 77) (Generation 20)
Flags: Point-To-Point Copy-PLP-To-CLP SNMP-Traps 0x4000
Encapsulation: ATM-SNAP
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 38, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.59.5, Local: 10.0.59.6, Broadcast: Unspecified,
Generation: 44
Protocol iso, MTU: 4470, Generation: 39, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 10
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:

Copyright 2014, Juniper Networks, Inc.

1061

Interfaces Fundamentals for Routing Devices

Input
Output
Input
Output

bytes :
bytes :
packets:
packets:

0
0
0
0

Logical interface at-0/3/1.32767 (Index 79) (SNMP ifIndex 76) (Generation 21)
Flags: Point-To-Multipoint Copy-PLP-To-CLP No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Traffic statistics:
Input bytes :
660
Output bytes :
5473
Input packets:
11
Output packets:
83
Local statistics:
Input bytes :
660
Output bytes :
5473
Input packets:
11
Output packets:
83
VCI 0.16
Flags: Active, ILMI
Total down time: 0 sec, Last down: Never
EPD threshold: 0, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
4320
Input packets:
0
Output packets:
72
VCI 0.4
Flags: Active, OAM
OAM, Period 30 sec, Up count: 10, Down count: 10
Total down time: 0 sec, Last down: Never
EPD threshold: 2129, Transmit weight cells: 0
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
572
Output bytes :
572
Input packets:
11
Output packets:
11
OAM F4 cell statistics:
Total received: 11, Total sent: 11
Loopback received: 11, Loopback sent: 11
Last received: 00:00:18, Last sent: 00:00:18
RDI received: 0, RDI sent: 0
AIS received: 0, AIS sent: 0

1062

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (ATM-over-ADSL)

Syntax

Release Information
Description

Options

show interfaces at-pim/0/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(J Series routers) Display status information about the specified ATM-over-asynchronous
DSL (ADSL) interface.
at-pim/0/portDisplay standard information about the specified ADSL interface.
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 the SNMP index of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (ATM-over-ADSL) on page 1065

show interfaces brief (ATM-over-ADSL) on page 1065
show interfaces detail (ATM-over-ADSL) on page 1066
show interfaces extensive (ATM-over-ADSL) on page 1068
Table 52 on page 1063 lists only output fields that are specific to the show interfaces
(ATM-over-ADSL) command. For information about all other output fields, see Table
92 under the show interfaces (ATM) command.

Table 52: ATM-over-ADSL show interfaces Output Fields

Field Name

Field Description

Level of Output

ADSL alarms

Number and type of ADSL alarms. See ADSL media for details.

detail extensive none

ADSL defects

Number and type of ADSL defects. See ADSL media for details.

detail extensive none

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1063

Interfaces Fundamentals for Routing Devices

Table 52: ATM-over-ADSL show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

ADSL status

Operational information for ATM-over-ADSL interfaces.

detail extensive none

Modem statusStatus of the modem: Down, Training, or Showtime.

DSL modeConfigured line type of the digital subscriber line: adsl2plus,

ansi-dmt, auto, itu-dmt, or itu-dmt-bis.

Last fail codeReason for failure: ATU-C not detected, incompatible line
condition, protocol error, message error, spurious ATU detected, forced silence,
unselectable operation mode, or none.

SubfunctionSpecified analog front-end chip and discrete front.

Seconds in showtimeNumber of seconds the ADSL connection is in

showtime.
ADSL media

Information about ADSL media-specific defects that can prevent the interface
from passing packets. The following information is displayed for each defect:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. A state other than OK indicates a problem.

extensive

The possible defects are as follows:

ADSL Statistics

LOFLoss of frame.

LOSLoss of signal.

LOMLoss of multiframe.

LOPLoss of pointer.

LOCDILoss of cell delineation for an interleaved channel.

LOCDNILoss of cell delineation for a noninterleaved channel.

Information about the ADSL terminal unit-remote (ATU-R) at the far end of
the connection and the ADSL terminal unit-central office (ATU-C) at the near
end:

Attenuation (dB)Attenuation in decibels.

Capacity used (%)Percentage of capacity used.

Noise margin (dB)Maximum extraneous signal allowed without causing the

detail extensive

output to deviate from an allowable level, in decibels.

Output power (dBm)Amount of power used by the ATM-over-ADSL

interface.

Bit rate (kbps)Speed of data transfer on the ATM-over-ADSL interface, in

kilobits per second.

1064

CRCNumber of cyclic redundancy check errors.

FECNumber of forward error corrections.

HECNumber of header error checksums.

Received cellsNumber of cells received through the interface.

Transmitted cellsNumber of cells sent through the interface.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Sample Output
show interfaces (ATM-over-ADSL)
user@host> show interfaces at-5/0/0
Physical interface: at-5/0/0, Enabled, Physical link is Down
Interface index: 149, SNMP ifIndex: 68
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, ADSL mode,
Speed: ADSL2+, Loopback: None
Device flags
: Present Running Down
Link flags
: None
CoS queues
: 8 supported, 8 in use
Current address: 00:05:85:c3:85:84
Last flapped
: 2005-12-19 15:36:02 PST (12w0d 18:33 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
ADSL alarms
: None
ADSL defects : None
ADSL status:
Modem status : Training
DSL mode
: Adsl2plus
Annex A
Last fail code: ATU-C not detected
Subfunction
: 0x00
Seconds in showtime : 0
Logical interface at-5/0/0.0 (Index 70) (SNMP ifIndex 71)
Flags: Device-Down Point-To-Multipoint SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
Input packets : 0
Output packets: 0
Protocol inet, MTU: 1500
Flags: None
VCI 0.128
Flags: Active, Multicast
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0
Logical interface at-5/0/0.32767 (Index 71) (SNMP ifIndex 70)
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0

show interfaces brief (ATM-over-ADSL)

user@host> show interfaces at-5/0/0 brief
Physical interface: at-5/0/0, Enabled, Physical link is Down
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, ADSL mode,
Speed: ADSL2+, Loopback: None
Device flags
: Present Running Down
Link flags
: None
Logical interface at-5/0/0.0
Flags: Device-Down Point-To-Multipoint SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
inet

Copyright 2014, Juniper Networks, Inc.

1065

Interfaces Fundamentals for Routing Devices

VCI 0.128
Flags: Active, Multicast
Total down time: 0 sec, Last down: Never
Logical interface at-5/0/0.32767
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never

show interfaces detail (ATM-over-ADSL)

user@host> show interfaces at-5/0/0 detail
Physical interface: at-5/0/0, Enabled, Physical link is Down
Interface index: 149, SNMP ifIndex: 68, Generation: 30
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, ADSL mode,
Speed: ADSL2+, Loopback: None
Device flags
: Present Running Down
Link flags
: None
CoS queues
: 8 supported, 8 in use
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:c3:85:84
Last flapped
: 2005-12-19 15:36:02 PST (12w0d 18:33 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

4 be-class

5 ef-class

6 af-class

ADSL alarms
: None
ADSL defects : None
ADSL status:
Modem status : Training
DSL mode
: Adsl2plus
Annex A
Last fail code: ATU-C not detected
Subfunction
: 0x00
Seconds in showtime : 0
ADSL Statistics:
Attenuation (dB)
:
Capacity used (%)
:
Noise margin (dB)
:
Output power (dBm)
:

ATU-R
0.0
0
0.0
0.0

Interleave

1066

ATU-C
0.0
0
0.0
0.0
Fast

Interleave

Fast

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Bit rate (kbps)

CRC
FEC
HEC
Received cells
Transmitted cells

:
:
:
:
:
:

0
0
0
0
0
0

0
0
0
0
0
0

0
0
0
0

0
0
0
0

Logical interface at-5/0/0.0 (Index 70) (SNMP ifIndex 71) (Generation 8)

Flags: Device-Down Point-To-Multipoint SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 1500, Generation: 12, Route table: 0
Flags: None
VCI 0.128
Flags: Active, Multicast
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-5/0/0.32767 (Index 71) (SNMP ifIndex 70) (Generation 9)
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
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
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

Copyright 2014, Juniper Networks, Inc.

1067

Interfaces Fundamentals for Routing Devices

show interfaces extensive (ATM-over-ADSL)

user@host> show interfaces at-5/0/0 extensive
Physical interface: at-5/0/0, Enabled, Physical link is Down
Interface index: 149, SNMP ifIndex: 68, Generation: 30
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, ADSL mode,
Speed: ADSL2+, Loopback: None
Device flags
: Present Running Down
Link flags
: None
CoS queues
: 8 supported, 8 in use
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:c3:85:84
Last flapped
: 2005-12-19 15:36:02 PST (12w0d 18:34 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
Resource
errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

4 be-class

5 ef-class

6 af-class

ADSL alarms
: None
ADSL defects : None
ADSL media:
Seconds
Count State
LOF
0
0 OK
LOS
0
0 OK
LOM
0
0 OK
LOP
0
0 OK
LOCDI
0
0 OK
LOCDNI
0
0 OK
ADSL status:
Modem status : Training
DSL mode
: Adsl2plus
Annex A
Last fail code: ATU-C not detected
Subfunction
: 0x00
Seconds in showtime : 0
ADSL Statistics:
ATU-R
Attenuation (dB)
:
0.0
Capacity used (%)
:
0
Noise margin (dB)
:
0.0

1068

ATU-C
0.0
0
0.0

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Output power (dBm)

0.0

0.0

Interleave
Fast Interleave
Fast
Bit rate (kbps)
:
0
0
0
0
CRC
:
0
0
0
0
FEC
:
0
0
0
0
HEC
:
0
0
0
0
Received cells
:
0
0
Transmitted cells :
0
0
ATM status:
HCS state:
Hunt
LOC
:
OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,
Tx cell FIFO overruns: 0, Rx cell FIFO overruns: 0,
Rx cell FIFO underruns: 0, Input cell count: 0, Output cell count: 0,
Output idle cell count: 0, Output VC queue drops: 0, Input no buffers: 0,
Input length errors: 0, Input timeouts: 0, Input invalid VCs: 0,
Input bad CRCs: 0, Input OAM cell no buffers: 0
Packet Forwarding Engine configuration:
Destination slot: 5
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
Limit
%
bps
%
usec
0 best-effort
95
7600000
95
0
low
none
3 network-control
5
400000
5
0
low
none
Logical interface at-5/0/0.0 (Index 70) (SNMP ifIndex 71) (Generation 8)
Flags: Device-Down Point-To-Multipoint SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 1500, Generation: 12, Route table: 0
Flags: None
VCI 0.128
Flags: Active, Multicast
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-5/0/0.32767 (Index 71) (SNMP ifIndex 70) (Generation 9)
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Traffic statistics:

Copyright 2014, Juniper Networks, Inc.

1069

Interfaces Fundamentals for Routing Devices

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
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

1070

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (ATM-over-SHDSL)

Syntax

Release Information
Description

Options

show interfaces at-pim/0/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(J Series routers) Display status information about the specified ATM-over-symmetric
high-speed DSL (SHDSL) interface.
at-pim/0/portDisplay standard information about the specified SHDSL interface
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 the SNMP index of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (ATM-over-SHDSL) on page 1073

show interfaces brief (ATM-over-SHDSL) on page 1074
show interfaces detail (ATM-over-SHDSL) on page 1074
show interfaces extensive (ATM-over-SHDSL) on page 1076
Table 53 on page 1072 lists only output fields that are specific to the show interfaces
(ATM-over-SHDSL) command. For information about all other output fields, see Table
92 under the show interfaces (ATM) command.

Copyright 2014, Juniper Networks, Inc.

1071

Interfaces Fundamentals for Routing Devices

Table 53: ATM-over-SHDSL show interfaces Output Fields

Field Name

Field Description

Level of Output

SHDSL alarms

Number and type of SHDSL alarms. See "SHDSL media" for details.

detail extensive none

SHDSL defects

Number and type of SHDSL defects. See "SHDSL media" for details.

detail extensive none

SHDSL media

Information about the SHDSL media-specific defects that can prevent the
interface from passing packets. The following information is displayed for each
defect:

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. A state other than OK indicates a problem.

The possible defects are as follows:

LOSDLoss of signal was detected at the remote application interface.

LOSWLoss of sync word. A message ID was sent.

ESErrored seconds. One or more cyclic redundancy check (CRC) anomalies

were detected.

SESSeverely errored seconds. At least 50 CRC anomalies were detected.

UASUnavailable seconds. An interval occurred during which one or more

LOSW defects were detected.

SHDSL status

Operational information for ATM-over-SHDSL interfaces.

detail extensive none

Line terminationSHDLS transceiver unit- remote (STU-R) (Only customer

premises equipment is supported.)

AnnexEither Annex A or Annex B. Annex A is supported in North America,

and Annex B is supported in Europe.

Line modeSHDSL mode configured on the G.SHDLS Physical Interface

Module (PIM), either 2-wire or 4-wire.

Modem statusData.

Bit rate (kbps)Speed of data transfer on the ATM-over-G.SHDSL interface,

in kilobits per second.

Last fail modeCode for the last interface failure.

Framer modeFramer mode of the underlying interface: ATM.

Dying gaspAbility of a J Series router that has lost power to send a message

informing the attached DSL access multiplexer (DSLAM) that it is about to

go offline: Enabled or Disabled.

1072

Framer sync statusFramer synchronization status: In sync or Out of sync

(OOS).

Chipset versionVersion number of the chipset on the interface.

Firmware versionVersion number of the firmware on the interface.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 53: ATM-over-SHDSL show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SHDSL statistics

Loop Attentuation (dB)Attenuation in decibels.

detail extensive

Transmit power (dBm)Power of the transmitting interface.

Receiver gain (db)Power increase of the receiving interface, in decibels.

SNR sampling (dB)Signal-to-noise ratio at a receiver point, in decibels.

CRC errorsNumber of cyclic redundancy check errors.

SEGA errorsNumber of segment anomaly errors. A regenerator operating

on a segment received corrupted data.

LOSW errorsNumber of loss of signal defect errors. Three or more

consecutively received frames contained one or more errors in the framing

bits.

Received cellsNumber of cells received through the interface.

Transmitted cellsNumber of cells sent through the interface.

HEC errorsNumber of header error checksum errors.

Cell DropNumber of dropped cells on the interface.

Sample Output
show interfaces (ATM-over-SHDSL)
user@host> show interfaces at-4/0/0
Physical interface: at-4/0/0, Enabled, Physical link is Down
Interface index: 141, SNMP ifIndex: 41
Link-level type: Ethernet-over-ATM, MTU: 4482, Clocking: Internal,
Speed: SHDSL(2-wire), Loopback: None
Device flags
: Present Running Down
Link flags
: None
CoS queues
: 8 supported, 8 in use
Current address: 00:05:85:c2:44:60
Last flapped
: 2006-03-21 15:07:11 PST (2w0d 00:59 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SHDSL alarms
: LOSD
SHDSL defects : LOSD
SHDSL status:
Line termination
: STU-R
Annex
: Unknown
Line mode
: 2-wire
Modem status
: Training
Bit rate (kbps)
: 0
Last fail mode
: No failure (0x00)
Framer mode
: ATM
Dying gasp
: Enabled
Framer sync status
: Out of sync
Chipset version
: 00
Firmware version
: R3.0.1
Logical interface at-4/0/0.0 (Index 68) (SNMP ifIndex 44)
Flags: Device-Down Point-To-Point SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
Input packets : 0
Output packets: 0
Protocol inet, MTU: 1500

Copyright 2014, Juniper Networks, Inc.

1073

Interfaces Fundamentals for Routing Devices

Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0
Logical interface at-4/0/0.32767 (Index 69) (SNMP ifIndex 43)
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0

show interfaces brief (ATM-over-SHDSL)

user@host> show interfaces at-4/0/0 brief
Physical interface: at-4/0/0, Enabled, Physical link is Down
Link-level type: Ethernet-over-ATM, MTU: 4482, Clocking: Internal,
Speed: SHDSL(2-wire), Loopback: None
Device flags
: Present Running Down
Link flags
: None
Logical interface at-4/0/0.0
Flags: Device-Down Point-To-Point SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
inet
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
Logical interface at-4/0/0.32767
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never

show interfaces detail (ATM-over-SHDSL)

user@host> show interfaces at-4/0/0 detail
Physical interface: at-4/0/0, Enabled, Physical link is Down
Interface index: 141, SNMP ifIndex: 41, Generation: 22
Link-level type: Ethernet-over-ATM, MTU: 4482, Clocking: Internal,
Speed: SHDSL(2-wire), Loopback: None
Device flags
: Present Running Down
Link flags
: None
CoS queues
: 8 supported, 8 in use
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:c2:44:60
Last flapped
: 2006-03-21 15:07:11 PST (2w0d 01:00 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Queue counters:
Queued packets Transmitted packets
Dropped packets

1074

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

SHDSL alarms
: LOSD
SHDSL defects : LOSD
SHDSL status:
Line termination
Annex
Line mode
Modem status
Bit rate (kbps)
Last fail mode
Framer mode
Dying gasp
Framer sync status
Chipset version
Firmware version
SHDSL statistics:
Loop attenuation (dB)
Transmit power (dBm)
Receiver gain (dB)
CRC errors
SEGA errors
LOSW errors
Received cells
Transmitted cells
HEC errors
Cell drop

:
:
:
:
:
:
:
:
:
:
:

STU-R
Unknown
2-wire
Training
0
No failure (0x00)
ATM
Enabled
Out of sync
00
R3.0.1

:
:
:
:
:
:
:
:
:
:

2.3
0.0
20.412
0
0
0
0
0
0
0

Logical interface at-4/0/0.0 (Index 68) (SNMP ifIndex 44) (Generation 8)

Flags: Device-Down Point-To-Point SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 1500, Generation: 11, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:

Copyright 2014, Juniper Networks, Inc.

1075

Interfaces Fundamentals for Routing Devices

Input
Output
Input
Output

bytes :
bytes :
packets:
packets:

0
0
0
0

Logical interface at-4/0/0.32767 (Index 69) (SNMP ifIndex 43) (Generation 9)

Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
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
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

show interfaces extensive (ATM-over-SHDSL)

user@host> show interfaces at-4/0/0 extensive
Physical interface: at-4/0/0, Enabled, Physical link is Down
Interface index: 141, SNMP ifIndex: 41, Generation: 22
Link-level type: Ethernet-over-ATM, MTU: 4482, Clocking: Internal,
Speed: SHDSL(2-wire), Loopback: None
Device flags
: Present Running Down
Link flags
: None
CoS queues
: 8 supported, 8 in use
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:c2:44:60
Last flapped
: 2006-03-21 15:07:11 PST (2w0d 01:02 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Queue counters:
0 best-effort

1076

Queued packets

Transmitted packets

Dropped packets

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

1 expedited-fo

2 assured-forw

3 network-cont

SHDSL alarms
: LOSD
SHDSL defects : LOSD
SHDSL media:
Seconds
Count State
LOSD
1228405
1 Defect Active
LOSW
0
0 OK
ES
0
SES
0
UAS
1228402
SHDSL status:
Line termination
: STU-R
Annex
: Unknown
Line mode
: 2-wire
Modem status
: Training
Bit rate (kbps)
: 0
Last fail mode
: No failure (0x00)
Framer mode
: ATM
Dying gasp
: Enabled
Framer sync status
: Out of sync
Chipset version
: 00
Firmware version
: R3.0.1
SHDSL statistics:
Loop attenuation (dB) : 2.3
Transmit power (dBm)
: 0.0
Receiver gain (dB)
: 20.412
CRC errors
: 0
SEGA errors
: 0
LOSW errors
: 0
Received cells
: 0
Transmitted cells
: 0
HEC errors
: 0
Cell drop
: 0
Packet Forwarding Engine configuration:
Destination slot: 4
CoS information:
CoS transmit queue
Bandwidth
Buffer
%
bps
%
usec
0 best-effort
95
2196400
95
0
3 network-control
5
115600
5
0

Priority

Limit

low
low

none
none

Logical interface at-4/0/0.0 (Index 68) (SNMP ifIndex 44) (Generation 8)

Flags: Device-Down Point-To-Point SNMP-Traps 0x4000
Encapsulation: Ether-over-ATM-LLC
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 bytes :
0
0 bps
Output bytes :
0
0 bps

Copyright 2014, Juniper Networks, Inc.

1077

Interfaces Fundamentals for Routing Devices

Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 1500, Generation: 11, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-4/0/0.32767 (Index 69) (SNMP ifIndex 43) (Generation 9)
Flags: Device-Down Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
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
VCI 0.4
Flags: Active
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

1078

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Channelized DS3-to-DS0)

Syntax

Release Information
Description

Options

show interfaces ds-fpc/pic/port:t1channel:ds0channel

<brief | detail | extensive>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
channelized DS3-to-DS0 interface.
ds-fpc/pic/port:t1channel:ds0channelDisplay standard information about the specified

channelized DS3-to-DS0 interface.

brief | detail | extensive(Optional) Display the specified level of output interface.
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.

Required Privilege
Level
List of Sample Output
Output Fields

view

show interfaces extensive (Channelized DS3-to-DS0) on page 1087

Table 54 on page 1079 lists the output fields for the show interfaces (all Channelized DS3
interfaces) command. Output fields are listed in the approximate order in which they
appear.

Table 54: Channelized DS3 show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, 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

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1079

Interfaces Fundamentals for Routing Devices

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source. It can be Internal or External.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Mode

Whether C-bit parity mode or M13 mode is enabled.

All levels

Framing

Physical layer framing format used on the link. It can be ESF or SF. The default
is ESF.

All levels

Parent

(Channelized IQ interfaces only) Name and interface index of the interface to

which a particular child interface belongs. None indicates that this interface is
the top level.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Keepalive settings

(PPP and HDLC) Configured settings for keepalives.

detail extensive none

1080

interval secondsThe time in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

down-count numberThe number of keepalive packets that 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 numberThe number of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Keepalive statistics

(PPP and HDLC) Information about keepalive packets.

detail extensive none

InputNumber of keepalive packets received by PPP.

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the format hh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

LMI settings

LMI

LCP state

NCP state

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

(Frame Relay) Settings for Local Management Interface (LMI) can be either
ANSI LMI settings or ITU LMI settings. ANSI LMI settings is the default. The format
is (ANSI or ITU) LMI settings: value, value, value...xx seconds, where value can be:

n391dteDTE full status polling interval (1255)

n392dceDCE error threshold (110)

n392dteDTE error threshold (110)

n393dceDCE monitored event count (110)

n393dteDTE monitored event count (110)

t391dteDTE polling timer (530 seconds)

t392dceDCE polling verification timer (530 seconds)

(Frame Relay) LMI packet statistics:

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
seen hh:mm:ss ago).

(PPP) Link Control Protocol state.

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not-configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

(PPP) Network Control Protocol state.

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not-configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

Copyright 2014, Juniper Networks, Inc.

detail extensive none

detail extensive none

detail extensive none

detail extensive none

1081

Interfaces Fundamentals for Routing Devices

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CHAP state

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

detail extensive none

Chap-Chal-receivedChallenge was received but response not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

CHAP has not yet moved into theSuccess state. (Most likely with RADIUS

authentication).

Chap-Resp-sentResponse was sent for the challenge received.

ClosedCHAP authentication is incomplete.

FailureCHAP authentication failed.

Not-configuredCHAP is not configured on the interface.

SuccessCHAP authentication was successful.

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 hh:mm:ss ago). For
example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).

detail extensive none

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytes, Output bytesNumber of bytes received and transmitted on the

interface.

Input packets, Output packetsNumber of packets received and transmitted

on the interface.

1082

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Input errors

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber 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 errorsNumber of packets received with an invalid frame checksum

(FCS).

GiantsNumber of frames received that are larger than the giant threshold.

RuntsNumber of frames received that are smaller than the runt threshold.

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsCounter increments when the software could not find a

valid logical interface for an incoming frame.

L2 mismatch timeoutsCount of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

SRAM errorsNumber of hardware errors that occurred in the static RAM

(SRAM) on the PIC. If the value in this field increments, the PIC is
malfunctioning.

HS link CRC errorsCount of errors on the high-speed links between the ASICs

responsible for handling the router interfaces.

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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.

Copyright 2014, Juniper Networks, Inc.

1083

Interfaces Fundamentals for Routing Devices

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

DS1 alarms

Media-specific defects that can render the interface unable to pass 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.

detail extensive none

DS1 defects

T1 media

LOSLoss of signal.

LOFLoss of frame.

AISAlarm indication signal.

YLWYellow alarm. Indicates errors at the remote site receiver.

Counts of T1 media-specific errors.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

The T1 media-specific error types can be:

1084

SEFSeverely errored framing

BEEBit error event

AISAlarm indication signal

LOFLoss of frame

LOSLoss of signal

YELLOWErrors at the remote site receiver

BPVBipolar violation

EXZExcessive zeros

LCVLine code violation

PCVPulse code violation

CSCarrier state

LESLine error seconds

ESErrored seconds

SEFSSeverely errored framing seconds (section)

SESSeverely errored seconds

BESBit error seconds

UASUnavailable seconds

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

DS3 media

Counts of T3 media-specific errors. For detailed definitions of the T3 (DS-3)

error events (BPV, EXZ, LCV, PCV, and CCV) and performance parameters (LES,
PES, PSES, CES, CSES, SEFS, and UAS), see RFC 2496.

extensive

HDLC configuration

Interface transmit
queues

PLL LockPhase-locked loop out of lock

ReframingFrame alignment recovery time

AISAlarm indication signal

LOFLoss of frame

LOSLoss of signal

IDLEIdle code detected

YELLOWRemote defect indication

BPVBipolar violation

EXZExcessive zeros

LCVLine code violation

PCVPulse code violation

CCVC-bit coding violation

LESLine error seconds

PESP-bit errored seconds

PSESP-bit errored seconds (section)

CESC-bit errored seconds

CSESC-bit severely errored seconds

SEFSSeverely errored framing seconds

UASUnavailable seconds

Information about the HDLC configuration.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

TimeslotsConfigured time slots for the interface.

Byte encodingByte encoding used: Nx64K or Nx56K.

Data inversionHDLC data inversion setting: Enabled or Disabled

Name of the transmit queues and their associated statistics for each DS1 channel
on the Channelized DS3-to-DS1 PIC.

B/WQueue bandwidth as a percentage of the total interface bandwidth.

WRRWeighted round-robin (in percent).

PacketsNumber of packets transmitted.

BytesNumber of bytes transmitted.

DropsNumber of packets dropped.

ErrorsNumber of packet errors.

Copyright 2014, Juniper Networks, Inc.

extensive

extensive

1085

Interfaces Fundamentals for Routing Devices

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

DS1 or DS3 BERT

configuration

BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.

detail extensive none

BERT time periodConfigured total time period that the BERT is to run.

ElapsedActual time elapsed since the start of the BERT (in seconds).

Induced error rateConfigured rate at which the bit errors are induced in the

BERT pattern.

Packet Forwarding
Engine
configuration

CoS information

AlgorithmType of algorithm selected for the BERT.

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

Information about the CoS queue for the physical interface.

extensive

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface; values are described in the Logical
Interface Flags section under Common Output Fields Description on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Bandwidth

Bandwidth configured on the interface.

All levels

Protocol

Protocol family configured on the logical interface, such as iso, inet6, mpls.

detail extensive none

1086

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 54: Channelized DS3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive none

Redundant Link

(LSQ redundancy) Backup link for Link Services IQ redundancy.

detail extensive none

Sample Output
show interfaces extensive (Channelized DS3-to-DS0)
user@host> show interfaces ds-0/0/0:0:0 extensive
Physical interface: ds-0/0/0:0:0, Enabled, Physical link is Up
Interface index: 174, SNMP ifIndex: 4298, Generation: 177
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: 640kbps, FCS: 16,
Mode: C/Bit parity, Framing: ESF
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 280 (last seen 00:00:09 ago)
Output: 286 (last sent 00:00:00 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Not-configured
Last flapped
: 2002-05-23 17:53:29 PDT (00:46:46 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
6814
16 bps
Output bytes :
28840
72 bps
Input packets:
568
0 pps

Copyright 2014, Juniper Networks, Inc.

1087

Interfaces Fundamentals for Routing Devices

Output packets:
893
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 39, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 2, L2 mismatch timeouts: 0,
HS link CRC errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0
DS1
alarms
: None
DS3
alarms
: None
DS1
defects : None
DS3
defects : None
T1 media:
Seconds
Count State
SEF
0
0 OK
BEE
5
1 OK
AIS
0
0 OK
LOF
0
0 OK
LOS
0
0 OK
YELLOW
17
1 OK
BPV
0
0
EXZ
0
0
LCV
5
27765
PCV
0
0
CS
0
0
LES
0
ES
0
SES
5
SEFS
10
BES
0
UAS
0
DS3 media:
Seconds
Count State
PLL Lock
0
0 OK
Reframing
0
0 OK
AIS
0
0 OK
LOF
0
0 OK
LOS
0
0 OK
IDLE
0
0 OK
YELLOW
0
0 OK
BPV
1
65535
EXZ
1
65535
LCV
2
131070
PCV
1
1825
CCV
0
0
LES
1
PES
1
PSES
1
CES
0
CSES
0
SEFS
0
UAS
0
Interface transmit queues:
B/W WRR
Packets
Bytes
Drops
Errors
Queue0
95
95
0
0
0
0
Queue1
5
5
893
28840
0
0
HDLC configuration:
Giant threshold: 1514, Runt threshold: 3
Timeslots
: 1-10
Byte encoding: Nx64K, Data inversion: Disabled
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^15 - 1, Induced error rate: 10e-0
DS1 BERT configuration:

1088

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

BERT time period: 10 seconds, Elapsed: 0 seconds

Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 2 (0x01)
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
Limit
%
bps
%
usec
0 best-effort
95
608000 95
0
low
none
3 network-control
5
32000
5
0
low
none
Logical interface ds-0/0/0:0:0.0 (Index 5) (SNMP ifIndex 4299)
(Generation 943)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 949, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 18.18.18.1, Local: 18.18.18.2, Broadcast: Unspecified,
Generation: 1849

Copyright 2014, Juniper Networks, Inc.

1089

Interfaces Fundamentals for Routing Devices

show interfaces (Channelized DS3-to-DS1)

Syntax

Release Information
Description

Options

show interfaces t1-fpc/pic/port:t1channel

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
channelized DS3-to-DS1 interface.
t1-fpc/pic/port:t1channelDisplay standard information about the specified channelized

DS3-to-DS1 interface.
brief | detail | extensive | terse(Optional) Display brief interface information.
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.

Required Privilege
Level
List of Sample Output
Output Fields

view

show interfaces extensive (channelized DS3-to-DS1) on page 1090

See the output field table for the show interfaces (Channelized DS3-to-DS0) command.

Sample Output
show interfaces extensive (channelized DS3-to-DS1)
user@host> show interfaces t1-0/0/0:0 extensive
Physical interface: t1-0/0/0:0, Enabled, Physical link is Up
Interface index: 210, SNMP ifIndex: 14, Generation: 2977
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: 640kbps,
Loopback: None, FCS: 16, Mode: C/Bit parity, Framing: ESF
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 30 (last seen 00:00:05 ago)
Output: 29 (last sent 00:00:00 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured

1090

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

CHAP state: Not-configured

Last flapped
: 2002-05-23 17:30:12 PDT (17:29:43 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
944
16 bps
Output bytes :
1162
16 bps
Input packets:
66
0 pps
Output packets:
82
0 pps
Input errors:
Errors: 1, Drops: 0, Framing errors: 1, Policed discards: 8,
L3 incompletes: 0, L2 channel errors: 1, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0
DS1
alarms
: None
DS3
alarms
: None
DS1
defects : None
DS3
defects : None
T1 media:
Seconds
Count State
SEF
0
0 OK
BEE
11
5 OK
AIS
28
1 OK
LOF
27
1 OK
LOS
0
0 OK
YELLOW
23
1 OK
BPV
0
0
EXZ
0
0
LCV
11
20574
PCV
0
0
CS
0
0
LES
28
ES
28
SES
39
SEFS
50
BES
0
UAS
0
DS3 media:
Seconds
Count State
PLL Lock
0
0 OK
Reframing
0
0 OK
AIS
0
0 OK
LOF
1
1 OK
LOS
1
1 OK
IDLE
0
0 OK
YELLOW
0
0 OK
BPV
2
131070
EXZ
3
49910
LCV
5
180980
PCV
2
327
CCV
12
264558
LES
3
PES
3
PSES
2
CES
13
CSES
13
SEFS
1
UAS
35
Interface transmit queues:
B/W WRR
Packets
Bytes
Drops
Errors
Queue0
95
95
0
0
0
0
Queue1
5
5
82
1162
0
0
HDLC configuration:

Copyright 2014, Juniper Networks, Inc.

1091

Interfaces Fundamentals for Routing Devices

Giant threshold: 1514, Runt threshold: 3

Timeslots
: 1-10
Line encoding: B8ZS, Byte encoding: Nx64K, Data inversion: Disabled
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^15 - 1, Induced error rate: 10e-0
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 2 (0x00) CoS information:
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95
608000 95
0
low
none
3 network-control
5
32000
5
0
low
none
Logical interface t1-0/0/0:0.0 (Index 11) (SNMP ifIndex 23) (Generation 497)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Bandwidth: 0
Protocol inet, MTU: 1500, Generation: 576, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 21.21.21.2, Local: 21.21.21.1, Broadcast: Unspecified,
Generation: 977

1092

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Channelized E1 IQ)

Syntax

Release Information
Description

Options

show interfaces (ce1-fpc/pic/port | type-fpc/pic/port<:channel>)

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
channelized E1 IQ interface.
type-fpc/pic/port:<channel>Interface type with optional corresponding channel levels.

For the physical channelized E1 IQ interface, type is ce. For the clear channel, type
is e1. At the first level of channelization, type is ds.
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.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (Channelized E1 IQ) (Physical) on page 1093

show interfaces extensive (Channelized E1 IQ Multilink PPP Encapsulation) on page 1094
show interfaces extensive (Channelized E1 IQ MLFR Encapsulation) on page 1095
show interfaces detail (Clear Channel E1) on page 1096
For information about output fields, see the output field table for the show interfaces
(Channelized E1) command. Output fields are listed in the approximate order in which
they appear.

Sample Output
show interfaces (Channelized E1 IQ) (Physical)
user@host> show interfaces ce1-1/2/3
Physical interface: ce1-1/2/3, Enabled, Physical link is Up
Interface index: 18, SNMP ifIndex: 1128
Link-level type: Frame-relay, Controller, MTU: 1504, Clocking: Internal,
E1, Loopback: None, FCS: 16, Framing: G704, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds

Copyright 2014, Juniper Networks, Inc.

Speed:

1093

Interfaces Fundamentals for Routing Devices

LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)

DTE statistics:
Enquiries sent
: 43186
Full enquiries sent
: 8515
Enquiry responses received
: 43185
Full enquiry responses received
: 8515
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 0
Nonmatching DCE-end DLCIs:
2
Last flapped
: 2002-10-04 17:52:51 PDT (00:32:57 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
DS1
alarms
: None
DS1
defects : None

show interfaces extensive (Channelized E1 IQ Multilink PPP Encapsulation)

user@host> show interfaces ds-0/3/4:1 extensive
Physical interface: ds-0/3/4:1, Enabled, Physical link is Up
Interface index: 151, SNMP ifIndex: 63, Generation: 34
Link-level type: Multilink-PPP, MTU: 1518, Clocking: Internal, Speed: 64kbps,
Loopback: None, FCS: 16,
Parent: ce1-0/3/4 Interface index 150
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Down
CHAP state: Closed
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: Never
Statistics last cleared: 2005-12-21 10:32:15 PST (1w0d 03:10 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
6070570
224 bps
Input packets:
0
0 pps
Output packets:
209330
0 pps
Input errors:
Errors: 3, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, HS link CRC errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
HDLC configuration:
Giant threshold: 1528, Runt threshold: 2
Timeslots
: 1
Data inversion: Disabled, Idle cycle flag: flags, Start end flag: shared

1094

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

DS0 BERT configuration:

BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 4 (0x00)
Logical interface ds-0/3/4:1.0 (Index 74) (SNMP ifIndex 64) (Generation 13)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol mlppp, Multilink bundle: ls-0/1/0.0, MTU: 1514, Generation: 24,
Route table: 0

show interfaces extensive (Channelized E1 IQ MLFR Encapsulation)

user@host> show interfaces ds-0/3/4:5 extensive
Physical interface: ds-0/3/4:5, Enabled, Physical link is Up
Interface index: 155, SNMP ifIndex: 72, Generation: 38
Link-level type: Multilink-FR, MTU: 1518, Clocking: Internal, Speed: 64kbps,
Loopback: None, FCS: 16,
Parent: ce1-0/3/4 Interface index 150
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: No-Keepalives DCE
Hold-times
: Up 0 ms, Down 0 ms
ANSI LMI settings: n392dce 3, n393dce 4, t392dce 15 seconds
LMI statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
DTE statistics:
Enquiries sent
: 0
Full enquiries sent
: 0
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 0
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2005-12-21 09:59:01 PST (1w0d 03:44 ago)
Statistics last cleared: 2005-12-21 10:32:15 PST (1w0d 03:10 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Input errors:
Errors: 3, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, HS link CRC errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
HDLC configuration:
Giant threshold: 1528, Runt threshold: 2
Timeslots
: 5
Data inversion: Disabled, Idle cycle flag: flags, Start end flag: shared

Copyright 2014, Juniper Networks, Inc.

1095

Interfaces Fundamentals for Routing Devices

DS0 BERT configuration:

BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 4 (0x01)
Logical interface ds-0/3/4:5.0 (Index 78) (SNMP ifIndex 73) (Generation 17)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol mlfr, Multilink bundle: ls-0/1/0.1, MTU: 1514, Generation: 28, Route
table: 0
DLCI 10
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :1 Inactive DLCI :0

show interfaces detail (Clear Channel E1)

user@host> show interfaces e1-1/2/6 detail
Physical interface: e1-1/2/6, Enabled, Physical link is Up
Interface index: 89, SNMP ifIndex: 1278, Generation: 341
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: E1, Loopback:None,
...
Logical interface e1-1/2/6.0 (Index 52) (SNMP ifIndex 1279) (Generation 169)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Bandwidth: 0
...

1096

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Channelized E1)

Syntax

Release Information

show interfaces ds-fpc/pic/port:ds0channel

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Description

(M Series and T Series routers only) Display status information the specified channelized
E1 interface.

Options

ds-fpc/pic/port:ds0channelDisplay standard information about the specified channelized

E1 interface.
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.

Required Privilege
Level
List of Sample Output
Output Fields

view

show interfaces extensive (Channelized E1) on page 1106

Table 55 on page 1097 lists the output fields for the show interfaces (Channelized E1 and
Channelized E1 IQ) command. Output fields are listed in the approximate order in which
they appear.

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, 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

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1097

Interfaces Fundamentals for Routing Devices

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source: Internal or External.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Framing

Physical layer framing format used on the link. It can be G704, G704-NO-CRC4,
or Unframed. The default is G704.

All levels

Parent

(Channelized E1 IQ interfaces only) Name and interface index of the interface

to which a particular child interface belongs. None indicates that this interface
is the top level.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Keepalive settings

(PPP and HDLC) Configured settings for keepalives.

detail extensive none

1098

Interval secondsTime in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

Down-count numberNumber 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 numberNumber 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.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

Keepalive statistics

(PPP and HDLC) Information about keepalive packets.

detail extensive none

InputNumber of keepalive packets received by PPP.

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the format hh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

LMI settings

LMI

DTE statistics

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

(Frame Relay) Settings for link management can be either ANSI LMI settings
or ITU LMI settings. ANSI LMI settings is the default. The format is (ANSI or ITU)
LMI settings: value, value... xx seconds, where value can be:

n391dteDTE full status polling interval (1255)

n392dceDCE error threshold (110)

n392dteDTE error threshold (110)

n393dceDCE monitored event count (110)

n393dteDTE monitored event count (110)

t391dteDTE polling timer (530 seconds)

t392dceDCE polling verification timer (530 seconds)

(Frame Relay) Statistics about the link management.

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago)

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
sent hh:mm:ss ago).

(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data circuit-terminating equipment (DCE):

Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.

Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.

Enquiry responses receivedNumber of enquiry responses received by the

detail extensive none

detail extensive none

detail extensive none

DTE from the DCE.

Full enquiry responses receivedNumber of full enquiry responses sent from

the DTE to the DCE.

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

Enquiries receivedNumber of enquiries received by the DCE from the DTE.

Full enquiries receivedNumber of full enquiries received by the DCE from

detail extensive none

the DTE.

Enquiry responses sentNumber of enquiry responses sent from the DCE to

the DTE.

Full enquiry responses sentNumber of full enquiry responses sent from the

DCE to the DTE.

Copyright 2014, Juniper Networks, Inc.

1099

Interfaces Fundamentals for Routing Devices

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

detail extensive none

Unknown messages receivedNumber of received packets that do not fall

into any category.

Asynchronous updates receivedNumber of link status peer changes received.

Out-of-sequence packets receivedNumber of packets for which the sequence

of the packets received is different from the expected sequence.

Keepalive responses timedoutNumber of keepalive responses that timed

out when no LMI packet was reported forn392dte or n393dce intervals. (See
LMI settings).

Nonmatching
DCE-end DLCIs

(Frame Relay, displayed only from the DTE) Number of DLCIs configured from
the DCE.

detail extensive none

LCP state

(PPP) Link Control Protocol state.

detail extensive none

CHAP state

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not-configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

Chap-Chal-receivedChallenge was received but response not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

detail extensive none

CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)

Chap-Resp-sentResponse was sent for the challenge received.

ClosedCHAP authentication is incomplete.

FailureCHAP authentication failed.

Not-configuredCHAP is not configured on the interface.

SuccessCHAP authentication was successful.

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).

detail extensive none

CoS Queues

Number of CoS queues configured.

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

1100

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

Traffic statistics

Number of bytes and packets received and transmitted on the physical interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

GiantsNumber of frames received that are larger than the giant threshold.

RuntsNumber of frames received that are smaller than the runt threshold.

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

HS link CRC errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

1101

Interfaces Fundamentals for Routing Devices

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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), then either the cable, the far-end system,
or the PIC is malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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.

DS1 alarms
DS1 defects

1102

MTU errorsNumber of packets larger than the MTU threshold.

Resource errorsSum of transmit drops.

E1 media-specific defects that can render the interface unable to pass 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.
The following lists all possible alarms and defects. For complete explanations
of most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.

LOSLoss of signal.

LOFLoss of frame.

AISAlarm indication signal.

YLWYellow alarm. Indicates errors at the remote site receiver.

detail extensive none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

E1 media

Active alarms and defects, plus counts of specific E1 errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

The E1 media-specific error types can be:

HDLC configuration

Interface transmit
queues

SEFSeverely errored framing

BEEBit error

AISAlarm indication signal

LOFLoss of frame

LOSLoss of signal

YELLOWErrors at the remote site receiver

BPVBipolar violation

EXZExcessive zeros

LCVLine code violation

PCVPulse code violation

CSCarrier state

FEBEFar-end block error

LESLine error seconds

ESErrored seconds

BESBursty errored seconds

SESSeverely errored seconds

SEFSSeverely errored framing seconds

UASUnavailable seconds

Information about the HDLC configuration.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

TimeslotsConfigured time slots for the interface.

Line encodingHDB3Line encoding used.

Names of the transmit queues and their associated statistics for each DS0
channel on the Channelized E1 to DS0 PIC.

B/WQueue bandwidth as a percentage of the total interface bandwidth.

WRRWeighted round robin (in percent).

PacketsNumber of packets transmitted.

BytesNumber of bytes transmitted.

DropsNumber of packets dropped.

ErrorsNumber of packet errors.

Copyright 2014, Juniper Networks, Inc.

extensive

extensive

1103

Interfaces Fundamentals for Routing Devices

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

DSx BERT
configuration

BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.

detail extensive none

BERT time periodConfigured total time period that the BERT is to run.

ElapsedActual time elapsed since the start of the BERT (in seconds).

Induced error rateConfigured rate at which the bit errors are induced in the

BERT pattern.

Packet Forwarding
Engine
configuration

CoS information

AlgorithmType of algorithm selected for the BERT.

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

Information about the CoS queue for the physical interface.

extensive

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Input packets

Number of packets received on the logical interface.

None specified

1104

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 55: Channelized E1 and Channelized E1 IQ show interfaces Output Fields (continued)
Field Name

Field Description

Level of Output

Output packets

Number of packets transmitted on the logical interface.

None specified

Traffic statistics

Number and rate of bytes and packets received and transmitted on the logical
interface.

detail extensive

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Local statistics

(Frame Relay) Statistics for traffic received from and transmitted to the Routing
Engine. When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. It takes awhile (generally, less than
one second) for this counter to stabilize.

detail extensive

Transit statistics

(Frame Relay) Statistics for traffic transiting the router. When a burst of traffic
is received, the value in the output packet rate field might briefly exceed the
peak cell rate. It takes awhile (generally, less than 1 second) for this counter to
stabilize.

detail extensive

Protocol

Protocol family configured on the logical interface, such as iso, inet6, mpls.

detail extensive none

Multilink bundle

(Multilink) Interface name for the multilink bundle, if configured.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:

detail extensive none

ActiveSet when the link is active and the DTE and DCE are exchanging

information.

DLCI statistics

DownSet when link is active, but no information is received from the DCE.

UnconfiguredSet when the corresponding DLCI in the DCE is not configured.

ConfiguredSet when the corresponding DLCI in the DCE is configured.

Dce-configuredDisplayed when the command is issued from the DTE.

(Frame Relay) Data-link connection identifier (DLCI) statistics.

Active DLCINumber of active DLCIs.

Inactive DLCINumber of inactive DLCIs.

Copyright 2014, Juniper Networks, Inc.

detail extensive none

1105

Interfaces Fundamentals for Routing Devices

Sample Output
show interfaces extensive (Channelized E1)
user@host> show interfaces ds-0/1/1:1 extensive
Physical interface: ds-0/1/1:1, Enabled, Physical link is Down
Interface index: 163, SNMP ifIndex: 37, Generation: 46
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: E1,
Loopback: None, FCS: 16, Framing: G704
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2005-12-28 14:44:06 PST (00:00:30 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
HS link CRC errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
DS1
alarms
: LOF, LOS
DS1
defects : LOF, LOS
E1 media:
Seconds
Count State
SEF
982318
1 Defect Active
BEE
0
0 OK
AIS
0
0 OK
LOF
982318
1 Defect Active
LOS
982318
1 Defect Active
YELLOW
0
0 OK
BPV
1
1
EXZ
1
1
LCV
1
1
PCV
1
2
CS
0
0
FEBE
1
9
LES
1
ES
982318
SES
982318
SEFS
982318
BES
1
UAS
0
Interface transmit queues:
B/W WRR
Packets
Bytes
Drops
Errors
Queue0
95
95
0
0
0
0
Queue1
5
5
0
0
0
0
HDLC configuration:
Giant threshold: 1514, Runt threshold: 3
Timeslots
: 31
Line encoding: HDB3, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS1 BERT configuration:
BERT time period: 0 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^11 - 1, O.152 and O.153 (2047 type),

1106

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Pseudorandom (8)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 2 (0x1b)
CoS information:
CoS transmit queue
Bandwidth
Buffer
%
bps
%
usec
0 best-effort
95
1945600
95
0
3 network-control 5
102400
5
0

Copyright 2014, Juniper Networks, Inc.

Priority

Limit

low
low

none
none

1107

Interfaces Fundamentals for Routing Devices

show interfaces (Channelized OC12 IQ and IQE)

Syntax

Release Information
Description
Options

show interfaces (type-fpc/pic/port<:channel><:channel><:channel>)

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Display status information about the specified channelized OC12 IQ and IQE interface.
type-fpc/pic/port:channel:channel:channelInterface type with optional corresponding

channel levels.
For SONET mode, the interface type can be one of the following:

type-fpc/pic/portFor the physical channelized OC12 IQ or IQE interface, type is

coc12. For the clear channel, type is so (for OC12).

type-fpc/pic/port:channelAt the first level of channelization, type can be

coc1(channelized OC1), ct3 (from coc1), so (for OC3), or t3.

type-fpc/pic/port:channel:channelAt the second level of channelization, type can

be ct1 (from ct3or coc1) or t1 (from ct3 or coc1).

type-fpc/pic/port:channel:channel:channelAt the third level of channelization,

type is ds (from ct1).

For SDH mode, the interface type can be one of the following:

type-fpc/pic/portFor the physical channelized OC12 IQ or IQE interface, type is

cstm4. For the clear channel, type is so (for SONET/SDH (vc-4-4c)).

type-fpc/pic/port:channelAt the first level of channelization,type can be so (from

cstm4) or cau4 (from cstm4).

type-fpc/pic/port:channel:channelAt the second level of channelization, type can

be ct3or t3 (from or cau4).

type-fpc/pic/port:channel:channel:channelAt the third level of channelization,

type is ct1 or t1 (from ct3).

type-fpc/pic/port:channel:channel:channelAt the fourth level of channelization,

type is ds (from ct1).

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.

1108

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

statistics(Optional) Display static interface statistics.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces extensive (CAU4 on Channelized OC-12 IQ) on page 1109

show interfaces extensive (Channelized OC1 on Channelized OC12 IQ) on page 1109
show interfaces extensive (Channelized OC12 IQ) (Physical) on page 1109
show interfaces extensive (Channelized T1 from Channelized OC12 IQ) on page 1110
show interfaces extensive (Channelized T3 on Channelized OC12 IQ) on page 1110
show interfaces extensive (CSTM4 on Channelized OC-12 IQ) on page 1110
show interfaces extensive (DS0 on Channelized OC12 IQ) on page 1110
show interfaces extensive (SONET Interface on Channelized OC12 IQ) on page 1110
show interfaces extensive (T1 on Channelized OC12 IQ) on page 1111
See the output field table for the show interfaces (Channelized OC3 IQ and IQE)
command.

Sample Output
show interfaces extensive (CAU4 on Channelized OC-12 IQ)
user@host> show interfaces cau4-0/2/0:1 extensive
Physical interface: cau4-0/2/0:1, Enabled, Physical link is Up
Interface index: 219, SNMP ifIndex: 139, Generation: 221
Link-level type: Controller, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, Parent: cstm4-0/2/0 Interface index 216
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: None
...

show interfaces extensive (Channelized OC1 on Channelized OC12 IQ)

user@host> show interfaces extensive coc1-4/2/0:7
Physical interface: coc1-4/2/0:7, Enabled, Physical link is Up
Interface index: 381, SNMP ifIndex: 2524, Generation: 728
Link-level type: Controller, MTU: 4474, Clocking: Internal, SONET mode,
Speed: 51840kbps, Loopback: None,
FCS: 16, Payload scrambler: Disabled, Parent: coc12-4/2/0 (Index 266)
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: None
...

show interfaces extensive (Channelized OC12 IQ) (Physical)

user@host> show interfaces extensive coc12-4/2/0
Physical interface: coc12-4/2/0, Enabled, Physical link is Up
Interface index: 266, SNMP ifIndex: 1269, Generation: 601
Link-level type: Controller, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC12, Loopback: None,
FCS: 16, Payload scrambler: Disabled, Parent: None Device flags
: Present
Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives DTE
...

Copyright 2014, Juniper Networks, Inc.

1109

Interfaces Fundamentals for Routing Devices

show interfaces extensive (Channelized T1 from Channelized OC12 IQ)

user@host> show interfaces extensive ct1-4/2/0:7:1
Physical interface: ct1-4/2/0:4:1, Enabled, Physical link is Up
Interface index: 305, SNMP ifIndex: 2410, Generation: 640
Link-level type: Controller, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16,
Framing: ESF, Parent: coc1-4/2/0:7 (Index 304)
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: None
...

show interfaces extensive (Channelized T3 on Channelized OC12 IQ)

user@host> show interfaces ct3-0/2/0:1 extensive
Physical interface: ct3-0/2/0:1:1, Enabled, Physical link is Up
Interface index: 220, SNMP ifIndex: 140, Generation: 222
Link-level type: Controller, Clocking: Internal, Speed: T3, Loopback: None,
Mode: C/Bit parity, Parent: cau4-0/2/0:1 Interface index 219
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: None
...

show interfaces extensive (CSTM4 on Channelized OC-12 IQ)

user@host> show interfaces cstm4-0/2/0 extensive
Physical interface: cstm4-0/2/0, Enabled, Physical link is Up
Interface index: 216, SNMP ifIndex: 33, Generation: 218
Link-level type: Controller, Clocking: Internal, SDH mode, Speed: OC12,
Loopback: None, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: None
...

show interfaces extensive (DS0 on Channelized OC12 IQ)

user@host> show interfaces extensive ds-4/2/0:7:1:1
Physical interface: ds-4/2/0:4:1:1, Enabled, Physical link is Up
Interface index: 306, SNMP ifIndex: 2411, Generation: 641
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: 64kbps,
Loopback: None, FCS: 16, Parent: ct1-4/2/0:7:1 (Index 305)
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives
...

show interfaces extensive (SONET Interface on Channelized OC12 IQ)

user@host> show interfaces so-0/2/0:1 extensive
Physical interface: so-0/2/0:1, Enabled, Physical link is Up
Interface index: 750, SNMP ifIndex: 23, Generation: 11709
Link-level type: Multilink-FR, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, FCS: 16,
Payload scrambler: Enabled, Parent: coc12-0/2/0 Interface index 749
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives DTE
...

1110

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces extensive (T1 on Channelized OC12 IQ)

user@host> show interfaces t1-0/2/0:1:1:1 extensive
Physical interface: t1-0/2/0:1:1:1, Enabled, Physical link is Up
Interface index: 222, SNMP ifIndex: 143, Generation: 226
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF, Parent: ct3-0/2/0:1:1
Interface index 221
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
...

Copyright 2014, Juniper Networks, Inc.

1111

Interfaces Fundamentals for Routing Devices

show interfaces (Channelized OC12)

Syntax

Release Information
Description
Options

show interfaces t3-fpc/pic/port:t3channel

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Display status information about the specified channelized OC12 interface.
t3-fpc/pic/port:t3channelDisplay standard information about the specified channelized

OC12 interface.
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.

Required Privilege
Level
List of Sample Output
Output Fields

view

show interfaces extensive (Channelized OC12) on page 1112

See the output field table for the show interfaces (Channelized OC3 IQ and IQE)
command.

Sample Output
show interfaces extensive (Channelized OC12)
user@host> show interfaces t3-0/3/0:0 extensive
Physical interface: t3-0/3/0:0, Enabled, Physical link is Up
Interface index: 32, SNMP ifIndex: 21, Generation: 2719
Link-level type: Frame-Relay, PPP, MTU: 4474, Clocking: Internal, SONET mode,
Speed: T3, Loopback: None, SONET Loopback: None, FCS: 16, Mode: C/Bit parity
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent
: 43186
Full enquiries sent
: 8515
Enquiry responses received
: 43185
Full enquiry responses received
: 8515
DCE statistics:

1112

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 0
Nonmatching DCE-end DLCIs:
2
Hold-times
: Up 0 ms, Down 0 ms
Last flapped
: 2002-05-23 16:59:03 PDT (18:23:58 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
1700
0 bps
Output bytes :
1714
0 bps
Input packets:
123
0 pps
Output packets:
124
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 1100817, Bucket drops: 0,
Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0
DS3
alarms
: None
SONET alarms
: None
DS3
defects : None
SONET defects : None
DS3 media:
Seconds
Count State
AIS
0
0 OK
LOF
18
1 OK
LOS
0
0 OK
IDLE
0
0 OK
YELLOW
0
0 OK
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
36
122399
CCV
72
91948
LES
0
PES
18
PSES
18
CES
18
CSES
18
SEFS
18
UAS
0
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 4484, Runt threshold: 3
DSU configuration:
Compatibility mode: None, Scrambling: Disabled, Subrate: Disabled
FEAC loopback: Inactive, Response: Disabled, Count: 0
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: Unknown (0), Induced error rate: 10e-0
Interface transmit queues:
B/W WRR
Packets
Bytes
Drops
Errors
Queue0
95
95
0
0
0
0
Queue1
5
5
529
6348
0
0

Copyright 2014, Juniper Networks, Inc.

1113

Interfaces Fundamentals for Routing Devices

SONET PHY:
Seconds
Count State
PLL Lock
0
0 OK
PHY Light
20
1 OK
SONET section:
BIP-B1
0
0
SEF
20
1 OK
LOS
20
1 OK
LOF
20
1 OK
ES-S
20
SES-S
20
SEFS-S
20
SONET line:
BIP-B2
0
0
REI-L
0
0
RDI-L
0
0 OK
AIS-L
0
0 OK
BERR-SF
18
1 OK
BERR-SD
2
1 OK
ES-L
20
SES-L
20
UAS-L
10
ES-LFE
0
SES-LFE
0
UAS-LFE
0
SONET path:
BIP-B3
0
0
REI-P
0
0
LOP-P
20
1 OK
AIS-P
0
0 OK
RDI-P
0
0 OK
UNEQ-P
0
0 OK
PLM-P
20
1 OK
ES-P
20
SES-P
20
UAS-P
10
ES-PFE
0
SES-PFE
0
UAS-PFE
0
Received SONET overhead:
F1
: 0x00, J0
: 0x00, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x04, C2(cmp) : 0x04, F2
: 0x00
Z3
: 0x00, Z4
: 0x00, S1(cmp) : 0x00, V5
: 0x00
V5(cmp) : 0x00
Transmitted SONET overhead:
F1
: 0x00, J0
: 0x01, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x04, F2
: 0x00, Z3
: 0x00
Z4
: 0x00, V5
: 0x00
Received path trace: t3-0/3/0:0
74 33 2d 30 2f 33 2f 30 3a 30 00 00 00 00 0d 0a
t3-0/3/0:0......
Transmitted path trace: t3-0/3/0:0
74 33 2d 30 2f 33 2f 30 3a 30 00 00 00 00 00 00
t3-0/3/0:0......
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95
42499200 95
0
low
none
3 network-control
5
2236800
5
0
low
none
Logical interface t3-0/3/0:0.0 (Index 11) (SNMP ifIndex 268) (Generation 499)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 4470, Generation: 578, Route table: 0

1114

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 22.22.22.1, Local: 22.22.22.2, Broadcast: Unspecified,
Generation: 98
DLCI 100
Flags: Active, Dce-configured
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :2 Inactive DLCI : 0

Copyright 2014, Juniper Networks, Inc.

1115

Interfaces Fundamentals for Routing Devices

show interfaces (Channelized OC3 IQ and IQE)

Syntax

Release Information
Description

Options

show interfaces (type-fpc/pic/port <:channel><:channel><:channel>)

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
channelized OC3 IQ or IQE interface.
type-fpc/pic/port:channel:channel:channelInterface type with optional corresponding

channel levels. The interface type can be one of the following:

type-fpc/pic/portFor the physical interface, type is coc3. For the clear channel,
type is so (for OC3).

type-fpc/pic/port:channelAt the first level of channelization, type can be coc1

(channelized OC1), ct3 (from coc1), or t3 (from coc1).

type-fpc/pic/port:channel:channelAt the second level of channelization, type can

be ct1 (from coc1 or ct3) or t1 (from coc1 or ct3).

type-fpc/pic/port:channel:channel:channelAt the third level of channelization,

type can be ds (from ct1).

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.

Required Privilege
Level
List of Sample Output

Output Fields

1116

view

show interfaces extensive (Channelized OC3 IQ) (Physical) on page 1130

show interfaces extensive (Channelized OC1 on Channelized OC3 IQ) on page 1131
show interfaces extensive (Channelized T1 on Channelized OC3 IQ) on page 1132
show interfaces extensive (DS0 on Channelized OC3 IQ) on page 1133
Table 56 on page 1117 lists the output fields for the show interfaces (all Channelized OC
interfaces) command. Output fields are listed in the approximate order in which they
appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 56: Channelized OC show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

SNMP index number for the physical interface.

detail extensive none

Description

Interface description.

All levels

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

MTU size on the physical interface.

All levels

Clocking

SONET/SDH reference clock source. It can be Internal or External. Clocking is

configured and displayed only for channel 0.

All levels

Framing mode

Framing mode: SONET or SDH.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

SONET loopback

Whether loopback is enabled on a SONET/SDH interface, and the type of

loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16-bit.

All levels

Payload scrambler

Whether payload scrambling is enabled.

All levels

Parent

Name and interface index of the interface to which a particular child interface
belongs. None indicates that this interface is the top level.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1117

Interfaces Fundamentals for Routing Devices

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

ANSI or ITU LMI

settings

(Frame Relay) Settings for Local Management Interface (LMI). The format is
(ANSI or ITU) LMI settings: value, value... nn seconds, where value can be:

All levels

LMI statistics

DTE statistics

n391dteDTE full status polling interval (1255)

n392dceDCE error threshold (110)

n392dteDTE error threshold (110)

n393dceDCE monitored event count (110)

n393dteDTE monitored event count (110)

t391dteDTE polling timer (530 seconds)

t392dceDCE polling verification timer (530 seconds)

(Frame Relay) Statistics about the link management.

detail extensive

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
sent hh:mm:ss ago).

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
sent hh:mm:ss ago).

(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data circuit-terminating equipment (DCE):

Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.

Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.

Enquiry responses receivedNumber of enquiry responses received by the

detail extensive none

DTE from the DCE.

Full enquiry responses receivedNumber of full enquiry responses sent from

the DTE to the DCE.

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

Enquiries receivedNumber of enquiries received by the DCE from the DTE.

Full enquiries receivedNumber of full enquiries received by the DCE from

detail extensive none

the DTE.

Enquiry responses sentNumber of enquiry responses sent from the DCE to

the DTE.

Full enquiry responses sentNumber of full enquiry responses sent from the

DCE to the DTE.

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

detail extensive none

Unknown messages receivedNumber of received packets that do not fall

into any category.

Asynchronous updates receivedNumber of link status peer changes received.

Out-of-sequence packets receivedNumber of packets for which the sequence

of the packets received is different from the expected sequence.

1118

Keepalive responses timedoutNumber of keepalive responses that timed

out when no LMI packet was reported for n392dte or n393dce intervals. (See
LMI settings.)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Nonmatching
DCE-end DLCIs

(Frame Relay) Number of DLCIs configured from the DCE, displayed only from
the DTE.

detail extensive none

Last flapped

Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hh:mm:ss timezone year-month-day (hh:mm:ss
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).

detail extensive none

CoS Queues

Number of CoS queues configured.

detail extensive none

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

DS1 alarms

E1or T1 media-specific defects that can prevent the interface from passing
packets. When a defect persists for a certain period, 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.
See the following list for all possible alarms and defects. For complete
explanations of most of these alarms and defects, see Bellcore Telcordia
GR-499-CORE.

detail extensive none

DS1 defects

LOSLoss of signal.

LOFLoss of frame.

AISAlarm indication signal.

YLWYellow alarm. Indicates errors at the remote site receiver.

Copyright 2014, Juniper Networks, Inc.

1119

Interfaces Fundamentals for Routing Devices

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

T1 media

Counts of T1 or E1 media-specific errors.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

The T1 or E1 media-specific error types are:

Traffic statistics

1120

SEFSeverely errored framing

BEEBit error

AISAlarm indication signal

LOFLoss of frame

LOSLoss of signal

YELLOWErrors at the remote site receiver

BPVBipolar violation

EXZExcessive zeros

LCVLine code violation

PCVPulse code violation

CSCarrier state

FEBEFar-end block error (E1 only)

LESLine error seconds

ESErrored seconds

BESBit error seconds

SESSeverely errored seconds

SEFSSeverely errored framing seconds

UASUnavailable seconds

Number and rate of bytes and packets received and transmitted on the physical
interface.

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

detail extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Input errors

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber 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 errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

GiantsNumber of frames received that are larger than the giant threshold.

Bucket DropsDrops caused by traffic load exceeding the interface

transmit/receive leaky bucket configuration. The default is off.

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

HS link CRC errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

SRAM errorsNumber of hardware errors that occurred in the static RAM

(SRAM) on the PIC. If the value of this field increments, the PIC is
malfunctioning.

HS link FIFO overflowsNumber of FIFO overflows on the high-speed links

between the ASICs responsible for handling the router interfaces.

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

1121

Interfaces Fundamentals for Routing Devices

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

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
is malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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 underflowsNumber of FIFO underflows on the high-speed links

between the ASICs responsible for handling the router interfaces.

MTU errorsNumber of packets whose size exceeds the MTU of the interface.

Resource errorsSum of transmit drops.

Egress queues

Total number of egress queues supported on the specified interface.

detail extensive

Queue counters

CoS queue number and its associated user-configured forwarding class name.

detail extensive

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Active alarms

Defects that can prevent the interface from passing packets:

Active defects

NoneThere are no active defects or alarms.

LOFLoss of frame.

SONET alarms
SONET defects

1122

detail extensive

Media-specific defects that can prevent the interface from passing 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 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.

All levels

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SONET vt

SONET virtual-tributary (VT) alarms and defects:

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SONET PHY

BIP-B2Bit interleaved parity for SONET line overhead

REI-VRemote error indication (near-end VT)

LOP-VLoss of pointer (near-end VT)

AIS-VAlarm indication signal (near-end VT)

RDI-VRemote defect indication (near-end VT)

UNEQ-VUnequipped (near-end VT)

PLM-VPayload label mismatch (near-end VT)

ES-VErrored seconds (near-end VT)

SES-VSeverely errored seconds (near-end VT)

UAS-VUnavailable seconds (near-end VT)

ES-VFEErrored seconds (far-end VT)

SES-VFESeverely errored seconds (far-end VT)

UAS-VFEUnavailable seconds (far-end VT)

Counts of specific SONET errors with detailed information:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

SONET section

PLL LockPhase-locked loop

PHY LightLoss of optical signal

Counts of specific SONET errors with detailed information:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

BIP-B1Bit interleaved parity for SONET section overhead

SEFSeverely errored framing

LOSLoss of signal

LOLLoss of light

LOFLoss of frame

ES-SErrored seconds (section)

SES-SSeverely errored seconds (section)

SEFS-SSeverely errored framing seconds (section)

Copyright 2014, Juniper Networks, Inc.

1123

Interfaces Fundamentals for Routing Devices

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SONET line

Active alarms and defects, plus counts of specific SONET errors with detailed
information:

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

State State of the error. State other than OK indicates a problem.

Subfields are:

SONET path

BIP-B2Bit interleaved parity for SONET line overhead

REI-LRemote error indication (near-end line)

RDI-LRemote defect indication (near-end line)

AIS-LAlarm indication signal (near-end line)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

ES-LErrored seconds (near-end line)

SES-LSeverely errored seconds (near-end line)

UAS-LUnavailable seconds (near-end line)

ES-LFEErrored seconds (far-end line)

SES-LFESeverely errored seconds (far-end line)

UAS-LFEUnavailable seconds (far-end line)

Active alarms and defects, plus counts of specific SONET errors with detailed
information:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

1124

BIP-B3Bit interleaved parity for SONET section overhead

REI-PRemote error indication

LOP-PLoss of pointer (path)

AIS-PPath alarm indication signal

RDI-PPath remote defect indication

UNEQ-PPath unequipped

PLM-PPath payload (signal) label mismatch

ES-PErrored seconds (near-end STS path)

SES-PSeverely errored seconds (near-end STS path)

UAS-PUnavailable seconds (near-end STS path)

ES-PFEErrored seconds (far-end STS path)

SES-PFESeverely errored seconds (far-end STS path)

UAS-PFEUnavailable seconds (far-end STS path)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Received SONET
overhead

Values of the received and transmitted SONET/SDH overhead:

extensive

F1Section user channel byte. This byte is set aside for the purposes of users.
Transmitted
SONET overhead

S1Synchronization Status (S1). The S1 byte is located in the first STS-1 of an

STS-N. Bits 5 through 8 convey the synchronization status of the network

element.
Z3 and Z4Path overhead.
V5Virtual Tributary (VT) path overhead byte.
SDH alarms
SDH defects

SDH media-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain period, 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 light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.

All levels

NOTE: For controller based SONET PICs, the SDH alarms and SDH defects
output in the show interface coc3 extensive command output only shows the
section and line level defects. The path level defects can be found under the
SONET (so) interface output.
SDH PHY

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

SDH regenerator
section

PLL LockPhase-locked loop

PHY LightLoss of optical signal

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

RS-BIP824-bit BIP for multiplex section overhead (B2 bytes)

OOFOut of frame

LOSLoss of signal

LOFLoss of frame

RS-ESErrored seconds (near-end regenerator section)

RS-SESSeverely errored seconds (near-end regenerator section)

RS-SEFSSeverely errored framing seconds (regenerator section)

Copyright 2014, Juniper Networks, Inc.

1125

Interfaces Fundamentals for Routing Devices

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SDH multiplex
section

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SDH path

MS-BIP248-bit BIP for high-order path overhead (B3 byte)

MS-FEBEFar-end block error (multiplex section)

MS-FERFFar-end remote fail (multiplex section)

MS-AISalarm indication signal (multiplex section)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

MS-ESErrored seconds (near-end multiplex section)

MS-SESSeverely errored seconds (near-end multiplex section)

MS-UASUnavailable seconds (near-end multiplex section)

MS-ES-FEErrored seconds (far-end multiplex section)

MS-SES-FESeverely errored seconds (far-end multiplex section)

MS-UAS-FEUnavailable seconds (far-end multiplex section

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

1126

HP-BIP88-bit BIP for regenerator section overhead (B1 byte)

HP-FEBEFar-end block error (high-order path)

HP-LOPLoss of pointer (high-order path)

HP-AISHigh-order-path alarm indication signal

HP-FERFFar-end remote fail (high-order path)

HP-UNEQUnequipped (high-order path)

HP-PLMPayload label mismatch (high-order path)

HP-ESErrored seconds (near-end high-order path)

HP-SESSeverely errored seconds (near-end high-order path)

HP-UASUnavailable seconds (near-end high-order path)

HP-ES-FEErrored seconds (far-end high-order path)

HP-SES-FESeverely errored seconds (far-end high-order path)

HP-UAS-FEUnavailable seconds (far-end high-order path)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Received SDH
overhead

Values of the received and transmitted SONET overhead:

extensive

Transmitted SDH
overhead

C2Signal label. Allocated to identify the construction and content of the

STS-level SPE and for PDI-P.

F1Section user channel byte. This byte is set aside for the purposes of users.

K1 and K2These bytes are allocated for APS signaling for the protection of

the multiplex section.

J0Section trace. This byte is defined for STS-1 number 1of 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.

S1Synchronization status. The S1 byte is located in the first STS-1 of an

STS-N.

Received path trace

Transmitted path
trace

DS3 media

Z3 and Z4Allocated for future use.

Channelized OC12 interfaces allow path trace bytes to be sent inband across
the SONET/SDH link. 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. This information is specific to each of
the 12 channelized OC12 interfaces.

extensive

Counts of T3 media-specific errors. For detailed definitions of the T3 (DS-3)

error events (BPV, EXZ, LCV, PCV, and CCV) and performance parameters (LES,
PES, PSES, CES, CSES, SEFS, and UAS), see RFC 2496.

extensive

The DS3 or E3 media-specific error types can be:

PLL LockPhase-locked loop out of lock

ReframingFrame alignment recovery time

AISAlarm indication signal

LOFLoss of frame

LOSLoss of signal

IDLEIdle code detected

YELLOWErrors at the remote site receiver

BPVBipolar violation

EXZExcessive zeros

LCVLine code violation

PCV(DS3 only) Pulse code violation

CCV(DS3 only) C-bit coding violation

FEBE(DS3 only) Far-end block error

LESLine error seconds

PES(DS3 only) P-bit errored seconds

PSES(DS3 only) P-bit errored seconds (section)

CES(DS3 only) C-bit errored seconds

CSES(DS3 only) C-bit severely errored seconds

SEFSSeverely errored framing seconds

UASUnavailable seconds

Copyright 2014, Juniper Networks, Inc.

1127

Interfaces Fundamentals for Routing Devices

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

HDLC configuration

Information about the HDLC configuration.

extensive

Interface transmit
queues

DSU configuration

Policing bucketConfigured state of the receiving policer.

Shaping bucketConfigured state of the transmitting shaper.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

TimeslotsConfigured time slots for the interface.

Line encodingLine encoding used. It is always HDB3.

Byte encoding(T1 only) Byte encoding used: Nx64K or Nx56K.

Line encodingLine encoding used. For T1, the value can be B8ZS or AMI. For
E1, the value is HDB3.

Data inversionHDLC data inversion setting: Enabled or Disabled.

Idle cycle flagIdle cycle flags.

Start end flagStart and end flag.

Name of the transmit queues and their associated statistics for each DS3
channel on the Channelized OC12 PIC.

B/WQueue bandwidth as a percentage of the total interface bandwidth.

WRRWeighted round-robin (in percent).

PacketsNumber of packets transmitted.

BytesNumber of bytes transmitted.

DropsNumber of packets dropped.

ErrorsNumber of packet errors.

Information about the DSU configuration. The last three lines (Bit count, Error
bit count, and LOS information) are displayed only if a BERT has ever been run
on the interface.

Compatibility modeCSU/DSU compatibility mode: None, Larscom, Kentrox,

or Digital-Link.

ScramblingPayload scrambling. It can be Enabled or Disabled.

SubrateConfigured subrate setting. Applies only whenDigital-Link

compatibility mode is used. It can be Disabled or display units in kbps.

FEAC loopback(T3) Whether a far-end alarm and control (FEAC) loopback

is Active or Inactive. This feature is used to send alarm or status information

extensive

extensive

from the far-end terminal back to the near-end terminal and to initiate T3
loopbacks at the far-end terminal from the near-end terminal.

BERT configuration

ResponseWhether the FEAC signal is Enabled or Disabled.

CountNumber of FEAC loopbacks.

(DS interfaces) BERT (bit error rate test) checks the quality of the line. This
output appears only when a BERT is run on the interface.

BERT time periodConfigured total time period that the BERT is to run.

ElapsedActual time elapsed since the start of the BERT (in seconds).

Induced error rateConfigured rate at which the bit errors are induced in the

detail extensive none

BERT pattern.

1128

AlgorithmType of algorithm selected for the BERT.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Packet Forwarding
Engine
configuration

Information about the configuration of the Packet Forwarding Engine:

extensive

CoS information

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Traffic statistics

Total number of bytes and packets received and transmitted on the logical
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. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Local statistics

Input rateRate of bits and packets received on the interface.

Output rateRate of bits and packets transmitted on the interface.

Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

Copyright 2014, Juniper Networks, Inc.

detail extensive

1129

Interfaces Fundamentals for Routing Devices

Table 56: Channelized OC show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Transit statistics

Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. It
takes awhile (generally, less than 1 second) for this counter to stabilize.

detail extensive

Protocol

Protocol family configured on the logical interface, such as iso, inet6, or mpls.

detail extensive none

Multilink bundle

(If the logical interface is configured as part of a multilink bundle.) Interface

name for the multilink bundle.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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.

detail extensive none

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:

detail extensive none

ActiveSet when the link is active and the DTE and DCE are exchanging

information.

DownSet when the link is active, but no information is received from the

DCE.

DLCI statistics

UnconfiguredSet when the corresponding DLCI in the DCE is not configured.

ConfiguredSet when the corresponding DLCI in the DCE is configured.

Dce-configuredDisplayed when the command is issued from the DTE.

(Frame Relay) Data-link connection identifier (DLCI) statistics.

Active DLCINumber of active DLCIs.

Inactive DLCINumber of inactive DLCIs.

detail extensive none

Sample Output
show interfaces extensive (Channelized OC3 IQ) (Physical)
user@host> show interfaces extensive coc3-0/0/0
Physical interface: coc3-0/0/0, Enabled, Physical link is Down
Interface index: 128, SNMP ifIndex: 22, Generation: 11

1130

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Description: pink coc3-0/0/0

Link-level type: Controller, Clocking: Internal, SONET mode, Speed: OC3,
Loopback: None, Parent: None
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point SNMP-Traps 16384
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 4 supported
Last flapped
: 2005-01-27 16:39:21 PST (1w0d 22:09 ago)
Statistics last cleared: Never
SONET alarms
: PLL, LOS
SONET defects : PLL, LOF, LOS, SEF, AIS-L
SONET PHY:
Seconds
Count State
PLL Lock
681767
1 PLL Lock Error
PHY Light
0
0 OK
SONET section:
BIP-B1
0
0
SEF
681767
1 Defect Active
LOS
681767
1 Defect Active
LOF
681767
1 Defect Active
ES-S
681767
SES-S
681767
SEFS-S
681767
SONET line:
BIP-B2
0
0
REI-L
0
0
RDI-L
0
0 OK
AIS-L
681767
1 Defect Active
BERR-SF
0
0 OK
BERR-SD
0
0 OK
ES-L
681767
SES-L
681767
UAS-L
681757
ES-LFE
0
SES-LFE
0
UAS-LFE
0
Received SONET overhead:
F1
: 0x00, J0
: 0x00, K1
: 0xff, K2
: 0xff
S1
: 0xff
Transmitted SONET overhead:
F1
: 0x00, J0
: 0x01, K1
: 0x00, K2
: 0x00
S1
: 0x00

show interfaces extensive (Channelized OC1 on Channelized OC3 IQ)

user@host> show interfaces extensive coc1-0/0/0:1
Physical interface: coc1-0/0/0:1, Enabled, Physical link is Down
Interface index: 133, SNMP ifIndex: 27, Generation: 16
Link-level type: Controller, Clocking: Internal, SONET mode, Speed: 51840kbps,
Loopback: None, Parent: coc3-0/0/0
Interface index 128
Device flags
: Present Running Down 16384
Interface flags: Hardware-Down Point-To-Point SNMP-Traps 16384
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 4 supported
Last flapped
: 2005-02-04 14:51:07 PST (00:00:35 ago)
Statistics last cleared: Never
SONET alarms
: None
SONET defects : AIS-P

Copyright 2014, Juniper Networks, Inc.

1131

Interfaces Fundamentals for Routing Devices

SONET path:
BIP-B3
0
0
REI-P
0
0
LOP-P
0
0 OK
AIS-P
36
1 Defect Active
RDI-P
0
0 OK
UNEQ-P
0
0 OK
PLM-P
0
0 OK
ES-P
36
SES-P
36
UAS-P
26
ES-PFE
0
SES-PFE
0
UAS-PFE
0
Received SONET overhead:
C2
: 0xff, C2(cmp) : 0x01, F2
: 0x00, Z3
: 0x00
Z4
: 0x00, S1(cmp) : 0x00
Transmitted SONET overhead:
C2
: 0x01, F2
: 0x00, Z3
: 0x00, Z4
: 0x00
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace: router-1 coc1-0/0/0:1
6b 61 76 65 72 69 20 63 6f 63 31 2d 30 2f 30 2f
router-1 coc1-0/0/0:1
30 3a 31 00 00 00 00 00 00 00 00 00 00 00 00 00
..............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)

show interfaces extensive (Channelized T1 on Channelized OC3 IQ)

user@host> show interfaces extensive ct1-0/0/0:1:1
Physical interface: ct1-0/0/0:1:1, Enabled, Physical link is Down
Interface index: 134, SNMP ifIndex: 62, Generation: 17
Link-level type: Controller, Clocking: Internal, Speed: T1, Loopback: None,
Framing: ESF, Parent: coc1-0/0/0:1 Interface index 133
Device flags
: Present Running Down 16384
Interface flags: Hardware-Down Point-To-Point SNMP-Traps 16384
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 4 supported
Last flapped
: 2005-02-04 14:54:35 PST (00:00:18 ago)
Statistics last cleared: Never
DS1
alarms
: None
DS1
defects : AIS, LOF
T1 media:
Seconds
Count State
SEF
1
1 OK
BEE
1
1 OK
AIS
18
1 Defect Active
LOF
18
1 Defect Active
LOS
0
0 OK
YELLOW
0
0 OK
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
0
0
CS
0
0
LES
18

1132

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

ES
18
SES
18
SEFS
18
BES
0
UAS
14
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
SONET alarms
: None
SONET defects : None
SONET vt:
BIP-BIP2
0
0
REI-V
0
0
LOP-V
0
0 OK
AIS-V
19
1 Defect Active
RDI-V
19
1 Defect Active
UNEQ-V
0
0 OK
PLM-V
19
1 Defect Active
ES-V
19
SES-V
19
UAS-V
9
ES-VFE
0
SES-VFE
0
UAS-VFE
0
Received SONET overhead:
V5
: 0x07, V5(cmp) : 0x02
Transmitted SONET overhead:
V5
: 0x02
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)

show interfaces extensive (DS0 on Channelized OC3 IQ)

user@host> show interfaces extensive ds-0/0/0:1:1:1
Physical interface: ds-0/0/0:1:1:1, Enabled, Physical link is Down
Interface index: 135, SNMP ifIndex: 63, Generation: 18
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: 320kbps,
Loopback: None, FCS: 16, Parent: ct1-0/0/0:1:1 Interface index 134
Device flags
: Present Running
Interface flags: Hardware-Down Point-To-Point SNMP-Traps 16384
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 4 supported
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, HS link CRC errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

Copyright 2014, Juniper Networks, Inc.

1133

Interfaces Fundamentals for Routing Devices

1 expedited-fo

2 assured-forw

3 network-cont

HDLC configuration:
Giant threshold: 1514, Runt threshold: 2
Timeslots
: 1-5
Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS0 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 4 (0x00)

1134

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Channelized STM1 IQ)

Syntax

Release Information
Description

Options

show interfaces (type-fpc/pic /port <:channel><:channel>)

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
channelized STM1 IQ interface.
type-fpc/pic/port:channel:channelInterface type with optional corresponding channel

levels. The interface type can be one of the following types:

type-fpc/pic/port:channelFor the physical channelized STM1 IQ interface, type

is cstm1. For the clear channel, type is so. For channelization, the STM1 IQ interface
must be converted to interface type cau4.

type-fpc/pic/port:channelAt the first level of channelization, type can be ce1 or

e1 ( clear channel or fractional channel from cau4).

type-fpc/pic/port:channel:channelAt the second level of channelization, type is

ds (from ce1).

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.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (Channelized STM1 IQ) (Physical) on page 1135

show interfaces (Channelized AU-4) (Physical) on page 1136
show interfaces (Channelized E1) (Physical) on page 1136
show interfaces (DS) on page 1137
See the output field table for the show interfaces (Channelized STM1) command.

Sample Output
show interfaces (Channelized STM1 IQ) (Physical)
user@host> show interfaces cstm1-0/0/0

Copyright 2014, Juniper Networks, Inc.

1135

Interfaces Fundamentals for Routing Devices

Physical interface: cstm1-0/0/0, Enabled, Physical link is Up

Interface index: 146, SNMP ifIndex: 35
Link-level type: Frame-relay, Controller, Clocking: Internal, SDH mode,
Speed: OC3, Loopback: None, Parent: None Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent
: 43186
Full enquiries sent
: 8515
Enquiry responses received
: 43185
Full enquiry responses received
: 8515
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 0
Nonmatching DCE-end DLCIs:
2
Last flapped
: 2003-02-06 15:01:56 PST (07:15:06 ago)
...

show interfaces (Channelized AU-4) (Physical)

user@host> show interfaces cau4-0/0/0
Physical interface: cau4-0/0/0, Enabled, Physical link is Up
Interface index: 147, SNMP ifIndex: 36
Link-level type: Controller, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, Parent: cstm1-0/0/0 Interface index 146
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: None
Last flapped
: 2003-02-06 19:36:31 PST (02:40:42 ago)
SDH
alarms
: None
SDH
defects : None
...

show interfaces (Channelized E1) (Physical)

user@host> show interfaces ce1-0/0/0:11
Physical interface: ce1-0/0/0:11, Enabled, Physical link is Up
Interface index: 169, SNMP ifIndex: 288
Link-level type: Frame-relay, Controller, Clocking: Internal, Speed: E1,
Loopback: None, Framing: G704, Parent: cau4-0/0/0 Interface index 147
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent
: 43186
Full enquiries sent
: 8515
Enquiry responses received
: 43185
Full enquiry responses received
: 8515
DCE statistics:

1136

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Enquiries received
Full enquiries received
Enquiry responses sent
Full enquiry responses sent
Common statistics:
Unknown messages received
Asynchronous updates received
Out-of-sequence packets received
Keepalive responses timedout
Nonmatching DCE-end DLCIs:
2
Last flapped
: 2003-02-06 22:05:23
DS1
alarms
: None
DS1
defects : None
SDH
alarms
: None
SDH
defects : None
...

:
:
:
:

0
0
0
0

:
:
:
:

0
0
0
0

PST (00:13:45 ago)

show interfaces (DS)

user@host> show interfaces ds-0/0/0:11:1
Physical interface: ds-0/0/0:11:1, Enabled, Physical link is Up
Interface index: 170, SNMP ifIndex: 289
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: 640kbps,
Loopback: Illegal, FCS: 16, Parent: ce1-0/0/0:11 Interface index 169
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives
CoS Queues: 8 maximum usable queues, 4 in use
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 0 (never), Output: 0 (never)
LCP state: Conf-req-sent
Egress queues: 8 supported, 4 in use
...
Logical interface ds-0/0/0:11:1.0 (Index 77) (SNMP ifIndex 290)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Bandwidth: 0
Protocol inet, MTU: 1500
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.134.1.0/30, Local: 10.134.1.1
DLCI 100
Flags: Active, Dce-configured
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
...

Copyright 2014, Juniper Networks, Inc.

1137

Interfaces Fundamentals for Routing Devices

show interfaces (Channelized STM1)

Syntax

Release Information

show interfaces e1-fpc/pic/port:e1channel

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Description

(M Series and T Series routers only) Display status information about the specified
channelized STM1 interface.

Options

e1-fpc/pic/port:e1channelDisplay standard status information about the specified

channelized STM1 interface.

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.

Required Privilege
Level
List of Sample Output
Output Fields

view

show interfaces extensive (Channelized STM1, SDH) on page 1149

Table 57 on page 1138 lists the output fields for the show interfaces (all Channelized STM1
interfaces) command. Output fields are listed in the approximate order in which they
appear.

Table 57: Channelized STM1 show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, 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

Physical Interface

1138

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source. It can be Internal or External.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Framing

Physical layer framing format used on the link. It can be G704, G704-NO-CRC4,
or Unframed. The default is G704.

All levels

Parent

(Channelized STM1 IQ interfaces only) Name and interface index of the interface
to which a particular child interface belongs. None indicates that this interface
is the top level.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Keepalive settings

(PPP and HDLC) Configured settings for keepalives.

detail extensive none

intervalsecondsThe time in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

down-count numberThe number of keepalive packets a destination must

fail to receive before the network takes a link down. The range is1 through
255, with a default of 3.

up-count numberThe number of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.

Copyright 2014, Juniper Networks, Inc.

1139

Interfaces Fundamentals for Routing Devices

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Keepalive statistics

(PPP and HDLC) Information about keepalive packets.

detail extensive none

InputNumber of keepalive packets received by PPP.

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the formathh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

ANSI LMI settingsor

ITU LMI settings

LMI

DTE statistics

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

(Frame Relay) Local Management Interface settings. The format is (ANSI or

ITU) LMI settings: value, value... xx seconds, where value can be:

n391dteDTE full status polling interval (1- 255)

n392dceDCE error threshold (1-10)

n392dteDTE error threshold (1-10)

n393dceDCE monitored event count (1-10)

n393dteDTE monitored event count (1-10)

t391dteDTE polling timer (5-30 seconds)

t392dceDCE polling verification timer (5-30 seconds)

(Frame Relay) Statistics about the link management.

detail extensive none

detail extensive none

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
seen hh:mm:ss ago).

(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data circuit-terminating equipment (DCE):

Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.

Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.

Enquiry responses receivedNumber of enquiry responses received by the

detail extensive none

DTE from the DCE.

Full enquiry responses receivedNumber of full enquiry responses sent from

the DTE to the DCE.

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

Enquiries receivedNumber of enquiries received by the DCE from the DTE.

Full enquiries receivedNumber of full enquiries received by the DCE from

detail extensive none

the DTE.

Enquiry responses sentNumber of enquiry responses sent from the DCE to

the DTE.

Full enquiry responses sentNumber of full enquiry responses sent from the

DCE to the DTE.

1140

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

detail extensive none

Unknown messages receivedNumber of received packets that do not fall

into any category.

Asynchronous updates receivedNumber of link status peer changes received.

Out-of-sequence packets receivedNumber of packets for which the sequence

of the packets received is different from the expected sequence.

Keepalive responses timedoutNumber of keepalive responses that timed

out when no LMI packet was reported for n392dte or n393dce intervals. (See
LMI settings.)

Nonmatching
DCE-end DLCIs

(Frame Relay, displayed only from the DTE) Number of DLCIs configured from
the DCE.

detail extensive none

LCP state

(PPP) Link Control Protocol state.

detail extensive none

NCP state

CHAP state

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not-configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

(PPP) Network Control Protocol state.

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not-configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

Chap-Chal-receivedChallenge was received but response not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

detail extensive none

detail extensive none

CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)

Last flapped

Chap-Resp-sentResponse was sent for the challenge received.

ClosedCHAP authentication is incomplete.

FailureCHAP authentication failed.

Not-configuredCHAP is not configured on the interface.

SuccessCHAP authentication was successful.

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).

Copyright 2014, Juniper Networks, Inc.

detail extensive none

1141

Interfaces Fundamentals for Routing Devices

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

HS link CRC errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

SRAM errorsNumber of hardware errors that occurred in the static RAM

(SRAM) on the PIC. If the value of this field increments, the PIC is
malfunctioning.

1142

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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
is malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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.
DS1 alarms
DS1 defects

SDH alarms
SDH defects

E1 media-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain period, 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. The
following lists all possible alarms and defects. For complete explanations of
most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.

LOSLoss of signal.

LOFLoss of frame.

AISAlarm indication signal.

YLWYellow alarm. Indicates errors at the remote site receiver.

SDH media-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain period, 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 light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.

detail extensive none

All levels

NOTE: For controller-based SONET PICs, the SDH alarms and SDH defects
output in the show interface cstm1 extensive command output only shows the
section and line level defects. The path level defects can be found under the
SONET (so) interface output.

Copyright 2014, Juniper Networks, Inc.

1143

Interfaces Fundamentals for Routing Devices

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

E1 media

Active alarms and defects, plus counts of specific E1 errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Error types can be:

Interface transmit
queues

HDLC configuration

1144

AISAlarm indication signal

BEEBit error

BESBit error seconds

BPVBipolar violation

CSCarrier state

ESErrored seconds

EXZExcessive zeros

FEBEFar-end block error

LCVLine code violation

LESLine error seconds

LOFLoss of frame

LOSLoss of signal

PCVPulse code violation

SEFSeverely errored framing

SEFS-SSeverely errored framing seconds (section)

SESSeverely errored seconds

UASUnavailable seconds

YELLOWErrors at the remote site receiver

Names of the transmit queues and their associated statistics for each E1 channel
on the Channelized STM1-to-E1 PIC.

B/WQueue bandwidth as a percentage of the total interface bandwidth.

WRRWeighted round-robin (in percent).

PacketsNumber of packets transmitted.

BytesNumber of bytes transmitted.

DropsNumber of packets dropped.

ErrorsNumber of packet errors.

Information about the HDLC configuration.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

TimeslotsConfigured time slots for the interface.

Line encodingLine encoding used. It is always HDB3.

extensive

extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

DS1 BERT
configuration

BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.

detail extensive none

BERT time periodConfigured total time period that the BERT is to run.

ElapsedActual time elapsed since the start of the BERT (in seconds).

Induced error rateConfigured rate at which the bit errors are induced in the

BERT pattern.

SDH PHY

AlgorithmType of algorithm selected for the BERT.

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

SDH regenerator
section

PLL LockPhase-locked loop

PHY LightLoss of optical signal

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

RS-BIP824-bit BIP for multiplex section overhead (B2 bytes)

OOFOut of frame

LOSLoss of signal

LOFLoss of frame

RS-ESErrored seconds (near-end regenerator section)

RS-SESSeverely errored seconds (near-end regenerator section)

RS-SEFSSeverely errored framing seconds (regenerator section)

Copyright 2014, Juniper Networks, Inc.

1145

Interfaces Fundamentals for Routing Devices

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SDH multiplex
section

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SDH path

MS-BIP248-bit BIP for high-order path overhead (B3 byte)

MS-FEBEFar-end block error (multiplex section)

MS-FERFFar-end remote fail (multiplex section)

MS-AISalarm indication signal (multiplex section)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

MS-ESErrored seconds (near-end multiplex section)

MS-SESSeverely errored seconds (near-end multiplex section)

MS-UASUnavailable seconds (near-end multiplex section)

MS-ES-FEErrored seconds (far-end multiplex section)

MS-SES-FESeverely errored seconds (far-end multiplex section)

MS-UAS-FEUnavailable seconds (far-end multiplex section)

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

1146

HP-BIP88-bit BIP for regenerator section overhead (B1 byte)

HP-FEBEFar-end block error (high-order path)

HP-LOPLoss of pointer (high-order path)

HP-AISHigh-order-path alarm indication signal

HP-FERFFar-end remote fail (high-order path)

HP-UNEQUnequipped (high-order path)

HP-PLMPayload label mismatch (high-order path)

HP-ESErrored seconds (near-end high-order path)

HP-SESSeverely errored seconds (near-end high-order path)

HP-UASUnavailable seconds (near-end high-order path)

HP-ES-FEErrored seconds (far-end high-order path)

HP-SES-FESeverely errored seconds (far-end high-order path)

HP-UAS-FEUnavailable seconds (far-end high-order path)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SDH tu

Active alarms and defects, plus counts of specific SDH tributary unit (TU) errors
with detailed information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

Received SDH
overhead

TU-BIP-2Bit interleaved parity for SONET line overhead

TU-FEBE(near-end TU)

TU-LOPLoss of pointer (near-end TU)

TU-AISAlarm indication signal (near-end TU)

TU-FERF(near-end TU)

TU-UNEQUnequipped (near-end TU)

TU-PLMPayload label mismatch (near-end TU)

TU-ESErrored seconds (near-end TU)

TU-SESSeverely errored seconds (near-end TU)

TU-UASUnavailable seconds (near-end TU)

TU-ES-FEErrored seconds (far-end TU)

TU-SES-FESeverely errored seconds (far-end TU)

TU-UAS-FEUnavailable seconds (far-end TU)

Values of the received and transmitted SONET overhead:

Transmitted SDH
overhead

extensive

C2Signal label. Allocated to identify the construction and content of the

STS-level SPE and for PDI-P.

F1Section user channel byte. This byte is set aside for the purposes of users.

K1 and K2These bytes are allocated for APS signaling for the protection of

the multiplex section.

J0Section 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.

S1Synchronization status. The S1 byte is located in the first STS-1 of an

STS-N signal.

Received path trace

Transmitted path
trace

Packet Forwarding
Engine
configuration

Z3 and Z4Allocated for future use.

Channelized OC12 interfaces allow path trace bytes to be sent inband across
the SONET/SDH link. 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. This information is specific to each of
the 12 channelized OC12 interfaces.

extensive

Information about the configuration of the Packet Forwarding Engine:

extensive

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

Copyright 2014, Juniper Networks, Inc.

1147

Interfaces Fundamentals for Routing Devices

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Protocol

Protocol family configured on the logical interface, such as iso, inet6, or mpls.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail extensive none

1148

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 57: Channelized STM1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

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.

detail extensive none

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:

detail extensive none

ActiveSet when the link is active and the DTE and DCE are exchanging

information.

DownSet when the link is active, but no information is received from the

DCE.

DLCI statistics

UnconfiguredSet when the corresponding DLCI in the DCE is not configured.

ConfiguredSet when the corresponding DLCI in the DCE is configured.

Dce-configuredDisplayed when the command is issued from the DTE.

(Frame Relay) Data-link connection identifier (DLCI) statistics.

Active DLCINumber of active DLCIs.

Inactive DLCINumber of inactive DLCIs.

detail extensive none

Sample Output
show interfaces extensive (Channelized STM1, SDH)
user@host> show interfaces e1-1/0/0:1 extensive
Physical interface: e1-1/0/0:1, Enabled, Physical link is Up
Interface index: 148, SNMP ifIndex: 285, Generation: 2915
Link-level type: Frame-relay, MTU: 1504, SDH mode, Speed: E1, Loopback: None,
FCS: 16, Framing: G704
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent
: 43186
Full enquiries sent
: 8515
Enquiry responses received
: 43185
Full enquiry responses received
: 8515
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 0
Nonmatching DCE-end DLCIs:

Copyright 2014, Juniper Networks, Inc.

1149

Interfaces Fundamentals for Routing Devices

2
Hold-times
: Up 0 ms, Down 0 ms
Last flapped
: 2002-05-23 17:02:59 PDT (17:23:45 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
592
48 bps
Output bytes :
644
48 bps
Input packets:
46
0 pps
Output packets:
46
0 pps
Input errors:
Errors: 0, Drops: 9, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 11, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0
DS1
alarms
: None
DS1
defects : None
SDH
alarms
: None
SDH
defects : None
E1 media:
Seconds
Count State
SEF
0
0 OK
BEE
0
0 OK
AIS
124
1 OK
LOF
124
1 OK
LOS
0
0 OK
YELLOW
0
0 OK
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
0
0
CS
0
0
FEBE
0
0
LES
124
ES
125
SES
124
SEFS
124
BES
0
UAS
37
Interface transmit queues:
B/W WRR
Packets
Bytes
Drops
Errors
Queue0
95
95
0
0
0
0
Queue1
5
5
529
6348
0
0
HDLC configuration:
Giant threshold: 0, Runt threshold: 0
Timeslots
: All active
Line encoding: HDB3
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
SDH PHY:
Seconds
Count State
PLL Lock
0
0 OK
PHY Light
0
0 OK
SDH regenerator section:
RS-BIP8
0
0
OOF
125
1 OK
LOS
125
1 OK
LOF
125
1 OK
RS-ES
125
RS-SES
125
RS-SEFS
125
SDH multiplex section:

1150

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

MS-BIP24
0
0
MS-FEBE
0
0
MS-FERF
0
0 OK
MS-AIS
125
1 OK
BERR-SF
0
0 OK
BERR-SD
0
0 OK
MS-ES
125
MS-SES
125
MS-UAS
115
MS-ES-FE
0
MS-SES-FE
0
MS-UAS-FE
0
SDH path:
HP-BIP8
0
0
HP-FEBE
0
0
HP-LOP
0
0 OK
HP-AIS
125
1 OK
HP-FERF
0
0 OK
HP-UNEQ
0
0 OK
HP-PLM
125
1 OK
HP-ES
125
HP-SES
125
HP-UAS
115
HP-ES-FE
0
HP-SES-FE
0
HP-UAS-FE
0
SDH tu:
TU-BIP2
0
0
TU-FEBE
124
1
TU-LOP
0
0 OK
TU-AIS
124
1 OK
TU-FERF
124
1 OK
TU-UNEQ
0
0 OK
TU-PLM
124
1 OK
TU-ES
125
TU-SES
125
TU-UAS
115
TU-ES-FE
0
TU-SES-FE
0
TU-UAS-FE
0
Received SDH overhead:
F1
: 0x00, J0
: 0x00, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x02, C2(cmp) : 0x02, F2
: 0x00
Z3
: 0x00, Z4
: 0x00, S1(cmp) : 0x00, V5
: 0x02
V5(cmp) : 0x02
Transmitted SDH overhead:
F1
: 0x00, J0
: 0x00, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x02, F2
: 0x00, Z3
: 0x00
Z4
: 0x00, V5
: 0x02
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Packet Forwarding Engine configuration:
Destination slot: 1, PLP byte: 2 (0x07)
CoS information:
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95
1945600 95
0
low
none
3 network-control
5
102400
5
0
low
none
Logical interface e1-1/0/0:1.0 (Index 10) (SNMP ifIndex 369) (Generation 496)

Copyright 2014, Juniper Networks, Inc.

1151

Interfaces Fundamentals for Routing Devices

Flags: Point-To-Point SNMP-Traps Encapsulation: PPP

Protocol inet, MTU: 1500, Generation: 575, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 19.19.19.3, Local: 19.19.19.4, Broadcast: Unspecified,
Generation: 975
DLCI 100
Flags: Active, Dce-configured
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :2 Inactive DLCI : 0

1152

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Channelized T1 IQ)

Syntax

Release Information
Description

Options

show interfaces (ct1-fpc/pic/port | type-fpc/pic/port<:channel><:channel>)

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced in Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
channelized T1 IQ interface.
type-fpc/pic/port:channelInterface type. With optional corresponding channel levels,

the interface type can be one of the following:

type-fpc/pic/portFor the physical channelized T1 IQ interface, type is ct1.

type-fpc/pic/port:channelFor the clear channel, type is t1. At the first level of

channelization, type can be ct1 or t1.

type-fpc/pic/port:channel:channelAt the second level of channelization, type can

be ds.
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.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces extensive (CT1) on page 1161

show interfaces extensive (T1) on page 1162
show interfaces extensive (DS0) on page 1163
Table 58 on page 1153 lists the output fields for the show interfaces (Channelized T1 IQ
and T3 IQ interfaces) command. Output fields are listed in the approximate order in
which they appear.

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields

Field Name

Field Description

Level of Output

Name of the physical interface.

All levels

Physical Interface
Physical interface

Copyright 2014, Juniper Networks, Inc.

1153

Interfaces Fundamentals for Routing Devices

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, 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

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source. It can be Internal or External.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Framing

Physical layer framing format used on the link. It can be ESF or SF. The default
is ESF.

All levels

Parent

Name and interface index of the interface to which a particular child interface
belongs. None indicates that this interface is the top level.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Keepalive settings

Configured settings for keepalives.

detail extensive none

1154

interval secondsThe time in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

down-count numberThe 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 numberThe number of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Keepalive statistics

Information about keepalive packets.

detail extensive none

InputNumber of keepalive packets received by PPP.

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the format hh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

LMI settings

LMI

DTE statistics

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

(Frame Relay) Settings for Local Management Interface (LMI) can be either
ANSI LMI settings or ITU LMI settings. ANSI LMI settings is the default. The format
is (ANSI or ITU) LMI settings: value, value... xx seconds, where value can be:

n391dteDTE full status polling interval (1255)

n392dceDCE error threshold (110)

n392dteDTE error threshold (110)

n393dceDCE monitored event count (110)

n393dteDTE monitored event count (110)

t391dteDTE polling timer (530 seconds)

t392dceDCE polling verification timer (530 seconds)

(Frame Relay) LMI packet statistics:

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
sent hh:mm:ss ago).

(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data communication equipment (DCE):

Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.

Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.

Enquiry responses receivedNumber of enquiry responses received by the

detail extensive none

detail extensive none

detail extensive none

DTE from the DCE.

Full enquiry responses receivedNumber of full enquiry responses sent from

the DTE to the DCE.

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

Enquiries receivedNumber of enquiries received by the DCE from the DTE.

Full enquiries receivedNumber of full enquiries received by the DCE from

detail extensive none

the DTE.

Enquiry responses sentNumber of enquiry responses sent from the DCE to

the DTE.

Full enquiry responses sentNumber of full enquiry responses sent from the

DCE to the DTE.

Copyright 2014, Juniper Networks, Inc.

1155

Interfaces Fundamentals for Routing Devices

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

detail extensive none

Unknown messages receivedNumber of received packets that do not fall

into any category.

Asynchronous updates receivedNumber of link status peer changes received.

Out-of-sequence packets receivedNumber of packets for which the sequence

of the packets received is different from the expected sequence.

Keepalive responses timedoutNumber of keepalive responses that timed

out when no LMI packet was reported for n392dte or n393dce intervals. (See
LMI settings.)

Nonmatching
DCE-end DLCIs

(Frame Relay) Number of DLCIs configured from the DCE, displayed only from
the DTE.

detail extensive none

LCP state

(PPP) Link Control Protocol state.

detail extensive none

NCP state

CHAP state

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not-configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

(PPP) Network Control Protocol state.

detail extensive none

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not-configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

Chap-Chal-receivedChallenge was received but response not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

CHAP has not yet moved into theSuccess state. (Most likely with RADIUS

detail extensive none

authentication.)

Last flapped

1156

Chap-Resp-sentResponse was sent for the challenge received.

ClosedCHAP authentication is incomplete.

FailureCHAP authentication failed.

Not-configuredCHAP is not configured on the interface.

SuccessCHAP authentication was successful.

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).

detail extensive none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CoS queues

Number of CoS queues configured.

detail extensive none

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytes, Output bytesNumber of bytes received and transmitted on the

interface.

Input packets, Output packetsNumber of packets received and transmitted

on the interface.
Input errors

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

GiantsNumber of frames received that are larger than the giant threshold.

RuntsNumber of frames received that are smaller than the runt threshold.

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsCounter increments when the software could not find a

valid logical interface for an incoming frame.

L2 mismatch timeoutsCount of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

HS link CRC errorsCount of errors on the high-speed links between the ASICs

responsible for handling the router interfaces.

SRAM errorsNumber of hardware errors that occurred in the static RAM

(SRAM) on the PIC. If the value in this field increments, the PIC is
malfunctioning.

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

1157

Interfaces Fundamentals for Routing Devices

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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
is malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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.

Queue counters

DS1 alarms DS1

defects

1158

MTU errorsNumber of packets whose size exceeds the MTU of the interface.

Resource errorsSum of transmit drops.

CoS queue number and its associated user-configured forwarding class name.

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Media-specific defects that can render the interface unable to pass 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.

LOSLoss of signal.

LOFLoss of frame.

AISAlarm indication signal.

YLWYellow alarm. Indicates errors at the remote site receiver.

detail extensive

detail extensive none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

T1 media

Counts of T1 media-specific errors.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

The T1 media-specific error types can be:

AISAlarm indication signal

BEEBit error event

BESBit error seconds

BPVBipolar violation

CSCarrier state

ESErrored seconds

EXZExcessive zeros

FEBEFar-end block error

LCVLine code violation

LESLine error seconds

LOFLoss of frame

LOSLoss of signal

PCVPulse code violation

SEFSeverely errored framing

SEFSSeverely errored framing seconds (section)

SESSeverely errored seconds

UASUnavailable seconds

YELLOWErrors at the remote site receiver

Line encoding

Line encoding used: B8ZS or AMI.

All levels

Buildout

Buildout setting.

All levels

HDLC configuration

Information about the HDLC configuration.

extensive

Policing bucketConfigured state of the receiving policer.

Shaping bucketConfigured state of the transmitting shaper.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

TimeslotsConfigured time slots for the interface.

Line encodingLine encoding used: B8ZS or AMI.

Byte encodingByte encoding used: Nx64K or Nx56K.

Data inversionHDLC data inversion setting: Enabled or Disabled.

Idle cycle FlagIdle cycle flags.

Start end FlagStart and end flag.

Copyright 2014, Juniper Networks, Inc.

1159

Interfaces Fundamentals for Routing Devices

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

DS0 or DS1 BERT

configuration

BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.

detail extensive none

BERT time periodConfigured total time period that the BERT is to run.

ElapsedActual time elapsed since the start of the BERT (in seconds).

Induced error rateConfigured rate at which the bit errors are induced in the

BERT pattern.

Packet Forwarding
Engine
configuration

AlgorithmType of algorithm selected for the BERT.

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

extensive

Logical Interface
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface; values are described in the Logical
Interface Flags section under Common Output Fields Description on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Protocol

Protocol family configured on the logical interface, such as iso, inet6, or mpls.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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

1160

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 58: Channelized T1 IQ and T3 IQ show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Broadcast

Broadcast address.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:

detail extensive none

ActiveSet when the link is active and the DTE and DCE are exchanging

information.

DownSet when the link is active, but no information is received from the

DCE.

DLCI statistics

UnconfiguredSet when the corresponding DLCI in the DCE is not configured.

ConfiguredSet when the corresponding DLCI in the DCE is configured.

Dce-configuredDisplayed when the command is issued from the DTE.

(Frame Relay) Data-link connection identifier (DLCI) statistics.

Active DLCINumber of active DLCIs.

Inactive DLCINumber of inactive DLCIs.

detail extensive none

Sample Output
show interfaces extensive (CT1)
user@host> show interfaces extensive ct1-0/1/1
Physical interface: ct1-0/1/1, Enabled, Physical link is Up
Interface index: 145, SNMP ifIndex: 32, Generation: 28
Link-level type: Controller, Clocking: Internal, Speed: T1,
Loopback: None, Framing: ESF, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps 16384
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 4 supported
Last flapped
: 2005-08-17 11:47:09 PDT (1d 03:38 ago)
Statistics last cleared: 2005-08-18 15:25:37 PDT (00:00:27 ago)
DS1
alarms
: None
DS1
defects : None
T1 media:
Seconds
Count State
SEF
0
0 OK
BEE
0
0 OK
AIS
0
0 OK
LOF
0
0 OK
LOS
0
0 OK
YELLOW
0
0 OK
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
0
0
CS
0
0
LES
0
ES
0

Copyright 2014, Juniper Networks, Inc.

1161

Interfaces Fundamentals for Routing Devices

SES
0
SEFS
0
BES
0
UAS
0
Line encoding: B8ZS
Buildout
: 0 to 132 feet
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)

show interfaces extensive (T1)

user@host> show interfaces extensive t1-0/2/0
Physical interface: t1-0/2/0, Enabled, Physical link is Up
Interface index: 161, SNMP ifIndex: 33, Generation: 61
Link-level type: PPP, MTU: 1504, Speed: T1, Loopback: None, FCS: 16,
Parent: ct1-0/2/0 Interface index 148
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps 16384
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent
: 43186
Full enquiries sent
: 8515
Enquiry responses received
: 43185
Full enquiry responses received
: 8515
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 0
Nonmatching DCE-end DLCIs:
2
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 4 supported
Last flapped
: 2005-09-07 15:43:47 PDT (00:00:06 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
14
0 bps
Input packets:
0
0 pps
Output packets:
1
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 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

1162

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

2 assured-forw
0
0
3 network-cont
1
1
DS1
alarms
: None
DS1
defects : None
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 1514, Runt threshold: 2
Timeslots
: All active
Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag:
flags, Start end flag: shared
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 4 (0x00)

0
0

show interfaces extensive (DS0)

user@host> show interfaces extensive ds-0/1/0:0
Physical interface: ds-0/1/0:1, Enabled, Physical link is Up
Interface index: 157, SNMP ifIndex: 52, Generation: 46
Link-level type: Frame-Relay, PPP, MTU: 1504, Clocking: Internal,
Speed: 640kbps, Loopback: None, FCS:16,
Parent: ct1-0/1/0 Interface index 143
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps 16384
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent
: 43186
Full enquiries sent
: 8515
Enquiry responses received
: 43185
Full enquiry responses received
: 8515
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 0
Nonmatching DCE-end DLCIs:
2
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 8 (last seen 00:00:12 ago)
Output: 8 (last sent 00:00:07 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Not-configured
CoS queues
: 4 supported
Last flapped
: 2005-08-18 15:23:46 PDT (00:03:17 ago)
Statistics last cleared: 2005-08-18 15:25:37 PDT (00:01:26 ago)
Traffic statistics:
Input bytes :
840
0 bps
Output bytes :
912
0 bps
Input packets:
25
0 pps
Output packets:
26
0 pps

Copyright 2014, Juniper Networks, Inc.

1163

Interfaces Fundamentals for Routing Devices

Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0, HS link CRC errors: 0,
Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 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
26
26
0
HDLC configuration:
Giant threshold: 1514, Runt threshold: 2
Timeslots
: 1-10
Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS0 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 4 (0x00)
Logical interface ds-0/1/0:1.0 (Index 67) (SNMP ifIndex 53) (Generation 11)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 26, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 11.11.11.0/30, Local: 11.11.11.2, Broadcast: 11.11.11.3,
Generation: 39
DLCI 100
Flags: Active, Dce-configured
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :2 Inactive DLCI : 0
...

1164

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Channelized T3 IQ)

Syntax

Release Information
Description

Options

show interfaces (ct3-fpc/pic/port | type-fpc/pic/port<:channel><:channel>)

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
channelized T3 IQ interface.
type-fpc/pic/port:channelInterface type. With optional corresponding channel levels,

the interface type can be one of the following:

type-fpc/pic/portFor the physical channelized T3 IQ interface, type is ct3.

type-fpc/pic/port:channelFor the clear channel, type is t3. At the first level of

channelization, type can be ct1 or t1.

type-fpc/pic/port:channel:channelAt the second level of channelization, type is

ds.

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.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces extensive (Channelized T3 IQ) (Physical) on page 1166

show interfaces extensive (Channelized T1 on Channelized T3 IQ) on page 1166
show interfaces extensive (DS0 on Channelized T3 IQ) on page 1166
See the output field table for the show interfaces (Channelized T1 IQ) command.

Copyright 2014, Juniper Networks, Inc.

1165

Interfaces Fundamentals for Routing Devices

Sample Output
show interfaces extensive (Channelized T3 IQ) (Physical)
user@host> show interfaces extensive ct3-0/0/1
Physical interface: ct3-0/0/1, Enabled, Physical link is Up
Interface index: 30, SNMP ifIndex: 317, Generation: 29
Link-level type: Controller, MTU: 4474, Clocking: Internal, Speed: T3,
Loopback: None, FCS: 16, Mode: C/Bit parity, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: None
...

show interfaces extensive (Channelized T1 on Channelized T3 IQ)

user@host> show interfaces extensive ct1-0/0/1:2
Physical interface: ct1-0/0/1:2, Enabled, Physical link is Up
Interface index: 175, SNMP ifIndex: 1505, Generation: 174
Link-level type: Controller, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF, Parent: ct3-0/0/1 (Index 32)
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: None
...

show interfaces extensive (DS0 on Channelized T3 IQ)

user@host> show interfaces extensive ds-0/0/1:2:1
Physical interface: ds-0/0/1:2:1, Enabled, Physical link is Up
Interface index: 176, SNMP ifIndex: 1563, Generation: 175
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: 640kbps,
Loopback: None, FCS: 16, Parent: ct1-0/0/1:2(Index 175)
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: Keepalives
...

1166

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Discard)

Syntax

Release Information
Description
Options

show interfaces dsc

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Display status information about the specified discard interface.
dscDisplay standard information about the specified discard interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
mediaThis option is not relevant for the discard interface and always shows a value of

0.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) This option is not relevant for the discard interface and always

shows a value of 0.
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show interfaces (ATM) on page 1028

show interfaces routing

show interfaces dsc on page 1170

show interfaces dsc brief on page 1170
show interfaces dsc detail on page 1170
show interfaces dsc extensive on page 1171
Table 59 on page 1167 lists the output fields for the show interfaces (discard) command.
Output fields are listed in the approximate order in which they appear.

Table 59: Discard show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface, whether the interface is enabled, and the state
of the physical interface: Up or Down.

All levels

Interface index

Physical interface's index number, which reflects its initialization sequence.

detail extensive none

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1167

Interfaces Fundamentals for Routing Devices

Table 59: Discard show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

SNMP ifIndex

SNMP index number for the physical interface.

detail extensive none

Type

Type of interface. Software-Pseudo indicates a standard software interface

with no associated hardware device.

All levels

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source. It can be Internal or External.

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 the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link type

Encapsulation being used on the physical interface.

detail extensive

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

detail extensive

Physical info

Information about the physical interface.

detail extensive

Hold-times

Current interface hold-time up and hold-time down. Value is in milliseconds.

detail extensive

Current address,
Hardware address

Configured MAC address and hardware MAC address.

detail extensive

Alternate link
address

Backup address of the link.

detail extensive

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).

detail extensive none

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

1168

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 59: Discard show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytes, Output bytesNumber of bytes received and transmitted on the

interface.

Input packets, Output packetsNumber of packets received and transmitted

on the interface.
Input errors

Input errors on the interface:

ErrorsSum of incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

detail extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

GiantsNumber of frames received that are larger than the giant threshold.

Policed discardsNumber 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.

Output errors

Resource errorsSum of transmit drops.

(Extensive only) Output errors on the interface. The following paragraphs explain
the counters whose meaning might not be obvious:

detail extensive

Carrier transitionsNumber 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
is malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

Logical Interface
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1169

Interfaces Fundamentals for Routing Devices

Table 59: Discard show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Protocol

Protocol family configured on the logical interface, such as iso, inet6, or mpls.

All levels

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route Table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Sample Output
show interfaces dsc
user@host> show interfaces dsc
Physical interface: dsc, Enabled, Physical link is Up
Interface index: 5, SNMP ifIndex: 5
Type: Software-Pseudo, MTU: Unlimited
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags
: None
Last flapped
: Never
Input packets : 0
Output packets: 0
Logical interface dsc.0 (Index 66) (SNMP ifIndex 235)
Flags: Point-To-Point SNMP-Traps Encapsulation: Unspecified
Protocol inet, MTU: Unlimited
Flags: None

show interfaces dsc brief

user@host> show interfaces dsc brief
Physical interface: dsc, Enabled, Physical link is Up
Type: Software-Pseudo, Link-level type: Unspecified, MTU: Unlimited, Clocking:
Unspecified, Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Logical interface dsc.0
Flags: Point-To-Point SNMP-Traps Encapsulation: Unspecified
inet

show interfaces dsc detail

user@host> show interfaces dsc detail
Physical interface: dsc, Enabled, Physical link is Up
Interface index: 5, SNMP ifIndex: 5, Generation: 9
Type: Software-Pseudo, Link-level type: Unspecified, MTU: Unlimited, Clocking:

1170

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Unspecified, Speed: Unspecified

Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Unspecified
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface dsc.0 (Index 66) (SNMP ifIndex 235) (Generation 6)
Flags: Point-To-Point SNMP-Traps Encapsulation: Unspecified
Protocol inet, MTU: Unlimited, Generation: 14, Route table: 0
Flags: None

show interfaces dsc extensive

user@host> show interfaces dsc extensive
Physical interface: dsc, Enabled, Physical link is Up
Interface index: 5, SNMP ifIndex: 5, Generation: 9
Type: Software-Pseudo, Link-level type: Unspecified, MTU: Unlimited, Clocking:
Unspecified, Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Unspecified
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: 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
Logical interface dsc.0 (Index 66) (SNMP ifIndex 235) (Generation 6)
Flags: Point-To-Point SNMP-Traps Encapsulation: Unspecified
Protocol inet, MTU: Unlimited, Generation: 14, Route table: 0

Copyright 2014, Juniper Networks, Inc.

1171

Interfaces Fundamentals for Routing Devices

show interfaces (Fast Ethernet)

Syntax

Release Information
Description
Options

show interfaces interface-type

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Display status information about the specified Fast Ethernet interface.
interface-typeOn M Series and T Series routers, the interface type is fe-fpc/pic/port. On

the J Series routers, the interface type is fe-pim/0/port.

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.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (Fast Ethernet) on page 1186

show interfaces brief (Fast Ethernet) on page 1186
show interfaces detail (Fast Ethernet) on page 1186
show interfaces extensive (Fast Ethernet) on page 1187
Table 60 on page 1172 lists the output fields for the show interfaces Fast Ethernet command.
Output fields are listed in the approximate order in which they appear.

Table 60: show interfaces Fast Ethernet Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

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

Physical Interface

1172

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

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

Link-mode

Type of link connection configured for the physical interface: Full-duplex or

extensive

Half-duplex
Speed

Speed at which the interface is running.

All levels

Loopback

Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback:

Local or Remote.

All levels

Source filtering

Source filtering status: Enabled or Disabled.

All levels

LAN-PHY mode

10-Gigabit Ethernet interface operating in Local Area Network Physical Layer

Device (LAN PHY) mode. LAN PHY allows 10-Gigabit Ethernet wide area links
to use existing Ethernet applications.

All levels

WAN-PHY mode

10-Gigabit Ethernet interface operating in Wide Area Network Physical 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.

All levels

Unidirectional

Unidirectional link mode status for 10-Gigabit Ethernet interface: Enabled or

Disabled for parent interface; Rx-only or Tx-only for child interfaces.

All levels

Flow control

Flow control status: Enabled or Disabled.

All levels

Auto-negotiation

(Gigabit Ethernet interfaces) Autonegotiation status: Enabled or Disabled.

All levels

Remote-fault

(Gigabit Ethernet interfaces) Remote fault status:

All levels

OnlineAutonegotiation is manually configured as online.

OfflineAutonegotiation is manually configured as offline.

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description on page 994.

All levels

Wavelength

(10-Gigabit Ethernet dense wavelength-division multiplexing [DWDM]

interfaces) Displays the configured wavelength, in nanometers (nm).

All levels

Copyright 2014, Juniper Networks, Inc.

1173

Interfaces Fundamentals for Routing Devices

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Frequency

(10-Gigabit Ethernet DWDM interfaces only) Displays the frequency associated

with the configured wavelength, in terahertz (THz).

All levels

CoS queues

Number of CoS queues configured.

detail extensive none

Schedulers

(GigabitEthernet intelligent queuing 2 (IQ2) interfaces only) Number of CoS

schedulers configured.

extensive

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

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 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).

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytesNumber of bytes received on the interface

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

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 (10-Gigabit Ethernet)
command.

1174

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Input errors

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber 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 errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

Policed discardsNumber 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 incompletesNumber 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 errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

FIFO errorsNumber 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 errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

1175

Interfaces Fundamentals for Routing Devices

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

CollisionsNumber 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 packetsNumber 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 errorsNumber 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 errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

Egress queues

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

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
(Egress)

1176

CoS queue number and its associated user-configured forwarding class name.

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

detail extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Ingress queues

Total number of ingress queues supported on the specified interface. Displayed

on IQ2 interfaces.

extensive

Queue counters
(Ingress)

CoS queue number and its associated user-configured forwarding class name.
Displayed on IQ2 interfaces.

extensive

Active alarms and

Active defects

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Ethernet-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain amount of time, it is promoted to an alarm.
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.

NoneThere are no active defects or alarms.

LinkInterface has lost its link state, which usually means that the cable is

detail extensive none

unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
OTN FEC statistics

The forward error correction (FEC) counters provide the following statistics:.

Corrected ErrorsThe count of corrected errors in the last second.

Corrected Error RatioThe 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) fault

conditions from the WAN PHY or the LAN PHY device.

detail extensive

Bit errorsThe number of seconds during which at least one bit error rate

(BER) occurred while the PCS receiver is operating in normal mode.

Errored blocksThe number of seconds when at least one errored block

occurred while the PCS receiver is operating in normal mode.

Copyright 2014, Juniper Networks, Inc.

1177

Interfaces Fundamentals for Routing Devices

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

MAC statistics

Receive and Transmit statistics reported by the PIC's MAC subsystem, including

extensive

the following:

Total octets and total packetsTotal 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 (10-Gigabit
Ethernet) command.

Unicast packets, Broadcast packets, and Multicast packetsNumber of unicast,

broadcast, and multicast packets.

CRC/Align errorsTotal 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 errorNumber 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 framesNumber of MAC control frames.

MAC pause framesNumber of MAC control frames with pause operational

code.

Oversized framesNumber of frames that exceed 1518 octets.

Jabber framesNumber 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 framesTotal 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 framesNumber 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 violationsNumber of times an event caused the PHY to indicate Data

reception error or invalid data symbol error.

OTN Received
Overhead Bytes

APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58 Payload

Type: 0x08

extensive

OTN Transmitted
Overhead Bytes

APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00

Payload Type: 0x08

extensive

1178

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

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 should enter the system or be rejected.

Input packet countNumber of packets received from the MAC hardware

that the filter processed.

Input packet rejectsNumber of packets that the filter rejected because of

either the source MAC address or the destination MAC address.

Input DA rejectsNumber 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 rejectsNumber 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 countNumber of packets that the filter has given to the MAC

hardware.

Output packet pad countNumber 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 countNumber 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 filtersNumber 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:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

extensive

Subfields are:

PHY LockPhase-locked loop

PHY LightLoss of optical signal

Copyright 2014, Juniper Networks, Inc.

1179

Interfaces Fundamentals for Routing Devices

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

WIS section

(10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information:

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

Subfields are:

WIS line

BIP-B1Bit interleaved parity for SONET section overhead

SEFSeverely errored framing

LOLLoss of light

LOFLoss of frame

ES-SErrored seconds (section)

SES-SSeverely errored seconds (section)

SEFS-SSeverely errored framing seconds (section)

(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

1180

BIP-B2Bit interleaved parity for SONET line overhead

REI-LRemote error indication (near-end line)

RDI-LRemote defect indication (near-end line)

AIS-LAlarm indication signal (near-end line)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

ES-LErrored seconds (near-end line)

SES-LSeverely errored seconds (near-end line)

UAS-LUnavailable seconds (near-end line)

ES-LFEErrored seconds (far-end line)

SES-LFESeverely errored seconds (far-end line)

UAS-LFEUnavailable seconds (far-end line)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

WIS path

(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

Subfields are:

BIP-B3Bit interleaved parity for SONET section overhead

REI-PRemote error indication

LOP-PLoss of pointer (path)

AIS-PPath alarm indication signal

RDI-PPath remote defect indication

UNEQ-PPath unequipped

PLM-PPath payload (signal) label mismatch

ES-PErrored seconds (near-end STS path)

SES-PSeverely errored seconds (near-end STS path)

UAS-PUnavailable seconds (near-end STS path)

SES-PFESeverely errored seconds (far-end STS path)

UAS-PFEUnavailable seconds (far-end STS path)

Copyright 2014, Juniper Networks, Inc.

1181

Interfaces Fundamentals for Routing Devices

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Autonegotiation
information

Information about link autonegotiation.

extensive

Negotiation status:

IncompleteEthernet interface has the speed or link mode configured.

No autonegotiationRemote Ethernet interface has the speed or link mode

configured, or does not perform autonegotiation.

CompleteEthernet interface is connected to a device that performs

autonegotiation and the autonegotiation process is successful.

Link partner statusOK when Ethernet interface is connected to a device that

performs autonegotiation and the autonegotiation process is successful.

Link partner:

Link modeDepending on the capability of the attached Ethernet device,

either Full-duplex or Half-duplex.

Flow controlTypes 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 faultRemote fault information from the link partnerFailure

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 resolutionInformation from the link partner:

Flow controlTypes 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 faultRemote fault information. Link OK (no error detected on

receive), Offline (local interface is offline), and Link Failure (link error

detected on receive).
Received path
trace, Transmitted
path trace

(10-Gigabit Ethernet interfaces, WAN PHY mode) SONET/SDH interfaces allow

path trace bytes to be sent inband across the SONET/SDH link. Juniper Networks
and other routing device 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 routing
device at the other end of the fiber. The transmitted path trace value is the
message that this routing device transmits.

extensive

Packet Forwarding
Engine
configuration

Information about the configuration of the Packet Forwarding Engine:

extensive

1182

Destination slotFPC slot number.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Copyright 2014, Juniper Networks, Inc.

1183

Interfaces Fundamentals for Routing Devices

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

VLAN-Tag

Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN
tag or for both the outer and inner (In) VLAN tags.

brief detail extensive

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

popThe outer VLAN tag of the incoming frame is removed.

swapThe outer VLAN tag of the incoming frame is overwritten with the user

none

specified VLAN tag information.

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

push-pushTwo VLAN tags are pushed in from the incoming frame.

swap-pushThe 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-swapBoth the inner and the outer VLAN tags of the incoming frame

are replaced by the user specified VLAN tag value.

pop-swapThe 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-popBoth 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

demux underlying interface. The output is one of the following:

Source Family Inet

Destination Family Inet

detail extensive none

Encapsulation

Encapsulation on the logical interface.

All levels

Protocol

Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description on page 994.

detail 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
the logical interface.

detail extensive none

Traffic statistics

Number and rate of bytes and packets received and transmitted on the specified
interface set.

detail extensive

Input bytes, Output bytesNumber of bytes received and transmitted on the

interface set

Input packets, Output packetsNumber of packets received and transmitted

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.

extensive

Local statistics

Number and rate of bytes and packets destined to the routing device.

extensive

1184

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

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.
Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route Table

Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive none

Flags

Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description on page 994.

detail extensive

Donor interface

(Unnumbered Ethernet) Interface from which an unnumbered Ethernet interface

borrows an IPv4 address.

detail extensive none

Preferred source
address

(Unnumbered Ethernet) Secondary IPv4 address of the donor loopback interface

that acts as the preferred source address for the unnumbered Ethernet interface.

detail extensive none

Input Filters

Names of any input filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.

detail extensive

Output Filters

Names of any output filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.

detail extensive

Mac-Validate
Failures

Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail extensive none

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.

brief

Flags

Information about address flag (possible values are described in the Addresses
Flags section under Common Output Fields Description on page 994.

detail 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

Copyright 2014, Juniper Networks, Inc.

1185

Interfaces Fundamentals for Routing Devices

Table 60: show interfaces Fast Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Sample Output
show interfaces (Fast Ethernet)
user@host> show interfaces fe-0/0/0
Physical interface: fe-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 22
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 4 supported, 4 maximum usable queues
Current address: 00:05:85:02:38:00, Hardware address: 00:05:85:02:38:00
Last flapped
: 2006-01-20 14:50:58 PST (2w4d 00:44 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Active alarms : None
Active defects : None
Logical interface fe-0/0/0.0 (Index 66) (SNMP ifIndex 198)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255

show interfaces brief (Fast Ethernet)

user@host> show interfaces fe-0/0/0 brief
Physical interface: fe-0/0/0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Logical interface fe-0/0/0.0
Flags: SNMP-Traps Encapsulation: ENET2
inet 10.10.10.1/24

show interfaces detail (Fast Ethernet)

user@host> show interfaces fe-0/0/0 detail
Physical interface: fe-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 22, Generation: 5391
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:02:38:00, Hardware address: 00:05:85:02:38:00
Last flapped
: 2006-01-20 14:50:58 PST (2w4d 00:45 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
42
0 bps

1186

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input packets:
0
0 pps
Output packets:
1
0 pps
Active alarms : None
Active defects : None
Logical interface fe-0/0/0.0 (Index 66) (SNMP ifIndex 198) (Generation 67)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 105, Route table: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255,
Generation: 136

show interfaces extensive (Fast Ethernet)

user@host> show interfaces fe-0/0/0 extensive
Physical interface: fe-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 22, Generation: 5391
Link-level type: Ethernet, MTU: 1514, Link-mode: Full-duplex, Speed:
100mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:02:38:00, Hardware address: 00:05:85:02:38:00
Last flapped
: 2006-01-20 14:50:58 PST (2w4d 00:46 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
42
0 bps
Input packets:
0
0 pps
Output packets:
1
0 pps
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:
Carrier transitions: 3, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Active alarms : None
Active defects : None
MAC statistics:
Receive
Transmit
Total octets
0
64
Total packets
0
1
Unicast packets
0
0
Broadcast packets
0
1
Multicast packets
0
0
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
Filter statistics:
Input packet count
0
Input packet rejects
0

Copyright 2014, Juniper Networks, Inc.

1187

Interfaces Fundamentals for Routing Devices

Input DA rejects
0
Input SA rejects
0
Output packet count
1
Output packet pad count
0
Output packet error count
0
CAM destination filters: 1, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link partner: Full-duplex, Flow control: None, Remote fault: Ok
Local resolution:
Packet Forwarding Engine configuration:
Destination slot: 0
CoS information:
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 fe-0/0/0.0 (Index 66) (SNMP ifIndex 198) (Generation 67)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 105, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255,
Generation: 136

1188

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (Gigabit Ethernet)

Syntax

Release Information
Description

Options

show interfaces ge-fpc/pic/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series, T Series, and MX Series routers and EX Series switches only) Display status
information about the specified Gigabit Ethernet interface.
ge-fpc/pic/portDisplay standard information about the specified Gigabit Ethernet

interface.
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.

Additional Information

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

In a logical system, this command displays information only about the logical interfaces
and not about the physical interfaces.
view

Verifying and Managing Agent Circuit Identifier-Based Dynamic VLAN Configuration

show interfaces (Gigabit Ethernet) on page 1205

show interfaces (Gigabit Ethernet on MX Series Routers) on page 1205
show interfaces extensive (Gigabit Ethernet on MX Series Routers showing interface
transmit statistics configuration) on page 1206
show interfaces brief (Gigabit Ethernet) on page 1206
show interfaces detail (Gigabit Ethernet) on page 1207
show interfaces extensive (Gigabit Ethernet IQ2) on page 1208
show interfaces (Gigabit Ethernet Unnumbered Interface) on page 1211
show interfaces (ACI Interface Set Configured) on page 1211
Table 61 on page 1190 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 62 on page 1204.

Copyright 2014, Juniper Networks, Inc.

1189

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

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

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 loopback:

Local or Remote.

All levels

Source filtering

Source filtering status: Enabled or Disabled.

All levels

LAN-PHY mode

10-Gigabit Ethernet interface operating in Local Area Network Physical Layer

Device (LAN PHY) mode. LAN PHY allows 10-Gigabit Ethernet wide area links
to use existing Ethernet applications.

All levels

WAN-PHY mode

10-Gigabit Ethernet interface operating in Wide Area Network Physical 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.

All levels

Unidirectional

Unidirectional link mode status for 10-Gigabit Ethernet interface: Enabled or

Disabled for parent interface; Rx-only or Tx-only for child interfaces.

All levels

Flow control

Flow control status: Enabled or Disabled.

All levels

Auto-negotiation

(Gigabit Ethernet interfaces) Autonegotiation status: Enabled or Disabled.

All levels

Remote-fault

(Gigabit Ethernet interfaces) Remote fault status:

All levels

Physical Interface

OnlineAutonegotiation is manually configured as online.

OfflineAutonegotiation is manually configured as offline.

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

1190

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Link flags

Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description on page 994.

All levels

Wavelength

(10-Gigabit Ethernet dense wavelength-division multiplexing [DWDM]

interfaces) Displays the configured wavelength, in nanometers (nm).

All levels

Frequency

(10-Gigabit Ethernet DWDM interfaces only) Displays the frequency associated

with the configured wavelength, in terahertz (THz).

All levels

CoS queues

Number of CoS queues configured.

detail extensive none

Schedulers

(Gigabit Ethernet intelligent queuing 2 [IQ2] interfaces only) Number of CoS

schedulers configured.

extensive

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 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).

detail extensive none

Input Rate

Input rate in bits per second (bps) and packets per second (pps). 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.

None

Output Rate

Output rate in bps and pps. 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.

None

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Egress account
overhead

Layer 2 overhead in bytes that is accounted in the interface statistics for egress
traffic.

detail extensive

Ingress account
overhead

Layer 2 overhead in bytes that is accounted in the interface statistics for ingress
traffic.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1191

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytesNumber 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 bytesNumber 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.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

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 (10-Gigabit Ethernet)
command.
Input errors

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

Policed discardsNumber 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 incompletesNumber 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 errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

FIFO errorsNumber 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.

1192

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

CollisionsNumber 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 packetsNumber 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 errorsNumber 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 errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

Egress queues

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

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

Copyright 2014, Juniper Networks, Inc.

1193

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Queue counters
(Egress)

CoS queue number and its associated user-configured forwarding class name.

detail extensive

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber 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. Displayed

on IQ2 interfaces.

extensive

Queue counters
(Ingress)

CoS queue number and its associated user-configured forwarding class name.
Displayed on IQ2 interfaces.

extensive

Active alarms and

Active defects

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Ethernet-specific defects that can prevent the interface from passing 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.

NoneThere are no active defects or alarms.

LinkInterface has lost its link state, which usually means that the cable is

detail extensive none

unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
Interface transmit
statistics

(On MX Series devices) Status of the interface-transmit-statistics configuration:

Enabled or Disabled.

detail extensive

EnabledWhen 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.

DisabledWhen 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 statistics:

Corrected ErrorsThe count of corrected errors in the last second.

Corrected Error RatioThe corrected error ratio in the last 25 seconds. For

detail extensive

example, 1e-7 is 1 error per 10 million bits.

1194

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

PCS statistics

(10-Gigabit Ethernet interfaces) Displays Physical Coding Sublayer (PCS) fault

conditions from the WAN PHY or the LAN PHY device.

detail extensive

Bit errorsThe number of seconds during which at least one bit error rate

(BER) occurred while the PCS receiver is operating in normal mode.

Errored blocksThe number of seconds when at least one errored block

occurred while the PCS receiver is operating in normal mode.

Copyright 2014, Juniper Networks, Inc.

1195

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

MAC statistics

Receive and Transmit statistics reported by the PIC's MAC subsystem, including

extensive

the following:

Total octets and total packetsTotal 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 (10-Gigabit
Ethernet) command.

Unicast packets, Broadcast packets, and Multicast packetsNumber of unicast,

broadcast, and multicast packets.

CRC/Align errorsTotal 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 errorNumber 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 framesNumber of MAC control frames.

MAC pause framesNumber of MAC control frames with pause operational

code.

Oversized framesThere are two possible conditions regarding the number

of oversized frames:

Packet length exceeds 1518 octets, or

Packet length exceeds MRU

Jabber framesNumber 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 framesTotal 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 framesNumber 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.
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 violationsNumber of times an event caused the PHY to indicate Data

reception error or invalid data symbol error.

OTN Received
Overhead Bytes

APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58 Payload

Type: 0x08

extensive

OTN Transmitted
Overhead Bytes

APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00

Payload Type: 0x08

extensive

1196

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

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 should enter the system or be rejected.

Input packet countNumber of packets received from the MAC hardware

that the filter processed.

Input packet rejectsNumber of packets that the filter rejected because of

either the source MAC address or the destination MAC address.

Input DA rejectsNumber 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 rejectsNumber 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 countNumber of packets that the filter has given to the MAC

hardware.

Output packet pad countNumber 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 countNumber 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 filtersNumber 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:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

extensive

Subfields are:

PHY LockPhase-locked loop

PHY LightLoss of optical signal

Copyright 2014, Juniper Networks, Inc.

1197

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

WIS section

(10-Gigabit Ethernet interfaces, WAN PHY mode) SONET error information:

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

Subfields are:

WIS line

BIP-B1Bit interleaved parity for SONET section overhead

SEFSeverely errored framing

LOLLoss of light

LOFLoss of frame

ES-SErrored seconds (section)

SES-SSeverely errored seconds (section)

SEFS-SSeverely errored framing seconds (section)

(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information:

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

extensive

Subfields are:

1198

BIP-B2Bit interleaved parity for SONET line overhead

REI-LRemote error indication (near-end line)

RDI-LRemote defect indication (near-end line)

AIS-LAlarm indication signal (near-end line)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

ES-LErrored seconds (near-end line)

SES-LSeverely errored seconds (near-end line)

UAS-LUnavailable seconds (near-end line)

ES-LFEErrored seconds (far-end line)

SES-LFESeverely errored seconds (far-end line)

UAS-LFEUnavailable seconds (far-end line)

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

WIS path

(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information:

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. Any state other than OK indicates a problem.

Subfields are:

BIP-B3Bit interleaved parity for SONET section overhead

REI-PRemote error indication

LOP-PLoss of pointer (path)

AIS-PPath alarm indication signal

RDI-PPath remote defect indication

UNEQ-PPath unequipped

PLM-PPath payload (signal) label mismatch

ES-PErrored seconds (near-end STS path)

SES-PSeverely errored seconds (near-end STS path)

UAS-PUnavailable seconds (near-end STS path)

SES-PFESeverely errored seconds (far-end STS path)

UAS-PFEUnavailable seconds (far-end STS path)

Copyright 2014, Juniper Networks, Inc.

1199

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Autonegotiation
information

Information about link autonegotiation.

extensive

Negotiation status:

IncompleteEthernet interface has the speed or link mode configured.

No autonegotiationRemote Ethernet interface has the speed or link mode

configured, or does not perform autonegotiation.

CompleteEthernet interface is connected to a device that performs

autonegotiation and the autonegotiation process is successful.

Link partner statusOK when Ethernet interface is connected to a device that

performs autonegotiation and the autonegotiation process is successful.

Link partnerInformation from the remote Ethernet device:

Link modeDepending on the capability of the link partner, either

Full-duplex or Half-duplex.

Flow controlTypes 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 faultRemote fault information from the link partnerFailure

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 resolutionInformation from the local Ethernet device:

Flow controlTypes 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 faultRemote fault information. Link OK (no error detected on

receive), Offline (local interface is offline), and Link Failure (link error

detected on receive).
Received path
trace, Transmitted
path trace

(10-Gigabit Ethernet interfaces, WAN PHY mode) 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
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.

extensive

Packet Forwarding
Engine
configuration

Information about the configuration of the Packet Forwarding Engine:

extensive

1200

Destination slotFPC slot number.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Copyright 2014, Juniper Networks, Inc.

1201

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

VLAN-Tag

Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN
tag or for both the outer and inner (In) VLAN tags.

brief detail extensive

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

popThe outer VLAN tag of the incoming frame is removed.

swapThe outer VLAN tag of the incoming frame is overwritten with the

none

user-specified VLAN tag information.

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

push-pushTwo VLAN tags are pushed in from the incoming frame.

swap-pushThe 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-swapBoth the inner and the outer VLAN tags of the incoming frame

are replaced by the user-specified VLAN tag value.

pop-swapThe 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-popBoth 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

demux underlying interface. The output is one of the following:

Source Family Inet

Destination Family Inet

detail extensive none

Encapsulation

Encapsulation on the logical interface.

All levels

ACI VLAN: Dynamic

Profile

Name of the dynamic profile that defines the agent circuit identifier (ACI)
interface set. If configured, the ACI interface set enables the underlying Ethernet
interface to create dynamic VLAN subscriber interfaces based on ACI
information.

brief detail extensive

Protocol

Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description on page 994.

detail extensive none

MTU

Maximum transmission unit size on the logical interface.

detail extensive none

Dynamic Profile

(MX Series routers with Trio MPCs only) Name of the dynamic profile that was
used to create this interface configured with a Point-to-Point Protocol over
Ethernet (PPPoE) family.

detail extensive none

Service Name Table

(MX Series routers with Trio MPCs only) Name of the service name table for
the interface configured with a PPPoE family.

detail extensive none

Max Sessions

(MX Series routers with Trio MPCs only) Maximum number of PPPoE logical
interfaces that can be activated on the underlying interface.

detail extensive none

1202

none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Duplicate
Protection

(MX Series routers with Trio MPCs only) State of PPPoE duplicate protection:
On or Off. When duplicate 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.

detail extensive none

Direct Connect

State of the configuration to ignore DSL Forum VSAs: On or Off. When configured,
the router ignores any of these VSAs received from a directly connected CPE
device on the interface.

detail extensive none

AC Name

Name of the access concentrator.

detail extensive none

Maximum labels

Maximum number of MPLS labels configured for the MPLS protocol family on
the logical interface.

detail extensive none

Traffic statistics

Number and rate of bytes and packets received and transmitted on the specified
interface set.

detail extensive

Input bytes, Output bytesNumber 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 packetsNumber of packets received and transmitted

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.

extensive

Local statistics

Number and rate of bytes and packets destined to the router.

extensive

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.
Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route Table

Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive none

Flags

Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description on page 994.

detail extensive

Donor interface

(Unnumbered Ethernet) Interface from which an unnumbered Ethernet interface

borrows an IPv4 address.

detail extensive none

Copyright 2014, Juniper Networks, Inc.

1203

Interfaces Fundamentals for Routing Devices

Table 61: show interfaces Gigabit Ethernet Output Fields (continued)

Field Name

Field Description

Level of Output

Preferred source
address

(Unnumbered Ethernet) Secondary IPv4 address of the donor loopback interface

that acts as the preferred source address for the unnumbered Ethernet interface.

detail extensive none

Input Filters

Names of any input filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parentheses next to all interfaces.

detail extensive

Output Filters

Names of any output filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parentheses next to all interfaces.

detail extensive

Mac-Validate
Failures

Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail extensive none

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.

brief

Flags

Information about the address flag. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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 interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Table 62: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type
Interface Type

Sample Command

Byte and Octet Counts Include

Comments

Inbound physical
interface

show interfaces
ge-0/3/0 extensive

Traffic statistics:

The additional 4 bytes are

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
ge-0/3/0.50 extensive

Traffic statistics:
Input bytes: 478 bytes per packet, representing
the Layer 3 packet

1204

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 62: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type (continued)
Interface Type

Sample Command

Byte and Octet Counts Include

Comments

Outbound physical
interface

show interfaces
ge-0/0/0 extensive

Traffic statistics:

For input bytes, the

additional 12 bytes include
6 bytes for the destination
MAC address plus 4 bytes
for VLAN plus 2 bytes for
the Ethernet type.

Input bytes: 490 bytes per packet, representing

the Layer 3 packet + 12 bytes
MAC statistics:
Received octets: 478 bytes per packet,
representing the Layer 3 packet
Outbound logical
interface

show interfaces
ge-0/0/0.50 extensive

Traffic statistics:
Input bytes: 478 bytes per packet, representing
the Layer 3 packet

Sample Output
show interfaces (Gigabit Ethernet)
user@host> show interfaces ge-3/0/2
Physical interface: ge-3/0/2, Enabled, Physical link is Up
Interface index: 167, SNMP ifIndex: 35
Link-level type: 52, MTU: 1522, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 4 supported, 4 maximum usable queues
Current address: 00:05:85:4a:e9:7c, Hardware address: 00:05:85:4a:e9:7c
Last flapped
: 2006-08-10 17:25:10 PDT (00:01:08 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Ingress rate at Packet Forwarding Engine
: 0 bps (0 pps)
Ingress drop rate at Packet Forwarding Engine : 0 bps (0 pps)
Active alarms : None
Active defects : None
Logical interface ge-3/0/2.0 (Index 72) (SNMP ifIndex 69)
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)

user@host> show interfaces ge-2/2/2
Physical interface: ge-2/2/2, Enabled, Physical link is Up
Interface index: 156, SNMP ifIndex: 188
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, MAC-REWRITE Error: None,
Loopback: Disabled,

Copyright 2014, Juniper Networks, Inc.

1205

Interfaces Fundamentals for Routing Devices

Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,

Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 4 maximum usable queues
Schedulers
: 0
Current address: 00:1f:12:b7:d7:c0, Hardware address: 00:1f:12:b7:d6:76
Last flapped
: 2008-09-05 16:44:30 PDT (3d 01:04 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Active alarms : None
Active defects : None
Logical interface ge-2/2/2.0 (Index 82) (SNMP ifIndex 219)
Flags: SNMP-Traps 0x20000000 Encapsulation: Ethernet-Bridge
Egress account overhead: 100
Ingress account overhead: 90
Input packets : 0
Output packets: 0
Protocol aenet, AE bundle: ae0.0
Link Index: 4

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"
Physical interface: ge-2/1/2, Enabled, Physical link is Up
Interface index: 151, SNMP ifIndex: 530, Generation: 154
Interface flags: SNMP-Traps Internal: 0x4000
Output bytes :
240614363944
772721536 bps
Output packets:
3538446506
1420444 pps
Direction : Output
Interface transmit statistics: Enabled
Logical interface ge-2/1/2.0 (Index 331) (SNMP ifIndex 955) (Generation 146)
Output bytes :
195560312716
522726272 bps
Output packets:
4251311146
1420451 pps

show interfaces brief (Gigabit Ethernet)

user@host> show interfaces ge-3/0/2 brief
Physical interface: ge-3/0/2, Enabled, Physical link is Up
Link-level type: 52, MTU: 1522, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
Logical interface ge-3/0/2.0
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
ccc
Logical interface ge-3/0/2.32767
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x0000.0 ]

1206

Encapsulation: ENET2

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces detail (Gigabit Ethernet)

user@host> show interfaces ge-3/0/2 detail
Physical interface: ge-3/0/2, Enabled, Physical link is Up
Interface index: 167, SNMP ifIndex: 35, Generation: 177
Link-level type: 52, MTU: 1522, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:4a:e9:7c, Hardware address: 00:05:85:4a:e9:7c
Last flapped
: 2006-08-09 17:17:00 PDT (01:31:33 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Ingress traffic statistics at Packet Forwarding Engine:
Input bytes :
0
0 bps
Input packets:
0
0 pps
Drop
bytes :
0
0 bps
Drop
packets:
0
0 pps
Ingress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Egress queues: 4 supported, 4 in use

Queue counters:
Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Active alarms : None

Active defects : None
Logical interface ge-3/0/2.0 (Index 72) (SNMP ifIndex 69) (Generation 140)
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
Traffic statistics:
Input bytes :
0
Output bytes :
0

Copyright 2014, Juniper Networks, Inc.

1207

Interfaces Fundamentals for Routing Devices

Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol ccc, MTU: 1522, Generation: 149, Route table: 0
Flags: Is-Primary

0
0
0
0

bps
bps
pps
pps

Logical interface ge-3/0/2.32767 (Index 71) (SNMP ifIndex 70)

(Generation 139)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x0000.0 ] Encapsulation: ENET2
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps

show interfaces extensive (Gigabit Ethernet IQ2)

user@host> show interfaces ge-7/1/3 extensive
Physical interface: ge-7/1/3, Enabled, Physical link is Up
Interface index: 170, SNMP ifIndex: 70, Generation: 171
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4004000
Link flags
: None
CoS queues
: 8 supported, 4 maximum usable queues
Schedulers
: 256
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:14:f6:30:5e:74, Hardware address: 00:14:f6:30:5e:74
Last flapped
: 2007-11-07 21:31:41 PST (02:03:33 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
38910844056
7952 bps
Output bytes :
7174605
8464 bps
Input packets:
418398473
11 pps
Output packets:
78903
12 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0

1208

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Ingress traffic statistics at Packet Forwarding Engine:

Input bytes :
38910799145
7952 bps
Input packets:
418397956
11 pps
Drop
bytes :
0
0 bps
Drop
packets:
0
0 pps
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:
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
Ingress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

418390823

418390823

1 expedited-fo

2 assured-forw

3 network-cont

7133

7133

Egress queues: 4 supported, 4 in use

Queue counters:
Queued packets

Transmitted packets

Dropped packets

1031

1031

1 expedited-fo

2 assured-forw

3 network-cont

77872

77872

0 best-effort

Active alarms : None

Active defects : None
MAC statistics:
Receive
Transmit
Total octets
38910844056
7174605
Total packets
418398473
78903
Unicast packets
408021893366
1026
Broadcast packets
10
12
Multicast packets
418398217
77865
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 OTN Received Overhead Bytes:
APS/PCC0: 0x02, APS/PCC1: 0x11, APS/PCC2: 0x47, APS/PCC3: 0x58
Payload Type: 0x08
OTN Transmitted Overhead Bytes:
APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00
Payload Type: 0x08
Filter statistics:
Input packet count
418398473
Input packet rejects
479
Input DA rejects
479

Copyright 2014, Juniper Networks, Inc.

1209

Interfaces Fundamentals for Routing Devices

Input SA rejects
0
Output packet count
78903
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:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric,
Remote fault: OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Packet Forwarding Engine configuration:
Destination slot: 7
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Buffer
Priority
%
bps
%
usec
0 best-effort
95
950000000
95
0
low
none
3 network-control
5
50000000
5
0
low
none
Direction : Input
CoS transmit queue
Bandwidth
Buffer
Priority
%
bps
%
usec
0 best-effort
95
950000000
95
0
low
none
3 network-control
5
50000000
5
0
low
none

Limit

Limit

Logical interface ge-7/1/3.0 (Index 70) (SNMP ifIndex 85) (Generation 150)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
812400
Output bytes :
1349206
Input packets:
9429
Output packets:
9449
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
812400
Output bytes :
1349206
Input packets:
9429
Output packets:
9449
Transit statistics:
Input bytes :
0
7440 bps
Output bytes :
0
7888 bps
Input packets:
0
10 pps
Output packets:
0
11 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 169, Route table: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Addresses, Flags: Is-Preferred Is-Primary

1210

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

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: 10.74.2/24, Local: 10.74.2.2, Broadcast: 10.74.2.255,
Generation: 196
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 61 on page 1190.
show interfaces (Gigabit Ethernet Unnumbered Interface)
user@host> show interfaces ge-3/2/0
Physical interface: ge-3/2/0, Enabled, Physical link is Up
Interface index: 148, SNMP ifIndex: 50
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 4 maximum usable queues
Current address: 00:14:f6:11:26:f8, Hardware address: 00:14:f6:11:26:f8
Last flapped
: 2006-10-27 04:42:23 PDT (08:01:52 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 624 bps (1 pps)
Active alarms : None
Active defects : None
Logical interface ge-3/2/0.0 (Index 67) (SNMP ifIndex 85)
Flags: SNMP-Traps Encapsulation: ENET2
Input packets : 0
Output packets: 6
Protocol inet, MTU: 1500
Flags: Unnumbered
Donor interface: lo0.0 (Index 64)
Preferred source address: 22.22.22.22

show interfaces (ACI Interface Set Configured)

user@host> show interfaces ge-1/0/0.4001
Logical interface ge-1/0/0.4001 (Index 340) (SNMP ifIndex 548)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.4001 ] Encapsulation: PPP-overEthernet
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

Copyright 2014, Juniper Networks, Inc.

1211

Interfaces Fundamentals for Routing Devices

Input packets : 9
Output packets: 8
Protocol multiservice, MTU: Unlimited

1212

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (ISDN B-Channel)

Syntax

Release Information

show interfaces bc-pim/0/port:channel

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Description

(J Series routers only) Display information about the specified ISDN B-channel interface.

Options

bc-pim/0/port:channelDisplay standard information about the specified ISDN B-channel

interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display the interface description string.
media(Optional) Display media-specific information.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) Display static interface statistics.

Additional Information
Required Privilege
Level
List of Sample Output

Output Fields

There are no user-configurable fields on B-channel interfaces.

view

show interfaces (ISDN B-Channel) on page 1216

show interfaces brief (ISDN B-Channel) on page 1217
show interfaces detail (ISDN B-Channel) on page 1217
show interfaces extensive (ISDN B-Channel) on page 1217
Table 63 on page 1213 lists the output fields for the show interfaces (ISDN B-channel)
command. Output fields are listed in the approximate order in which they appear.

Table 63: ISDN B-Channel show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical Interface

Name of the physical interface type.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Fiel section
under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

SNMP index number for the physical interface.

detail extensive none

Copyright 2014, Juniper Networks, Inc.

1213

Interfaces Fundamentals for Routing Devices

Table 63: ISDN B-Channel show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Type

Type of interface.

All levels

Link-level type

Encapsulation used on the physical interface.

All levels

MTU

Maximum transmission unit (MTU)Size of the largest packet to be transmitted.

All levels

Clocking

Reference clock source of the interface.

All levels

Speed

Network speed on the interface.

All levels

Parent

Name and interface index of the interface to which a particular child interface
belongs. None indicates that this is the top level.

detail extensive none

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link type

Data transmission type.

detail extensive none

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

detail extensive

Physical info

Information about the physical interface.

detail extensive

Hold-times

Current interface hold-time up and hold-time down. Value is in milliseconds.

detail extensive

Current address

Configured media access control (MAC) address.

detail extensive

Hardware address

MAC address of the hardware.

detail extensive

Alternate link
address

Backup address of the link.

detail extensive

CoS queues

Number of class-of-service (CoS) queues configured.

detail extensive none

Last flapped

Date, time, and length of time since the interface changed its status from down
to up.

detail extensive none

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

Statistics last
cleared

Time when the interface statistics were last set to zero.

detail extensive

1214

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 63: ISDN B-Channel show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Traffic statistics

Number and rate of bytes and packets received and transmitted on the logical
and physical interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

ErrorsInput errors on the interface.

DropsNumber of packets dropped by the output queue of the I/O Manager

extensive

ASIC.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsFrames received smaller than the runt threshold.

GiantsFrames received larger than the giant threshold.

Policed discardsFrames that the incoming packet match code discarded

because they were not recognized or were not of interest. Usually, this field
reports protocols that the Junos OS does not support.

Output errors

Resource errorsSum of transmit drops.

Carrier transitionsNumber of times the interface has gone from down to up.

extensive

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,
possibly once every 10 seconds, the cable, the remote system, or the interface
is malfunctioning.

ErrorsSum of outgoing frame aborts and FCS errors.

DropsNumber 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 dropped by the ASIC RED mechanism.

Queue counters

Packet Forwarding
Engine
configuration

MTU errorsNumber of packets larger than the MTU threshold.

Resource errorsSum of transmit drops.

CoS queue number and its associated user-configured forwarding class name.

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

Copyright 2014, Juniper Networks, Inc.

detail extensive

extensive

1215

Interfaces Fundamentals for Routing Devices

Table 63: ISDN B-Channel show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Sample Output
show interfaces (ISDN B-Channel)
user@host> show interfaces bc-4/0/0:1
Physical interface: bc-4/0/0:1, Enabled, Physical link is Up
Interface index: 151, SNMP ifIndex: 75
Type: Serial, Link-level type: 57, MTU: 4092, Clocking: Internal,
Speed: 64kbps,
Parent: br-4/0/0 Interface index 129
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-06-13 19:50:38 PDT (14:39:03 ago)
Input rate
: 0 bps (0 pps)

1216

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Output rate

: 0 bps (0 pps)

Logical interface bc-4/0/0:1.0 (Index 74) (SNMP ifIndex 79)

Flags: Point-To-Point SNMP-Traps Encapsulation: 64

show interfaces brief (ISDN B-Channel)

user@host> show interfaces bc-4/0/0:1 brief
Physical interface: bc-4/0/0:1, Enabled, Physical link is Up
Type: Serial, Link-level type: 57, MTU: 4092, Clocking: Internal,
Speed: 64kbps
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Logical interface bc-4/0/0:1.0
Flags: Point-To-Point SNMP-Traps Encapsulation: 64

show interfaces detail (ISDN B-Channel)

user@host> show interfaces bc-4/0/0:1 detail
Physical interface: bc-4/0/0:1, Enabled, Physical link is Up
Interface index: 151, SNMP ifIndex: 75, Generation: 152
Type: Serial, Link-level type: 57, MTU: 4092, Clocking: Internal,
Speed: 64kbps,
Parent: br-4/0/0 Interface index 129
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-06-13 19:50:38 PDT (14:39:06 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
4096
0 bps
Output bytes :
128423
96 bps
Input packets:
0
0 pps
Output packets:
9801
0 pps
Egress queues: 8 supported, 8 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

13

13

1 expedited-fo

2 assured-forw

3 network-cont

9788

9788

Logical interface bc-4/0/0:1.0 (Index 74) (SNMP ifIndex 79) (Generation 140)
Flags: Point-To-Point SNMP-Traps Encapsulation: 64

show interfaces extensive (ISDN B-Channel)

user@host> show interfaces bc-4/0/0:1 extensive
Physical interface: bc-4/0/0:1, Enabled, Physical link is Up
Interface index: 151, SNMP ifIndex: 75, Generation: 152
Type: Serial, Link-level type: 57, MTU: 4092, Clocking: Internal,

Copyright 2014, Juniper Networks, Inc.

1217

Interfaces Fundamentals for Routing Devices

Speed: 64kbps,
Parent: br-4/0/0 Interface index 129
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-06-13 19:50:38 PDT (14:39:12 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
4096
0 bps
Output bytes :
128423
0 bps
Input packets:
0
0 pps
Output packets:
9801
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, Resource errors: 0
Output errors:
Carrier transitions: 4, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
Egress queues: 8 supported, 8 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

13

13

1 expedited-fo

2 assured-forw

3 network-cont

9788

9788

Packet Forwarding Engine configuration:

Destination slot: 4, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority Limit
%
bps
%
usec
0 best-effort
95
60800 95
0
low
none
3 network-control
5
3200 5
0
low
none
Logical interface bc-4/0/0:1.0 (Index 74) (SNMP ifIndex 79) (Generation 140)
Flags: Point-To-Point SNMP-Traps Encapsulation: 64

1218

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (ISDN BRI)

Syntax

Release Information
Description

Options

show interfaces br-pim/0/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(J Series routers only) Display status information about the specified ISDN Basic Rate
Interface (BRI) interface.
br-pim/0/portDisplay standard information about the specified ISDN BRI interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display the interface description string.
media(Optional) Display media-specific information.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (ISDN BRI) on page 1221

show interfaces brief (ISDN BRI) on page 1222
show interfaces detail (ISDN BRI) on page 1222
show interfaces extensive (ISDN BRI) on page 1222
Table 64 on page 1219 lists the output fields for the show interfaces (ISDN BRI) command.
Output fields are listed in the approximate order in which they appear.

Table 64: ISDN BRI show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical Interface

Name of the physical interface type.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface index number that 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

Copyright 2014, Juniper Networks, Inc.

1219

Interfaces Fundamentals for Routing Devices

Table 64: ISDN BRI show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Type

Type of interface.

All levels

Link-level type

Encapsulation type used on the physical interface.

All levels

MTU

Maximum transmission unit (MTU)Size of the largest packet to be transmitted.

All levels

Clocking

Reference clock source of the interface.

All levels

Speed

Network speed on the interface.

All levels

Parent

Name and interface index of the interface to which a particular child interface
belongs. None indicates that this is the top level.

detail extensive none

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link type

Data transmission type.

detail extensive none

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

detail extensive none

Physical info

Information about the physical interface.

detail extensive none

Hold-times

Current interface hold-time up and hold-time down. Value is in milliseconds.

detail extensive

Current address

Configured MAC address.

detail extensive

Hardware address

Media access control (MAC) address of the interface.

detail extensive

Alternate link
address

Backup link address.

detail extensive

Last flapped

Date, time, and length of time since the interface changed its status from down
to up.

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

1220

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 64: ISDN BRI show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Traffic statistics

Number and rate of bytes and packets received and transmitted on the logical
and physical interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

ErrorsInput errors on the interface.

DropsNumber of packets dropped by the output queue of the I/O Manager

extensive

ASIC.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsFrames received smaller than the runt threshold.

GiantsFrames received larger than the giant threshold.

Policed discardsFrames that the incoming packet match code discarded

because they were not recognized or were not of interest. Usually, this field
reports protocols that the Junos OS does not support.

Output errors

Resource errorsSum of transmit drops.

Carrier transitions Number of times the interface has gone from down to up.

extensive

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,
possibly once every 10 seconds, the cable, the remote system, or the interface
is malfunctioning.

ErrorsSum of outgoing frame aborts and FCS errors.

DropsNumber 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 dropped by the ASIC RED mechanism.

MTU errorsNumber of packets larger than the MTU threshold.

Resource errorsSum of transmit drops.

Sample Output
show interfaces (ISDN BRI)
user@host> show interfaces br-4/0/0
Physical interface: br-4/0/0, Enabled, Physical link is Up
Interface index: 129, SNMP ifIndex: 59
Type: BRI, Link-level type: Controller, MTU: 4092, Clocking: 1,
Speed: 128kbps, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
Physical info : S/T
Last flapped
: 2006-06-13 19:50:38 PDT (15:18:26 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)

Copyright 2014, Juniper Networks, Inc.

1221

Interfaces Fundamentals for Routing Devices

show interfaces brief (ISDN BRI)

user@host> show interfaces brief br-4/0/0
Physical interface: br-4/0/0, Enabled, Physical link is Up
Type: BRI, Link-level type: Controller, MTU: 4092, Clocking: 1, Speed: 128kbps
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000

show interfaces detail (ISDN BRI)

user@host> show interfaces br-4/0/0 detail
Physical interface: br-4/0/0, Enabled, Physical link is Up
Interface index: 129, SNMP ifIndex: 59, Generation: 130
Type: BRI, Link-level type: Controller, MTU: 4092, Clocking: 1,
Speed: 128kbps, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
Physical info : S/T
Hold-times
: Up 0 ms, Down 0 ms
Last flapped
: 2006-06-13 19:50:38 PDT (15:18:32 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps

show interfaces extensive (ISDN BRI)

user@host> show interfaces br-4/0/0 extensive
Physical interface: br-4/0/0, Enabled, Physical link is Up
Interface index: 129, SNMP ifIndex: 59, Generation: 130
Type: BRI, Link-level type: Controller, MTU: 4092, Clocking: 1,
Speed: 128kbps, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex Link flags
: None
Physical info : S/T
Hold-times
: Up 0 ms, Down 0 ms
Last flapped
: 2006-06-13 19:50:38 PDT (15:18:38 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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

1222

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (ISDN D-channel)

Syntax

Release Information
Description
Options

show interfaces dc-pim/0/port:0

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(J Series routers only) Display information about the specified ISDN D-channel interface.
dc-pim/0/port:0Display standard information about the specified ISDN D-channel

interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display the interface description string.
media(Optional) Display media-specific information.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) Display static interface statistics.

Additional Information
Required Privilege
Level
List of Sample Output

Output Fields

There are no user-configurable features on D-channel interfaces.

view

show interfaces (ISDN D-Channel) on page 1226

show interfaces brief (ISDN D-Channel) on page 1226
show interfaces detail (ISDN D-Channel) on page 1227
show interfaces extensive (ISDN D-Channel) on page 1227
Table 65 on page 1223 lists the output fields for the show interfaces (ISDN D-channel)
command. Output fields are listed in the approximate order in which they appear.

Table 65: ISDN D-Channel show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical Interface

Name of the physical interface type.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface index number that reflects its initialization sequence.

detail extensive none

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1223

Interfaces Fundamentals for Routing Devices

Table 65: ISDN D-Channel show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

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

Type

Type of interface.

All levels

Link-level type

Encapsulation type used on the physical interface.

All levels

MTU

Maximum transmission unitSize of the largest packet to be transmitted.

All levels

Clocking

Reference clock source of the interface.

All levels

Speed

Network speed on the interface.

All levels

Parent

Name and interface index of the interface to which a particular child interface
belongs. None indicates that this is the top level.

detail extensive none

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link type

Type of data transmission.

detail extensivenone

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

detail extensive none

Physical info

Information about the physical interface.

detail extensive

Hold-times

Current interface hold-time up and hold-time down. Value is in milliseconds.

detail extensive

Current address

Configured MAC address.

detail extensive

Hardware address

MAC address of the hardware.

detail extensive

Alternate link
address

Backup address for the link.

detail extensive

Last flapped

Date, time, and length of time since the interface changed its status from down
to up.

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

1224

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 65: ISDN D-Channel show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

ErrorsInput errors on the interface.

DropsNumber of packets dropped by the output queue of the I/O Manager

extensive

ASIC.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsFrames received smaller than the runt threshold.

GiantsFrames received larger than the giant threshold.

Policed DiscardsFrames that the incoming packet match code discarded

because they were not recognized or were not of interest. Usually, this field
reports protocols that Junos does not support.

Output errors

Resource errorsSum of transmit drops.

Carrier transitions Number of times the interface has gone from down to up.

extensive

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,
possibly once every 10 seconds, the cable, the remote system, or the interface
is malfunctioning.

ErrorsSum of outgoing frame aborts and FCS errors.

DropsNumber 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 dropped by the ASIC Red mechanism.

MTU errorsNumber of packets larger than the MTU threshold.

Resource errorsSum of transmit drops.

ISDN Alarms

ISDN alarms.

All levels

ISDN Media

LOFLoss of frame

extensive

LOSLoss of signal

Logical Interface
Logical interface

Name of the logical interface.

All levels

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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1225

Interfaces Fundamentals for Routing Devices

Table 65: ISDN D-Channel show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Input packets

Number of packets received on the logical interface.

None specified

Output packets

Number of packets transmitted on the logical interface.

None specified

Traffic statistics

Total number of bytes and packets received and transmitted on the logical
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. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Local statistics

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the logical interface.

Output packetsNumber of packets transmitted on the logical interface

Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Sample Output
show interfaces (ISDN D-Channel)
user@host> show interfaces dc-4/0/0
Physical interface: dc-4/0/0, Enabled, Physical link is Up
Interface index: 150, SNMP ifIndex: 73
Type: Serial, Link-level type: 55, MTU: 4092, Clocking: Internal,
Speed: 16kbps,
Parent: br-4/0/0 Interface index 129
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
Last flapped
: 2006-06-13 19:50:38 PDT (15:29:32 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
ISDN alarms
: None
Logical interface dc-4/0/0.32767 (Index 73) (SNMP ifIndex 74)
Flags: Point-To-Point SNMP-Traps Encapsulation: 60
Input packets : 23482
Output packets: 21686

show interfaces brief (ISDN D-Channel)

user@host> show interfaces dc-4/0/0 brief

1226

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Physical interface: dc-4/0/0, Enabled, Physical link is Up

Type: Serial, Link-level type: 55, MTU: 4092, Clocking: Internal,
Speed: 16kbps
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
ISDN alarms
: None
Logical interface dc-4/0/0.32767
Flags: Point-To-Point SNMP-Traps Encapsulation: 60

show interfaces detail (ISDN D-Channel)

user@host> show interfaces dc-4/0/0 detail
Physical interface: dc-4/0/0, Enabled, Physical link is Up
Interface index: 150, SNMP ifIndex: 73, Generation: 151
Type: Serial, Link-level type: 55, MTU: 4092, Clocking: Internal,
Speed: 16kbps,
Parent: br-4/0/0 Interface index 129
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: 2006-06-13 19:50:38 PDT (15:29:42 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
257592
0 bps
Output bytes :
231162
0 bps
Input packets:
23483
0 pps
Output packets:
21687
0 pps
ISDN alarms
: None
Logical interface dc-4/0/0.32767 (Index 73) (SNMP ifIndex 74) (Generation 139)
Flags: Point-To-Point SNMP-Traps Encapsulation: 60
Traffic statistics:
Input bytes :
257592
Output bytes :
664902
Input packets:
23483
Output packets:
21687
Local statistics:
Input bytes :
257592
Output bytes :
664902
Input packets:
23483
Output packets:
21687

show interfaces extensive (ISDN D-Channel)

user@host> show interfaces dc-4/0/0 extensive
Physical interface: dc-4/0/0, Enabled, Physical link is Up
Interface index: 150, SNMP ifIndex: 73, Generation: 151
Type: Serial, Link-level type: 55, MTU: 4092, Clocking: Internal,
Speed: 16kbps,
Parent: br-4/0/0 Interface index 129
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None

Copyright 2014, Juniper Networks, Inc.

1227

Interfaces Fundamentals for Routing Devices

Physical info : Unspecified

Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: 2006-06-13 19:50:38 PDT (15:29:49 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
257596
0 bps
Output bytes :
231167
0 bps
Input packets:
23484
0 pps
Output packets:
21688
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, Resource errors: 0
Output errors:
Carrier transitions: 5, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
ISDN alarms
: None
ISDN media:
Seconds
Count State
LOF
1874
2 0K
LOS
1874
2 0K
Logical interface dc-4/0/0.32767 (Index 73) (SNMP ifIndex 74) (Generation 139)
Flags: Point-To-Point SNMP-Traps Encapsulation: 60
Traffic statistics:
Input bytes :
257596
Output bytes :
664927
Input packets:
23484
Output packets:
21688
Local statistics:
Input bytes :
257596
Output bytes :
664927
Input packets:
23484
Output packets:
21688

1228

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (ISDN Dialer)

Syntax

Release Information
Description
Options

show interfaces dlnumber

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(J Series routers only) Display information about the ISDN dialer interface.
dlnumberDisplay standard information about the specified ISDN dialer interface.
brief | detail | extensive | terse(Optional) Display brief interface information.
descriptions(Optional) Display the interface description string.
media(Optional) Display media-specific information.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (ISDN Dialer) on page 1234

show interfaces brief (ISDN Dialer) on page 1235
show interfaces detail (ISDN Dialer) on page 1235
show interfaces extensive (ISDN Dialer) on page 1237
Table 66 on page 1229 lists the output fields for the show interfaces (ISDN dialer) command.
Output fields are listed in the approximate order in which they appear.

Table 66: ISDN Dialer show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical Interface

Name of the physical interface type.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface index number that 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

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1229

Interfaces Fundamentals for Routing Devices

Table 66: ISDN Dialer show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Type

Interface type.

All levels

Link-level type

Type of encapsulation configured on the physical interface.

All levels

MTU

Maximum transmission unit (MTU)Size of the largest transmitted packet.

All levels

Clocking

Reference clock source of the interface.

All levels

Speed

Network speed on the interface.

All levels

Device flags

Information about the physical device.

All levels

Interface flags

Information about the interface.

All levels

Link type

Data transmission type.

detail extensive none

Link flags

Information about the link.

detail extensive none

Physical info

Information about the physical interface.

detail extensive

Hold-times

Current interface hold-time up and hold-time down. Value is in milliseconds.

detail extensive

Current address

Configured MAC address.

detail extensive

Hardware address

MAC address of the hardware.

detail extensive

Alternate link
address

Backup link address.

detail extensive

Last flapped

Date, time, and length of time since the interface status changed from down to
up.

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

1230

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 66: ISDN Dialer show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Input errors

ErrorsInput errors on the interface.

extensive

DropsNumber of packets dropped by the output queue of the I/O Manager

ASIC.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsFrames received smaller than the runt threshold.

GiantsFrames received larger than the giant threshold.

Policed discardsFrames that the incoming packet match code discarded

because they were not recognized or were not of interest. Usually, this field
reports protocols that the Junos OS does not support.

Output errors

Resource errorsSum of transmit drops.

Carrier transitionsNumber of times the interface has gone from down to up.

extensive

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,
possibly once every 10 seconds, the cable, the remote system, or the interface
is malfunctioning.

ErrorsSum of outgoing frame aborts and FCS errors.

DropsNumber 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 dropped by the ASIC RED mechanism.

MTU errorsNumber of packets larger than the MTU threshold.

Resource errorsSum of transmit drops.

Logical Interface
Logical interface

Name of the logical interface.

All levels

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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Copyright 2014, Juniper Networks, Inc.

1231

Interfaces Fundamentals for Routing Devices

Table 66: ISDN Dialer show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Dialer

Information about the status and configuration of the dialer interface:

All levels

StateState of the interface: Active or Inactive.

Dial poolDial pool name.

Dial stringsDialing number for the ISDN connection.

Subordinate interfacesAssociated B-channel interface name and SNMP

index number.

Activation delayLength of time (in seconds) to wait before enabling the

interface after the primary interface has failed.

Deactivation delayLength of time (in seconds) to wait before disabling the

interface after the primary interface is operational.

Initial route check delayWait period (in seconds) for the software to check

if the primary interface is up after the router comes up. The range is from 1
through 300 seconds. The default is 120 seconds.

Redial delay(Available on interfaces configured for ISDN dial-out.) Delay,

in seconds, between two successive calls made. The range of values is 2 to
255. The default value is 3.

Callback wait periodTime, in seconds, that the dialer waits before it calls
back the caller ID. The default value is 5.

Load thresholdBandwidth threshold percentage used for adding interfaces.

Another link is added to the multilink bundle when the load reaches the
threshold value you set. The range of values is 0 to 100. The default value is
100.

Load intervalInterval used to calculate the average load on the network. By

default, the average interface load is calculated every 60 seconds.

Bandwidth

Speed at which the interface is running.

detail extensive none

Input packets

Number of packets received on the logical interface.

None specified

Output packets

Number of packets transmitted on the logical interface.

None specified

Traffic statistics

Total number of bytes and packets received and transmitted on the logical
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. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Local statistics

1232

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the logical interface.

Output packetsNumber of packets transmitted on the logical interface

Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 66: ISDN Dialer show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Transit statistics

Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. This
counter normally stabilizes in less than 1 second.

detail extensive

Keepalive settings

Configured settings for keepalives.

detail extensive none

Keepalive statistics

interval secondsTime in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

up-count numberNumber of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.

down-count numberNumber 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.

Information about keepalive packets. (When no level of output is specified, the

word statistics is not part of the field name and the phrase last seen is not
displayed.)

InputNumber of keepalive packets received by PPP.

detail extensive none

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the format hh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

LCP state

NCP state

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

Link Control Protocol state.

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

Network Control Protocol state.

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

Copyright 2014, Juniper Networks, Inc.

detail extensive none

detail extensive none

1233

Interfaces Fundamentals for Routing Devices

Table 66: ISDN Dialer show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CHAP state

Displays the state of the Challenge Handshake Authentication Protocol (CHAP)

during its transaction.

detail extensive none

Chap-Resp-receivedResponse received for the challenge sent, but CHAP

not yet moved into the Success state. (Most likely with RADIUS
authentication.)

Chap-Resp-sentResponse sent for the challenge received.

Chap-Chal-sentChallenge sent.

Chap-Chal-receivedChallenge received but response not yet sent.

DownCHAP authentication is incomplete (not yet completed or has failed).

Not-configuredCHAP is not configured on the interface.

OpenedCHAP authentication was successful.

protocol family

Protocol family configured on the logical interface. If the family is inet, the IP
address of the logical interface and the IP address on the remote side of the
connection are included.

brief

Protocol

Protocol family configured on the logical interface.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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.

detail extensive

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Sample Output
show interfaces (ISDN Dialer)
user@host>show interfaces dl0
Physical interface: dl0, Enabled, Physical link is Up
Interface index: 153, SNMP ifIndex: 77

1234

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Type: 27, Link-level type: PPP, MTU: 1504

Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Link flags
: Keepalives
Last flapped
: Never
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Logical interface dl0.0 (Index 76) (SNMP ifIndex 78)
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: 10
Dial strings: 5551212
Subordinate interfaces: bc-4/0/0:1 (Index 151)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
Bandwidth: 64kbps
Input packets : 13
Output packets: 10846
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 5412 (00:00:06 ago), Output: 5416 (00:00:05 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 1500
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.40.1, Local: 10.0.40.2

show interfaces brief (ISDN Dialer)

user@host> show interfaces dl0 brief
Physical interface: dl0, Enabled, Physical link is Up
Type: 27, Link-level type: PPP, MTU: 1504, Clocking: Unspecified,
Speed: Unspecified
Device flags
: Present Running
Interface flags: SNMP-Traps
Logical interface dl0.0
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: 10
Dial strings: 5551212
Subordinate interfaces: bc-4/0/0:1 (Index 151)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
inet 10.0.40.2
--> 10.0.40.1

show interfaces detail (ISDN Dialer)

user@host> show interfaces dl0 detail
Physical interface: dl0, Enabled, Physical link is Up
Interface index: 153, SNMP ifIndex: 77, Generation: 154

Copyright 2014, Juniper Networks, Inc.

1235

Interfaces Fundamentals for Routing Devices

Type: 27, Link-level type: PPP, MTU: 1504, Clocking: Unspecified,

Speed: Unspecified
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Link flags
: Keepalives
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
131116
40 bps
Output bytes :
0
0 bps
Input packets:
10847
0 pps
Output packets:
0
0 pps
Logical interface dl0.0 (Index 76) (SNMP ifIndex 78) (Generation 142)
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: 10
Dial strings: 5551212
Subordinate interfaces: bc-4/0/0:1 (Index 151)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
Bandwidth: 64kbps
Traffic statistics:
Input bytes :
1092
Output bytes :
131459
Input packets:
13
Output packets:
10848
Local statistics:
Input bytes :
1092
Output bytes :
131459
Input packets:
13
Output packets:
10848
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 5413 (last seen 00:00:03 ago)
Output: 5417 (last sent 00:00:02 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 1500, Generation: 142, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.40.1, Local: 10.0.40.2, Broadcast: Unspecified,
Generation: 142

1236

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces extensive (ISDN Dialer)

user@host> show interfaces dl0 extensive
Physical interface: dl0, Enabled, Physical link is Up
Interface index: 153, SNMP ifIndex: 77, Generation: 154
Type: 27, Link-level type: PPP, MTU: 1504, Clocking: Unspecified,
Speed: Unspecified
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Link flags
: Keepalives
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
131116
0 bps
Output bytes :
0
0 bps
Input packets:
10847
0 pps
Output packets:
0
0 pps
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 dl0.0 (Index 76) (SNMP ifIndex 78) (Generation 142)
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: 10
Dial strings: 5551212
Subordinate interfaces: bc-4/0/0:1 (Index 151)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
Bandwidth: 64kbps
Traffic statistics:
Input bytes :
1092
Output bytes :
131459
Input packets:
13
Output packets:
10848
Local statistics:
Input bytes :
1092
Output bytes :
131459
Input packets:
13
Output packets:
10848
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 5413 (last seen 00:00:07 ago)
Output: 5417 (last sent 00:00:06 ago)

Copyright 2014, Juniper Networks, Inc.

1237

Interfaces Fundamentals for Routing Devices

LCP state: Opened

NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 1500, Generation: 142, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.40.1, Local: 10.0.40.2, Broadcast: Unspecified,
Generation: 142

1238

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (M Series, MX Series and T Series Routers, and PTX Series Packet
Transport Routers Management and Internal Ethernet)
List of Syntax

Syntax (M Series, MX
Series T Series, and
PTX Series Routers
Management Ethernet
Interface)
Syntax (M Series, MX
Series, T Series, and
PTX Series Routers
Internal Ethernet
Interface)
Release Information

Syntax (M Series, MX Series T Series, and PTX Series Routers Management Ethernet
Interface) on page 1239
Syntax (M Series, MX Series, T Series, and PTX Series Routers Internal Ethernet
Interface) on page 1239
show interfaces em0 | fxp0
<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>
show interfaces bcm0 | em0 | em1| fxp1 | fxp2 | ixgbe0 | ixgbe1
<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Command introduced on PTX Series Packet Transport Routers for Junos OS Release
12.1.

Description

(M Series, T Series, TX Matrix Plus, and PTX Series devices only) Display status information
about the management Ethernet and internal Ethernet interfaces.

Options

em0 | fxp0(M Series, MX Series, T Series, and PTX Series) Display standard information

about the management Ethernet interface. For supported Ethernet interface by

chassis and Routing Engine, see Supported Routing Engines by Router on page 14.
bcm0 | em0 | em1 | fxp1 | fxp2 | ixgbe0 | ixgbe1(M Series, MX Series, T Series, and PTX

Series) Display standard information about the internal Ethernet interfaces. See
Supported Routing Engines by Router on page 14 for the internal Ethernet interface
names for each Routing Engine by hardware platform.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege
Level

view

Copyright 2014, Juniper Networks, Inc.

1239

Interfaces Fundamentals for Routing Devices

List of Sample Output

Output Fields

show interfaces brief (Management Ethernet) on page 1243

show interfaces (Management Ethernet) on page 1243
show interfaces (Management Ethernet [TX Matrix Plus Router]) on page 1244
show interfaces (Management Ethernet [PTX Series Packet Transport
Routers]) on page 1244
show interfaces detail (Management Ethernet) on page 1244
show interfaces detail (Management Ethernet [TX Matrix Plus Router]) on page 1245
show interfaces detail (Management Ethernet [PTX Packet Transport
Routers]) on page 1246
show interfaces extensive (Management Ethernet) on page 1246
show interfaces extensive (Management Ethernet [TX Matrix Plus Router]) on page 1247
show interfaces extensive (Management Ethernet [PTX Series Packet Transport
Routers]) on page 1248
show interfaces brief (Management Ethernet) on page 1249
show interfaces brief (Management Ethernet [TX Matrix Plus Router]) on page 1249
show interfaces brief (Management Ethernet [PTX Series Packet Transport
Routers]) on page 1249
show interfaces (Internal Ethernet) on page 1249
show interfaces (Internal Ethernet [TX Matrix Plus Router]) on page 1250
show interfaces detail (Internal Ethernet) on page 1250
show interfaces detail (Internal Ethernet [TX Matrix Plus Router]) on page 1251
show interfaces extensive (internal Ethernet) on page 1252
show interfaces extensive (internal Ethernet [TX Matrix Plus Router]) on page 1253
Table 67 on page 1240 lists the output fields for the show interfaces (management)
command on the M Series routers, T Series routers, TX Matrix Plus routers, and PTX
Series Packet Transport Routers. Output fields are listed in the approximate order in
which they appear.

Table 67: M Series and T Series Router Management and Internal Ethernet show interfaces
Output Fields
Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface index number, 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

Type

Type of interface.

All levels

Link-level type

Encapsulation type used on the physical interface.

All levels

Physical Interface

1240

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 67: M Series and T Series Router Management and Internal Ethernet show interfaces
Output Fields (continued)
Field Name

Field Description

Level of Output

MTU

Maximum transmission unit (MTU)Size of the largest packet to be transmitted.

All levels

Clocking

Reference clock source of the interface.

All levels

Speed

Network speed on the interface.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link type

Data transmission type.

detail extensive none

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

detail extensive

Physical info

Information about the physical interface.

detail extensive

Hold-times

Current interface hold-time up and hold-time down. Value is in milliseconds.

detail extensive

Current address

Configured MAC address.

detail extensive none

Hardware address

Media access control (MAC) address of the interface.

detail extensive none

Alternate link
address

Backup link address.

detail extensive

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).

detail extensive none

Input packets

Number of packets received on the physical interface.

None specified

Output packets

Number of packets transmitted on the physical interface.

None specified

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the logical
and physical interface.

detail extensive

Input bytes, Output bytesNumber of bytes received and transmitted on the

interface.

Input packets, Output packetsNumber of packets received and transmitted

on the interface.

Copyright 2014, Juniper Networks, Inc.

1241

Interfaces Fundamentals for Routing Devices

Table 67: M Series and T Series Router Management and Internal Ethernet show interfaces
Output Fields (continued)
Field Name

Field Description

Level of Output

Input errors

ErrorsInput errors on the interface.

extensive

DropsNumber of packets dropped by the output queue of the I/O Manager

ASIC.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsFrames received smaller than the runt threshold.

GiantsFrames received larger than the giant threshold.

Policed DiscardsFrames that the incoming packet match code discarded

because they were not recognized or were not of interest. Usually, this field
reports protocols that Junos does not support.

Output errors

Resource errorsSum of transmit drops.

Carrier transitionsNumber of times the interface has gone from down to up.

extensive

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,
possibly once every 10 seconds, the cable, the remote system, or the interface
is malfunctioning.

ErrorsSum of outgoing frame aborts and FCS errors.

DropsNumber 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 dropped by the ASIC RED mechanism.

Resource errorsSum of transmit drops.

Logical Interface
Logical interface

Name of the logical interface

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface; values are described in the Device
Flags section under Common Output Fields Description on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

detail extensive none

inet

IP address of the logical interface.

brief

Protocol

Protocol family configured on the logical interface (such as iso or inet6).

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

1242

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 67: M Series and T Series Router Management and Internal Ethernet show interfaces
Output Fields (continued)
Field Name

Field Description

Level of Output

Route table

Route table in which this address exists. For example, Route table:0 refers to
inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

Addresses, Flags

Information about address flags. Possible values are described in the Addresses
Flags section under Common Output Fields Description on page 994.

detail 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.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Sample Output
show interfaces brief (Management Ethernet)
user@host> show interfaces fxp0 brief
Physical interface: fxp0, Enabled, Physical link is Up
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Logical interface fxp0.0
Flags: SNMP-Traps Encapsulation: ENET2
inet 192.168.70.143/21

show interfaces (Management Ethernet)

user@host> show interfaces fxp0
Physical interface: fxp0, Enabled, Physical link is Up
Interface index: 1, SNMP ifIndex: 1
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Half-Duplex
Current address: 00:a0:a5:56:01:89, Hardware address: 00:a0:a5:56:01:89
Last flapped
: Never
Input packets : 80804
Output packets: 1105
Logical interface fxp0.0 (Index 2) (SNMP ifIndex 13)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary

Copyright 2014, Juniper Networks, Inc.

1243

Interfaces Fundamentals for Routing Devices

Destination: 192.168.64/21, Local: 192.168.70.143,

Broadcast: 192.168.71.255

show interfaces (Management Ethernet [TX Matrix Plus Router])

user@host> show interfaces em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 17
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Current address: 00:80:f9:26:00:c0, Hardware address: 00:80:f9:26:00:c0
Last flapped
: Never
Input packets : 1424
Output packets: 5282
Logical interface em0.0 (Index 3) (SNMP ifIndex 18)
Flags: SNMP-Traps Encapsulation: ENET2
Input packets : 1424
Output packets: 5282
Protocol inet, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.178.0/25, Local: 192.168.178.11, Broadcast:
192.168.178.127

show interfaces (Management Ethernet [PTX Series Packet Transport Routers])

user@host> show interfaces em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 0
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Current address: 00:80:f9:25:00:1b, Hardware address: 00:80:f9:25:00:1b
Last flapped
: Never
Input packets : 212581
Output packets: 71
Logical interface em0.0 (Index 3) (SNMP ifIndex 0)
Flags: SNMP-Traps Encapsulation: ENET2
Input packets : 212551
Output packets: 71
Protocol inet, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 192.168.3/24, Local: 192.168.3.30,
Broadcast: 192.168.3.255

show interfaces detail (Management Ethernet)

user@host> show interfaces fxp0 detail
Physical interface: fxp0, Enabled, Physical link is Up
Interface index: 1, SNMP ifIndex: 1, Generation: 0
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Half-Duplex
Physical info : Unspecified

1244

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:a0:a5:56:01:89, Hardware address: 00:a0:a5:56:01:89
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
6484031
Output bytes :
167503
Input packets:
81008
Output packets:
1110
Logical interface fxp0.0 (Index 2) (SNMP ifIndex 13) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 6, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.64/21, Local: 192.168.70.143,
Broadcast: 192.168.71.255, Generation: 1

show interfaces detail (Management Ethernet [TX Matrix Plus Router])

user@host> show interfaces em0 detail
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 17, Generation: 2
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:80:f9:26:00:c0, Hardware address: 00:80:f9:26:00:c0
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
124351
Output bytes :
1353212
Input packets:
1804
Output packets:
5344
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface em0.0 (Index 3) (SNMP ifIndex 18) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
117135
Output bytes :
1331647
Input packets:
1804
Output packets:
5344
Local statistics:
Input bytes :
117135
Output bytes :
1331647
Input packets:
1804
Output packets:
5344
Protocol inet, MTU: 1500, Generation: 1, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary

Copyright 2014, Juniper Networks, Inc.

1245

Interfaces Fundamentals for Routing Devices

Destination: 192.168.178.0/25, Local: 192.168.178.11, Broadcast:

192.168.178.127, Generation: 1

show interfaces detail (Management Ethernet [PTX Packet Transport Routers])

user@host> show interfaces detail em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 0, Generation: 3
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:80:f9:25:00:1b, Hardware address: 00:80:f9:25:00:1b
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
15255909
Output bytes :
4608
Input packets:
214753
Output packets:
72
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface em0.0 (Index 3) (SNMP ifIndex 0) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
14394630
Output bytes :
3024
Input packets:
214723
Output packets:
72
Local statistics:
Input bytes :
14394630
Output bytes :
3024
Input packets:
214723
Output packets:
72
Protocol inet, MTU: 1500, Generation: 1, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 192.168.3/24, Local: 192.168.3.30,
Broadcast: 192.168.3.255, Generation: 1

show interfaces extensive (Management Ethernet)

user@host> show interfaces fxp0 extensive
Physical interface: fxp0, Enabled, Physical link is Up
Interface index: 1, SNMP ifIndex: 1, Generation: 0
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Half-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms

1246

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Current address: 00:a0:a5:56:01:89, Hardware address: 00:a0:a5:56:01:89

Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
6678904
Output bytes :
169657
Input packets:
83946
Output packets:
1127
Input errors:
Errors: 12, 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 fxp0.0 (Index 2) (SNMP ifIndex 13) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 6, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.64/21, Local: 192.168.70.143,
Broadcast: 192.168.71.255, Generation: 1

show interfaces extensive (Management Ethernet [TX Matrix Plus Router])

user@host> show interfaces em0 extensive
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 17, Generation: 2
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:80:f9:26:00:c0, Hardware address: 00:80:f9:26:00:c0
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
127120
Output bytes :
1357414
Input packets:
1843
Output packets:
5372
IPv6 transit 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 em0.0 (Index 3) (SNMP ifIndex 18) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:

Copyright 2014, Juniper Networks, Inc.

1247

Interfaces Fundamentals for Routing Devices

Input bytes :
119748
Output bytes :
1335719
Input packets:
1843
Output packets:
5372
Local statistics:
Input bytes :
119748
Output bytes :
1335719
Input packets:
1843
Output packets:
5372
Protocol inet, MTU: 1500, Generation: 1, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.178.0/25, Local: 192.168.178.11, Broadcast:
192.168.178.127, Generation: 1

show interfaces extensive (Management Ethernet [PTX Series Packet Transport Routers])
user@host> show interfaces extensive em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 0, Generation: 3
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:80:f9:25:00:1b, Hardware address: 00:80:f9:25:00:1b
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
15236459
Output bytes :
4608
Input packets:
214482
Output packets:
72
IPv6 transit 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 em0.0 (Index 3) (SNMP ifIndex 0) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
14376264
Output bytes :
3024
Input packets:
214452
Output packets:
72
Local statistics:
Input bytes :
14376264
Output bytes :
3024
Input packets:
214452
Output packets:
72

1248

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Protocol inet, MTU: 1500, Generation: 1, Route table: 0

Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 192.168.3/24, Local: 192.168.3.30,
Broadcast: 192.168.3.255, Generation: 1

show interfaces brief (Management Ethernet)

user@host> show interfaces fxp1 brief
Physical interface: fxp1, Enabled, Physical link is Up
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Logical interface fxp1.0
Flags: SNMP-Traps Encapsulation: ENET2
inet 10.0.0.4/8
inet6 fe80::200:ff:fe00:4/64
fec0::10:0:0:4/64
tnp
4

show interfaces brief (Management Ethernet [TX Matrix Plus Router])

user@host> show interfaces em0 brief
Physical interface: em0, Enabled, Physical link is Up
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Logical interface em0.0
Flags: SNMP-Traps Encapsulation: ENET2
inet 192.168.178.11/25

show interfaces brief (Management Ethernet [PTX Series Packet Transport Routers])
user@host> show interfaces em0 brief
Physical interface: em0, Enabled, Physical link is Up
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Logical interface em0.0
Flags: SNMP-Traps Encapsulation: ENET2
inet 192.168.3.30/24
root@aboslutely> show interfaces em0 terse
Interface
Admin Link Proto
em0
up
up
em0.0
up
up
inet

Local

Remote

192.168.3.30/24

show interfaces (Internal Ethernet)

user@host> show interfaces fxp1
Physical interface: fxp1, Enabled, Physical link is Up
Interface index: 2, SNMP ifIndex: 2
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps

Copyright 2014, Juniper Networks, Inc.

1249

Interfaces Fundamentals for Routing Devices

Link type
: Full-Duplex
Current address: 02:00:00:00:00:04, Hardware address: 02:00:00:00:00:04
Last flapped
: Never
Input packets : 30655
Output packets: 33323
Logical interface fxp1.0 (Index 3) (SNMP ifIndex 14)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 10/8, Local: 10.0.0.4, Broadcast: 10.255.255.255
Protocol inet6, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe00:4
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::10:0:0:4
Protocol tnp, MTU: 1500
Flags: Primary, Is-Primary
Addresses
Local: 4

show interfaces (Internal Ethernet [TX Matrix Plus Router])

user@host> show interfaces ixgbe0
Physical interface: ixgbe0, Enabled, Physical link is Up
Interface index: 2, SNMP ifIndex: 116
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Current address: 02:00:00:22:00:04, Hardware address: 02:00:00:22:00:04
Last flapped
: Never
Input packets : 2301738
Output packets: 3951155
Logical interface ixgbe0.0 (Index 4) (SNMP ifIndex 117)
Flags: SNMP-Traps Encapsulation: ENET2
Input packets : 2301595
Output packets: 3951155
Protocol inet, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: 10/8, Local: 10.34.0.4, Broadcast: 10.255.255.255
Addresses, Flags: Primary Is-Default Is-Preferred Is-Primary
Destination: 128/2, Local: 162.0.0.4, Broadcast: 191.255.255.255
Protocol inet6, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe22:4
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::a:22:0:4
Protocol tnp, MTU: 1500
Flags: Primary, Is-Primary
Addresses
Local: 0x22000004

show interfaces detail (Internal Ethernet)

user@host> show interfaces fxp1 detail

1250

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Physical interface: fxp1, Enabled, Physical link is Up

Interface index: 2, SNMP ifIndex: 2, Generation: 1
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 02:00:00:00:00:04, Hardware address: 02:00:00:00:00:04
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
2339969
Output bytes :
15880707
Input packets:
30758
Output packets:
33443
Logical interface fxp1.0 (Index 3) (SNMP ifIndex 14) (Generation 2)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 7, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 10/8, Local: 10.0.0.4, Broadcast: 10.255.255.255,
Generation: 3
Protocol inet6, MTU: 1500, Generation: 8, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe00:4,
Broadcast: Unspecified, Generation: 5
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::10:0:0:4, Broadcast: Unspecified,
Generation: 7
Protocol tnp, MTU: 1500, Generation: 9, Route table: 1
Flags: Primary, Is-Primary
Addresses, Flags: None
Destination: Unspecified, Local: 4, Broadcast: Unspecified,
Generation: 8

show interfaces detail (Internal Ethernet [TX Matrix Plus Router])

user@host> show interfaces ixgbe0 detail
Physical interface: ixgbe0, Enabled, Physical link is Up
Interface index: 2, SNMP ifIndex: 116, Generation: 3
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 02:00:00:22:00:04, Hardware address: 02:00:00:22:00:04
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
238172825
Output bytes :
1338948955
Input packets:
2360984
Output packets:
4061512

Copyright 2014, Juniper Networks, Inc.

1251

Interfaces Fundamentals for Routing Devices

IPv6 transit statistics:

Input bytes :
Output bytes :
Input packets:
Output packets:

0
0
0
0

Logical interface ixgbe0.0 (Index 4) (SNMP ifIndex 117) (Generation 2)

Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
228720309
Output bytes :
1261387447
Input packets:
2360841
Output packets:
4061512
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
228720309
Output bytes :
1261387447
Input packets:
2360841
Output packets:
4061512
Protocol inet, MTU: 1500, Generation: 2, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: 10/8, Local: 10.34.0.4, Broadcast: 10.255.255.255, Generation:
2
Addresses, Flags: Primary Is-Default Is-Preferred Is-Primary
Destination: 128/2, Local: 162.0.0.4, Broadcast: 191.255.255.255,
Generation: 3
Protocol inet6, MTU: 1500, Generation: 3, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe22:4
Generation: 4
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::a:22:0:4
Protocol tnp, MTU: 1500, Generation: 5
Generation: 4, Route table: 1
Flags: Primary, Is-Primary
Addresses, Flags: None
Destination: Unspecified, Local: 0x22000004, Broadcast: Unspecified,
Generation: 6

show interfaces extensive (internal Ethernet)

user@host> show interfaces fxp1 extensive
Physical interface: fxp1, Enabled, Physical link is Up
Interface index: 2, SNMP ifIndex: 2, Generation: 1
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 02:00:00:00:00:04, Hardware address: 02:00:00:00:00:04
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never

1252

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Traffic statistics:
Input bytes :
2349897
Output bytes :
15888605
Input packets:
30896
Output packets:
33607
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 fxp1.0 (Index 3) (SNMP ifIndex 14) (Generation 2)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 7, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 10/8, Local: 10.0.0.4, Broadcast: 10.255.255.255,
Generation: 3
Protocol inet6, MTU: 1500, Generation: 8, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe00:4,
Broadcast: Unspecified, Generation: 5
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::10:0:0:4, Broadcast: Unspecified,
Generation: 7
Protocol tnp, MTU: 1500, Generation: 9, Route table: 1
Flags: Primary, Is-Primary
Addresses, Flags: None
Destination: Unspecified, Local: 4, Broadcast: Unspecified,
Generation: 8

show interfaces extensive (internal Ethernet [TX Matrix Plus Router])

user@host> show interfaces ixgbe0 extensive
Physical interface: ixgbe0, Enabled, Physical link is Up
Interface index: 2, SNMP ifIndex: 116, Generation: 3
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 02:00:00:22:00:04, Hardware address: 02:00:00:22:00:04
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
242730780
Output bytes :
1348312269
Input packets:
2398737
Output packets:
4133510
IPv6 transit 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:

Copyright 2014, Juniper Networks, Inc.

1253

Interfaces Fundamentals for Routing Devices

0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Logical interface ixgbe0.0 (Index 4) (SNMP ifIndex 117) (Generation 2)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
233127252
Output bytes :
1269350897
Input packets:
2398594
Output packets:
4133510
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
233127252
Output bytes :
1269350897
Input packets:
2398594
Output packets:
4133510
Protocol inet, MTU: 1500, Generation: 2, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: 10/8, Local: 10.34.0.4, Broadcast: 10.255.255.255, Generation:
2
Addresses, Flags: Primary Is-Default Is-Preferred Is-Primary
Destination: 128/2, Local: 162.0.0.4, Broadcast: 191.255.255.255,
Generation: 3
Protocol inet6, MTU: 1500, Generation: 3, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe22:4
Generation: 4
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::a:22:0:4
Protocol tnp, MTU: 1500, Generation: 5
Generation: 4, Route table: 1
Flags: Primary, Is-Primary
Addresses, Flags: None
Destination: Unspecified, Local: 0x22000004, Broadcast: Unspecified,
Generation: 6

1254

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (PPPoE)

Syntax

Release Information
Description

Options

show interfaces pp0.logical

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(J Series Services Routers, M120 routers, M320 routers, and MX Series routers only)
Display status information about the PPPoE interface.
pp0.logicalDisplay standard status information about the PPPoE interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information about PPPoE interfaces.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) Display PPPoE interface statistics.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (PPPoE) on page 1261

show interfaces (PPPoE over Aggregated Ethernet) on page 1261
show interfaces brief (PPPoE) on page 1262
show interfaces detail (PPPoE) on page 1262
show interfaces detail (PPPoE on J Series Services Routers) on page 1263
show interfaces extensive (PPPoE on M120 and M320 Routers) on page 1264
Table 68 on page 1255 lists the output fields for the show interfaces (PPPoE) command.
Output fields are listed in the approximate order in which they appear.

Table 68: show interfaces (PPPoE) Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface index number, which reflects its initialization sequence.

detail extensive none

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1255

Interfaces Fundamentals for Routing Devices

Table 68: show interfaces (PPPoE) Output Fields (continued)

Field Name

Field Description

Level of Output

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

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

Speed

Speed at which the interface is running.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

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 Flags
section under Common Output Fields Description on page 994.

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

Current address

Configured MAC address.

detail extensive

Hardware address

MAC address of the hardware.

detail extensive

Alternate link
address

Backup address of the link.

detail extensive

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

1256

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 68: show interfaces (PPPoE) Output Fields (continued)

Field Name

Field Description

Level of Output

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

IPv6 transit
statistics

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Number of IPv6 transit bytes and packets received and transmitted on the
physical interface if IPv6 statistics tracking is enabled.

detail extensive

NOTE: These fields include dropped traffic and exception traffic, as those fields
are not separately defined.

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Input errors on the interface:

ErrorsSum of incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

GiantsNumber of frames received that are larger than the giant threshold.

Policed discardsNumber 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.

Output errors

Resource errorsSum of B chip Tx drops and IXP Tx net transmit drops.

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

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), then the cable, the far-end system, or the
PIM is malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of B chip Tx drops and IXP Tx net transmit drops.

Logical Interface

Copyright 2014, Juniper Networks, Inc.

1257

Interfaces Fundamentals for Routing Devices

Table 68: show interfaces (PPPoE) Output Fields (continued)

Field Name

Field Description

Level of Output

Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number (which reflects its initialization sequence).

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Type of encapsulation configured on the logical interface.

All levels

PPP parameters

PPP status:

detail

PPPoE

LCP restart timerLength of time (in milliseconds) between successive Link

Control Protocol (LCP) configuration requests.

NCP restart timerLength of time (in milliseconds) between successive

Network Control Protocol (NCP) configuration requests.

PPPoE status:

All levels

StateState of the logical interface (up or down).

Session IDPPPoE session ID.

Service nameType of service required. Can be used to indicate an Internet

service provider (ISP) name or a class or quality of service.

Configured AC nameConfigured access concentrator name.

Auto-reconnect timeoutTime after which to try to reconnect after a PPPoE

session is terminated, in seconds.

Idle TimeoutLength of time (in seconds) that a connection can be idle before

disconnecting.

Underlying interfaceInterface on which PPPoE is running.

Link

Name of the physical interfaces for member links in an aggregated Ethernet

bundle for a PPPoE over aggregated Ethernet configuration. PPPoE traffic goes
out on these interfaces.

All levels

Traffic statistics

Total number of bytes and packets received and transmitted on the logical
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.

detail extensive

1258

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 68: show interfaces (PPPoE) Output Fields (continued)

Field Name

Field Description

Level of Output

IPv6 transit
statistics

Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.

detail extensive

NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Local statistics

Statistics for traffic received from and transmitted to the Routing Engine. 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.

detail extensive

Transit statistics

Statistics for traffic transiting the router. 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.

detail extensive

NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.
Keepalive settings

Keepalive statistics

(PPP and HDLC) Configured settings for keepalives.

interval secondsThe time in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

down-countnumberThe 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 numberThe number of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.

(PPP and HDLC) Information about keepalive packets.

detail extensive

InputNumber of keepalive packets received by PPP.

detail extensive

(last seen 00:00:00 ago)Time the last keepalive packet was received,
in the format hh:mm:ss.

OutputNumber 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

Copyright 2014, Juniper Networks, Inc.

1259

Interfaces Fundamentals for Routing Devices

Table 68: show interfaces (PPPoE) Output Fields (continued)

Field Name

Field Description

Level of Output

LCP state

(PPP) Link Control Protocol state.

none detail extensive

NCP state

CHAP state

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not-configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

(PPP) Network Control Protocol state.

detail extensive none

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not-configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

Chap-Chal-receivedChallenge was received but response not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

none detail extensive

CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)

Chap-Resp-sentResponse was sent for the challenge received.

ClosedCHAP authentication is incomplete.

FailureCHAP authentication failed.

Not-configuredCHAP is not configured on the interface.

SuccessCHAP 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, the IP
address of the interface is also displayed.

brief

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive none

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

1260

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 68: show interfaces (PPPoE) Output Fields (continued)

Field Name

Field Description

Level of Output

Addresses, Flags

Information about the addresses configured for the protocol family. Possible
values are described in the Addresses Flags section under Common Output
Fields Description on page 994.

detail 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.

detail extensive none

Sample Output
show interfaces (PPPoE)
user@host> show interfaces pp0
Physical interface: pp0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 24
Type: PPPoE, Link-level type: PPPoE, MTU: 1532
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
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
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 100
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:10:94:00:00:01,
Underlying interface: demux0.100 (Index 88)
Link:
ge-1/0/0.32767
ge-1/0/1.32767
Input packets : 6

Copyright 2014, Juniper Networks, Inc.

1261

Interfaces Fundamentals for Routing Devices

Output packets: 6
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
Not-configured
CHAP state: Closed
PAP state: Success
Protocol inet, MTU: 1500
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Primary
Local: 45.63.24.1

mpls:

show interfaces brief (PPPoE)

user@host> show interfaces pp0 brief
Physical interface: pp0, Enabled, Physical link is Up
Type: PPPoE, Link-level type: PPPoE, MTU: 1532, Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Logical interface pp0.0
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)
inet

show interfaces detail (PPPoE)

user@host> show interfaces pp0 detail
Physical interface: pp0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 24, Generation: 9
Type: PPPoE, Link-level type: PPPoE, MTU: 1532, Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Logical interface pp0.0 (Index 72) (SNMP ifIndex 72) (Generation 14)
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)
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:

1262

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Transit statistics:
Input bytes :
0
0
Output bytes :
0
0
Input packets:
0
0
Output packets:
0
0
LCP state: Not-configured
NCP state: inet: Not-configured, inet6: Not-configured, iso:
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 100, Generation: 14, Route table: 0
Flags: User-MTU, Negotiate-Address

bps
bps
pps
pps
Not-configured,

show interfaces detail (PPPoE on J Series Services Routers)

user@host> show interfaces pp0 detail
Physical interface: pp0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 24, Generation: 9
Type: PPPoE, Link-level type: PPPoE, MTU: 1532, Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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 72) (SNMP ifIndex 72) (Generation 14)
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)
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:

Copyright 2014, Juniper Networks, Inc.

1263

Interfaces Fundamentals for Routing Devices

Input bytes :
0
0
Output bytes :
0
0
Input packets:
0
0
Output packets:
0
0
LCP state: Not-configured
NCP state: inet: Not-configured, inet6: Not-configured, iso:
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 100, Generation: 14, Route table: 0
Flags: User-MTU, Negotiate-Address

bps
bps
pps
pps
Not-configured,

show interfaces extensive (PPPoE on M120 and M320 Routers)

user@host> show interfaces pp0 extensive
Physical interface: pp0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 93, Generation: 129
Type: PPPoE, Link-level type: PPPoE, MTU: 1532, Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Statistics last cleared: Never
Traffic statistics:
Input bytes :
972192
0 bps
Output bytes :
975010
0 bps
Input packets:
1338
0 pps
Output packets:
1473
0 pps
IPv6 transit 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:17:cb:48:c8: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
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0

1264

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Output packets:
0
Local statistics:
Input bytes :
252
Output bytes :
296
Input packets:
7
Output packets:
8
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 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
Protocol inet, MTU: 1492, Generation: 171, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 12.12.12.2, Local: 12.12.12.1, Broadcast: Unspecified,
Generation: 206

Copyright 2014, Juniper Networks, Inc.

1265

Interfaces Fundamentals for Routing Devices

show interfaces (PTX Series Packet Transport Routers)

Syntax

show interfaces et-fpc/pic/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Release Information

Command introduced in Junos OS Release 8.0.

Command introduced in Junos OS Release 12.1 for PTX Series Packet Transport Routers.

Description

(PTX Series Packet Transport Routers only) Display status information about the specified
Ethernet interface.

Options

et-fpc/pic/portDisplay standard information about the specified Ethernet interface.

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.

Required Privilege
Level
List of Sample Output

Output Fields

1266

view

show interfaces brief (PTX5000 Packet Transport Router) on page 1276

show interfaces extensive (PTX5000 Packet Transport Router) on page 1276
show interfaces terse (PTX5000 Packet Transport Router) on page 1277
See Table 69 on page 1267 for the output fields for the show interfaces (PTX Series Packet
Transport Routers) command.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 69: show interfaces PTX Series Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

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

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

BPDU Error

Bridge protocol data unit (BPDU) errors (if any).

All levels

MAC-Rewrite

MAC Rewrite errors (if any).

All levels

Loopback

Loopback status: Enabled or Disabled. If loopback is enabled, type of loopback:

Local or Remote.

All levels

Source filtering

Source filtering status: Enabled or Disabled.

All levels

Flow control

Flow control status: Enabled or Disabled.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description on page 994.

All levels

CoS queues

Number of CoS queues configured.

detail extensive none

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Current address

Configured MAC address.

detail extensive none

Hardware address

Hardware MAC address.

detail extensive none

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1267

Interfaces Fundamentals for Routing Devices

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

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).

detail extensive none

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

NOTE: Input bytes and output bytes are counted as Layer 3 packet length.
Input errors

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

Policed discardsNumber 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 incompletesNumber 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.
NOTE: The L3 incompletes field is not supported on PTX Series Packet
Transport Routers.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

FIFO errorsNumber 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.

1268

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

CollisionsNumber 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 packetsNumber 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 errorsNumber 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 errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

Egress queues

Total number of egress queues supported on the specified interface.

detail extensive

Queue counters
(Egress)

CoS queue number and its associated user-configured forwarding class name.

detail extensive

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Ingress queues

Total number of ingress queues supported on the specified interface.

extensive

Queue counters
(Ingress)

CoS queue number and its associated user-configured forwarding class name.

extensive

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Copyright 2014, Juniper Networks, Inc.

1269

Interfaces Fundamentals for Routing Devices

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

Active alarms and

Active defects

Ethernet-specific defects that can prevent the interface from passing 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.

detail extensive none

NoneThere are no active defects or alarms.

LinkInterface 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.
MAC statistics

Receive and Transmit statistics reported by the PIC's MAC subsystem, including

extensive

the following:

Total octets and total packetsTotal number of octets and packets.

Unicast packets, Broadcast packets, and Multicast packetsNumber of unicast,

broadcast, and multicast packets.

CRC/Align errorsTotal 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 errorNumber 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 framesNumber of MAC control frames.

MAC pause framesNumber of MAC control frames with pause operational

code.

Oversized framesNumber of frames that exceed 1518 octets.

Jabber framesNumber 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 framesTotal 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 framesNumber 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 violationsNumber of times an event caused the PHY to indicate Data

reception error or invalid data symbol error.

1270

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

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 should enter the system or be rejected.

Input packet countNumber of packets received from the MAC hardware

that the filter processed.

Input packet rejectsNumber of packets that the filter rejected because of

either the source MAC address or the destination MAC address.

Input DA rejectsNumber 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 rejectsNumber 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 countNumber of packets that the filter has given to the MAC

hardware.

Output packet pad countNumber 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 countNumber 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 filtersNumber 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.

Copyright 2014, Juniper Networks, Inc.

1271

Interfaces Fundamentals for Routing Devices

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

Autonegotiation
information

Information about link autonegotiation.

extensive

Negotiation status:

IncompleteEthernet interface has the speed or link mode configured.

No autonegotiationRemote Ethernet interface has the speed or link mode

configured, or does not perform autonegotiation.

CompleteEthernet interface is connected to a device that performs

autonegotiation and the autonegotiation process is successful.

Link partner statusOK when Ethernet interface is connected to a device that

performs autonegotiation and the autonegotiation process is successful.

Link partner:

Link modeDepending on the capability of the attached Ethernet device,

either Full-duplex or Half-duplex.

Flow controlTypes 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 faultRemote fault information from the link partnerFailure

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 resolutionInformation from the link partner:

Flow controlTypes 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 faultRemote fault information. Link OK (no error detected on

receive), Offline (local interface is offline), and Link Failure (link error

detected on receive).
Packet Forwarding
Engine
configuration

1272

Information about the configuration of the Packet Forwarding Engine:

extensive

Destination slotFPC slot number.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Copyright 2014, Juniper Networks, Inc.

1273

Interfaces Fundamentals for Routing Devices

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

VLAN-Tag

Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN
tag or for both the outer and inner (In) VLAN tags.

brief detail extensive

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

popThe outer VLAN tag of the incoming frame is removed.

swapThe outer VLAN tag of the incoming frame is overwritten with the

none

user-specified VLAN tag information.

pushAn outer VLAN tag is pushed in front of the existing VLAN tag.

push-pushTwo VLAN tags are pushed in from the incoming frame.

swap-pushThe 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-swapBoth the inner and the outer VLAN tags of the incoming frame

are replaced by the user-specified VLAN tag value.

pop-swapThe 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-popBoth 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

demux underlying interface. The output is one of the following:

Source Family Inet

Destination Family Inet

detail extensive none

Encapsulation

Encapsulation on the logical interface.

All levels

Protocol

Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description on page 994.

detail 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
the logical interface.

detail extensive none

Traffic statistics

Number and rate of bytes and packets received and transmitted on the specified
interface set.

detail extensive

Input bytes, Output bytesNumber of bytes received and transmitted on the

interface set

Input packets, Output packetsNumber of packets received and transmitted

on the interface set.

NOTE: Input bytes and output bytes are counted as Layer 3 packet length.
IPv6 transit
statistics

Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.

extensive

Local statistics

Number and rate of bytes and packets destined to the router.

extensive

1274

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 69: show interfaces PTX Series Output Fields (continued)

Field Name

Field Description

Level of Output

Transit statistics

Number and rate of bytes and packets transiting the switch.

extensive

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route Table

Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive none

Flags

Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description on page 994.

detail extensive

Donor interface

(Unnumbered Ethernet) Interface from which an unnumbered Ethernet interface

borrows an IPv4 address.

detail extensive none

Preferred source
address

(Unnumbered Ethernet) Secondary IPv4 address of the donor loopback interface

that acts as the preferred source address for the unnumbered Ethernet interface.

detail extensive none

Input Filters

Names of any input filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parentheses next to all interfaces.

detail extensive

Output Filters

Names of any output filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parentheses next to all interfaces.

detail extensive

Mac-Validate
Failures

Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail extensive none

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.

brief

Flags

Information about flags (possible values are described in the Addresses Flags
section under Common Output Fields Description on page 994.

detail 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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1275

Interfaces Fundamentals for Routing Devices

Sample Output
show interfaces brief (PTX5000 Packet Transport Router)
user@host> show interfaces brief et-7/0/0
Physical interface: et-7/0/0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Loopback: Disabled, Source
filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None

show interfaces extensive (PTX5000 Packet Transport Router)

user@host> show interfaces et-7/0/0 extensive
Physical interface: et-7/0/0, Enabled, Physical link is Up
Interface index: 168, SNMP ifIndex: 501, Generation: 171
Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow
control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 88:e0:f3:3b:de:43, Hardware address: 88:e0:f3:3b:de:43
Last flapped
: 2012-01-18 11:48:24 PST (01:51:00 ago)
Statistics last cleared: 2012-01-18 13:38:54 PST (00:00:30 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit 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:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Queue number:
0
1
2
3

1276

Mapped forwarding classes

best-effort
expedited-forwarding
assured-forwarding
network-control

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Active alarms : None

Active defects : None
MAC statistics:
Receive
Total octets
0
Total packets
0
Unicast packets
0
Broadcast packets
0
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Autonegotiation information:
Negotiation status: Incomplete
Packet Forwarding Engine configuration:
Destination slot: 7
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Limit
%
bps
%
0 best-effort
95
9500000000
95
none
3 network-control
5
500000000
5
none
Interface transmit statistics: Disabled

Transmit
0
0
0
0
0
0
0
0
0

0
0
0

Buffer Priority
usec
0

low

low

show interfaces terse (PTX5000 Packet Transport Router)

user@host> show interfaces terse
Interface
Admin Link Proto
et-2/0/0
up
up
et-2/0/1
up
up
et-2/0/2
up
up
et-2/0/3
up
up
et-2/0/4
up
up
et-2/0/5
up
down
et-2/0/6
up
up
et-2/0/7
up
up
et-2/0/8
up
up
et-2/0/9
up
down
et-2/0/10
up
up
et-2/0/11
up
up
et-2/0/12
up
up
et-2/0/13
up
down
et-2/0/14
up
up
et-2/0/15
up
up

Copyright 2014, Juniper Networks, Inc.

Local

Remote

1277

Interfaces Fundamentals for Routing Devices

et-2/0/16
et-2/0/17
et-2/0/18
et-2/0/19
et-2/0/20
et-2/0/21
et-2/0/22
et-2/0/23
et-2/1/0
et-2/1/1
et-2/1/2
et-2/1/3
et-2/1/4
et-2/1/5
et-2/1/6
et-2/1/7
et-2/1/8
et-2/1/9
et-2/1/10
et-2/1/11
et-2/1/12
et-2/1/13
et-2/1/14
et-2/1/15
et-2/1/16
et-2/1/17
et-2/1/18
et-2/1/19
et-2/1/20
et-2/1/21
et-2/1/22
et-2/1/23
et-5/0/0
et-5/0/0.0
et-5/0/0.32767
et-5/0/1
et-5/0/2
et-5/0/3
et-5/0/4
et-5/0/5
et-5/0/5.0
et-5/0/5.32767
et-5/0/6
et-5/0/7
et-5/0/8
et-5/0/9
et-5/0/10
et-5/0/11
et-5/0/12
et-5/0/13
et-5/0/14
et-5/0/15
et-5/0/16
et-5/0/17
et-5/0/18
et-5/0/19
et-5/0/20
et-5/0/21
et-5/0/22
et-5/0/23
et-5/1/0

1278

up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up

up
down
down
up
down
up
down
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
down
down
up
up
up
up
up
down
up
up
up
up
down
down
up
up
up
up
up
down
down
up
up
up

ccc
multiservice

ccc
multiservice

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

et-5/1/1
et-7/0/0
et-7/0/1
et-7/0/2
et-7/0/3
et-7/0/4
et-7/0/5
et-7/0/6
et-7/0/7
et-7/0/8
et-7/0/9
et-7/0/10
et-7/0/11
et-7/0/12
et-7/0/13
et-7/0/14
et-7/0/15
et-7/0/16
et-7/0/17
et-7/0/18
et-7/0/19
et-7/0/20
et-7/0/21
et-7/0/22
et-7/0/23
dsc
em0
em0.0
gre
ipip
ixgbe0
ixgbe0.0

up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up

up
up
up
up
up
up
up
up
up
up
up
down
down
down
down
down
down
down
down
down
down
down
down
down
down
up
up
up
inet
up
up
up
up
inet

inet6
tnp
ixgbe1
ixgbe1.0

up
up

up
up

inet

inet6
tnp
lo0
lo0.0

up
up

up
up

inet

192.168.177.61/25

10.0.0.4/8
128.0.0.1/2
128.0.0.4/2
fe80::200:ff:fe00:4/64
fec0::a:0:0:4/64
0x4
10.0.0.4/8
128.0.0.1/2
128.0.0.4/2
fe80::200:1ff:fe00:4/64
fec0::a:0:0:4/64
0x4
10.255.177.61
127.0.0.1

--> 0/0
--> 0/0

iso
47.0005.80ff.f800.0000.0108.0001.0102.5517.7061
inet6
abcd::10:255:177:61
fe80::ee9e:cd0f:fc02:b01e
lo0.16384
up
up
inet
127.0.0.1
--> 0/0
lo0.16385
up
up
inet
lsi
up
up
mtun
up
up
pimd
up
up
pime
up
up
tap
up
up

Copyright 2014, Juniper Networks, Inc.

1279

Interfaces Fundamentals for Routing Devices

show interfaces (SONET/SDH)

Syntax

Release Information
Description

Options

show interfaces so-fpc/pic/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

(M Series and T Series routers only) Display status information about the specified
SONET/SDH interface.
so-fpc/pic/portDisplay standard information about the specified SONET/SDH interface.
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.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

1280

view

SONET/SDH Interfaces Overview

show interfaces (SDH Mode, PPP) on page 1293

show interfaces brief (SDH Mode, PPP) on page 1294
show interfaces detail (SDH Mode, PPP) on page 1294
show interfaces extensive (SDH Mode, PPP) on page 1295
show interfaces brief (SONET Mode, Frame Relay) on page 1297
show interfaces (SONET Mode, Frame Relay) on page 1297
show interfaces detail (SONET Mode, Frame Relay) on page 1298
show interfaces extensive (SONET Mode, Frame Relay) on page 1300
show interfaces extensive (OC768-over-4xOC192 Mode) on page 1302
show interfaces detail (IPv6 Tracking) on page 1305
show interfaces (shared interface) on page 1306
Table 70 on page 1281 lists the output fields for the show interfaces (SONET/SDH)
command. Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 70: SONET/SDH show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, 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

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

SONET/SDH reference clock source: Internal or External. Clocking is configured

and displayed only for channel 0.

All levels

Framing mode

Framing mode: SONET or SDH.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Payload scrambler

Whether payload scrambling is enabled.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Shared-interface

Indicates whether the routing domain is the owner or non-owner of the shared
interface. If the routing domain is the Root System Domain (RSD), the value is
Owner. If the routing domain is a Protected System Domain (PSD) under the
RSD, the value is Non-owner.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Physical Interface

Copyright 2014, Juniper Networks, Inc.

1281

Interfaces Fundamentals for Routing Devices

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

ANSI or ITU LMI

settings

(Frame Relay) Settings for Local Management Interface (LMI). The format is
(ANSI or ITU) LMI settings: value, value... xx seconds, where value can be:

All levels

n391dteDTE full status polling interval (1-255)

n392dceDCE error threshold (1-10)

n392dteDTE error threshold (1-10)

n393dceDCE monitored event count (1-10)

n393dteDTE monitored event count (1-10)

t391dteDTE polling timer (5-30 seconds)

t392dceDCE polling verification timer (5-30 seconds)

LMI

Input: value (hh:mm:ss ago), Output: value (hh:mm:ss ago)

brief none

LMI statistics

(Frame Relay) LMI packet statistics:

detail extensive

DTE statistics

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
sent hh:mm:ss ago).

(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data circuit-terminating equipment (DCE):

Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.

Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.

Enquiry responses receivedNumber of enquiry responses received by the

detail extensive none

DTE from the DCE.

Full enquiry responses receivedNumber of full enquiry responses sent from

the DTE to the DCE.

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

Enquiries receivedNumber of enquiries received by the DCE from the DTE.

Full enquiries receivedNumber of full enquiries received by the DCE from

detail extensive none

the DTE.

Enquiry responses sentNumber of enquiry responses sent from the DCE to

the DTE.

Full enquiry responses sentNumber of full enquiry responses sent from the

DCE to the DTE.

1282

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

detail extensive none

Unknown messages receivedNumber of received packets that do not fall

into any category.

Asynchronous updates receivedNumber of link status peer changes received.

Out-of-sequence packets receivedNumber of packets for which the sequence

of the packets received is different from the expected sequence.

Keepalive responses timedoutNumber of keepalive responses that timed

out when no LMI packet was reported for n392dte or n393dce intervals. (See
LMI settings.)

Nonmatching
DCE-end DLCIs

(Frame Relay. Displayed only from the DTE) Number of DLCIs configured from
the DCE.

detail extensive

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Keepalive settings

(PPP and HDLC) Configured settings for keepalives.

All levels

Keepalive or
Keepalive statistics

interval secondsThe time in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

down-count numberThe 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 numberThe number of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.

(PPP and HDLC) Information about keepalive packets.

InputNumber of keepalive packets received by PPP.

All levels

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the format hh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

LCP state

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

(PPP) Link Control Protocol state.

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not-configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

Copyright 2014, Juniper Networks, Inc.

detail extensive none

1283

Interfaces Fundamentals for Routing Devices

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

NCP state

(PPP) Network Control Protocol state.

detail extensive none

CHAP state

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not-configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

Chap-Chal-receivedChallenge was received but response not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

CHAP has not yet moved into the Success state. (Most likely with RADIUS

detail extensive none

authentication.)

Chap-Resp-sentResponse was sent for the challenge received.

ClosedCHAP authentication is incomplete.

FailureCHAP authentication failed.

Not-configuredCHAP is not configured on the interface.

SuccessCHAP authentication was successful.

CoS queues

Number of CoS queues configured.

detail extensive none

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).

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number of bytes and packets received and transmitted on the physical interface,
and the traffic rate in bits per seconds (bps).

detail extensive

1284

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Label-switched
interface (LSI)
traffic statistics

(Frame Relay) LSI traffic statistics:

extensive

Input bytesNumber of bytes and speed, in bits per second (bps), received

on the interface.

Output packetsNumber of packets and speed, in bps, transmitted on the

interface.
Input errors

Input errors on the interface whose definitions are as follows:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

GiantsNumber of frames received that are larger than the giant threshold.

Bucket DropsDrops resulting from the traffic load exceeding the interface
transmit/receive leaky bucket configuration. The default is off.

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

HS link CRC errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

HS link FIFO overflowsNumber of FIFO overflows on the high-speed links

between the ASICs responsible for handling the router interfaces.

Copyright 2014, Juniper Networks, Inc.

1285

Interfaces Fundamentals for Routing Devices

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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 underflowsNumber of FIFO underflows on the high-speed links

between the ASICs responsible for handling the router interfaces.

IPv6 transit
statistics

MTU errorsNumber of packets whose size exceeds the MTU of the interface.

Number of transit bytes and packets received and transmitted on the physical
interface if IPv6 statistics tracking is enabled.

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

detail extensive

Egress queues

Total number of egress queues supported on the specified interface.

detail extensive

Queue counters

CoS queue number and its associated user-configured forwarding class name.

extensive

SONET alarms
SONET defects

Link

1286

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

(SONET) SONET media-specific alarms and defects that prevents the interface
from passing packets. When a defect persists for a certain period, 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 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.

All levels

(For 4-port OC192c PIC operating in OC768-over-4xOC192 mode) The link

number. Errors and alarms are displayed for each link.

extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SONET PHY

Counts of specific SONET errors with detailed information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SONET section

PLL LockPhase-locked loop

PHY LightLoss of optical signal

Counts of specific SONET errors with detailed information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

SONET line

BIP-B1Bit interleaved parity for SONET section overhead

SEFSeverely errored framing

LOLLoss of light

LOFLoss of frame

ES-SErrored seconds (section)

SES-SSeverely errored seconds (section)

SEFS-SSeverely errored framing seconds (section)

Active alarms and defects, plus counts of specific SONET errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

BIP-B2Bit interleaved parity for SONET line overhead

REI-LRemote error indication (near-end line)

RDI-LRemote defect indication (near-end line)

AIS-LAlarm indication signal (near-end line)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

ES-LErrored seconds (near-end line)

SES-LSeverely errored seconds (near-end line)

UAS-LUnavailable seconds (near-end line)

ES-LFEErrored seconds (far-end line)

SES-LFESeverely errored seconds (far-end line)

UAS-LFEUnavailable seconds (far-end line)

Copyright 2014, Juniper Networks, Inc.

1287

Interfaces Fundamentals for Routing Devices

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SONET path

Active alarms and defects, plus counts of specific SONET errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other thanOK indicates a problem.

Subfields are:

Received SONET
overhead

BIP-B3Bit interleaved parity for SONET section overhead

REI-PRemote error indication

LOP-PLoss of pointer (path)

AIS-PPath alarm indication signal

RDI-PPath remote defect indication

UNEQ-PPath unequipped

PLM-PPath payload (signal) label mismatch

ES-PErrored seconds (near-end STS path)

SES-PSeverely errored seconds (near-end STS path)

UAS-PUnavailable seconds (near-end STS path)

ES-PFEErrored seconds (far-end STS path)

SES-PFESeverely errored seconds (far-end STS path)

UAS-PFEUnavailable seconds (far-end STS path)

Values of the received and transmitted SONET overhead:

Transmitted
SONET overhead

extensive

C2Signal label. Allocated to identify the construction and content of the

STS-level SPE and for PDI-P.

F1Section user channel byte. This byte is set aside for the purposes of users.

K1 and K2These bytes are allocated for APS signaling for the protection of

the multiplex section.

J0Section 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.

S1Synchronization status. The S1 byte is located in the first STS-1 of an

STS-N.

SDH alarms
SDH defects

1288

Z3 and Z4Allocated for future use.

SDH media-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain period, 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 light the red or yellow alarm LED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.

All levels

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SDH PHY

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

SDH regenerator
section

PLL LockPhase-locked loop

PHY LightLoss of optical signal

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

SDH multiplex
section

RS-BIP824-bit BIP for multiplex section overhead (B2 bytes)

OOFOut of frame

LOSLoss of signal

LOFLoss of frame

RS-ESErrored seconds (near-end regenerator section)

RS-SESSeverely errored seconds (near-end regenerator section)

RS-SEFSSeverely errored framing seconds (regenerator section)

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

extensive

Subfields are:

MS-BIP248-bit BIP for high-order path overhead (B3 byte)

MS-FEBEFar-end block error (multiplex section)

MS-FERFFar-end remote fail (multiplex section)

MS-AISAlarm indication signal (multiplex section)

BERR-SFBit error rate fault (signal failure)

BERR-SDBit error rate defect (signal degradation)

MS-ESErrored seconds (near-end multiplex section)

MS-SESSeverely errored seconds (near-end multiplex section)

MS-UASUnavailable seconds (near-end multiplex section)

MS-ES-FEErrored seconds (far-end multiplex section)

MS-SES-FESeverely errored seconds (far-end multiplex section)

MS-UAS-FEUnavailable seconds (far-end multiplex section)

Copyright 2014, Juniper Networks, Inc.

1289

Interfaces Fundamentals for Routing Devices

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

SDH path

Active alarms and defects, plus counts of specific SDH errors with detailed
information.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

Subfields are:

Received SDH
overhead

HP-BIP88-bit BIP for regenerator section overhead (B1 byte)

HP-FEBEFar-end block error (high-order path)

HP-LOPLoss of pointer (high-order path)

HP-AISHigh-order-path alarm indication signal

HP-FERFFar-end remote fail (high-order path)

HP-UNEQUnequipped (high-order path)

HP-PLMPayload label mismatch (high-order path)

HP-ESErrored seconds (near-end high-order path)

HP-SESSeverely errored seconds (near-end high-order path)

HP-UASUnavailable seconds (near-end high-order path)

HP-ES-FEErrored seconds (far-end high-order path)

HP-SES-FESeverely errored seconds (far-end high-order path)

HP-UAS-FEUnavailable seconds (far-end high-order path)

Values of the received and transmitted SONET overhead:

Transmitted SDH
overhead

extensive

C2Signal label. Allocated to identify the construction and content of the

STS-level SPE and for PDI-P.

F1Section user channel byte. This byte is set aside for the purposes of users.

K1 and K2These bytes are allocated for APS signaling for the protection of

the multiplex section.

J0Section 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.

S1Synchronization status. The S1 byte is located in the first STS-1 of an

STS-N.

Received path trace

Transmitted path
trace

1290

Z3 and Z4Allocated for future use.

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 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.

extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

HDLC configuration

Information about the HDLC configuration.

extensive

CoS information

Policing bucketConfigured state of the receiving policer.

Shaping bucketConfigured state of the transmitting shaper.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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.
Packet Forwarding
Engine
configuration

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

extensive

Logical Interface
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

PPP parameters

The PPP loopback clear timer value.

extensive

Copyright 2014, Juniper Networks, Inc.

1291

Interfaces Fundamentals for Routing Devices

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Shared interface

Provides the following information:

All levels

shared with(RSD only) Indicates which PSD owns the logical shared
interface. For example, psd3.

peer interface(PSD only) Lists the logical tunnel interface that peers with
the logical shared interface. For example, ut-2/1/0.2.

tunnel tokenSpecifies the receive (RX) and transmit (TX) tunnel tokens.
For example, Rx: 5.519, Tx: 13.514.

Input packets

Number of packets received on the logical interface.

None specified

Output packets

Number of packets transmitted on the logical interface.

None specified

Traffic statistics

Total number of bytes and packets received and transmitted on the logical
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. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Local statistics

Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Transit statistics

Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. It
takes awhile (generally, less than 1 second) for this counter to stabilize.

detail extensive

Protocol

Protocol family configured on the logical interface, such as iso, inet6, or mpls.

detail extensive none

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.

brief

Multilink bundle

(If the logical interface is configured as part of a multilink bundle.) Interface

name for the multilink bundle.

detail extensive none

AS bundle

(If the logical interface is configured as part of an aggregated SONET bundle.)

AS bundle number.

detail extensive

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

1292

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 70: SONET/SDH show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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 interface.

detail extensive none

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI
information is displayed: Flags, Total down time, Last down, and Traffic statistics.
Flags is one or more of the following:

detail extensive

ActiveSet when the link is active and the DTE and DCE are exchanging

information.

DownSet when the link is active, but no information is received from the

DCE.

DLCI statistics

UnconfiguredSet when the corresponding DLCI in the DCE is not configured.

ConfiguredSet when the corresponding DLCI in the DCE is configured.

Dce-configuredDisplayed when the command is issued from the DTE.

(Frame Relay) Data-link connection identifier (DLCI) statistics.

Active DLCINumber of active DLCIs.

Inactive DLCINumber of inactive DLCIs.

detail extensive none

Sample Output
show interfaces (SDH Mode, PPP)
user@host> show interfaces so-0/0/0
Physical interface: so-0/0/0, Enabled, Physical link is Up
Interface index: 149, SNMP ifIndex: 66
Link-level type: PPP, MTU: 4474, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 30 (00:00:07 ago), Output: 29 (00:00:05 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2006-03-24 13:20:56 PST (00:05:09 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SDH
alarms
: None
SDH
defects : None

Copyright 2014, Juniper Networks, Inc.

1293

Interfaces Fundamentals for Routing Devices

Logical interface so-0/0/0.0 (Index 66) (SNMP ifIndex 43)

Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.0/30, Local: 10.0.12.1, Broadcast: 10.0.12.3
Protocol iso, MTU: 4470
Flags: Protocol-Down
Protocol mpls, MTU: 4458, Maximum labels: 3
Flags: Protocol-Down, Is-Primary

show interfaces brief (SDH Mode, PPP)

user@host> show interfaces so-0/0/0 brief
Physical interface: so-0/0/0, Enabled, Physical link is Up
Link-level type: PPP, MTU: 4474, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 25 (00:00:01 ago), Output: 24 (00:00:04 ago)
SDH
alarms
: None
SDH
defects : None
Logical interface so-0/0/0.0
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
inet 10.0.12.1/30
iso
mpls

show interfaces detail (SDH Mode, PPP)

user@host> show interfaces so-0/0/0 detail
Physical interface: so-0/0/0, Enabled, Physical link is Up
Interface index: 149, SNMP ifIndex: 66, Generation: 35
Link-level type: PPP, MTU: 4474, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 33 (last seen 00:00:05 ago)
Output: 32 (last sent 00:00:06 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2006-03-24 13:20:56 PST (00:05:38 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
862
0 bps
Output bytes :
3592
64 bps
Input packets:
70
0 pps
Output packets:
330
0 pps
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets

1294

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

329

329

SDH
SDH

alarms
defects

: None
: None

Logical interface so-0/0/0.0 (Index 66) (SNMP ifIndex 43) (Generation 19)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 4470, Generation: 48, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.0/30, Local: 10.0.12.1, Broadcast: 10.0.12.3,
Generation: 48
Protocol iso, MTU: 4470, Generation: 49, Route table: 0
Flags: Protocol-Down
Protocol mpls, MTU: 4458, Maximum labels: 3, Generation: 50, Route table: 0
Flags: Protocol-Down, Is-Primary

show interfaces extensive (SDH Mode, PPP)

user@host> show interfaces so-0/0/0 extensive
Physical interface: so-0/0/0, Enabled, Physical link is Up
Interface index: 149, SNMP ifIndex: 66, Generation: 35
Link-level type: PPP, MTU: 4474, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 36 (last seen 00:00:01 ago)
Output: 35 (last sent 00:00:10 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2006-03-24 13:20:56 PST (00:06:08 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
922
0 bps
Output bytes :
3850
64 bps
Input packets:
75
0 pps
Output packets:
356
0 pps
Label-switched interface (LSI) traffic statistics:
Input bytes :
0
0 bps
Input packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Bucket drops: 0, Policed discards: 218, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 2, HS link CRC errors: 0,
HS link FIFO overflows: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0,
HS link FIFO underflows: 0, MTU errors: 0

Copyright 2014, Juniper Networks, Inc.

1295

Interfaces Fundamentals for Routing Devices

Egress queues: 4 supported, 4 in use

Queue counters:
Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

354

354

SDH
alarms
: None
SDH
defects : None
SDH PHY:
Seconds
Count
PLL Lock
0
0
PHY Light
2
1
SDH regenerator section:
RS-BIP8
0
0
OOF
3
8
LOS
3
2
LOF
3
2
RS-ES
3
RS-SES
3
RS-SEFS
3
SDH multiplex section:
MS-BIP24
0
0
MS-FEBE
0
0
MS-FERF
3
2
MS-AIS
2
1
BERR-SF
0
0
BERR-SD
0
0
MS-ES
3
MS-SES
3
MS-UAS
0
MS-SES-FE
3
MS-UAS-FE
0
SDH path:
HP-BIP8
0
0
HP-FEBE
0
0
HP-LOP
1
1
HP-AIS
2
1
HP-FERF
3
2
HP-UNEQ
0
0
HP-PLM
1
1
HP-ES
3
HP-SES
3
HP-UAS
0
HP-ES-FE
3
HP-SES-FE
3
HP-UAS-FE
0
Received SDH overhead:
F1
: 0x00, J0
: 0x00, K1
:
S1
: 0x00, C2
: 0xcf, C2(cmp) :
Z3
: 0x00, Z4
: 0x00, S1(cmp) :
Transmitted SDH overhead:
F1
: 0x00, J0
: 0x01, K1
:
S1
: 0x00, C2
: 0xcf, F2
:
Z4
: 0x00
Received path trace: R2 so-0/0/0
52 32 20 73 6f 2d 30 2f 30 2f 30 00 00 00
Transmitted path trace: R1 so-0/0/0

1296

State
OK
OK

OK
OK
OK

OK
OK
OK
OK

OK
OK
OK
OK
OK

0x00, K2
0xcf, F2
0x00

: 0x00
: 0x00

0x00, K2
0x00, Z3

: 0x00
: 0x00

00 00

R2 so-0/0/0.....

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

52 31 20 73 6f 2d 30 2f 30 2f 30 00 00 00 00 00
R1 so-0/0/0.....
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 4484, Runt threshold: 3
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95 147744000 95
0
low
none
3 network-control 5
7776000
5
0
low
none
Logical interface so-0/0/0.0 (Index 66) (SNMP ifIndex 43) (Generation 19)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
PPP parameters:
PPP loopback clear timer: 3 sec
Protocol inet, MTU: 4470, Generation: 48, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.12.0/30, Local: 10.0.12.1, Broadcast: 10.0.12.3,
Generation: 48
Protocol iso, MTU: 4470, Generation: 49, Route table: 0
Flags: Protocol-Down
Protocol mpls, MTU: 4458, Maximum labels: 3, Generation: 50, Route table: 0
Flags: Protocol-Down, Is-Primary
MS-ES-FE
3

show interfaces brief (SONET Mode, Frame Relay)

user@host> show interfaces so-0/0/0 brief
Physical interface: so-0/0/0, Enabled, Physical link is Up
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 29 (00:00:02 ago), Output: 28 (00:00:01 ago)
SONET alarms
: None
SONET defects : None
Logical interface so-0/0/0.0
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
inet 10.0.12.1
--> 10.0.12.2
iso
mpls
DLCI 16
Flags: Down, DCE-Unconfigured
Total down time: 00:04:12 sec, Last down: 00:04:12 ago

show interfaces (SONET Mode, Frame Relay)

user@host> show interfaces so-0/0/0
Physical interface: so-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 66
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives DTE

Copyright 2014, Juniper Networks, Inc.

1297

Interfaces Fundamentals for Routing Devices

ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds

LMI: Input: 23 (00:00:05 ago), Output: 22 (00:00:03 ago)
DTE statistics:
Enquiries sent
: 19
Full enquiries sent
: 3
Enquiry responses received
: 20
Full enquiry responses received
: 3
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2006-03-06 11:53:20 PST (3d 03:09 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 56 bps (0 pps)
SONET alarms
: None
SONET defects : None
Logical interface so-0/0/0.0 (Index 79) (SNMP ifIndex 43)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Input packets : 0
Output packets: 0
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.0.12.2, Local: 10.0.12.1
Protocol iso, MTU: 4470
Flags: None
Protocol mpls, MTU: 4450, Maximum labels: 3
DLCI 16
Flags: Down, DCE-Unconfigured
Total down time: 00:03:11 sec, Last down: 00:03:11 ago
Input packets : 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

show interfaces detail (SONET Mode, Frame Relay)

user@host> show interfaces so-0/0/0 detail
Physical interface: so-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 66, Generation: 11
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives DTE
Hold-times
: Up 0 ms, Down 0 ms
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI statistics:
Input : 33 (last seen 00:00:09 ago)
Output: 32 (last sent 00:00:01 ago)
DTE statistics:
Enquiries sent
: 27
Full enquiries sent
: 5

1298

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Enquiry responses received

: 28
Full enquiry responses received
: 5
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2006-03-06 11:53:20 PST (3d 03:10 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
495368
0
Output bytes :
2765014
56
Input packets:
41165
0
Output packets:
133530
0
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
0 best-effort

bps
bps
pps
pps
Dropped packets

18

18

1 expedited-fo

2 assured-forw

3 network-cont

133506

133506

SONET alarms
: None
SONET defects : None
Logical interface so-0/0/0.0 (Index 79) (SNMP ifIndex 43) (Generation 28)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 49, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.0.12.2, Local: 10.0.12.1, Broadcast: Unspecified,
Generation: 61
Protocol iso, MTU: 4470, Generation: 50, Route table: 0
Flags: None
Protocol mpls, MTU: 4450, Maximum labels: 3, Generation: 51, Route table: 0
DLCI 16
Flags: Down, DCE-Unconfigured
Total down time: 00:04:54 sec, Last down: 00:04:54 ago

Copyright 2014, Juniper Networks, Inc.

1299

Interfaces Fundamentals for Routing Devices

Traffic statistics:
Input bytes :
Output bytes :
Input packets:
Output packets:
DLCI statistics:
Active DLCI :0 Inactive DLCI

0
0
0
0
:1

show interfaces extensive (SONET Mode, Frame Relay)

user@host> show interfaces so-0/0/0 extensive
Physical interface: so-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 66, Generation: 11
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives DTE
Hold-times
: Up 0 ms, Down 0 ms
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI statistics:
Input : 39 (last seen 00:00:02 ago)
Output: 36 (last sent 00:00:07 ago)
DTE statistics:
Enquiries sent
: 30
Full enquiries sent
: 6
Enquiry responses received
: 33
Full enquiry responses received
: 6
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2006-03-06 11:53:20 PST (3d 03:11 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
495452
56 bps
Output bytes :
2765074
0 bps
Input packets:
41171
0 pps
Output packets:
133534
0 pps
Label-switched interface (LSI) traffic statistics:
Input bytes :
0
0 bps
Input packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Bucket drops: 0, Policed discards: 0, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0, HS link CRC errors: 0,
HS link FIFO overflows: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0,
HS link FIFO underflows: 0, MTU errors: 0
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1300

18

18

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

1 expedited-fo

2 assured-forw

3 network-cont

133510

133510

SONET alarms
: None
SONET defects : None
SONET PHY:
Seconds
Count
PLL Lock
0
0
PHY Light
60
1
SONET section:
BIP-B1
0
0
SEF
108
158
LOS
108
2
LOF
108
2
ES-S
108
SES-S
108
SEFS-S
108
SONET line:
BIP-B2
0
0
REI-L
0
0
RDI-L
1
1
AIS-L
107
1
BERR-SF
0
0
BERR-SD
44
2
ES-L
108
SES-L
108
UAS-L
97
ES-LFE
1
SES-LFE
1
UAS-LFE
0
SONET path:
BIP-B3
0
0
REI-P
0
0
LOP-P
1
1
AIS-P
107
1
RDI-P
1
1
UNEQ-P
0
0
PLM-P
1
1
ES-P
108
SES-P
108
UAS-P
97
ES-PFE
1
SES-PFE
1
UAS-PFE
0
Received SONET overhead:
F1
: 0x00, J0
: 0x00, K1
:
S1
: 0x00, C2
: 0xcf, C2(cmp) :
Z3
: 0x00, Z4
: 0x00, S1(cmp) :
Transmitted SONET overhead:
F1
: 0x00, J0
: 0x01, K1
:
S1
: 0x00, C2
: 0xcf, F2
:
Z4
: 0x00
Received path trace: R2 so-0/0/0
52 32 20 73 6f 2d 30 2f 30 2f 30 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
Transmitted path trace: R1 so-0/0/0

Copyright 2014, Juniper Networks, Inc.

State
OK
OK

OK
OK
OK

OK
OK
OK
OK

OK
OK
OK
OK
OK

0x00, K2
0xcf, F2
0x00

: 0x00
: 0x00

0x00, K2
0x00, Z3

: 0x00
: 0x00

00
00
00
0d

00
R2 so-0/0/0.....
00 ................
00 ................
0a ................

1301

Interfaces Fundamentals for Routing Devices

52 31 20 73 6f 2d 30 2f 30 2f 30 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 4484, Runt threshold: 3
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
%
bps
%
0 best-effort
95
147744000
95
3 network-control
5
7776000
5

00
00
00
00

00
R1 so-0/0/0.....
00 ................
00 ................
00 ................

Buffer
usec
0
0

Priority

Limit

low
low

none
none

Logical interface so-0/0/0.0 (Index 79) (SNMP ifIndex 43) (Generation 28)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 49, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.0.12.2, Local: 10.0.12.1, Broadcast: Unspecified,
Generation: 61
Protocol iso, MTU: 4470, Generation: 50, Route table: 0
Flags: None
Protocol mpls, MTU: 4450, Maximum labels: 3, Generation: 51, Route table: 0
DLCI 16
Flags: Down, DCE-Unconfigured
Total down time: 00:05:42 sec, Last down: 00:05:42 ago
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

show interfaces extensive (OC768-over-4xOC192 Mode)

user@host> show interfaces so-7/0/0 extensive
Physical interface: so-7/0/0, Enabled, Physical link is Up
Interface index: 163, SNMP ifIndex: 23, Generation: 186
Link-level type: Cisco-HDLC, MTU: 4474, Clocking: Internal, SONET mode, Speed:
OC768,
Loopback: Local, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running

1302

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000

Link flags
: No-Keepalives
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-01-13 10:43:39 PST (01:05:33 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
76992
200 bps
Output bytes :
83707
216 bps
Input packets:
1343
0 pps
Output packets:
1343
0 pps
Input errors:
Errors: 0, Drops: 3885, Framing errors: 68154624, Runts: 0, Giants: 0, Bucket
drops: 0,
Policed discards: 0, L3 incompletes: 95040248, L2 channel errors: 0, L2
mismatch timeouts: 0,
HS link CRC errors: 0, HS link FIFO overflows: 30742070
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, HS link FIFO
underflows: 0,
MTU errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

1341

1341

SONET alarms
SONET defects
Link : 0
SONET alarms
SONET defects
SONET PHY:
PLL Lock
PHY Light
SONET section:
BIP-B1
SEF
LOS
LOF
ES-S
SES-S
SEFS-S
SONET line:
BIP-B2
REI-L
RDI-L
AIS-L
BERR-SF
BERR-SD
ES-L
SES-L
UAS-L
ES-LFE
SES-LFE
UAS-LFE

Copyright 2014, Juniper Networks, Inc.

: None
: None
: None
: None
Seconds
0
0

Count
0
0

State
OK
OK

0
2
0
3
2
2
2

0
1
0
2

OK
OK
OK

0
0
1
2
0
0
3
3
0
1
1
0

0
0
1
1
0
0

OK
OK
OK
OK

1303

Interfaces Fundamentals for Routing Devices

SONET path:
BIP-B3
0
0
REI-P
0
0
LOP-P
0
0
AIS-P
2
1
RDI-P
0
0
UNEQ-P
0
0
PLM-P
0
0
ES-P
3
SES-P
3
UAS-P
0
ES-PFE
0
SES-PFE
0
UAS-PFE
0
Payload pointer:
Current pointer
: 522
Pointer increment count
: 0
Pointer decrement count
: 0
New pointer NDF count
: 0
Received SONET overhead:
F1
: 0x00, J0
: 0x01, K1
:
S1
: 0x00, C2
: 0xcf, C2(cmp) :
Z3
: 0x00, Z4
: 0x00, S1(cmp) :
Transmitted SONET overhead:
F1
: 0x00, J0
: 0x01, K1
:
S1
: 0x00, C2
: 0xcf, F2
:
Z4
: 0x00
Received path trace: fold so-7/0/0
66 6f 6c 64 20 73 6f 2d 37 2f 30 2f 30 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
Transmitted path trace: fold so-7/0/0
66 6f 6c 64 20 73 6f 2d 37 2f 30 2f 30 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
Link : 1
SONET alarms
: None
SONET defects : None
SONET PHY:
Seconds
Count
PLL Lock
0
0
PHY Light
0
0
SONET section:
BIP-B1
0
0
SEF
2
1
LOS
0
0
LOF
3
2
ES-S
2
SES-S
2
SEFS-S
2
SONET line:
BIP-B2
0
0
REI-L
0
0
RDI-L
0
0
AIS-L
2
1
BERR-SF
0
0
BERR-SD
0
0
ES-L
3
SES-L
3
UAS-L
0

1304

OK
OK
OK
OK
OK

0x00, K2
0xcf, F2
0x00

: 0x00
: 0x00

0x00, K2
0x00, Z3

: 0x00
: 0x00

00
00
00
0d

00
fold so-7/0/0...
00 ................
00 ................
0a ................

00
00
00
00

00
fold so-7/0/0...
00 ................
00 ................
00 ................

State
OK
OK

OK
OK
OK

OK
OK
OK
OK

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

ES-LFE
0
SES-LFE
0
UAS-LFE
0
SONET path:
BIP-B3
0
0
REI-P
0
0
LOP-P
0
0
AIS-P
2
1
RDI-P
0
0
UNEQ-P
0
0
PLM-P
0
0
ES-P
3
SES-P
3
UAS-P
0
ES-PFE
0
SES-PFE
0
UAS-PFE
0
Payload pointer:
Current pointer
: 522
Pointer increment count
: 0
Pointer decrement count
: 0
New pointer NDF count
: 0
Received SONET overhead:
F1
: 0x00, J0
: 0x01, K1
:
S1
: 0x00, C2
: 0xcf, C2(cmp) :
Z3
: 0x00, Z4
: 0x00, S1(cmp) :
Transmitted SONET overhead:
F1
: 0x00, J0
: 0x01, K1
:
S1
: 0x00, C2
: 0xcf, F2
:
Z4
: 0x00
Received path trace: fold so-7/0/0
66 6f 6c 64 20 73 6f 2d 37 2f 30 2f 30 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
Transmitted path trace: fold so-7/0/0
66 6f 6c 64 20 73 6f 2d 37 2f 30 2f 30 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00
...

OK
OK
OK
OK
OK

0x00, K2
0xcf, F2
0x00

: 0x00
: 0x00

0x00, K2
0x00, Z3

: 0x00
: 0x00

00
00
00
0d

00
fold so-7/0/0...
00 ................
00 ................
0a ................

00
00
00
00

00
fold so-7/0/0...
00 ................
00 ................
00 ................

show interfaces detail (IPv6 Tracking)

user@host> show interfaces so-0/2/0 detail
Physical interface: so-0/2/0, Enabled, Physical link is Up
Interface index: 130, SNMP ifIndex: 26, Generation: 131
Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC3,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 7 (last seen 00:00:01 ago)
Output: 6 (last sent 00:00:08 ago)
LCP state: Opened
NCP state: inet: Not-configured, inet6: Opened, iso: Not- configured, mpls:
Not-configured

Copyright 2014, Juniper Networks, Inc.

1305

Interfaces Fundamentals for Routing Devices

CHAP state: Closed

PAP state: Closed
CoS queues
: 4 supported, 4 maximum usable queues
Last flapped
: 2007-11-29 08:45:47 PST (1d 03:44 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
7407782
40
Output bytes :
7307322
48
Input packets:
107570
0
Output packets:
108893
0
IPv6 transit statistics:
Input bytes :
57328
Output bytes :
57400
Input packets:
1024
Output packets:
1025
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
0 best-effort
1191
1191
1 expedited-fo
0
0
2 assured-forw
0
0
3 network-cont
107700
107700
SONET alarms
: None
SONET defects : None

bps
bps
pps
pps

Dropped packets
0
0
0
0

Logical interface so-0/2/0.0 (Index 70) (SNMP ifIndex 47) (Generation 231)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet6, MTU: 4470, Generation: 433, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: abcd::a18:104/126, Local: abcd::a18:105,
Broadcast: Unspecified, Generation: 683
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::2a0:a5ff:fe56:52a,
Broadcast: Unspecified, Generation: 684

show interfaces (shared interface)

user@rsd1> show interfaces so-7/2/0
Physical interface: so-7/2/0, Enabled, Physical link is Down
Interface index: 128, SNMP ifIndex: 109
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, SONET mode,
Speed: OC192, Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x4000
Shared-interface : Owner
Link flags
: No-Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 0 (never), Output: 0 (never)
DTE statistics:
Enquiries sent
: 0
Full enquiries sent
: 0
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0

1306

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Out-of-sequence packets received

: 0
Keepalive responses timedout
: 0
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2008-08-11 10:51:51 PDT (1w1d 04:47 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SONET alarms
: LOL, PLL
SONET defects : LOL, PLL, LOF, SEF, AIS-L, AIS-P
Logical interface so-7/2/0.0 (Index 67) (SNMP ifIndex 117)
Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: FR-NLPID
Shared interface:
Shared with: psd5
Tunnel token: Rx: 2.517, Tx: 1.517
Input packets : 0
Output packets: 0
DLCI 700
Flags: Active
Total down time: 00:01:09 sec, Last down: 284:58:21 ago
Input packets : 0
Output packets: 0
DLCI statistics:
Active DLCI :1 Inactive DLCI :0

Copyright 2014, Juniper Networks, Inc.

1307

Interfaces Fundamentals for Routing Devices

show interfaces (Serial)

Syntax

Release Information

show interfaces interface-type

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Description

Display status information about serial interfaces, including RS-232, RS-422/449, EIA-530,
X.21, and V.35.

Options

interface-typeOn M Series and T Series routers, the interface type is se-fpc/pic/port. On

the J Series routers, the interface type is se-pim/0/port.

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.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (Serial, EIA-530) on page 1314

show interfaces brief (Serial, EIA-530) on page 1314
show interfaces detail (Serial, EIA-530) on page 1315
show interfaces extensive (Serial, EIA-530) on page 1315
show interfaces (Serial, V.35) on page 1316
show interfaces brief (Serial, V.35) on page 1317
show interfaces detail (Serial, V.35) on page 1317
show interfaces extensive (Serial, V.35) on page 1318
show interfaces statistics detail (RS 449) on page 1319
Table 71 on page 1308 lists the output fields for the show interfaces (Serial) command.
Output fields are listed in the approximate order in which they appear.

Table 71: show interfaces (Serial) Output Fields

Field Name

Field Description

Level of Output

Name of the physical interface.

All levels

Physical Interface
Physical interface

1308

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 71: show interfaces (Serial) Output Fields (continued)

Field Name

Field Description

Level of Output

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, 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

Type

Type of interface.

All levels

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

Maximum transmission unit (MTU) size on the physical interface.

All levels

Maximum speed

Maximum speed. The nonconfigurable value is 16,384 kbps.

detail extensive none

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Keepalive settings

(PPP and HDLC) Configured settings for keepalive packets.

All levels

Interval secondsTime between successive keepalive requests. The range of

values, in seconds, is 10 to 32,767. The default value is 10.

Up-count numberNumber of keepalive packets a destination must receive

to change a link's status from down to up. The range of values is 1 to 255. The
default value is 1.

Down-count numberNumber of keepalive packets a destination must fail

to receive before the network takes a link down. The range is 1 to 255. The
default value is 3.
Keepalive

(PPP and HDLC) Information about keepalive packets.

brief none

Input: number (hh:mm:ss ago)Number of keepalive packets received by PPP

and the time since the last keepalive packet was received.

Output: number (hh:mm:ss ago)Number of keepalive packets sent by PPP

and the time since the last keepalive packet was sent.

Copyright 2014, Juniper Networks, Inc.

1309

Interfaces Fundamentals for Routing Devices

Table 71: show interfaces (Serial) Output Fields (continued)

Field Name

Field Description

Level of Output

Keepalive statistics

(PPP and HDLC) Information about keepalive packets.

detail extensive

Input: number (last seen hh:mm:ssago)Number of keepalive packets received

by PPP and the time since the last keepalive packet was received.

Output: number(last seen hh:mm:ss ago)Number of keepalive packets sent

by PPP and the time since the last keepalive packet was sent.
LCP state

NCP state

CHAP state

(PPP) Link Control Protocol state.

detail extensive none

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not-configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

(PPP) Network Control Protocol state.

detail extensive none

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not-configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

Chap-Chal-receivedChallenge was received but response not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

detail extensive none

CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)

Chap-Resp-sentResponse was sent for the challenge received.

ClosedCHAP authentication is incomplete.

FailureCHAP authentication failed.

Not-configuredCHAP is not configured on the interface.

SuccessCHAP authentication was successful.

CoS queues

Number of CoS queues configured.

detail extensive none

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).

detail extensive none

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

1310

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 71: show interfaces (Serial) Output Fields (continued)

Field Name

Field Description

Level of Output

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

GiantsNumber of frames received that are larger than the giant threshold.

Policed discardsNumber 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.

Output errors

Resource errorsSum of transmit drops.

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

MTU errorsNumber of packets whose size exceeds the MTU of the interface.

Resource errorsSum of transmit drops.

Egress queues
supported

Total number of egress queues supported on the specified interface. Displayed

with the statistics option.

detail extensive

Egress queues in
use

Total number of egress queues in use on the specified interface. Displayed with
the statistics option.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1311

Interfaces Fundamentals for Routing Devices

Table 71: show interfaces (Serial) Output Fields (continued)

Field Name

Field Description

Level of Output

Queue counters

CoS queue number and its associated user-configured forwarding class name.
Displayed with the statistics option.

detail extensive

Serial media
information

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

Information about the physical media:

Line protocoleia530, eia530a, rs232, rs449, v.35, or x.21..

Resync historyInformation about resynchronization events:

detail extensive

Sync loss countNumber of times the synchronization was lost.

Data signal(X.21 and V.35) Information about the data signal:

Rx ClockReceive clock status: OK (DTE is receiving the receive clock

signal) or Not detected (receive clock signal is not being received).

Control signalsInformation about modem control signals:

Local mode:DCE (data communication equipment) or DTE (data terminal

equipment)

To DCEControl signals that the Serial PIC sent to the DCE: DTR (Data
Terminal Ready:up or down) or RTS (Request To Send: up or down.)

From DCControl signals that the Serial PIC received from the DCE: CTS
(Clear To Send: up or down), DCD (Data Carrier Detect: up or down), DSR
(Data Set Ready: up or down), or TM (Test Mode: up or down).

Clocking modeClocking used for the transmit clock:

dteTransmit clock is generated by DTE.

dceTransmit clock is generated by the DCE and is looped back as the

transmit clock.

loop-timedReceive clock from the DCE is looped back as the transmit

clock.

Clock rateRate, in megahertz (MHz), at which the clock is configured.

LoopbackConfigured loopback mode for the interface: dce-remote, dce-local,

liu, local, or none.

Tx clockClocking phase of the transmit clock: invert (transmit clock polarity

is inverted) or non-invert (transmit clock polarity is not inverted).

Line encodingType of line encoding used: nrz (nonreturn to zero) or nrzi

(return to zero inverted).

Packet Forwarding
Engine
configuration

1312

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 71: show interfaces (Serial) Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface:

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

protocol-family

Protocol family configured on the logical interface. If the protocol is inet, the
source and destination address are also displayed.

brief

Protocol

Protocol family configured on the logical interface, such as iso, inet6, mpls.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route Table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description on page 994.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1313

Interfaces Fundamentals for Routing Devices

Table 71: show interfaces (Serial) Output Fields (continued)

Field Name

Field Description

Level of Output

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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 interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Sample Output
show interfaces (Serial, EIA-530)
user@host> show interfaces se-5/0/1
Physical interface: se-5/0/1, Enabled, Physical link is Up
Interface index: 144, SNMP ifIndex: 41
Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 16384kbps
Device flags
: Present Running
Interface flags: Point-To-Point Internal: 0x4000
Link flags
: Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 32 (00:00:10 ago), Output: 31 (00:00:07 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-04-26 15:10:18 PDT (00:05:22 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Logical interface se-5/0/1.0 (Index 71) (SNMP ifIndex 45)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 1500
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 12.0.0.0/30, Local: 12.0.0.1, Broadcast: 12.0.0.3

show interfaces brief (Serial, EIA-530)

user@host> show interfaces se-5/0/1 brief
Physical interface: se-5/0/1, Enabled, Physical link is Up
Type: Serial, Link-level type: PPP, MTU: 1504
Device flags
: Present Running
Interface flags: Point-To-Point Internal: 0x4000
Link flags
: Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 235 (00:00:10 ago), Output: 234 (00:00:00 ago)
Logical interface se-5/0/1.0

1314

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP

inet 12.0.0.1/30

show interfaces detail (Serial, EIA-530)

user@host> show interfaces se-5/0/1 detail
Physical interface: se-5/0/1, Enabled, Physical link is Up
Interface index: 144, SNMP ifIndex: 41, Generation: 25
Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 16384kbps
Device flags
: Present Running
Interface flags: Point-To-Point Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 37 (last seen 00:00:06 ago)
Output: 35 (last sent 00:00:01 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-04-26 15:10:18 PDT (00:06:02 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
928
40 bps
Output bytes :
1023
48 bps
Input packets:
76
0 pps
Output packets:
77
0 pps
Serial media information:
Line protocol: eia530
Resync history:
Sync loss count: 0
Data signal:
Rx Clock: OK
Control signals:
Local mode: DTE
To DCE: DTR: up, RTS: up
From DCE: CTS: up, DCD: up, DSR: up
Clocking mode: loop-timed
Clock rate: 8.0 MHz
Loopback: none
Tx clock: non-invert
Line encoding: nrz
Logical interface se-5/0/1.0 (Index 71) (SNMP ifIndex 45) (Generation 9)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 15, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 12.0.0.0/30, Local: 12.0.0.1, Broadcast: 12.0.0.3,
Generation: 23

show interfaces extensive (Serial, EIA-530)

user@host> show interfaces se-5/0/1 extensive
Physical interface: se-5/0/1, Enabled, Physical link is Up
Interface index: 144, SNMP ifIndex: 41, Generation: 25
Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 16384kbps
Device flags
: Present Running
Interface flags: Point-To-Point Internal: 0x4000

Copyright 2014, Juniper Networks, Inc.

1315

Interfaces Fundamentals for Routing Devices

Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 40 (last seen 00:00:00 ago)
Output: 37 (last sent 00:00:09 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-04-26 15:10:18 PDT (00:06:28 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
988
40 bps
Output bytes :
1088
48 bps
Input packets:
81
0 pps
Output packets:
82
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 2, Runts: 0, Giants: 0,
Policed discards: 0, Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
Serial media information:
Line protocol: eia530
Resync history:
Sync loss count: 0
Data signal:
Rx Clock: OK
Control signals:
Local mode: DTE
To DCE: DTR: up, RTS: up
From DCE: CTS: up, DCD: up, DSR: up
Clocking mode: loop-timed
Clock rate: 8.0 MHz
Loopback: none
Tx clock: non-invert
Line encoding: nrz
Packet Forwarding Engine configuration:
Destination slot: 5, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
Limit
%
bps
%
usec
0 best-effort
95
15564800
95
0
low
none
3 network-control
5
819200
5
0
low
none
Logical interface se-5/0/1.0 (Index 71) (SNMP ifIndex 45) (Generation 9)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 15, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 12.0.0.0/30, Local: 12.0.0.1, Broadcast: 12.0.0.3,
Generation: 23

show interfaces (Serial, V.35)

user@host> show interfaces se-5/0/0
Physical interface: se-5/0/0, Enabled, Physical link is Down
Interface index: 150, SNMP ifIndex: 39
Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 16384kbps

1316

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point Internal: 0x4000
Link flags
: Loose-NCP
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 0 (never), Output: 0 (never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-04-26 14:51:27 PDT (01:02:23 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Logical interface se-5/0/0.0 (Index 73) (SNMP ifIndex 27)
Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps
Encapsulation: PPP
Protocol inet, MTU: 1500
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 13.0.0.0/30, Local: 13.0.0.2, Broadcast: 13.0.0.3

show interfaces brief (Serial, V.35)

user@host> show interfaces se-5/0/0 brief
Physical interface: se-5/0/0, Enabled, Physical link is Down
Type: Serial, Link-level type: PPP, MTU: 1504
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point Internal: 0x4000
Link flags
: Loose-NCP
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 0 (never), Output: 0 (never)
Logical interface se-5/0/0.0
Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps
Encapsulation: PPP
inet 13.0.0.2/30

show interfaces detail (Serial, V.35)

user@host> show interfaces se-5/0/0 detail
Physical interface: se-5/0/0, Enabled, Physical link is Down
Interface index: 150, SNMP ifIndex: 39, Generation: 31
Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 16384kbps
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point Internal: 0x4000
Link flags
: Loose-NCP
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-04-26 14:51:27 PDT (01:03:15 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps

Copyright 2014, Juniper Networks, Inc.

1317

Interfaces Fundamentals for Routing Devices

Output bytes :
0
Input packets:
0
Output packets:
0
Serial media information:
Line protocol: v.35
Resync history:
Sync loss count: 0
Data signal:
Rx Clock: Not Detected
Control signals:
Local mode: DCE
To DTE: CTS: down, DCD: down, DSR: up
From DTE: DTR: down, RTS: down
DCE loopback override: Off
Clocking mode: internal
Clock rate: 38.4 KHz
Loopback: none
Tx clock: non-invert
Line encoding: nrz

0 bps
0 pps
0 pps

Logical interface se-5/0/0.0 (Index 73) (SNMP ifIndex 27) (Generation 12)
Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps
Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 17, Route table: 0
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 13.0.0.0/30, Local: 13.0.0.2, Broadcast: 13.0.0.3,
Generation: 23

show interfaces extensive (Serial, V.35)

user@host> show interfaces se-5/0/0 extensive
Physical interface: se-5/0/0, Enabled, Physical link is Down
Interface index: 150, SNMP ifIndex: 39, Generation: 31
Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 16384kbps
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point Internal: 0x4000
Link flags
: Loose-NCP
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2006-04-26 14:51:27 PDT (01:04:17 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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

1318

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Serial media information:

Line protocol: v.35
Resync history:
Sync loss count: 0
Data signal:
Rx Clock: Not Detected
Control signals:
Local mode: DCE
To DTE: CTS: down, DCD: down, DSR: up
From DTE: DTR: down, RTS: down
DCE loopback override: Off
Clocking mode: internal
Clock rate: 38.4 KHz
Loopback: none
Tx clock: non-invert
Line encoding: nrz
Packet Forwarding Engine configuration:
Destination slot: 5, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
%
bps
0 best-effort
95
15564800
3 network-control
5
819200

%
95
5

Buffer
usec
0
0

Priority

Limit

low
low

none
none

Logical interface se-5/0/0.0 (Index 73) (SNMP ifIndex 27) (Generation 12)
Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps
Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 17, Route table: 0
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 13.0.0.0/30, Local: 13.0.0.2, Broadcast: 13.0.0.3,
Generation: 23

show interfaces statistics detail (RS 449)

user@host> show interfaces se-6/0/0 statistics detail
Interface index: 149, SNMP ifIndex: 59, Generation: 150
Type: Serial, Link-level type: PPP, MTU: 1504, Maximum speed: 8mbps
Device flags
: Present Running
Interface flags: Point-To-Point Internal: 0x4000
Link flags
: No-Keepalives Loose-NCP
Hold-times
: Up 0 ms, Down 0 ms
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
PAP state: Closed
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2007-11-28 19:38:36 PST (00:14:06 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
744
0 bps
Output bytes :
5978
0 bps
Input packets:
33
0 pps
Output packets:
129
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
0,
Resource errors: 0
Output errors:
Carrier transitions: 13, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:

Copyright 2014, Juniper Networks, Inc.

1319

Interfaces Fundamentals for Routing Devices

0
Egress queues: 8 supported, 5 in use
Queue counters:
Queued packets

Transmitted packets

Dropped packets

24

24

1 expedited-fo

2 bulk

105

105

0 best-effort

3 assured-forw
4 voip

Serial media information:

Line protocol: rs449
Resync history:
Sync loss count: 0
Data signal:
Rx Clock: OK
Control signals:
Local mode: DTE
To DCE: DTR: up, RTS: up
From DCE: CTS: up, DCD: up, DSR: up
Clocking mode: internal
Loopback: none
Tx clock: non-invert
Line encoding: nrz
Logical interface se-6/0/0.0 (Index 75) (SNMP ifIndex 69) (Generation 141)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 256, Generation: 145, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 11.11.11/24, Local: 11.11.11.2, Broadcast: 11.11.11.255,
Generation: 157

1320

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces (T1, E1, or DS)

Syntax

Release Information
Description
Options

show interfaces interface-type

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Display status information about the specified T1, E1, or DS interface.
interface-typeOn ACX Series, M Series, MX Series, and T Series routers, the T1 interface

type is t1-fpc/pic/port, whereas the E1 interface type is e1-fpc/pic/port, and DS

interface type is ds-fpc/pic/port:<channel>. On the J Series routers, the T1 interface
type is t1-pim/0/port, whereas the E1 interface type is e1-pim/0/port.
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.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Understanding Interfaces on ACX Series Universal Access Routers

show interfaces (T1, IMA Link) on page 1333

show interfaces (T1, PPP) on page 1334
show interfaces detail (T1, PPP) on page 1334
show interfaces extensive (T1 CRC Errors) on page 1335
show interfaces extensive (T1, PPP) on page 1335
show interfaces (E1, Frame Relay) on page 1337
show interfaces detail (E1, Frame Relay) on page 1338
show interfaces extensive (E1, Frame Relay) on page 1339
show interfaces (E1, IMA Link) on page 1341
show interfaces extensive (T1, TDM-CCC-SATOP) on page 1342
show interfaces extensive (DS, TDM-CCC-CESoPSN) on page 1343
Table 72 on page 1322 lists the output fields for the show interfaces (T1 or E1) command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1321

Interfaces Fundamentals for Routing Devices

Table 72: T1 or E1 show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, 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

Link-level type

Encapsulation being used on the physical interface.

All levels

MTU

MTU size on the physical interface.

All levels

Clocking

Reference clock source: Internal or External.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Framing

Physical layer framing format used for the E1 interface on the link: G704,
G704-NO-CRC4, or Unframed. The default is G704.

All levels

Physical Interface

Physical layer framing format used for the T1 interface on the link: SF and ESF.
The default is ESF.
Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

1322

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

IMA Link alarms

Current active IMA link alarms, including the following:

detail extensive none

IMA Link defects

IMA Link state

LIF

LODS

RFI-IMA

Tx-Mis-Connected

Tx-Unusable-FE

Rx-Unusable-FE

Link Fault

Current active IMA link defects, including the following:

LIF

LODS

RFI-IMA

Tx-Mis-Connected

Tx-Unusable-FE

Rx-Unusable-FE

Link Fault

Current active IMA link status, including the following:

Line: synchronized or not synchronized

Near end:Status of near-end receive and transmit links

Rx: Usable or Unusable

Tx: Usable or Unusable

detail extensive none

detail extensive none

Far end:Status of far-end receive and transmit links

Rx: Usable or Unusable

Tx: Usable or Unusable

Copyright 2014, Juniper Networks, Inc.

1323

Interfaces Fundamentals for Routing Devices

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

IMA link media

IMA Link Media Status, which provides the seconds and count state for the
following link media parameters:

detail extensive none

Keepalive settings

Keepalive statistics

LIF

LODS

Err-ICP

IV

Rx-FC

Tx-FC

FE-Defects

FE-Rx-FC

FE-Tx-FC

Rx-ICP

Rx-Stuff

Tx-ICP

Tx-Stuff

Rx-SES

Rx-UAS

Rx-UUS

Tx-UUS

FE-Rx-SES

FE-Rx-UAS

FE-Rx-UUS

FE-Tx-UUS

(PPP and HDLC) Configured settings for keepalives.

detail extensive none

interval secondsThe time in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

down-count numberThe 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 numberThe number of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.

(PPP and HDLC) Information about keepalive packets. (When no level of output
is specified, the word statistics is not part of the field name and the last seen
text is not displayed.)

InputNumber of keepalive packets received by PPP.

detail extensive none

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the format hh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

1324

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

LMI settings

(Frame Relay) Settings for Local Management Interface (LMI) which can be
either ANSI LMI settings or ITU LMI settings. ANSI LMI settings is the default.
The format is (ANSI or ITU) LMI settings: value, value... xx seconds, where value
can be:

detail extensive none

LMI

DTE statistics

n391dteDTE full status polling interval (1255)

n392dceDCE error threshold (110)

n392dteDTE error threshold (110)

n393dceDCE monitored event count (110)

n393dteDTE monitored event count (110)

t391dteDTE polling timer (530 seconds)

t392dceDCE polling verification timer (530 seconds)

(Frame Relay) Local Management Interface (LMI) packet statistics:

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
sent hh:mm:ss ago).

(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data communications equipment (DCE):

Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.

Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.

Enquiry responses receivedNumber of enquiry responses received by the

detail extensive none

detail extensive none

DTE from the DCE.

Full enquiry responses receivedNumber of full enquiry responses sent from

the DTE to the DCE.

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

Enquiries receivedNumber of enquiries received by the DCE from the DTE.

Full enquiries receivedNumber of full enquiries received by the DCE from

detail extensive none

the DTE.

Enquiry responses sentNumber of enquiry responses sent from the DCE to

the DTE.

Full enquiry responses sentNumber of full enquiry responses sent from the

DCE to the DTE.

Copyright 2014, Juniper Networks, Inc.

1325

Interfaces Fundamentals for Routing Devices

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

detail extensive none

Unknown messages receivedNumber of received packets that do not fall

into any category.

Asynchronous updates receivedNumber of link status peer changes received.

Out-of-sequence packets receivedNumber of packets for which the sequence

of the packets received is different from the expected sequence.

Keepalive responses timedoutNumber of keepalive responses that timed

out when no Local Management Interface (LMI) packet was reported for
n392dte or n393dce intervals. (See LMI settings.)
Nonmatching
DCE-end DLCIs

(Frame Relay. Displayed only from the DTE.) Number of DLCIs configured from
the DCE.

detail extensive none

LCP state

(PPP) Link Control Protocol state.

detail extensive none

NCP state

CHAP state

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

Not configuredLCP is not configured on the interface.

OpenedLCP negotiation is successful.

(PPP) Network Control Protocol state.

detail extensive none

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

Not configuredNCP is not configured on the interface.

OpenedNCP negotiation is successful.

(PPP) State of the Challenge Handshake Authentication Protocol (CHAP)

during its transaction.

Chap-Chal-receivedChallenge was received but response is not yet sent.

Chap-Chal-sentChallenge was sent.

Chap-Resp-receivedResponse was received for the challenge sent, but

detail extensive none

CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)

Last flapped

1326

Chap-Resp-sentResponse was sent for the challenge received.

DownCHAP authentication is incomplete (not yet completed or has failed).

Not-configuredCHAP is not configured on the interface.

OpenedCHAP authentication was successful.

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).

detail extensive none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CoS Queues

Number of CoS queues configured.

detail extensive none

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface

Output packetsNumber of packets transmitted on the interface.

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

HS link CRC errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

SRAM errorsNumber of hardware errors that occurred in the static RAM

(SRAM) on the PIC or PIM. If the value of this field increments, the PIC or PIM
is malfunctioning.

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

1327

Interfaces Fundamentals for Routing Devices

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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
or PIM is malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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.

Queue counters

DS1 alarms
DS1 defects

1328

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

CoS queue number and its associated user-configured forwarding class name.

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

E1 media-specific defects that can prevent the interface from passing 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.
The following lists all possible alarms and defects. For complete explanations
of most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.

AISAlarm indication signal.

LOFLoss of frame.

LOSLoss of signal.

YLWYellow alarm. Indicates errors at the remote site receiver.

detail extensive

detail extensive none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

T1 media or E1
media

Counts of T1 or E1 media-specific errors.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

The T1 or E1 media-specific error types are:

SAToP
Configuration

SEFSeverely errored framing

BEEBit error

AISAlarm indication signal

LOFLoss of frame

LOSLoss of signal

YELLOWErrors at the remote site receiver

CRC MajorCyclic redundancy check major alarm threshold exceeded

CRC MinorCyclic redundancy check minor alarm threshold exceeded

BPVBipolar violation

EXZExcessive zeros

LCVLine code violation

PCVPulse code violation

CSCarrier state

CRCCyclic redundancy check

FEBEFar-end block error (E1 only)

LESLine error seconds

ESErrored seconds

BESBursty errored seconds

SESSeverely errored seconds

SEFSSeverely errored framing seconds

UASUnavailable seconds

Information about the SAToP configuration.

extensive

payload-sizeConfigure the payload size, in bytes (from 32 through 1024

bytes).

idle-patternAn 8-bit hexadecimal pattern to replace TDM data in a lost

packet (from 0 through 255).

jitter-buffer-packetsNumber of packets in the jitter buffer (from 1 through

64 packets).

jitter-buffer-latencyTime delay in the jitter buffer (from 1 through 1000

milliseconds).

excessive-packet-loss-rateSet packet loss options. The options are groups,

sample-period, and threshold.

sample-periodTime required to calculate excessive packet loss rate (from

1000 through 65,535 milliseconds).

thresholdPercentile designating the threshold of excessive packet loss rate

(1100 percent).

Copyright 2014, Juniper Networks, Inc.

1329

Interfaces Fundamentals for Routing Devices

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CESoPSN
Configuration

Information about the CESoPSN configuration.

extensive

packetization-latencyTime required to create packets (from 1000 through

8000 microseconds).

idle-patternAn 8-bit hexadecimal pattern to replace TDM data in a lost

packet (from 0 through 255).

jitter-buffer-packetsNumber of packets in the jitter buffer (from 1 through

64 packets).

jitter-buffer-latencyTime delay in the jitter buffer (from 1 through 1000

milliseconds).

excessive-packet-loss-rateSet packet loss options. The options are

sample-period and threshold.

sample-periodTime required to calculate excessive packet loss rate (from

1000 through 65,535 milliseconds).

thresholdPercentile designating the threshold of excessive packet loss rate

(1100 percent).
HDLC configuration

Information about the HDLC configuration.

extensive

Policing bucketConfigured state of the receiving policer.

Shaping bucketConfigured state of the transmitting shaper.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

TimeslotsTime slots configured on the interface.

Buildout(T1 only) Buildout setting: 0-132, 133-265, 266-398, 399-531, or

532-655 feet.

DS1 BERT
configuration

TimeslotsConfigured time slots for the interface.

Byte encoding(T1 only) Byte encoding used: Nx64K or Nx56K.

Line encodingLine encoding used. For T1, the value can be B8ZS or AMI. For
E1, the value is HDB3.

Data inversionHDLC data inversion setting: Enabled or Disabled.

Idle cycle flagIdle cycle flags.

Start end flagStart and end flag.

BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.

BERT time periodConfigured total time period that the BERT is to run.

ElapsedActual time elapsed since the start of the BERT (in seconds).

Induced error rateConfigured rate at which the bit errors are induced in the

detail extensive none

BERT pattern.

Packet Forwarding
Engine
configuration

1330

AlgorithmType of algorithm selected for the BERT.

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CoS information

Information about the CoS queue for the physical interface.

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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
Logical interface

Name of the logical interface.

All levels

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Input packets

Number of packets received on the logical interface.

None specified

Output packets

Number of packets transmitted on the logical interface.

None specified

Traffic statistics

(Frame Relay) Number and rate of bytes and packets received and transmitted
on the logical interface.

detail extensive

Local statistics

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

(Frame Relay) Statistics for traffic received from and transmitted to the Routing
Engine. When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. It takes a while (generally, less than
1 second) for this counter to stabilize.

Copyright 2014, Juniper Networks, Inc.

detail extensive

1331

Interfaces Fundamentals for Routing Devices

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Transit statistics

(Frame Relay) Statistics for traffic transiting the router. When a burst of traffic
is received, the value in the output packet rate field might briefly exceed the
peak cell rate. This counter normally stabilizes in less than 1 second.

detail extensive

Protocol

Protocol family configured on the logical interface, such as iso, inet6, mlfr, or
mpls.

detail extensive none

Multilink bundle

Interface name for the multilink bundle, if configured.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive none

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI
information is displayed: Flags, Total down time, Last down, and Traffic statistics
or (Input packets, Output packets). Flags can be one or more of the following:

detail extensive none

ActiveSet when the link is active and the DTE and DCE are exchanging

information.

DownSet when the link is active, but no information is received from the

DCE.

DCE-UnconfiguredSet when the corresponding DLCI in the DCE is not

configured.

DLCI statistics

1332

ConfiguredSet when the corresponding DLCI in the DCE is configured.

DCE-configuredDisplayed when the command is issued from the DTE.

(Frame Relay) Data-link connection identifier (DLCI) statistics.

Active DLCINumber of active DLCIs.

Inactive DLCINumber of inactive DLCIs.

detail extensive none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 72: T1 or E1 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

CE Info

Information related to the circuit emulation statistics.

extensive

CE TxNumber of transmitted packets and bytes (TDM to PSN flow).

CE RxNumber of received packets and bytes and forward bytes (PSN to

TDM flow).

CE Rx ForwardedNumber of forwarded bytes.

CE StrayedNumber of stray packets.

CE LostNumber of lost packets.

CE MalformedNumber of malformed packets

CE MisinsertedNumber of misinserted packets.

CE AIS droppedNumber of dropped bytes due to buffer overrun (PSN to

TDM).

CE DroppedNumber of dropped packets during resynchronization

CE Overrun EventsNumber of overrun events.

CE Underrun EventsNumber of underrun events.

Sample Output
show interfaces (T1, IMA Link)
user@host> show interfaces t1-1/0/0
IMA Link alarms
: None
IMA Link defects : LIF, LODS
IMA Link state:
Line
: Not synchronized
Near end : Rx: Unusable, Tx: Usable
Far end : Rx: Unusable, Tx: Usable
IMA link media:
Seconds
LIF
LODS
Err-ICP
IV
Rx-FC
Tx-FC
FE-Defects
FE-Rx-FC
FE-Tx-FC
Rx-ICP
Rx-Stuff
Tx-ICP
Tx-Stuff
Rx-SES
0
Rx-UAS
0
Rx-UUS
1
Tx-UUS
0
FE-Rx-SES
0
FE-Rx-UAS
0
FE-Rx-UUS
0
FE-Tx-UUS
0

Copyright 2014, Juniper Networks, Inc.

Count
0
0
0
0
0
0
0
0
0
0
0
11
0

State
OK
OK
OK
OK
OK
OK

1333

Interfaces Fundamentals for Routing Devices

show interfaces (T1, PPP)

user@host> show interfaces t1-1/1/0
Physical interface: t1-1/1/0, Enabled, Physical link is Up
Interface index: 149, SNMP ifIndex: 45
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 0 (never), Output: 0 (never)
LCP state: Opened
NCP state: Opened
CHAP state: Opened
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:43:06 PST (02:13:35 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 72 bps (0 pps)
DS1
alarms
: None
DS1
defects : None
Logical interface t1-1/1/0.0 (Index 66) (SNMP ifIndex 51)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 1500
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255

show interfaces detail (T1, PPP)

user@host> show interfaces t1-1/1/0 detail
Physical interface: t1-1/1/0, Enabled, Physical link is Up
Interface index: 149, SNMP ifIndex: 45, Generation: 32
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Opened
NCP state: Opened
CHAP state: Opened
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:43:06 PST (02:13:52 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
798
0 bps
Input packets:
0
0 pps
Output packets:
42
0 pps
Queue counters:
Queued packets Transmitted packets
Dropped packets

1334

0 best-effort

1 expedited-fo

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

2 assured-forw

3 network-cont

40

40

DS1
alarms
: None
DS1
defects : None
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1
Logical interface t1-1/1/0.0 (Index 66) (SNMP ifIndex 51) (Generation 5)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 14, Route table: 0
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 18

show interfaces extensive (T1 CRC Errors)

user@host> show interfaces t1-3/2/0:1:1 extensive
Physical interface: t1-3/2/0:1:1, Enabled, Physical link is Down
Interface index: 179, SNMP ifIndex: 79, Generation: 180
:
:
DS1
alarms
: AIS, LOF, CRC Major, CRC Minor
DS1
defects : AIS, LOF, CRC Major, CRC Minor
T1 media:
Seconds
Count State
SEF
1
1 OK
BEE
1
1 OK
AIS
1128
1 Defect Active
LOF
1128
1 Defect Active
LOS
0
0 OK
YELLOW
0
0 OK
CRC Major
154
1 Defect Active
CRC Minor
154
1 Defect Active
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
0
0
CS
0
0
CRC
154
15400
...

show interfaces extensive (T1, PPP)

user@host> show interfaces t1-1/1/0 extensive
Physical interface: t1-1/1/0, Enabled, Physical link is Up
Interface index: 149, SNMP ifIndex: 45, Generation: 32
Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured

Copyright 2014, Juniper Networks, Inc.

1335

Interfaces Fundamentals for Routing Devices

CHAP state: Closed

CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:43:06 PST (02:13:54 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
817
72 bps
Input packets:
0
0 pps
Output packets:
43
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Queue counters:

Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

42

42

DS1
alarms
: None
DS1
defects : None
T1 media:
Seconds
Count State
SEF
1
1 OK
BEE
0
0 OK
AIS
0
0 OK
LOF
1
1 OK
LOS
0
0 OK
YELLOW
1
1 OK
BPV
1
1
EXZ
1
1
LCV
1
65535
PCV
1
1023
CS
0
0
LES
1
ES
1
SES
1
SEFS
1
BES
0
UAS
0
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 1514, Runt threshold: 3
Timeslots
: All active
Line encoding: B8ZS
Buildout
: 0 to 132 feet
Byte encoding: Nx64K, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1
Packet Forwarding Engine configuration:
Destination slot: 1, PLP byte: 1 (0x00)

1336

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

CoS information:
CoS transmit queue
0 best-effort
3 network-control

%
95
5

Bandwidth
bps
1459200
76800

%
95
5

Buffer
usec
0
0

Priority
low
low

Limit
none
none

Logical interface t1-1/1/0.0 (Index 66) (SNMP ifIndex 51) (Generation 5)

Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 14, Route table: 0
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 18

show interfaces (E1, Frame Relay)

user@host> show interfaces e1-3/0/0
Physical interface: e1-3/0/0, Enabled, Physical link is Up
Interface index: 146, SNMP ifIndex: 37
Link-level type: Frame-Relay, MTU: 1504, Clocking: Internal, Speed: E1,
Loopback: None, FCS: 16, Framing: G704
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps 16384
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 0 (never), Output: 11 (00:00:05 ago)
DTE statistics:
Enquiries sent
: 10
Full enquiries sent
: 1
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 8 supported
Last flapped
: 2005-11-30 14:50:34 PST (4d 20:33 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
DS1
alarms
: None
DS1
defects : None
Logical interface e1-3/0/0.0 (Index 72) (SNMP ifIndex 32)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Input packets : 0
Output packets: 0
Protocol inet, MTU: 1500
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.1.3/24, Local: 10.1.3.1, Broadcast: 10.1.3.255
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:01:13 sec, Last down: 00:01:13 ago
Input packets : 0
Output packets: 0

Copyright 2014, Juniper Networks, Inc.

1337

Interfaces Fundamentals for Routing Devices

DLCI statistics:
Active DLCI :0

Inactive DLCI

:1

show interfaces detail (E1, Frame Relay)

user@host> show interfaces e1-3/0/0 detail
Physical interface: e1-3/0/0, Enabled, Physical link is Up
Interface index: 146, SNMP ifIndex: 37, Generation: 69
Link-level type: Frame-Relay, MTU: 1504, Clocking: Internal, Speed: E1,
Loopback: None, FCS: 16, Framing: G704
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps 16384
Link flags
: Keepalives DTE
Hold-times
: Up 0 ms, Down 0 ms
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI statistics:
Input : 0 (last seen: never)
Output: 12 (last sent 00:00:02 ago)
DTE statistics:
Enquiries sent
: 10
Full enquiries sent
: 2
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 8 supported
Last flapped
: 2005-11-30 14:50:34 PST (4d 20:33 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
225
56 bps
Input packets:
0
0 pps
Output packets:
15
0 pps
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 limited

1 expedited-fo

2 real-plus

15

15

3 network-cont

DS1
alarms
: None
DS1
defects : None
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Logical interface e1-3/0/0.0 (Index 72) (SNMP ifIndex 32) (Generation 26)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Traffic statistics:
Input bytes :
0
Output bytes :
0

1338

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
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: 32, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.1.3/24, Local: 10.1.3.1, Broadcast: 10.1.3.255,
Generation: 42
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:01:18 sec, Last down: 00:01:18 ago
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

show interfaces extensive (E1, Frame Relay)

user@host> show interfaces e1-3/0/0 extensive
Physical interface: e1-3/0/0, Enabled, Physical link is Up
Interface index: 146, SNMP ifIndex: 37, Generation: 69
Link-level type: Frame-Relay, MTU: 1504, Clocking: Internal, Speed: E1,
Loopback: None, FCS: 16, Framing: G704
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps 16384
Link flags
: Keepalives DTE
Hold-times
: Up 0 ms, Down 0 ms
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI statistics:
Input : 0 (last seen: never)
Output: 12 (last sent 00:00:05 ago)
DTE statistics:
Enquiries sent
: 10
Full enquiries sent
: 2
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 8 supported
Last flapped
: 2005-11-30 14:50:34 PST (4d 20:33 ago)
Statistics last cleared: Never

Copyright 2014, Juniper Networks, Inc.

1339

Interfaces Fundamentals for Routing Devices

Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
225
0 bps
Input packets:
0
0 pps
Output packets:
15
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 17, Errors: 0, Drops: 0, Aged packets: 0,
MTU errors: 0, Resource errors: 0
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 limited

1 expedited-fo

2 real-plus

15

15

3 network-cont

DS1
alarms
: None
DS1
defects : None
E1 media:
Seconds
Count State
SEF
0
0 OK
BEE
5
5 OK
AIS
0
0 OK
LOF
245
15 OK
LOS
245
4 OK
YELLOW
0
11 OK
BPV
0
0
EXZ
9
9
LCV
0
0
PCV
0
0
CS
0
0
FEBE
0
0
LES
0
ES
0
SES
0
SEFS
0
BES
0
UAS
271
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 1506, Runt threshold: 0
Timeslots
: All active
Line encoding: HDB3, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 3, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
Limit
%
bps
%
usec
0 limited
95
1945600
95
0
low
none
3 network-control
5
102400
5
0
low
none
Logical interface e1-3/0/0.0 (Index 72) (SNMP ifIndex 32) (Generation 26)

1340

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID

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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 1500, Generation: 32, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.1.3/24, Local: 10.1.3.1, Broadcast: 10.1.3.255,
Generation: 42
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:01:21 sec, Last down: 00:01:21 ago
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

show interfaces (E1, IMA Link)

user@host> show interfaces e1-1/0/0
IMA Link alarms
: None
IMA Link defects : LIF, LODS
IMA Link state:
Line
: Not synchronized
Near end : Rx: Unusable, Tx: Usable
Far end : Rx: Unusable, Tx: Usable
IMA link media:
Seconds
LIF
LODS
Err-ICP
IV
Rx-FC
Tx-FC
FE-Defects
FE-Rx-FC
FE-Tx-FC
Rx-ICP
Rx-Stuff
Tx-ICP
Tx-Stuff
Rx-SES
0
Rx-UAS
0
Rx-UUS
1
Tx-UUS
0
FE-Rx-SES
0
FE-Rx-UAS
0

Copyright 2014, Juniper Networks, Inc.

Count
0
0
0
0
0
0
0
0
0
0
0
11
0

State

1341

Interfaces Fundamentals for Routing Devices

FE-Rx-UUS
FE-Tx-UUS

0
0

show interfaces extensive (T1, TDM-CCC-SATOP)

user@host>show interfaces t1-1/0/0:1:1 extensive
Physical interface: t1-1/0/0:1:1, Enabled, Physical link is Down
Interface index: 153, SNMP ifIndex: 579, Generation: 817
Link-level type: TDM-CCC-SATOP, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF,
Parent: coc1-1/0/0:1 Interface index 152
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x0
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2012-10-28 02:12:40 PDT (22:32:13 ago)
Statistics last cleared: 2012-10-29 00:44:52 PDT (00:00:01 ago)
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
DS1
alarms
: None
DS1
defects : None
T1 media:
Seconds
Count State
SEF
0
0 OK
BEE
0
0 OK
AIS
0
0 OK
LOF
0
0 OK
LOS
0
0 OK
YELLOW
0
0 OK
CRC Major
0
0 OK
CRC Minor
0
0 OK
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
0
0
CS
0
0
CRC
0
0
LES
0
ES
0
SES
0
SEFS
0
BES
0
UAS
0
SAToP configuration:
Payload size: 192
Idle pattern: 0xFF
Octet aligned: Disabled

1342

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Jitter buffer: packets: 8, latency: 7 ms, auto adjust: Disabled

Excessive packet loss rate: sample period: 10000 ms, threshold: 30%
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
SONET alarms
: None
SONET defects : AIS-V, RDI-V
SONET vt:
BIP-BIP2
0
0
REI-V
0
0
LOP-V
0
0 OK
AIS-V
2
0 Defect Active
RDI-V
2
0 Defect Active
UNEQ-V
0
0 OK
PLM-V
0
0 OK
ES-V
0
SES-V
0
UAS-V
2
ES-VFE
0
SES-VFE
0
UAS-VFE
0
Received SONET overhead:
V5
: 0x07
V5(cmp) : 0x02
Transmitted SONET overhead:
V5
: 0x02
Packet Forwarding Engine configuration:
Destination slot: 1
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95
1459200
95
0
low
none
3 network-control
5
76800
5
0
low
none
Logical interface t1-1/0/0:1:1.0 (Index 69) (SNMP ifIndex 580) (Generation 525)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: TDM-CCC-SATOP
CE info
Packets
Bytes Count
CE Tx
1005
192960
CE Rx
1004
192768
CE Rx Forwarded
0
CE Strayed
0
CE Lost
0
CE Malformed
0
CE Misinserted
0
CE AIS dropped
0
CE Dropped
1005
192960
CE Overrun Events
0
CE Underrun Events
0
Protocol ccc, MTU: 1504, Generation: 814, Route table: 0
Flags: Is-Primary

show interfaces extensive (DS, TDM-CCC-CESoPSN)

user@host>show interfaces ds-1/0/0:1:1:1 extensive
Physical interface: ds-1/0/0:1:1:1, Enabled, Physical link is Down
Interface index: 154, SNMP ifIndex: 597, Generation: 819

Copyright 2014, Juniper Networks, Inc.

1343

Interfaces Fundamentals for Routing Devices

Link-level type: TDM-CCC-CESoPSN, MTU: 1504, Speed: 1536kbps, Loopback: None,

FCS: 16, Parent: ct1-1/0/0:1:1 Interface index 153
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x0
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 8 supported, 8 maximum usable queues
Last flapped
: 2012-10-29 00:49:03 PDT (00:00:35 ago)
Statistics last cleared: Never
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
CESoPSN configuration:
Packetization latency: 1000 us
Idle pattern: 0xFF
Jitter buffer: packets: 8, latency: 8 ms, auto adjust: Disabled
Excessive packet loss rate: sample period: 10000 ms, threshold: 30%
DS0 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Packet Forwarding Engine configuration:
Destination slot: 1
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95
1459200
95
0
low
none
3 network-control
5
76800
5
0
low
none
Logical interface ds-1/0/0:1:1:1.0 (Index 69) (SNMP ifIndex 598) (Generation
549)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: TDM-CCC-CESoPSN
CE info
Packets
Bytes Count
CE Tx
0
0
CE Rx
35712
6856704
CE Rx Forwarded
0
CE Strayed
0
CE Lost
0
CE Malformed
0
CE Misinserted
0
CE AIS dropped
0
CE Dropped
0
0
CE Overrun Events
0
CE Underrun Events
1

1344

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Protocol ccc, MTU: 1504, Generation: 857, Route table: 0

Flags: Is-Primary

Copyright 2014, Juniper Networks, Inc.

1345

Interfaces Fundamentals for Routing Devices

show interfaces (T3 or E3)

Syntax

Release Information
Description
Options

show interfaces interface-type

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Display status information about the specified T3 or E3 interface.
interface-typeOn M Series and T Series routers, the T3 interface type is t3-fpc/pic/port,

whereas the E3 interface type is e3-fpc/pic/port On the J Series routers, the T3

interface type is t3-pim/0/port, whereas the E3 interface type is e3-pim/0/port.
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.

Required Privilege
Level
List of Sample Output

Output Fields

view

show interfaces (T3, PPP) on page 1355

show interfaces detail (T3, PPP) on page 1356
show interfaces extensive (T3, PPP) on page 1357
show interfaces (E3, Frame Relay) on page 1358
show interfaces detail (E3, Frame Relay) on page 1359
show interfaces extensive (E3, Frame Relay) on page 1360
Table 73 on page 1346 lists the output fields for the show interfaces (T3 or E3) command.
Output fields are listed in the approximate order in which they appear.

Table 73: T3 or E3 show interfaces Output Fields

Field Name

Field Description

Level of Output

Physical interface

Name of the physical interface.

All levels

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

All levels

Interface index

Physical interface's index number, which reflects its initialization sequence.

detail extensive none

Physical Interface

1346

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

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

MTU size on the physical interface.

All levels

Clocking

Reference clock source. It can be Internal or External.

All levels

Speed

Speed at which the interface is running.

All levels

Loopback

Whether loopback is enabled and the type of loopback (local or remote).

All levels

FCS

Frame check sequence on the interface (either 16 or 32). The default is 16 bits.

All levels

Mode

(T3 only) Whether C-bit parity mode or M13 mode is enabled.

All levels

Long buildout

(T3 only) Buildout setting: less than 255 feet (68 meters) or greater than 255
feet and shorter than 450 feet (137 meters).

All levels

Framing

(E3 only) Physical layer framing format used on the link. It can be G751 or
Unframed. The default is G751.

All levels

Device flags

Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description on page 994.

All levels

Interface flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

All levels

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

All levels

Hold-times

Current interface hold-time up and hold-time down, in milliseconds.

detail extensive

Keepalive settings

(PPP and HDLC) Configured settings for keepalives.

detail extensive none

interval secondsTime in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.

down-count numberNumber 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 numberNumber 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.

Copyright 2014, Juniper Networks, Inc.

1347

Interfaces Fundamentals for Routing Devices

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Keepalive statistics
or Keepalive

(PPP and HDLC) Information about keepalive packets.

detail extensive none

InputNumber of keepalive packets received by PPP.

(last seen 00:00:00 ago)Time since the last keepalive packet was
received, in the format hh:mm:ss.

OutputNumber of keepalive packets sent by PPP and how long ago the last

keepalive packets were sent and received.

LMI settings

LMI

DTE statistics

(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

(Frame Relay) Local Management Interface (LMI) settings (ANSI or ITU). ANSI
LMI settings is the default. The format is LMI settings: value, value... xx seconds,
where value can be:

n391dteDTE full status polling interval (1255)

n392dceDCE error threshold (110)

n392dteDTE error threshold (110)

n393dceDCE monitored event count (110)

n393dteDTE monitored event count (110)

t391dteDTE polling timer (530 seconds)

t392dceDCE polling verification timer (530 seconds)

(Frame Relay) LMI statistics:

detail extensive none

detail extensive none

InputNumber of packets coming in on the interface (nn) and how much

time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).

OutputNumber of packets sent out on the interface (nn) and how much
time has passed since the last packet was sent. The format is Output: nn (last
sent hh:mm:ss ago).

(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data communications equipment (DCE):

Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.

Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.

Enquiry responses receivedNumber of enquiry responses received by the

detail extensive none

DTE from the DCE.

Full enquiry responses receivedNumber of full enquiry responses sent from

the DTE to the DCE.

DCE statistics

(Frame Relay) Statistics about messages transmitted from the DCE to the DTE:

Enquiries receivedNumber of enquiries received by the DCE from the DTE.

Full enquiries receivedNumber of full enquiries received by the DCE from

detail extensive none

the DTE.

Enquiry responses sentNumber of enquiry responses sent from the DCE to

the DTE.

Full enquiry responses sentNumber of full enquiry responses sent from the

DCE to the DTE.

1348

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Common statistics

(Frame Relay) Statistics about messages sent between the DTE and the DCE:

detail extensive none

Unknown messages receivedNumber of received packets that do not fall

into any category.

Asynchronous updates receivedNumber of link status peer changes received.

Out-of-sequence packets receivedNumber of packets for which the sequence

of the packets received is different from the expected sequence.

Keepalive responses timedoutNumber of keepalive responses that timed

out when no LMI packet was reported for n392dte or n393dce intervals. (See
LMI settings.)

Nonmatching
DCE-end DLCIs

(Frame Relay. Displayed only from the DTE.) Number of DLCIs configured from
the DCE.

detail extensive none

LCP state

(PPP) Link Control Protocol state.

detail extensive none

NCP state

CHAP state

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownLCP negotiation is incomplete (not yet completed or has failed).

OpenedLCP negotiation is successful.

(PPP) Network Control Protocol state.

Conf-ack-receivedAcknowledgement was received.

Conf-ack-sentAcknowledgement was sent.

Conf-req-sentRequest was sent.

DownNCP negotiation is incomplete (not yet completed or has failed).

OpenedNCP negotiation is successful.

(PPP) Displays the state of the Challenge Handshake Authentication Protocol

(CHAP) during its transaction.

detail extensive none

detail extensive none

Chap-Resp-receivedResponse received for the challenge sent, but CHAP

not yet moved into the Success state. (Most likely with RADIUS
authentication.)

Chap-Resp-sentResponse sent for the challenge received.

Chap-Chal-sentChallenge sent.

Chap-Chal-receivedChallenge received but response not yet sent.

DownCHAP authentication is incomplete (not yet completed or has failed).

Not-configuredCHAP is not configured on the interface.

OpenedCHAP authentication was successful.

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 (year-month-day
hour:minute:second ago) . For example, Last flapped: 2002-04-26 10:52:40 PDT
(04:33:20 ago).

detail extensive none

CoS queues

Number of CoS queues configured.

detail extensive none

Copyright 2014, Juniper Networks, Inc.

1349

Interfaces Fundamentals for Routing Devices

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

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

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input errors

Input bytesNumber of bytes received on the interface

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface

Output packetsNumber of packets received on the interface.

Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

Runts(T3 only) Number of frames received that are smaller than the runt

threshold.

Giants(T3 only) Number of frames received that are larger than the giant

threshold.

Bucket DropsDrops resulting from the traffic load exceeding the interface
transmit/receive leaky bucket configuration. The default is off.

Policed discardsNumber 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 incompletesNumber 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.

L2 channel errorsNumber of times the software did not find a valid logical

interface for an incoming frame.

L2 mismatch timeoutsNumber of malformed or short packets that caused

the incoming packet handler to discard the frame as unreadable.

HS link CRC errorsNumber of errors on the high-speed links between the

ASICs responsible for handling the router interfaces.

SRAM errorsNumber of hardware errors that occurred in the static RAM

(SRAM) on the PIC or PIM. If the value of this field increments, the PIC or PIM
is malfunctioning.

1350

Resource errorsSum of transmit drops.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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 (perhaps once
every 10 seconds), the cable, the far-end system, or the PIC or PIM is
malfunctioning.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Aged packetsNumber 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.

Queue counters

Active alarms
Active defects

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

CoS queue number and its associated user-configured forwarding class name.

Queued packetsNumber of queued packets.

Transmitted packetsNumber of transmitted packets.

Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.

E3 media-specific defects that can render the interface unable to pass 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.

AISAlarm indication signal

EXZExcessive zeros

FERFFar-end receive failures

IDLEIdle code detected

LCDLoss of cell delineation

LCVLine code violation

LOFLoss of frame

LOSLoss of signal

PLLPhase-locked loop

YLWRemote defect indication

Copyright 2014, Juniper Networks, Inc.

detail extensive

detail extensive none

1351

Interfaces Fundamentals for Routing Devices

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

DS3 media or E3
media

Counts of DS3 (T3) or E3 media-specific errors.

extensive

SecondsNumber of seconds the defect has been active.

CountNumber of times that the defect has gone from inactive to active.

StateState of the error. State other than OK indicates a problem.

The DS3 or E3 media-specific error types can be:

HDLC configuration

1352

PLL LockPhase-locked loop out of lock

ReframingFrame alignment recovery time

AISAlarm indication signal

LOFLoss of frame

LOSLoss of signal

IDLEIdle code detected

YELLOWErrors at the remote site receiver

BPVBipolar violation

EXZExcessive zeros

LCVLine code violation

PCV(DS3 only) Pulse code violation

CCV(DS3 only) C-bit coding violation

FEBE(DS3 only) Far-end block error

LESLine error seconds

PES(DS3 only) P-bit errored seconds

PSES(DS3 only) P-bit errored seconds (section)

CES(DS3 only) C-bit errored seconds

CSES(DS3 only) C-bit severely errored seconds

SEFSSeverely errored framing seconds

UASUnavailable seconds

Information about the HDLC configuration.

Policing bucketConfigured state of the receiving policer.

Shaping bucketConfigured state of the transmitting shaper.

Giant thresholdGiant threshold programmed into the hardware.

Runt thresholdRunt threshold programmed into the hardware.

Idle cycle flagIdle cycle flags.

Start end flagStart and end flag.

extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

DSU configuration

Information about the DSU configuration. The last three lines (Bit count, Error
bit count, and LOS information) are displayed only if a BERT has ever been run
on the interface.

extensive

Compatibility modCSU/DSU compatibility mode: None, Larscom, Kentrox,

or Digital-Link.

ScramblingPayload scrambling: Enabled or Disabled.

SubrateConfigured subrate setting. Applies only when Digital-Link

compatibility mode is used. The subrate can be Disabled or display units in

Kbps.

FEAC loopbac(T3) Whether a far-end alarm and control (FEAC) loopback

is Active or Inactive. This feature is used to send alarm or status information

from the far-end terminal back to the near-end terminal and to initiate T3
loopbacks at the far-end terminal from the near-end terminal.

DS3 (or E3) BERT

configuration

ResponseWhether the FEAC signal is Enabled or Disabled.

CountNumber of FEAC loopbacks.

BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.

BERT time periodConfigured total time period that the BERT is to run.

ElapsedActual time elapsed since the start of the BERT (in seconds).

Induced error rateConfigured rate at which the bit errors are induced in the

detail extensive none

BERT pattern.

Packet Forwarding
Engine
configuration

CoS information

AlgorithmType of algorithm selected for the BERT.

Information about the configuration of the Packet Forwarding Engine:

Destination slotFPC slot number.

PLP bytePacket Level Protocol byte.

Information about the CoS queue for the physical interface.

extensive

extensive

CoS transmit queueQueue number and its associated user-configured

forwarding class name.

Bandwidth %Percentage of bandwidth allocated to the queue.

Bandwidth bpsBandwidth allocated to the queue (in bps).

Buffer %Percentage of buffer space allocated to the queue.

Buffer usecAmount of buffer space allocated to the queue, in microseconds.

This value is nonzero only if the buffer size is configured in terms of time.

PriorityQueue priority: low or high.

LimitDisplayed 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

Copyright 2014, Juniper Networks, Inc.

1353

Interfaces Fundamentals for Routing Devices

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Logical interface

Name of the logical interface.

detail extensive none

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

Logical interface SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

extensive

Flags

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

detail extensive none

Encapsulation

Encapsulation on the logical interface.

detail extensive none

Input packets

Number of packets received on the logical interface.

None specified

Output packets

Number of packets transmitted on the logical interface.

None specified

Traffic statistics

(Frame Relay) Number and rate of bytes and packets received and transmitted
on the logical interface.

detail extensive

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Local statistics

(Frame Relay) Statistics for traffic received from and transmitted to the Routing
Engine. When a burst of traffic is received, the value in the output packet rate
field might briefly exceed the peak cell rate. It takes awhile (generally, less than
1 second) for this counter to stabilize.

detail extensive

Transit statistics

(Frame Relay) Statistics for traffic transiting the router. When a burst of traffic
is received, the value in the output packet rate field might briefly exceed the
peak cell rate. This counter normally stabilizes in less than 1 second.

detail extensive

Protocol

Protocol family configured on the logical interface, such as iso, inet6, mlfr, or
mpls.

detail extensive none

Multilink bundle

(Multilink) Interface name for the multilink bundle.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

1354

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 73: T3 or E3 show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail 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.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive none

DLCI

(Frame Relay) DLCI number of the logical interface. The following DLCI
information is displayed: Flags, Total down time, Last down, and Traffic statistics
(or Input packets, Output packets). Flags is one or more of the following:

detail extensive none

ActiveSet when the link is active and the DTE and DCE are exchanging

information.

DownSet when the link is active, but no information is received from the

DCE.

DCE UnconfiguredSet when the corresponding DLCI in the DCE is not

configured.

DLCI statistics

ConfiguredSet when the corresponding DLCI in the DCE is configured.

DCE-configuredDisplayed when the command is issued from the DTE.

(Frame Relay) Data-link connection identifier (DLCI) statistics.

Active DLCINumber of active DLCIs.

Inactive DLCINumber of inactive DLCIs.

detail extensive none

Sample Output
show interfaces (T3, PPP)
user@host> show interfaces t3-0/2/0
Physical interface: t3-0/2/0, Enabled, Physical link is Up
Interface index: 139, SNMP ifIndex: 35
Link-level type: PPP, MTU: 4474, Clocking: Internal, Speed: T3,
Loopback: None, FCS: 16, Mode: C/Bit parity,
Long buildout: Shorter than 255 feet
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 0 (never), Output: 0 (never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:43:06 PST (02:18:40 ago)
Input rate
: 0 bps (0 pps)

Copyright 2014, Juniper Networks, Inc.

1355

Interfaces Fundamentals for Routing Devices

Output rate
: 72 bps (0 pps)
Active alarms : None
Active defects : None
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^15 - 1, O.151, Pseudorandom (9), Induced error rate: 10e-0
Logical interface t3-0/2/0.0 (Index 66) (SNMP ifIndex 54)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 4470
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255

show interfaces detail (T3, PPP)

user@host> show interfaces t3-0/2/0 detail
Physical interface: t3-0/2/0, Enabled, Physical link is Up
Interface index: 139, SNMP ifIndex: 35, Generation: 22
Link-level type: PPP, MTU: 4474, Clocking: Internal, Speed: T3,
Loopback: None, FCS: 16, Mode: C/Bit parity,
Long buildout: Shorter than 255 feet
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:43:06 PST (02:18:45 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
152
0 bps
Input packets:
0
0 pps
Output packets:
8
0 pps
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Active alarms : None

Active defects : None
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^15 - 1, O.151, Pseudorandom (9), Induced error rate: 10e-0
Logical interface t3-0/2/0.0 (Index 66) (SNMP ifIndex 54) (Generation 8)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 4470, Generation: 17, Route table: 0

1356

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 24

show interfaces extensive (T3, PPP)

user@host> show interfaces t3-0/2/0 extensive
Physical interface: t3-0/2/0, Enabled, Physical link is Up
Interface index: 139, SNMP ifIndex: 35, Generation: 22
Link-level type: PPP, MTU: 4474, Clocking: Internal, Speed: T3,
Loopback: None, FCS: 16, Mode: C/Bit parity,
Long buildout: Shorter than 255 feet
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives
Hold-times
: Up 0 ms, Down 0 ms
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:43:06 PST (02:18:47 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
171
72 bps
Input packets:
0
0 pps
Output packets:
9
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Bucket drops: 0, Policed discards: 0, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0, HS link CRC errors: 0,
SRAM errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Queue counters:

Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Active alarms : None

Active defects : None
DS3 media:
Seconds
PLL Lock
0
Reframing
0
AIS
0
LOF
0
LOS
0
IDLE
0

Copyright 2014, Juniper Networks, Inc.

Count
0
0
0
0
0
0

State
OK
OK
OK
OK
OK
OK

1357

Interfaces Fundamentals for Routing Devices

YELLOW
0
0 OK
BPV
0
0
EXZ
0
0
LCV
1
4
PCV
0
0
CCV
0
0
FEBE
1
11
LES
1
PES
0
PSES
0
CES
0
CSES
0
SEFS
0
UAS
0
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 4484, Runt threshold: 3
Idle cycle flag: flags, Start end flag: shared
DSU configuration:
Compatibility mode: None, Scrambling: Disabled, Subrate: Disabled
FEAC loopback: Inactive, Response: Disabled, Count: 0
DS3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^15 - 1, O.151, Pseudorandom (9), Induced error rate: 10e-0
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
Limit
%
bps
%
usec
0 best-effort
95
42499200
95
0
low
none
3 network-control
5
2236800
5
0
low
none
Logical interface t3-0/2/0.0 (Index 66) (SNMP ifIndex 54) (Generation 8)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 4470, Generation: 17, Route table: 0
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 24

show interfaces (E3, Frame Relay)

user@host> show interfaces e3-1/2/0
Physical interface: e3-1/2/0, Enabled, Physical link is Up
Interface index: 153, SNMP ifIndex: 49
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, Speed: E3,
Loopback: None, FCS: 16, Framing: G751
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 0 (never), Output: 4 (00:00:06 ago)
DTE statistics:
Enquiries sent
: 4
Full enquiries sent
: 0
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0

1358

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Enquiry responses sent

:
Full enquiry responses sent
:
Common statistics:
Unknown messages received
:
Asynchronous updates received
:
Out-of-sequence packets received
:
Keepalive responses timedout
:
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:46:14 PST
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Active alarms : None
Active defects : None

0
0
0
0
0
1
(02:27:17 ago)

Logical interface e3-1/2/0.0 (Index 66) (SNMP ifIndex 57)

Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Input packets : 0
Output packets: 0
Protocol inet, MTU: 4470
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:00:06 sec, Last down: 00:00:06 ago
Input packets : 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

show interfaces detail (E3, Frame Relay)

user@host> show interfaces e3-1/2/0 detail
Physical interface: e3-1/2/0, Enabled, Physical link is Up
Interface index: 153, SNMP ifIndex: 49, Generation: 36
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, Speed: E3,
Loopback: None, FCS: 16, Framing: G751
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000
Link flags
: Keepalives DTE
Hold-times
: Up 0 ms, Down 0 ms
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI statistics:
Input : 0 (last seen: never)
Output: 5 (last sent 00:00:07 ago)
DTE statistics:
Enquiries sent
: 5
Full enquiries sent
: 0
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 4 supported, 4 in use

Copyright 2014, Juniper Networks, Inc.

1359

Interfaces Fundamentals for Routing Devices

Last flapped
: 2005-12-05 08:46:14 PST (02:27:27 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0
Output bytes :
806
0
Input packets:
0
0
Output packets:
44
0
Queue counters:
Queued packets Transmitted packets

bps
bps
pps
pps
Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

43

43

Active alarms : None

Active defects : None
Logical interface e3-1/2/0.0 (Index 66) (SNMP ifIndex 57) (Generation 15)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 24, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 38
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:00:16 sec, Last down: 00:00:16 ago
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

show interfaces extensive (E3, Frame Relay)

user@host> show interfaces e3-1/2/0 extensive
Physical interface: e3-1/2/0, Enabled, Physical link is Up
Interface index: 153, SNMP ifIndex: 49, Generation: 36
Link-level type: Frame-Relay, MTU: 4474, Clocking: Internal, Speed: E3,
Loopback: None, FCS: 16, Framing: G751
Device flags
: Present Running

1360

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps Internal: 0x4000

Link flags
: Keepalives DTE
Hold-times
: Up 0 ms, Down 0 ms
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI statistics:
Input : 0 (last seen: never)
Output: 6 (last sent 00:00:02 ago)
DTE statistics:
Enquiries sent
: 5
Full enquiries sent
: 1
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
Common statistics:
Unknown messages received
: 0
Asynchronous updates received
: 0
Out-of-sequence packets received
: 0
Keepalive responses timedout
: 1
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:46:14 PST (02:27:30 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
821
56 bps
Input packets:
0
0 pps
Output packets:
45
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 21118, Bucket drops: 0,
Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, HS link CRC errors: 0, SRAM errors: 0,
Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
Queue counters:

Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

44

44

Active alarms : None

Active defects : None
E3 media:
Seconds
PLL Lock
0
Reframing
187
AIS
0
LOF
187
LOS
187
IDLE
0
YELLOW
0
BPV
0
EXZ
0

Copyright 2014, Juniper Networks, Inc.

Count
0
1
0
1
1
0
0
0
0

State
OK
OK
OK
OK
OK
OK
OK

1361

Interfaces Fundamentals for Routing Devices

LCV
188
12303167
LES
188
SEFS
187
UAS
195
DSU configuration:
Compatibility mode: None, Scrambling: Disabled
E3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^15 - 1, O.151, Pseudorandom (9), Induced Error rate: 10e-0
Packet Forwarding Engine configuration:
Destination slot: 1, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
Limit
%
bps
%
usec
0 best-effort
95
32649600
95
0
low
none
3 network-control
5
1718400
5
0
low
none
Logical interface e3-1/2/0.0 (Index 66) (SNMP ifIndex 57) (Generation 15)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 4470, Generation: 24, Route table: 0
Flags: None
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 38
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:00:19 sec, Last down: 00:00:19 ago
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

1362

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces demux0 (Demux Interfaces)

Syntax

Release Information
Description

Options

show interfaces demux0.logical-interface-number

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Command introduced in Junos OS Release 9.0.

(MX Series and M Series routers only) Display status information about the specified
demux interface.
noneDisplay standard information about the specified demux interface.
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.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Verifying and Managing Agent Circuit Identifier-Based Dynamic VLAN Configuration

show interfaces (Demux) on page 1369

show interfaces (PPPoE over Aggregated Ethernet) on page 1370
show interfaces extensive (Targeted Distribution for Aggregated Ethernet
Links) on page 1370
show interfaces demux0 (ACI Interface Set Configured) on page 1371
Table 74 on page 1363 lists the output fields for the show interfaces (demux interfaces)
command. Output fields are listed in the approximate order in which they appear.

Table 74: Demux show interfaces Output Fields

Field Name

Field Description

Level of Output

Name of the physical interface.

brief detail extensive

Physical Interface
Physical interface

none
Interface index

Index number of the physical interface, which reflects its initialization sequence.

brief detail extensive

none

Copyright 2014, Juniper Networks, Inc.

1363

Interfaces Fundamentals for Routing Devices

Table 74: Demux show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Enabled

State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description on page 994.

brief detail extensive

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 sequence.

detail extensive none

Link

Status of the physical link (Up or Down).

terse

Targeting summary

Status of aggregated Ethernet links that are configured with targeted distribution
(primary or backup)

extensive

Bandwidth

Bandwidth allocated to the aggregated Ethernet links that are configured with
targeted distribution.

extensive

Proto

Protocol family configured on the interface.

terse

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

Type

Type of interface. Software-Pseudo indicates a standard software interface

with no associated hardware device.

brief detail extensive

Link-level type

Encapsulation being used on the physical interface.

brief detail extensive

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 the
Device Flags section under Common Output Fields Description on page 994.

brief detail extensive

Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description on page 994.

brief detail extensive

Link type

Data transmission type.

detail extensive none

Link flags

Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description on page 994.

detail extensive 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

Interface flags

1364

none

none

none

none

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 74: Demux show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Current address

Configured MAC address.

detail extensive

Hardware address

Hardware MAC address.

detail extensive

Alternate link
address

Backup address of the link.

detail extensive

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).

detail extensive none

Statistics last
cleared

Time when the statistics for the interface were last set to zero.

detail extensive

Traffic statistics

Number and rate of bytes and packets received and transmitted on the physical
interface.

detail extensive

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

IPv6 transit statisticsNumber 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 errors

Input bytesNumber of bytes received on the interface

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Input errors on the interface whose definitions are as follows:

ErrorsSum of the incoming frame aborts and FCS errors.

DropsNumber of packets dropped by the input queue of the I/O Manager

extensive

ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.

Framing errorsNumber of packets received with an invalid frame checksum

(FCS).

RuntsNumber of frames received that are smaller than the runt threshold.

GiantsNumber of frames received that are larger than the giant packet

threshold.

Policed discardsNumber 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.

Input Rate

Resource errorsSum of transmit drops.

Input rate in bits per second (bps) and packets per second (pps).

Copyright 2014, Juniper Networks, Inc.

none

1365

Interfaces Fundamentals for Routing Devices

Table 74: Demux show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output errors

Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:

extensive

Carrier transitionsNumber 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.

ErrorsSum of the outgoing frame aborts and FCS errors.

DropsNumber 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.

Output Rate

MTU errorsNumber of packets whose size exceeded the MTU of the interface.

Resource errorsSum of transmit drops.

Output rate in bps and pps.

none

Name of the logical interface.

brief detail extensive

Logical Interface
Logical interface

none
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

Generation

Unique number for use by Juniper Networks technical support only.

detail

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

brief detail extensive

Encapsulation

Encapsulation on the logical interface.

brief extensive none

ACI VLAN: Dynamic

Profile

Name of the dynamic profile that defines the agent circuit identifier (ACI)
interface set. If configured, the ACI interface set enables the underlying demux
interface to create dynamic VLAN subscriber interfaces based on ACI
information.

brief detail extensive

Demux

Specific IP demultiplexing (demux) values:

detail extensive none

Underlying interfaceThe underlying interface that the demux interface uses.

IndexIndex number of the logical interface.

FamilyProtocol family configured on the logical interface.

Source prefixes, totalTotal number of source prefixes for the underlying

none

none

interface.

Destination prefixes, totalTotal number of destination prefixes for the

underlying interface.

1366

Prefixinet family prefix.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 74: Demux show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

protocol-family

Protocol family configured on the logical interface.

brief

Traffic statistics

Number and rate of bytes and packets received and transmitted on the specified
interface set.

detail extensive

Input bytes, Output bytesNumber of bytes received and transmitted on the

interface set.

Input packets, Output packetsNumber of packets received and transmitted

on the interface set.

IPv6 transit statisticsNumber 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

Transit statistics

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Number of transit bytes and packets received and transmitted on the local
interface.

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Number and rate of bytes and packets transiting the switch.

detail extensive

detail extensive

NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.

IPv6 Transit
statistics

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.

detail extensive

NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.

Input packets

Input bytesNumber of bytes received on the interface.

Output bytesNumber of bytes transmitted on the interface.

Input packetsNumber of packets received on the interface.

Output packetsNumber of packets transmitted on the interface.

Number of packets received on the interface.

Copyright 2014, Juniper Networks, Inc.

none

1367

Interfaces Fundamentals for Routing Devices

Table 74: Demux show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Output packets

Number of packets transmitted on the interface.

none

Protocol

Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description on page 994.

detail 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
the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Route table

Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.

detail extensive

Flags

Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description on page 994.

detail extensive none

Mac-Validate
Failures

Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.

detail extensive none

Addresses, Flags

Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description on
page 994.

detail extensive 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

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Link

Name of the physical interfaces for member links in an aggregated Ethernet

bundle for a PPPoE over aggregated Ethernet configuration. PPPoE traffic goes
out on these interfaces.

detail extensive none

Dynamic-profile

Name of the PPPoE dynamic profile assigned to the underlying interface.

detail extensive none

Service Name Table

Name of the PPPoE service name table assigned to the PPPoE underlying
interface.

detail extensive none

Max Sessions

Maximum number of dynamic PPPoE logical interfaces that the router can
activate on the underlying interface.

detail extensive none

1368

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Table 74: Demux show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Duplicate
Protection

State of duplicate protection: On or Off. Duplicate protection prevents the

activation of another dynamic PPPoE logical interface on the same underlying
interface when a dynamic PPPoE logical interface for a client with the same
MAC address is already active on that interface.

detail extensive none

Direct Connect

State of the configuration to ignore DSL Forum VSAs: On or Off. When configured,
the router ignores any of these VSAs received from a directly connected CPE
device on the interface.

detail extensive none

AC Name

Name of the access concentrator.

detail extensive none

Sample Output
show interfaces (Demux)
user@host> show interfaces demux0
Physical interface: demux0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 79, Generation: 129
Type: Software-Pseudo, Link-level type: Unspecified, MTU: 9192, Clocking: 1,
Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit 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 demux0.0 (Index 87) (SNMP ifIndex 84) (Generation 312)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Demux:
Underlying interface: ge-2/0/1.0 (Index 74)
Family Inet Source prefixes, total 1
Prefix: 1.1.1/24
Traffic statistics:
Input bytes :
0

Copyright 2014, Juniper Networks, Inc.

1369

Interfaces Fundamentals for Routing Devices

Output bytes :
1554
Input packets:
0
Output packets:
37
IPv6 transit statistics:
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
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 395, Route table: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 11.1.1/24, Local: 11.1.1.1, Broadcast: 11.1.1.255,
Generation: 434

show interfaces (PPPoE over Aggregated Ethernet)

user@host> show interfaces demux0.100
Logical interface demux0.100 (Index 76) (SNMP ifIndex 61160)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.100 ]
Encapsulation: ENET2
Demux:
Underlying interface: ae0 (Index 199)
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,
Direct Connect: Off,
AC Name: pppoe-server-1

show interfaces 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)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1 ] Encapsulation: ENET2
Demux:
Underlying interface: ae0 (Index 201)
Link:
ge-1/0/0

1370

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

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
Logical interface demux0.1073741827 (Index 346) (SNMP ifIndex 527)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1802 0x8100.302 ] Encapsulation:
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
Protocol inet, MTU: 1500
Flags: Sendbcast-pkt-to-re, Unnumbered
Donor interface: lo0.0 (Index 322)
Preferred source address: 100.20.200.202
Addresses, Flags: Primary Is-Default Is-Primary
Local: 10.4.12.119
Protocol 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

Copyright 2014, Juniper Networks, Inc.

1371

Interfaces Fundamentals for Routing Devices

show interfaces extensive

Syntax
Release Information

Description

show interfaces extensive

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1x48 for PTX Series Packet Transport
Routers.
Display extensive information about all interfaces configured on the router.

NOTE:

At some times, the cumulative byte counters displayed with the show
interfaces extensive command on the 10-Gigabit Ethernet MPC with SFP+
is not always increasing and cumulative and does not give the correct
results. There is a time lag in collecting these statistics, during which the
display might decrease or go from a nonzero number to zero. Eventually,
the counter will display the correct result.

When the show interfaces extensive command is executed on a router with

an MPC or a T4000 Type 5 FPC, the Input packet rejects counter of the Filter
statistics field also displays statistics related to the following packet errors:

1372

Invalid VLAN range

Tagged packet received on an untagged interface

When the show interfaces extensive command is executed on an interface

that is configured on a T4000 Type 5 FPC, the IPv6 transit statistics field
displays:

Total statistics (sum of transit and local statistics) at the physical

interface level

Transit statistics at the logical interface level

When the show interfaces extensive command is executed on an aggregate

interface in a T1600 Core Router, the IPv6 Input bytes is displayed for an
aggregate interface. However, the IPv6 Input bytes is always zero on a
member link of an aggregated bundle even when there is IPv6 transit traffic
on the member link. This is because the logical interface index of the
aggregate logical interface is updated but not the logical interface of the
member links in the channel lookup table.

The Output packets field under the Traffic statistics section in the output
of the show interfaces extensive command includes both IPv4 and IPv6
packets. For example, in a scenario in which both IPv4 and IPv6 packets
are being mirrored on the same interface and when you deactivate an IPv4
port-mirroring instance on the chassis, the output of the show interfaces
extensive command shows a value in the Output packets field of the Traffic
statistics section, which is the value of IPv6 packets that are mirrored and
not of the IPv4 packets. This behavior is expected.

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Options
Required Privilege
Level

This command has no options.

view

List of Sample Output

show interfaces extensive (Circuit Emulation) on page 1373

show interfaces extensive (Fast Ethernet) on page 1374
show interfaces extensive (Gigabit Ethernet) on page 1376
show interfaces extensive (10-Gigabit Ethernet) on page 1376
show interfaces extensive (IQ2 and IQ2E) on page 1378
show interfaces extensive (100-Gigabit Ethernet Type 4 PIC with CFP) on page 1381
show interfaces extensive (PTX5000 Packet Transport Router) on page 1383
show interfaces extensive (MX Series Routers) on page 1385
show interfaces extensive (MX480 Router with MPC5E and 10-Gigabit Ethernet OTN
Interface) on page 1387
show interfaces extensive (MX480 Router with MPC5E and 100-Gigabit Ethernet OTN
Interface) on page 1388
show interfaces extensive (MX2020 Router with MPC6E and OTN MIC) on page 1391
show interfaces extensive (MX2010 Router with MPC6E and 100-Gigabit Ethernet
OTN Interface) on page 1394
show interfaces extensive (MX2010 Router with MPC6E and 10-Gigabit Ethernet
Interface) on page 1395
show interfaces extensive (T4000 Routers with Type 5 FPCs) on page 1397
show interfaces extensive (Aggregated Ethernet) on page 1399

Output Fields

For more information, see the output fields table for the particular interface type in which
you are interested. For information about destination class and source class statistics,
see the Destination Class Field section and the Source Class Field section under
Common Output Fields Description on page 994. For sample output for specific interfaces,
see the other topics in this collection.

Sample Output
show interfaces extensive (Circuit Emulation)
If a Circuit Emulation (CE) PIC is configured for SAToP pseudowire, then pseudowire
statistics are displayed in the CE information section of the show interface extensive
output. If SAToP pseudowire is not configured on the CE PIC, then all CE information
counters display 0 (zero).
user@host> show interface t1-0/0/0 extensive
Physical interface :t1-0/0/0, Enabled, Physical Link : Up
Interface index:61441
Speed : 1.54 Mbps, Loopback: Disabled
Operational state : Enabled,
Encapsulation : Trans
Encoding : b8zs,
Framing
: unframe,
Build-out : 0-30
Inversion
: enable, Clock source : master
Description :
Traffic statistics:
T1 media:
Seconds
ES
1643
SES
1643

Copyright 2014, Juniper Networks, Inc.

1373

Interfaces Fundamentals for Routing Devices

CE
CE
CE
CE
CE

Info
Rx
:
Tx
:
Rx Drop:
Tx Drop:

Packets
2395529
2396259
0
0

Bytes
306627712
306721152
0
0

CE Overrun Events: 0
CE Underrun Events: 0

Sample Output
show interfaces extensive (Fast Ethernet)
user@host> show interfaces fe-0/2/1 extensive
Physical interface: fe-0/2/0, Enabled, Physical link is Up
Interface index: 129, SNMP ifIndex: 23, Generation: 130
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 4 supported, 4 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:90:69:91:c4:3e, Hardware address: 00:90:69:91:c4:3e
Last flapped
: 2006-04-16 23:00:41 PDT (02:08:05 ago)
Statistics last cleared: 2006-04-16 21:42:00 PDT (03:26:46 ago)
Traffic statistics:
Input bytes :
17539
152 bps
Output bytes :
92968
224 bps
Input packets:
348
0 pps
Output packets:
1349
0 pps
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:
Carrier transitions: 3, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

66

66

1 expedited-fo

2 assured-forw

3 network-cont

1283

1283

Active alarms : None

Active defects : None
MAC statistics:
Total octets
Total packets
Unicast packets
Broadcast packets
Multicast packets
CRC/Align errors
FIFO errors
MAC control frames
MAC pause frames

1374

Receive
24721
348
347
1
0
0
0
0
0

Transmit
105982
1349
430
37
882
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
348
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
1349
Output packet pad count
0
Output packet error count
0
CAM destination filters: 3, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link mode: Full-duplex, Flow control: None, Remote fault: OK
Packet Forwarding Engine configuration:
Destination slot: 0
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority

Limit

%
bps
%
usec
0 best-effort
95
95000000 95
0
low
none
3 network-control
5
5000000
5
0
low
none
Logical interface fe-0/2/0.0 (Index 66) (SNMP ifIndex 46) (Generation 133)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 142, Route table: 0
Flags: DCU, SCU-out
Packets
Bytes
Destination class
(packet-per-second)
(bits-per-second)
silv1_new
0
0
(
0) (
0)
silv2_new
0
0
(
0) (
0)
silv_misc
0
0
(
0) (
0)
silver0
0
0
(
0) (
0)
silver2
0
0
(
0) (
0)
silver3
0
0
(
0) (
0)
silver4
0
0
(
0) (
0)
silver5
0
0
(
0) (
0)
silver6
0
0
(
0) (
0)
silver7
0
0
(
0) (
0)
silver9
0
0
(
0) (
0)
Packets
Bytes
Source class
(packet-per-second)
(bits-per-second)
gold1
0
0
(
0) (
0)
gold2
16600
1062400
(
0) (
0)
gold3
0
0

Copyright 2014, Juniper Networks, Inc.

1375

Interfaces Fundamentals for Routing Devices

(
0) (
Addresses, Flags: Is-Preferred Is-Primary
Destination: 12.1.1/24, Local: 12.1.1.1, Broadcast: 12.1.1.255,
Generation: 150

0)

show interfaces extensive (Gigabit Ethernet)

user@host> show interfaces ge-5/0/0.0 extensive
Logical interface ge-5/0/0.0 (Index 71) (SNMP ifIndex 1930) (Generation 139)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Traffic statistics:
Input bytes :
0
Output bytes :
42
Input packets:
0
Output packets:
1
Local statistics:
Input bytes :
0
Output bytes :
42
Input packets:
0
Output packets:
1
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Output Filters: f-any
Protocol inet, MTU: 1500, Generation: 155, Route table: 0
Output Filters: f-inet,
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.11.1/24, Local: 10.11.1.1, Broadcast: 10.11.1.255,
Generation: 170
Protocol multiservice, MTU: Unlimited, Generation: 156, Route table: 0
Flags: Is-Primary
Policer: Input: __default_arp_policer__

show interfaces extensive (10-Gigabit Ethernet)

user@host> show interfaces xe-2/1/0 extensive
Physical interface: xe-2/1/0, Enabled, Physical link is Up
Interface index: 258, SNMP ifIndex: 762, Generation: 2046
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, BPDU Error:
None, Loopback: None, Source filtering: Disabled,
Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:1d:b5:f8:6d:eb, Hardware address: 00:1d:b5:f8:6d:eb
Last flapped
: 2011-12-17 00:19:02 PST (07:36:37 ago)
Statistics last cleared: 2011-12-17 07:55:24 PST (00:00:15 ago)
Traffic statistics:
Input bytes :
110000
0 bps
Output bytes :
0
0 bps
Input packets:
1000
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
110000
Output bytes :
0

1376

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input packets:
1000
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:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0,
MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : None
Active defects : None
PCS statistics
Seconds
Bit errors
0
Errored blocks
0
MAC statistics:
Receive
Total octets
128000
Total packets
1000
Unicast packets
1000
Broadcast packets
0
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
1000
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 2
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Limit

Copyright 2014, Juniper Networks, Inc.

Transmit
0
0
0
0
0
0
0
0
0

0
0
0

Buffer Priority

1377

Interfaces Fundamentals for Routing Devices

%
bps
0 best-effort
95
9500000000
none
3 network-control
5
500000000
none
Interface transmit statistics: Disabled

%
95

usec
0

low

low

Logical interface xe-2/1/0.0 (Index 83) (SNMP ifIndex 1677) (Generation 10082)
Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
Traffic statistics:
Input bytes :
110000
Output bytes :
0
Input packets:
1000
Output packets:
0
IPv6 transit statistics:
Input bytes :
55000
Output bytes :
0
Input packets:
500
Output packets:
0
Local statistics:
Input bytes :
55000
Output bytes :
0
Input packets:
500
Output packets:
0
Transit statistics:
Input bytes :
55000
0 bps
Output bytes :
0
0 bps
Input packets:
500
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
55000
Output bytes :
0
Input packets:
500
Output packets:
0
Protocol inet6, MTU: 1500, Generation: 23739, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 2001:1000:abcd:2312:1432:abcd:1234:0/112, Local:
2001:1000:abcd:2312:1432:abcd:1234:1234
Generation: 506
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::21d:b5ff:fef8:6deb
Protocol multiservice, MTU: Unlimited, Generation: 508
Generation: 23740, Route table: 0
Policer: Input: __default_arp_policer__

show interfaces extensive (IQ2 and IQ2E)

user@host> show interfaces ge-3/2/2 extensive
Physical interface: ge-3/2/2, Enabled, Physical link is Up
Interface index: 156, SNMP ifIndex: 548, Generation: 159
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
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 8 supported, 8 maximum usable queues
Schedulers
: 128
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:14:f6:12:86:fa, Hardware address: 00:14:f6:12:86:fa
Last flapped
: 2010-03-17 04:03:11 PDT (00:45:30 ago)

1378

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Statistics last cleared: Never

Traffic statistics:
Input bytes :
1716096
0 bps
Output bytes :
1716448
0 bps
Input packets:
13407
0 pps
Output packets:
13411
0 pps
IPv6 total statistics:
Input bytes :
1716096
Output bytes :
1716096
Input packets:
13407
Output packets:
13407
Ingress traffic statistics at Packet Forwarding Engine:
Input bytes :
1716096
0 bps
Input packets:
13407
0 pps
Drop
bytes :
0
0 bps
Drop
packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 1, L2 mismatch timeouts: 0, FIFO errors:
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
Ingress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped
packets
0 best-effort
13407
13407
0
1 expedited-fo
0
0
0
2 assured-forw
0
0
0
3 network-cont
0
0
0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped
packets
0 best-effort
13407
13407
0
1 expedited-fo
0
0
0
2 assured-forw
0
0
0
3 network-cont
4
4
0
Active alarms : None
Active defects : None
MAC statistics:
Receive
Transmit
Total octets
1716096
1716448
Total packets
13407
13411
Unicast packets
13407
13407
Broadcast packets
0
0
Multicast packets
0
4
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

Copyright 2014, Juniper Networks, Inc.

1379

Interfaces Fundamentals for Routing Devices

VLAN tagged frames

0
Code violations
0
Filter statistics:
Input packet count
13407
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
13411
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:
Link mode: Full-duplex, Flow control: None, Remote fault: OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Packet Forwarding Engine configuration:
Destination slot: 3
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
Direction : Input
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-3/2/2.0 (Index 83) (SNMP ifIndex 6080) (Generation
148)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.100 ]
Traffic statistics:
Input bytes :
0
Output bytes :
336
Input packets:
0
Output packets:
4
IPv6 total statistics:
Input bytes :
1716096
Output bytes :
1716096
Input packets:
13407
Output packets:
13407
Local statistics:
Input bytes :
0
Output bytes :
336
Input packets:
0
Output packets:
4
Transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
IPv6 total statistics:

1380

Encapsulation: ENET2

0
0
0
0

bps
bps
pps
pps

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input bytes :
1716096
Output bytes :
1716096
Input packets:
13407
Output packets:
13407
Protocol inet6, MTU: 1500, Generation: 159, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Primary
Destination: Unspecified, Local: 2000::2
Generation: 146
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::214:f600:6412:86fa
Protocol multiservice, MTU: Unlimited, Generation: 148
Generation: 160, Route table: 0
Policer: Input: __default_arp_policer__
Logical interface ge-3/2/2.32767 (Index 84) (SNMP ifIndex 6081) (Generation
149)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x0000.0 ] Encapsulation: ENET2
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol multiservice, MTU: Unlimited, Generation: 161, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__

show interfaces extensive (100-Gigabit Ethernet Type 4 PIC with CFP)

user@host> show interfaces et-0/0/0:0 extensive
Physical interface: et-0/0/0:0, Enabled, Physical link is Down
Interface index: 156, SNMP ifIndex: 516, Generation: 163
Link-level type: Ethernet, MTU: 9192, Speed: 50000mbps, BPDU Error: None,
MAC-REWRITE 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
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Damping
: half-life: 5 sec, max-suppress: 20 sec, reuse 1000, suppress:
2000, state: enabled
Current address: 00:aa:aa:aa:aa:00, Hardware address: 00:21:59:5c:48:00
Last flapped
: 2010-01-07 16:36:49 PST (18:02:35 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:

Copyright 2014, Juniper Networks, Inc.

1381

Interfaces Fundamentals for Routing Devices

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:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0,
HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 8 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 DEFAULT, NC-

1 REALTIME

2 PRIVATE, NC-

1253

1253

4 BC-H, CLASS_

5 BC-M, CLASS_

6 IA, CLASS_V_

7 CLASS_S_OUTP

3 CONTROL

Queue
Mapped Forwarding Class
0
DEFAULT, NC-Q0
1
REALTIME
2
PRIVATE, NC-Q1
3
CONTROL
4
BC-H, CLASS-Q4
5
BC-M, CLASS-Q5
6
IA, CLASS_V_OUTPUT
7
CLASS_S_OUTPUT
Active alarms : None
Active defects : None
MAC statistics:
Receive
Total octets
0
Total packets
0
Unicast packets
0
Broadcast packets
0
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Packet Forwarding Engine configuration:
Destination slot: 0
CoS information:

1382

Transmit
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Direction : Output
CoS transmit queue

0 best-effort
3 network-control

Bandwidth

Buffer Priority Limit

%
95

bps
47500000000

%
95

usec
0

low none

2500000000

low none

Logical interface et-0/0/0:0.0 (Index 68) (SNMP ifIndex 546) (Generation 161)
Flags: Deviet-Down SNMP-Traps Encapsulation: ENET2
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 9178, Generation: 220, Route table: 0
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 210.160.0/24, Local: 210.160.0.1, Broadcast: 210.160.0.255,
Generation: 192
Protocol mpls, MTU: 9166, Maximum labels: 3, Generation: 221, Route table: 0
Protocol multiservice, MTU: Unlimited, Generation: 222, Route table: 0
Policer: Input: __default_arp_policer

show interfaces extensive (PTX5000 Packet Transport Router)

user@host> show interfaces et-7/0/0 extensive
Physical interface: et-7/0/0, Enabled, Physical link is Up
Interface index: 168, SNMP ifIndex: 501, Generation: 171
Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, BPDU Error: None,
MAC-REWRITE Error: None,
Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Damping
: half-life: 5 sec, max-suppress: 20 sec, reuse 1000, suppress:
2000, state: enabled
Current address: 88:e0:f3:3b:de:43, Hardware address: 88:e0:f3:3b:de:43
Last flapped
: 2012-01-18 11:48:24 PST (01:47:08 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
3583014
0 bps
Output bytes :
758050
0 bps
Input packets:
17740
0 pps
Output packets:
3418
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0

Copyright 2014, Juniper Networks, Inc.

1383

Interfaces Fundamentals for Routing Devices

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:
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
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

252

252

1 expedited-fo

2 assured-forw

3 network-cont

6196

6196

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : None
Active defects : None
MAC statistics:
Receive
Total octets
4108825
Total packets
21166
Unicast packets
14824
Broadcast packets
3
Multicast packets
6339
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
16091
Code violations
0
Filter statistics:
Input packet count
9
Input packet rejects
9
Input DA rejects
9
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Autonegotiation information:
Negotiation status: Incomplete
Packet Forwarding Engine configuration:
Destination slot: 7
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Limit

1384

Transmit
1159686
6448
3255
0
3193
0
0
0
0

0
0
0

Buffer Priority

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

%
bps
0 best-effort
95
9500000000
none
3 network-control
5
500000000
none
Interface transmit statistics: Disabled

%
95

usec
0

low

low

show interfaces extensive (MX Series Routers)

user@host> show interfaces xe-0/0/0 extensive
Physical interface: xe-0/0/0, Enabled, Physical link is Up
Interface index: 145, SNMP ifIndex: 592, Generation: 148
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, BPDU Error:
None,
Loopback: None, Source filtering: Disabled, Flow control: Enabled
Pad to minimum frame size: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x0
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 08:81:f4:82:a3:f0, Hardware address: 08:81:f4:82:a3:f0
Last flapped
: 2013-10-26 03:20:40 test (2w3d 03:15 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0

Queue number:
0

Copyright 2014, Juniper Networks, Inc.

Mapped forwarding classes

best-effort

1385

Interfaces Fundamentals for Routing Devices

1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : LINK
Active defects : LINK
PCS statistics
Seconds
Bit errors
109
Errored blocks
109
MAC statistics:
Receive
1
0

Transmit
0

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : LINK
Active defects : LINK
PCS statistics
Seconds
Bit errors
109
Errored blocks
109
MAC statistics:
Receive
Total octets
0
Total packets
0
Unicast packets
0
Broadcast packets
0
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Total errors
0
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 0
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Limit
%
bps
%
0 best-effort
95
9500000000
95
none
3 network-control
5
500000000
5

1386

Transmit
0
0
0
0
0
0
0
0
0

0
0
0

Buffer Priority
usec
0

low

low

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

none
Interface transmit statistics: Disabled

show interfaces extensive (MX480 Router with MPC5E and 10-Gigabit Ethernet OTN Interface)
user@host> show interfaces xe-0/0/3 extensive
Physical interface: xe-0/0/3, Enabled, Physical link is Up
Interface index: 200, SNMP ifIndex: 577, Generation: 203
Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps,
BPDU Error: None, MAC-REWRITE Error: None, Loopback: None, Source filtering:
Disabled, Flow control: Enabled
Pad to minimum frame size: Disabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Schedulers
: 0
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:23:9c:fc:98:03, Hardware address: 00:23:9c:fc:98:03
Last flapped
: 2014-06-26 18:16:50 PDT (04:58:35 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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
Output errors:
Carrier transitions: 5, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0

Queue number:
0
1
2
3
Active alarms : None
Active defects : None

Copyright 2014, Juniper Networks, Inc.

Mapped forwarding classes

best-effort
expedited-forwarding
assured-forwarding
network-control

1387

Interfaces Fundamentals for Routing Devices

PCS statistics
Seconds
Bit errors
0
Errored blocks
4
MAC statistics:
Receive
Total octets
0
Total packets
0
Unicast packets
0
Broadcast packets
0
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Total errors
0
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Limit
%
bps
%
0 best-effort
95
9500000000
95
none
3 network-control
5
500000000
5
none
Interface transmit statistics: Disabled

Transmit
0
0
0
0
0
0
0
0
0

0
0
0

Buffer Priority
usec
0

low

low

show interfaces extensive (MX480 Router with MPC5E and 100-Gigabit Ethernet OTN Interface)
user@host> show interfaces et-2/1/0 extensive
Physical interface: et-2/1/0, Enabled, Physical link is Up
Interface index: 215, SNMP ifIndex: 872, Generation: 218
Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 100Gbps, BPDU Error:
None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled
Pad to minimum frame size: Disabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Schedulers
: 0
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:23:9c:fc:9a:e6, Hardware address: 00:23:9c:fc:9a:e6
Last flapped
: 2014-06-26 18:42:04 PDT (04:36:58 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps

1388

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input packets:
0
0 pps
Output packets:
0
0 pps
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
Output errors:
Carrier transitions: 263, Errors: 0, Drops: 0, Collisions: 0, Aged packets:
0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : None
Active defects : None
PCS statistics
Seconds
Bit errors
0
Errored blocks
754
MAC statistics:
Receive
Total octets
14960
Total packets
104
Unicast packets
0
Broadcast packets
0
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
2
Fragment frames
6
VLAN tagged frames
0
Code violations
0
Total errors
98
Filter statistics:
Input packet count
104
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0

Copyright 2014, Juniper Networks, Inc.

Transmit
0
0
0
0
0
0
0
0
0

1389

Interfaces Fundamentals for Routing Devices

Output packet count

0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 0
OTN alarms
: None
OTN defects
: None
OTN FEC Mode
: GFEC
OTN Rate
:
OTU4 100Gbps
OTN Line Loopback : None
OTN Local Loopback: None
OTN Payload PRBS
: None
OTN FEC statistics:
Corrected Errors
169828399453
Uncorrected Words
28939961456
Corrected Error Ratio (
17963 sec average) 8.46e-05
OTN FEC alarms:
Seconds
Count State
FEC Degrade
1180
3 OK
FEC Excessive
1160
5 OK
OTN OC:
Seconds
Count State
LOS
129
1 OK
LOF
2
1 OK
LOM
0
0 OK
Wavelength Lock
0
0 OK
OTN OTU:
AIS
0
0 OK
BDI
7
1 OK
IAE
0
0 OK
TTIM
168
45 OK
BIAE
0
0 OK
TSF
0
0 OK
SSF
0
0 OK
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 ODU:
AIS
130
1 OK
OCI
0
0 OK
LCK
0
0 OK
BDI
7
1 OK
TTIM
133
1 OK
IAE
0
0 OK
LTC
0
0 OK
CSF
8
4 OK
TSF
0
0 OK
SSF
0
0 OK
PTIM
130
1 OK
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: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00

1390

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Payload Type: 0x00

ODU Delay Management :
Result : 0x00
PRBS:
Result: Test not enabled
OTN Transmitted Overhead Bytes:
APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00
Payload Type: 0x00
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
95000000000
95
0
low
none
3 network-control
5
5000000000
5
0
low
none
Interface transmit statistics: Disabled

show interfaces extensive (MX2020 Router with MPC6E and OTN MIC)
user@host> show interfaces xe-3/0/0 extensive
Physical interface: xe-3/0/0, Enabled, Physical link is Up
Interface index: 166, SNMP ifIndex: 516, Generation: 169
Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps,
BPDU Error:
None, MAC-REWRITE Error: None, Loopback: None, Source filtering: Disabled, Flow
control:
Enabled
Pad to minimum frame size: Disabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 4c:96:14:72:22:63, Hardware address: 4c:96:14:72:22:63
Last flapped
: 2014-05-28 17:53:12 PDT (05:56:24 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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
Output errors:

Copyright 2014, Juniper Networks, Inc.

1391

Interfaces Fundamentals for Routing Devices

Carrier transitions: 3, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,

FIFO
errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort
1 expedited-forwarding
0
2 assured-forwarding
0
3 network-control

0
0
0
Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : None
Active defects : None
PCS statistics
Seconds
Bit errors
2
Errored blocks
2
MAC statistics:
Receive
Transmit
Total octets
0
0
Total packets
0
0
Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0
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
0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 0
OTN alarms
: None
OTN defects
: None
OTN FEC Mode
: GFEC
OTN Rate
: Fixed Stuff Bytes 11.0957Gbps
OTN Line Loopback : None
OTN Local Loopback: None
OTN Payload PRBS
: None
OTN FEC statistics:
Corrected Errors
0
Uncorrected Words
0
Corrected Error Ratio (
21387 sec average) 0.00e+00
OTN FEC alarms:
Seconds
Count State

1392

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

FEC Degrade
0
0 OK
FEC Excessive
0
0 OK
OTN OC:
Seconds
Count State
LOS
0
0 OK
LOF
0
0 OK
LOM
0
0 OK
Wavelength Lock
0
0 OK
OTN OTU:
AIS
0
0 OK
BDI
0
0 OK
IAE
0
0 OK
TTIM
0
0 OK
BIAE
0
0 OK
TSF
0
0 OK
SSF
0
0 OK
Received DAPI:
00 53 4d 2d 54 52 43 20 44 41 50 49 2d 53 45 43
.SM-TRC DAPI-SEC
Received SAPI:
00 53 4d 2d 54 52 43 20 53 41 50 49 2d 53 45 43
.SM-TRC SAPI-SEC
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 ODU:
AIS
0
0 OK
OCI
0
0 OK
LCK
0
0 OK
BDI
0
0 OK
TTIM
0
0 OK
IAE
0
0 OK
LTC
0
0 OK
CSF
0
0 OK
TSF
0
0 OK
SSF
0
0 OK
PTIM
0
0 OK
Received DAPI:
00 50 4d 2d 54 52 43 20 44 41 50 49 2d 53 45 43
.PM-TRC DAPI-SEC
Received SAPI:
00 50 4d 2d 54 52 43 20 53 41 50 49 2d 53 45 43
.PM-TRC SAPI-SEC
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: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00
Payload Type: 0x00
ODU Delay Management :
Result : 0x00
PRBS:
Result: Test not enabled
OTN Transmitted Overhead Bytes:
APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00
Payload Type: 0x00
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
9500000000
95
0
low

Copyright 2014, Juniper Networks, Inc.

1393

Interfaces Fundamentals for Routing Devices

none
3 network-control
5
500000000
none
Interface transmit statistics: Disabled

low

show interfaces extensive (MX2010 Router with MPC6E and 100-Gigabit Ethernet OTN Interface)
user@host> show interfaces et-9/0/0 extensive
Physical interface: et-9/0/0, Enabled, Physical link is Up
Interface index: 196, SNMP ifIndex: 623, Generation: 199
Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 100Gbps, BPDU Error:
None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled
Pad to minimum frame size: Disabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 3c:8a:b0:38:6e:f6, Hardware address: 3c:8a:b0:38:6e:f6
Last flapped
: 2014-06-26 18:18:34 PDT (04:17:07 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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
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
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0

Queue number:
0
1
2
3
Active alarms

1394

Mapped forwarding classes

best-effort
expedited-forwarding
assured-forwarding
network-control
: None

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Active defects : None

PCS statistics
Seconds
Bit errors
0
Errored blocks
0
MAC statistics:
Receive
Total octets
0
Total packets
0
Unicast packets
0
Broadcast packets
0
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Total errors
0
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Limit
%
bps
%
0 best-effort
95
95000000000
95
none
3 network-control
5
5000000000
5
none
Interface transmit statistics: Disabled

Transmit
0
0
0
0
0
0
0
0
0

0
0
0

Buffer Priority
usec
0

low

low

show interfaces extensive (MX2010 Router with MPC6E and 10-Gigabit Ethernet Interface)
user@host> show interfaces xe-6/1/0 extensive
Physical interface: xe-6/1/0, Enabled, Physical link is Up
Interface index: 159, SNMP ifIndex: 603, Generation: 162
Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps,
BPDU Error: None, MAC-REWRITE Error: None, Loopback: None, Source filtering:
Disabled, Flow control: Enabled
Pad to minimum frame size: Disabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Schedulers
: 0
Hold-times
: Up 0 ms, Down 0 ms
Current address: 3c:8a:b0:38:6c:d5, Hardware address: 3c:8a:b0:38:6c:d5
Last flapped
: 2014-06-26 18:16:50 PDT (04:21:04 ago)
Statistics last cleared: Never

Copyright 2014, Juniper Networks, Inc.

1395

Interfaces Fundamentals for Routing Devices

Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
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
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
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0

Queue number:
0
1
2
3
Active alarms : None
Active defects : None
PCS statistics
Bit errors
Errored blocks
MAC statistics:
Total octets
Total packets
Unicast packets
Broadcast packets
Multicast packets
CRC/Align errors
FIFO errors
MAC control frames
MAC pause frames
Oversized frames
Jabber frames
Fragment frames
VLAN tagged frames
Code violations
Total errors
Filter statistics:
Input packet count

1396

Mapped forwarding classes

best-effort
expedited-forwarding
assured-forwarding
network-control

Seconds
0
1
Receive
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Transmit
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Input packet rejects

0
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 0 (0x00)
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Limit
%
bps
%
0 best-effort
95
9500000000
95
none
3 network-control
5
500000000
5
none
Interface transmit statistics: Disabled

0
0
0

Buffer Priority
usec
0

low

low

show interfaces extensive (T4000 Routers with Type 5 FPCs)

The output fields for the show interfaces interface extensive command remains the same
for 12-port 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PF-12XGE-SFPP), 24-port
10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PF-24XGE-SFPP), and 100-Gigabit
Ethernet Type 5 PIC with CFP (PF-1CGE-CFP).
user@host> show interfaces xe-4/0/0 extensive
Physical interface: xe-4/0/0, Enabled, Physical link is Up
Interface index: 200, SNMP ifIndex: 592, Generation: 203
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, BPDU Error:
None, Loopback: None, Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Damping
: half-life: 5 sec, max-suppress: 20 sec, reuse 1000, suppress:
2000, state: enabled
Current address: 00:12:1e:37:53:f8, Hardware address: 00:12:1e:37:53:f8
Last flapped
: 2013-06-03 16:01:56 PDT (06:04:07 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit 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:
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
Egress queues: 8 supported, 4 in use

Copyright 2014, Juniper Networks, Inc.

1397

Interfaces Fundamentals for Routing Devices

Queue counters:

Queued packets

Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Queue number:
Mapped forwarding classes
0
best-effort
1
expedited-forwarding
2
assured-forwarding
3
network-control
Active alarms : None
Active defects : None
PCS statistics
Seconds
Bit errors
0
Errored blocks
0
MAC statistics:
Receive
Transmit
Total octets
0
0
Total packets
0
0
Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0
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
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 0
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
9500000000
95
0
low
none
3 network-control
5
500000000
5
0
low
none
Preclassifier statistics:
Traffic Class
Received Packets
Transmitted Packets
Dropped Packets
real-time
0
network-control
0
best-effort
0
Interface transmit statistics: Disabled

1398

0
0
0

0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces extensive (Aggregated Ethernet)

user@host> show interfaces ae0 extensive
Physical interface: ae0, Enabled, Physical link is Up
Interface index: 199, SNMP ifIndex: 570, Generation: 202
Link-level type: Ethernet, MTU: 1514, Speed: 2Gbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
Flow control: Disabled, Minimum links needed: 1, Minimum bandwidth needed: 0
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Current address: 2c:6b:f5:d1:0f:c0, Hardware address: 2c:6b:f5:d1:0f:c0
Last flapped
: 2012-06-06 23:33:03 PDT (00:00:58 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
18532
1984 bps
Output bytes :
0
0 bps
Input packets:
158
2 pps
Output packets:
0
0 pps
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, Giants: 0, Policed discards:
0,
Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Ingress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Egress queues: 8 supported, 4 in use

Queue counters:
Queued packets

Transmitted packets

Dropped packets

57

57

1 expedited-fo

2 assured-forw

3 network-cont

63605

63605

0 best-effort

Queue number:
0
1
2

Copyright 2014, Juniper Networks, Inc.

Mapped forwarding classes

best-effort
expedited-forwarding
assured-forwarding

1399

Interfaces Fundamentals for Routing Devices

network-control

Logical interface ae0.0 (Index 331) (SNMP ifIndex 583) (Generation 142)
Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
149
2
17416
1984
Output:
0
0
0
0
Link:
ge-3/2/5.0
Input :
90
1
10100
992
Output:
0
0
0
0
ge-3/3/9.0
Input :
59
1
7316
992
Output:
0
0
0
0
LACP info:
Role
System
System
Port
Port Port
priority
identifier priority
number
key
ge-3/2/5.0
Actor
100
00:00:00:00:00:01
127
1
1
ge-3/2/5.0
Partner
127 00:24:dc:98:67:c0
127
1
1
ge-3/3/9.0

Actor

ge-3/3/9.0

Partner

100

00:00:00:00:00:01

127

1
127

00:24:dc:98:67:c0

127

LACP Statistics:
LACP Rx
LACP Tx
Unknown Rx
Illegal Rx
ge-3/2/5.0
38
137
0
0
ge-3/3/9.0
36
139
0
0
Marker Statistics:
Marker Rx
Resp Tx
Unknown Rx
Illegal Rx
ge-3/2/5.0
0
0
0
0
ge-3/3/9.0
0
0
0
0
Protocol inet, MTU: 1500, Generation: 169, Route table: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.2, Broadcast: 1.1.1.255, Generation:
153
Protocol multiservice, MTU: Unlimited, Generation: 170, Route table: 0
Flags: Is-Primary
Policer: Input: __default_arp_policer__

Sample Output

1400

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces lsi (Label-Switched Interface)

Syntax

Release Information
Description
Options

show interfaces interface-type

<brief | detail | extensive | terse>
<descriptions>
<media>
<routing-instance instance-name>
<snmp-index snmp-index>
<statistics>

Command introduced before Junos OS Release 7.4.

Display status information about the specified label-switched interface (LSI).
interface-typeOn most routers, the interface type is lt-fpc/pic/port. On J Series routers,

the interface type is lt-pim/0/port.

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.
routing-instance instance-name(Optional) Display information for the specified routing

instance.
snmp-index snmp-index(Optional) Display information for the specified SNMP index

of the interface.
statistics(Optional) Display static interface statistics.

Required Privilege
Level

view

Related
Documentation
List of Sample Output
Output Fields

show interfaces lsi extensive on page 1403

Table 75 on page 1401 lists the output fields for the show interfaces (logical tunnel)
command. Output fields are listed in the approximate order in which they appear.

Table 75: Logical Tunnel show interfaces Output Fields

Field Name

Field Description

Level of Output

Name of the physical interface.

All levels

Name of the logical interface.

All levels

Physical
Interface
Physical interface

Logical Interface
Logical interface

Copyright 2014, Juniper Networks, Inc.

1401

Interfaces Fundamentals for Routing Devices

Table 75: Logical Tunnel show interfaces Output Fields (continued)

Field Name

Field Description

Level of Output

Index

Logical interface index number, which reflects its initialization sequence.

detail extensive none

SNMP ifIndex

SNMP interface index number.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description
on page 994.

All levels

Encapsulation

Encapsulation on the logical interface.

All levels

Traffic statistics

Total number of bytes and packets received and transmitted on the logical
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. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Input bytesRate of bytes received on the interface.

Output bytesRate of bytes transmitted on the interface.

Input packetsRate of packets received on the interface.

Output packetsRate of packets transmitted on the interface.

Local statistics

Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. It takes awhile (generally, less than 1 second) for this
counter to stabilize.

detail extensive

Transit statistics

Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. It
takes awhile (generally, less than 1 second) for this counter to stabilize.

detail extensive

Protocol

Protocol family configured on the logical interface, such as iso, inet6, mpls.

detail extensive none

MTU

MTU size on the logical interface.

detail extensive none

Generation

Unique number for use by Juniper Networks technical support only.

detail extensive

Flags

Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description on
page 994.

detail extensive none

1402

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Sample Output
show interfaces lsi extensive
user@host> show interfaces lsi extensive
Physical interface: lsi
Logical interface lsi.84934656 (Index 363) (SNMP ifIndex 586) (Generation 194)
Flags: Up Point-To-Point SNMP-Traps 0x4000000 Encapsulation: LSI-NULL
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol vpls, MTU: Unlimited, Generation: 279, Route table: 10
Logical interface lsi.84934657 (Index 366) (SNMP ifIndex 589) (Generation 197)
Flags: Up Point-To-Point SNMP-Traps 0x4000000 Encapsulation: LSI-NULL
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 bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol vpls, MTU: Unlimited, Generation: 282, Route table: 10

Copyright 2014, Juniper Networks, Inc.

1403

Interfaces Fundamentals for Routing Devices

show interfaces media

Syntax
Release Information

Description

show interfaces media

Command introduced before Junos OS Release 7.4.

Command introduced on PTX Series Packet Transport Routers for Junos OS Release
12.1.
Display media-specific information about all configured network interfaces.

NOTE: show interfaces media lists details for all interfaces, whereas show
interfaces media interface-name lists details only for the specified interface.

Options
Additional Information

Required Privilege
Level
List of Sample Output

Output Fields

This command has no options.

Output from both the show interfaces interface-name detail and the show interfaces
interface-name extensive commands includes all the information displayed in the output
from the show interfaces media command.
view

show interfaces media (SONET/SDH) on page 1404

show interfaces media (MX Series Routers) on page 1405
show interfaces media (PTX Series Packet Transport Routers) on page 1405
The output from the show interfaces media command includes fields that display interface
media-specific information. These fields are also included in the show interfaces
interface-name command for each particular interface type, and the information provided
in the fields is unique to each interface type.
One field unique to the show interfaces media command is interface-type errors (for
example, SONET errors). This field appears for channelized E3, channelized T3, channelized
OC, E1, E3, SONET, T1, and T3 interfaces. The information provided in this output field is
also provided in the output from the show interfaces interface-name command. (For
example, for SONET interfaces, these fields are SONET section, SONET line, and SONET
path). For a description of errors, see the chapter with the particular interface type in
which you are interested.

Sample Output
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):
user@host> show interfaces media so-4/1/2

1404

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

Physical interface: so-4/1/2, Enabled, Physical link is Up

Interface index: 168, SNMP ifIndex: 495
Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC48,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
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
CoS queues
: 8 supported
Last flapped
: 2005-06-15 12:14:59 PDT (04:31:29 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
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 media (MX Series Routers)

user@host>show interfaces media xe-0/0/0
Physical interface: xe-0/0/0, Enabled, Physical link is Up
Interface index: 145, SNMP ifIndex: 592
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, BPDU Error:
None,
Loopback: None, Source filtering: Disabled, Flow control: Enabled
Pad to minimum frame size: Enabled
Device flags
: Present Running
Interface flags: Hardware-Down SNMP-Traps Internal: 0x0
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Current address: 08:81:f4:82:a3:f0, Hardware address: 08:81:f4:82:a3:f0
Last flapped
: 2013-10-26 03:20:40 test (1w6d 00:19 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Active alarms : LINK
Active defects : LINK
PCS statistics
Seconds
Bit errors
78
Errored blocks
78
MAC statistics:
Input bytes: 0, Input packets: 0, Output bytes: 0, Output packets: 0
Filter statistics:
Filtered packets: 0, Padded packets: 0, Output packet errors: 0
Interface transmit statistics: Disabled

show interfaces media (PTX Series Packet Transport Routers)

user@host> show interfaces media em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 0
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex

Copyright 2014, Juniper Networks, Inc.

1405

Interfaces Fundamentals for Routing Devices

Current address: 00:80:f9:25:00:1b, Hardware address: 00:80:f9:25:00:1b

Last flapped
: Never
Input packets : 215151
Output packets: 72

1406

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

show interfaces terse

Syntax
Release Information

Description
Options
Additional Information

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

show interfaces terse

Command introduced before Junos OS Release 7.4.

Command introduced on PTX Series Packet Transport Routers for Junos OS Release
12.1.
Display summary information about interfaces.
This command has no options.
Interfaces are always displayed in numerical order, from the lowest to the highest FPC
slot number. Within that slot, the lowest PIC slot is shown first. On an individual PIC, the
lowest port number is always first.
view

Examples: Configuring Logical System Interfaces

show interfaces terse on page 1408

show interfaces terse (TX Matrix Plus Router) on page 1408
show interfaces terse (PTX Series Packet Transport Routers) on page 1409
Table 76 on page 1407 lists the output fields for the show interfaces terse command. Output
fields are listed in the approximate order in which they appear.

Table 76: show interfaces terse Output Fields

Field Name

Field Description

Interface

Interface name.

Admin

Whether the interface is turned on (up) or off (down).

Link

Link state: up or down.

Proto

Protocol family configured on the logical interface. A logical interface

on a router that supports Ethernet OAM always shows the
multiservice protocol.

Local

Local IP address of the logical interface.

Remote

Remote IP address of the logical interface.

Copyright 2014, Juniper Networks, Inc.

1407

Interfaces Fundamentals for Routing Devices

Sample Output
show interfaces terse
user@host> show interfaces terse
Interface
Admin
t1-0/1/0:0
up
t1-0/1/0:0.0
up
t1-0/1/0:1
up
t1-0/1/0:2
up
t1-0/1/0:3
up
at-1/0/0
up
at-1/0/1
up
dsc
up
fxp0
up
fxp0.0
up
fxp1
up
fxp1.0
up

Link
up
up
up
up
up
up
up
up
up
up
up
up

gre
ipip
lo0
lo0.0

up
up
up
up

lo0.16385
lsi
mtun

Proto

Local

Remote

inet

192.168.220.18/30

inet

192.168.71.249/21

inet
tnp

10.0.0.4/8
4

up
up
up
up

inet

10.0.1.4
127.0.0.1

up

up

inet

up
up

up
up

--> 0/0
--> 0/0

show interfaces terse (TX Matrix Plus Router)

user@host> show interfaces terse
Interface
xe-0/0/0
xe-0/0/1
xe-0/0/2
xe-0/0/3
xe-6/0/0
xe-6/0/1
xe-6/0/2
xe-6/0/3
xe-6/1/0
xe-6/1/1
xe-6/1/2
xe-6/1/3
so-0/0/0
so-0/0/0.0
ge-1/3/0.0
ge-7/0/0
ge-7/0/0.0
ge-7/0/0.1
ge-7/0/0.2
ge-7/0/0.3
ge-7/0/0.4
ge-7/0/0.5
...
em0
em0.0
gre

1408

Admin
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up

Link
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up

up
up
up

up
up
up

Proto

Local

Remote

inet
inet

1.1.1.1/30
--> 0/0

inet
inet
inet
inet
inet
inet

2.15.1.1/30
2.15.1.5/30
2.15.1.9/30
2.15.1.13/30
2.15.1.17/30
2.15.1.21/30

inet

192.168.178.11/25

Copyright 2014, Juniper Networks, Inc.

Chapter 14: Interface Operational Commands

ipip
ixgbe0
ixgbe0.0

up
up
up

up
up
up

inet
inet6
tnp

ixgbe1
ixgbe1.0

up
up

up
up

inet
inet6
tnp

10.34.0.4/8
162.0.0.4/2
fe80::200:ff:fe22:4/64
fec0::a:22:0:4/64
0x22000004
10.34.0.4/8
162.0.0.4/2
fe80::200:1ff:fe22:4/64
fec0::a:22:0:4/64
0x22000004

show interfaces terse (PTX Series Packet Transport Routers)

user@host> show interfaces em0 terse
Interface
Admin Link Proto
em0
up
up
em0.0
up
up
inet

Copyright 2014, Juniper Networks, Inc.

Local

Remote

192.168.3.30/24

1409

Interfaces Fundamentals for Routing Devices

1410

Copyright 2014, Juniper Networks, Inc.

CHAPTER 15

ANCP Operational Commands

clear ancp neighbor

clear ancp statistics

clear ancp subscriber

request ancp oam interface

request ancp oam neighbor

show ancp cos

show ancp neighbor

show ancp statistics

show ancp subscriber

show ancp summary

show ancp summary neighbor

show ancp summary subscriber

Copyright 2014, Juniper Networks, Inc.

1411

Interfaces Fundamentals for Routing Devices

clear ancp neighbor

Syntax

Release Information
Description

Options

clear ancp neighbor

<ip-address ip-address>
<system-name mac-address>

Command introduced in Junos OS Release 9.4.

Clear the ANCP agent connection with all ANCP neighbors or with the specified ANCP
neighbor. This command deletes information for subscribers associated with the neighbor,
causing the adjusted traffic rates to revert to the configured rate for the subscriber
interfaces. The neighbor remains configured (its administrative state is enabled) and can
reestablish adjacencies.
noneClear all ANCP neighbors.
ip-address ip-address(Optional) Clear the ANCP neighbor specified by the IP address.
system-name mac-address(Optional) Clear the ANCP neighbor specified by the MAC

address.
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

clear

show ancp neighbor on page 1425

clear ancp neighbor on page 1412

show ancp neighbor on page 1412
When you enter this command, you are provided no feedback on the status of your
request. You can enter the show ancp neighbor command before and after clearing the
ANCP neighbors to verify the clear operation.

Sample Output
clear ancp neighbor
user@host> clear ancp neighbor

show ancp neighbor

The following sample output displays the connections with ANCP neighbors before and
after the clear ancp neighbor command was issued.
user@host> show ancp neighbor

1412

IP Address

MAC Address

10.10.10.2
12.12.12.2
13.13.13.2

ba:ad:be:ef:10:10
ba:ad:be:ef:10:12
ba:ad:be:ef:10:13

State
Established
Established
Established

Subscriber
Count
5
5
5

Capabilities
Topo
Topo
Topo

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

14.14.14.2

ba:ad:be:ef:10:14

Established

Topo

user@host> clear ancp neighbor ip-address 10.10.10.2

user@host> show ancp neighbor
IP Address

MAC Address

12.12.12.2
13.13.13.2
14.14.14.2

ba:ad:be:ef:10:12
ba:ad:be:ef:10:13
ba:ad:be:ef:10:14

Copyright 2014, Juniper Networks, Inc.

State
Established
Established
Established

Subscriber
Count
5
5
5

Capabilities
Topo
Topo
Topo

1413

Interfaces Fundamentals for Routing Devices

clear ancp statistics

Syntax

Release Information
Description

Options

clear ancp statistics

<ip-address ip-address>
<system-name mac-address>

Command introduced in Junos OS Release 13.3.

Clear current statistics accumulated by the ANCP agent for all ANCP neighbors or the
specified neighbor.
noneClear all ANCP statistics.
ip-address ip-address(Optional) Clear statistics for the ANCP neighbor specified by the

IP address.
system-name mac-address(Optional) Clear statistics for the ANCP neighbor specified

by the MAC address.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

clear

show ancp neighbor on page 1425

clear ancp statistics on page 1414

show ancp neighbor on page 1414
When you enter this command, you are provided no feedback on the status of your
request. You can enter the show ancp neighbor command before and after clearing the
ANCP neighbor statistics to verify the clear operation.

Sample Output
clear ancp statistics
user@host> clear ancp statistics

show ancp neighbor

The following sample output displays statistics for an ANCP neighbor before and after
the clear ancp statistics command was issued.
user@host> show ancp neighbor ip-address 192.168.10.1 detail
Neighbor Information
IP Address
: 192.168.10.1
System Name
: 00:00:64:1b:01:02
Up Time
: 38
TCP Port
: 64959
State
: Established
Subscriber Count
: 7
Capabilities
: Topology Discovery
System Instance
: 11

1414

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

Peer Instance
Adjacency Timer (in 100ms)
Peer Adjacency Timer (in 100ms)
Partition Type
Partition Flag
Partition Identifier
Dead Timer
Received Syn Count
Received Synack Count
Received Rstack Count
Received Ack Count
Received Port Up Count
Received Port Down Count
Received Other Count
Sent Syn Count
Sent Synack Count
Sent Rstack Count
Sent Ack Count
Max Discovery Limit Exceed Count

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

1
50
100
0
1
0
22
47
48
2
12
8
2
0
48
47
1
12
0

user@host> clear ancp statistics ip-address 192.168.10.1

user@host> show ancp neighbor ip-address 192.168.10.1 detail
Neighbor Information
IP Address
: 192.168.10.1
System Name
: 00:00:64:1b:01:02
Up Time
: 38
TCP Port
: 64959
State
: Established
Subscriber Count
: 7
Capabilities
: Topology Discovery
System Instance
: 11
Peer Instance
: 1
Adjacency Timer (in 100ms)
: 50
Peer Adjacency Timer (in 100ms)
: 100
Partition Type
: 0
Partition Flag
: 1
Partition Identifier
: 0
Dead Timer
: 22
Received Syn Count
: 0
Received Synack Count
: 0
Received Rstack Count
: 0
Received Ack Count
: 0
Received Port Up Count
: 0
Received Port Down Count
: 0
Received Other Count
: 0
Sent Syn Count
: 0
Sent Synack Count
: 0
Sent Rstack Count
: 0
Sent Ack Count
: 0
Max Discovery Limit Exceed Count
: 0

Copyright 2014, Juniper Networks, Inc.

1415

Interfaces Fundamentals for Routing Devices

clear ancp subscriber

Syntax

Release Information
Description

Options

clear ancp subscriber

<identifier identifier-string>
<ip-address ip-address>
system-name mac-address>

Command introduced in Junos OS Release 11.4.

Clear the ANCP agent connection with all ANCP subscribers or with the specified ANCP
subscriber. This command deletes information for the subscribers, causing the adjusted
traffic rate to revert to the configured rate for the subscriber interface, but otherwise has
no affect on ANCP neighbors.
noneClear all ANCP subscribers.
identifier identifier-string(Optional) Clear the ANCP subscriber identified by the access

loop ID.
ip-address ip-address(Optional) Clear all ANCP subscribers on the neighbor specified

by the IP address.
system-name mac-address(Optional) Clear all ANCP subscribers on the neighbor

specified by the MAC address.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

clear

show ancp subscriber on page 1438

show ancp subscriber brief on page 1416

clear ancp subscriber on page 1417
When you enter this command, you are provided no feedback on the status of your
request. You can enter the show ancp subscriber command before and after clearing the
ANCP neighbors to verify the clear operation.

Sample Output
show ancp subscriber brief
user@host> show ancp subscriber brief
Loop Identifier
Type
Interface

Rate
Kbps
64

Neighbor

port-1-10

VDSL2

set-ge-10410

10.10.10.2

port-1-11

VDSL2

set-ge-10411

64

11.11.11.2

port-2-10
port-2-10
port-2-11

VDSL2
VDSL2
VDSL2

ge-1/0/4.12
ge-1/0/4.12
ge-1/0/4.13

64
64
64

10.12.12.2
10.12.12.3
10.13.13.2

user@host> clear ancp subscriber identifier port-2-10

1416

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

user@host> show ancp subscriber brief

Loop Identifier
Type
Interface

Rate
Kbps
64

Neighbor

port-1-10

VDSL2

set-ge-10410

10.10.10.2

port-1-11

VDSL2

set-ge-10411

64

11.11.11.2

port-2-11

VDSL2

ge-1/0/4.13

64

10.13.13.2

clear ancp subscriber

user@host> clear ancp subscriber

Copyright 2014, Juniper Networks, Inc.

1417

Interfaces Fundamentals for Routing Devices

request ancp oam interface

Syntax

Release Information
Description

Options

request ancp oam interface

(interface-name | interface-set set-name)
<count count>
<timeout duration>

Command introduced in Junos OS Release 11.4.

Trigger the access node to run a loopback test on the local loop between the access
node and the customer premises equipment. You must specify either an ANCP interface
or an ANCP interface set. The access node responds to the NAS with the results of the
test.
interface-nameName of the ANCP interface on whose local loop the loopback test is

run.
interface-set set-nameName of the ANCP interface set on whose local loop the loopback

test is run.
count count(Optional) Number of times a loopback message is sent on the local loop.

Range: 1 through 32. Default: 1.

timeout duration(Optional) Period of time in seconds that the NAS waits for a response

to the OAM request.

Range: 0 through 255. Default: 5.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

Triggering ANCP OAM to Test the Local Loop

request ancp oam interface on page 1418

When you enter this command, you are provided feedback on the status of your request,
including the result of the test, the response code, and the response string returned with
the OAM response in the event of failure, an error code is displayed.

Sample Output
request ancp oam interface
user@host> request ancp oam interface ge-1/0/4.12 count 5 timeout 40
request succeeded
0x503 : DSL line status showtime
DEFAULT RESPONSE

1418

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

request ancp oam neighbor

Syntax

Release Information

request ancp oam neighbor

(ip-address ip-address | system-name neighbor-name)
subscriber identifier-string
<count count>
<timeout duration>

Command introduced in Junos OS Release 11.4.

Description

Trigger the access node to run a loopback test on the local loop between the access
node and the customer premises equipment. You must specify both the access node
and the subscriber. The access node responds to the NAS with the results of the test.

Options

ip-address ip-addressIP address that specifies the access node on whose local loop

the loopback test is run.

system-name neighbor-nameSystem name that specifies the access node on whose

local loop the loopback test is run.

subscriber identifier-stringAccess identifier that specifies the subscriber on whose local

loop the loopback test is run.

count count(Optional) Number of times a loopback message is sent on the local loop.

Range: 1 through 32. Default: 1.

timeout duration(Optional) Period of time in seconds that the NAS waits for a response

to the OAM request.

Range: 0 through 255. Default: 5.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

Triggering ANCP OAM to Test the Local Loop

request ancp oam subscriber on page 1419

When you enter this command, you are provided feedback on the status of your request,
including the result of the test, the response code, and the response string returned with
the OAM response in the event of failure, an error code is displayed.

Sample Output
request ancp oam subscriber
user@host> request ancp oam neighbor 10.10.10.1 subscriber dslam port-1-11
request succeeded
0x503 : DSL line status showtime
DEFAULT RESPONSE

Copyright 2014, Juniper Networks, Inc.

1419

Interfaces Fundamentals for Routing Devices

show ancp cos

Syntax

Release Information
Description
Options

show ancp cos

identifier
<last-update>
<pending-update>

Command introduced in Junos OS Release 9.4.

Display information about the CoS state for subscriber traffic.
identifier identifier(Optional) Display information about the local loops for the specified

access identifier.
last-update(Optional) Display the most recently updated CoS information.
pending-update(Optional) Display the pending update of CoS information.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show ancp neighbor on page 1425

show ancp statistics on page 1433

show ancp subscriber on page 1438

show ancp cos on page 1422

show ancp cos last-update on page 1423
show ancp cos pending-update on page 1423
Table 77 on page 1420 lists the output fields for the show ancp cos command. Output fields
are listed in the approximate order in which they appear.

Table 77: show ancp cos Output Fields

Field Name

Field Description

Per-DSL CoS
adjustment

Adjustment values applied by the ANCP agent to the actual downstream rates
and frame overhead for frame-mode DSL types. The agent then reports the
adjusted rates to CoS to establish a shaping rate for the CoS node that
corresponds to the subscriber access line.

QoS Adjust Flag

State of QoS adjust:

TRUEThe ANCP agent is enabled to adjust the actual downstream data

rates and frame overhead and report the adjusted values to CoS.

SDSL overhead
adjusted

1420

FALSEThe ANCP agent is not enabled to adjust and report values to CoS.

Percentage by which the actual SDSL downstream rate is adjusted before

reporting it to CoS.

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

Table 77: show ancp cos Output Fields (continued)

Field Name

Field Description

SDSL bytes

Number of bytes by which the actual SDSL downstream frame overhead is

adjusted before reporting it to CoS.

VDSL overhead
adjusted

Percentage by which the actual VDSL downstream rate is adjusted before

reporting it to CoS.

VDSL bytes

Number of bytes by which the actual VDSL downstream frame overhead is

adjusted before reporting it to CoS.

VDSL2 overhead
adjusted

Percentage by which the actual VDSL2 downstream rate is adjusted before

reporting it to CoS.

VDSL2 bytes

Number of bytes by which the actual VDSL2 downstream frame overhead is

adjusted before reporting it to CoS.

Per-DSL
adjustment for
reporting

Adjustment values applied by the ANCP agent to the actual downstream rates
for individual DSL types to account for traffic overhead. The agent then reports
the adjusted rates to AAA.

ADSL adjustment
factor

Percentage by which the actual ADSL downstream rate is adjusted before

reporting it to AAA.

ADSL2 adjustment
factor

Percentage by which the actual ADSL2 downstream rate is adjusted before

reporting it to AAA.

ADSL2+
adjustment factor

Percentage by which the actual ADSL2+ downstream rate is adjusted before

reporting it to AAA.

VDSL adjustment
factor

Percentage by which the actual VDSL downstream rate is adjusted before

reporting it to AAA.

VDSL2 adjustment
factor

Percentage by which the actual VDSL2 downstream rate is adjusted before

reporting it to AAA.

SDSL adjustment
factor

Percentage by which the actual SDSL downstream rate is adjusted before

reporting it to AAA.

Keepalive Timer

Interval between the keepalive messages that the ANCP agent sends to CoS.

Cos State

State of the interaction between the ANCP agent and CoS:

Connect Time

Copyright 2014, Juniper Networks, Inc.

ANCPD_COS_CONNECT_NEEDED

ANCPD_COS_CONNECT_PENDING

ANCPD_COS_CONNECT_DONE

ANCPD_COS_SESSION_SENT

ANCPD_COS_WRITE_READY

Time at which the ANCP agent connected to CoS; useful for debugging.

1421

Interfaces Fundamentals for Routing Devices

Table 77: show ancp cos Output Fields (continued)

Field Name

Field Description

Session Time

Time at which the ANCP agent sent a session connect message to CoS; useful
for debugging.

Routing Instance
Time

Time at which the ANCP agent sent the routing instance to CoS; useful for
debugging.

Keepalive Time

Time at which the last keepalive message was sent.

Update Time

Time at which the shaping rate was last updated.

Type

Subscriber access type: ifl indicates that a single VLAN carries subscriber traffic
and iflset indicates that a set of VLANs carries subscriber traffic.

Name

System-wide name of the particular subscriber access.

Index

Access identifier.

Pending Update

Actual downstream data rate to be applied next to this local loop, in Kbps.

Last Update

Adjusted downstream data rate last reported to CoS by the ANCP agent for
this local loop, in Kbps.

Sample Output
show ancp cos
user@host> show ancp cos
Per-DSL CoS adjustment:
Qos Adjust Flag:
VDSL overhead adjusted:
VDSL bytes:
VDSL2 overhead adjusted:
VDSL2 bytes:
SDSL overhead adjusted:
SDSL bytes:

TRUE
90
20
95
-20
85
30

Per-DSL adjustment for reporting:

ADSL adjustment factor: 100
ADSL2 adjustment factor: 100
ADSL2+ adjustment factor:100
VDSL adjustment factor: 100
VDSL2 adjustment factor: 100
SDSL adjustment factor: 100
Keepalive Timer:
State:
Connect Time:
Session Time:
Routing Instance Time:
Keepalive Time:
Update Time:

1422

45 secs
WRITE_READY
Fri May 2 12:08:49
Fri May 2 12:18:52
Fri May 2 12:18:53
Fri May 2 13:44:14
Fri May 2 13:02:55

2014
2014
2014
2014
2014

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

Type
iflset

Name
Index
Pending Update
aci-1004-ge-2/0/0.1073741834 4 None

Last Update
36000 Kbps

show ancp cos last-update

Per-DSL CoS adjustment:
Qos Adjust Flag:
VDSL overhead adjusted:
VDSL bytes:
VDSL2 overhead adjusted:
VDSL2 bytes:
SDSL overhead adjusted:
SDSL bytes:

TRUE
90
20
95
-20
85
30

Per-DSL adjustment for reporting:

ADSL adjustment factor: 100
ADSL2 adjustment factor: 100
ADSL2+ adjustment factor:100
VDSL adjustment factor: 100
VDSL2 adjustment factor: 100
SDSL adjustment factor: 100
Keepalive Timer:
State:
Connect Time:
Session Time:
Routing Instance Time:
Keepalive Time:
Update Time:

Type
iflset

45 secs
WRITE_READY
Fri May 2 12:08:49
Fri May 2 12:18:52
Fri May 2 12:18:53
Fri May 2 13:44:34
Fri May 2 13:02:55

2014
2014
2014
2014
2014

Name
Index
Pending Update
aci-1004-ge-2/0/0.1073741834 4 None

Last Update
36000 Kbps

show ancp cos pending-update

user@host> show ancp cos pending-update
Per-DSL CoS adjustment:
Qos Adjust Flag:
TRUE
VDSL overhead adjusted: 90
VDSL bytes:
20
VDSL2 overhead adjusted: 95
VDSL2 bytes:
-20
SDSL overhead adjusted: 85
SDSL bytes:
30
Per-DSL adjustment for reporting:
ADSL adjustment factor: 100
ADSL2 adjustment factor: 100
ADSL2+ adjustment factor:100
VDSL adjustment factor: 100
VDSL2 adjustment factor: 100
SDSL adjustment factor: 100
Keepalive Timer:
State:
Connect Time:
Session Time:
Routing Instance Time:

Copyright 2014, Juniper Networks, Inc.

45 secs
WRITE_READY
Fri May 2 12:08:49 2014
Fri May 2 12:18:52 2014
Fri May 2 12:18:53 2014

1423

Interfaces Fundamentals for Routing Devices

Keepalive Time:
Update Time:

1424

Fri May
Fri May

2 13:44:34 2014
2 13:02:55 2014

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

show ancp neighbor

Syntax

Release Information
Description

Options

show ancp neighbor

<brief | detail>
<ip-address ip-address>
<system-name mac-address>

Command introduced in Junos OS Release 9.4.

Display information about all ANCP neighbors or the specified ANCP neighbor, regardless
of operational state.
brief | detail(Optional) Display the specified level of detail.
ip-address ip-address(Optional) IP address of the ANCP neighbor (access node).
system-name mac-address(Optional) MAC address of the ANCP neighbor (access

node).
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show ancp cos on page 1420

show ancp subscriber on page 1438

show ancp neighbor on page 1428

show ancp neighbor detail on page 1428
show ancp neighbor ip-address on page 1430
show ancp neighbor system-name on page 1431
Table 78 on page 1425 lists the output fields for the show ancp neighbor command. Output
fields are listed in the approximate order in which they appear.

Table 78: show ancp neighbor Output Fields

Field Name

Field Description

Level of Outp

Version

Version of the ANCP implementation:

brief detail non

0x31General Switch Management Protocol (GSMP) version 3, sub-version

1; ANCP version before RFC 6320, Protocol for Access Node Control Mechanism
in Broadband Networks.

0x32ANCP version 1, defined in RFC 6320, Protocol for Access Node Control

Mechanism in Broadband Networks.

IP Address

IP address of the ANCP neighbor.

brief detail non

PartId

Number that associates the ANCP message with a specific partition.

brief none

Copyright 2014, Juniper Networks, Inc.

1425

Interfaces Fundamentals for Routing Devices

Table 78: show ancp neighbor Output Fields (continued)

Field Name

Field Description

Level of Outp

State

Operational state of the ANCP adjacency:

All levels

ConfiguredThe neighbor has been configured, but has never been in the
Established state. An asterisk (*) is prefixed to the neighbor entry for this
state.

EstablishingAdjacency negotiations are in progress for the neighbor. An

asterisk (*) is prefixed to the neighbor entry for this state. This state is rarely
seen because the adjacency is established so quickly.

EstablishedAdjacency negotiations have succeeded for the neighbor and

an ANCP session has been established.

Time

Not EstblshedNot Established; adjacency negotiations are ready to begin.

Indicates that this neighbor previously had been in the Established state; that
is, it has lost a previously established adjacency. An asterisk (*) is prefixed
to the neighbor entry for this state.

How long the adjacency has been up in one of the following formats:

nwndnhnumber of weeks, days, and hours

nd hh:mm:ssnumber of days, hours, minutes, and seconds

brief detail non

Subscriber Count

Number of subscribers associated with the ANCP neighbor (access local loop).

brief none

Capabilities

Negotiated ANCP capability:

All levels

TopoTopology discovery.

OAMPerformance of local Operations Administration Maintenance (OAM)

procedures on an access loop controlled by the router.

System Name

MAC address of the ANCP neighbor.

detail

TCP Port

TCP port on which ANCP messages are exchanged.

detail

System Instance

Number identifying the ANCP link instance from the edge devices perspective.

detail

Peer Instance

Number identifying the ANCP instance from the access nodes perspective. This
number is unique and changes when the node or link comes back up after going
down.

detail

Timer

Adjacency timer value advertised by the ANCP peer in 100 ms increments; the
interval between ANCP ACK messages. This value remains constant for the
duration of an ANCP session.

detail

Partition Type

Number that identifies whether partitions are used and how the ID is negotiated:

detail

Partition Flag

1426

0No partition.

1Fixed partition requested.

2Fixed partition assigned.

Number that specifies the type of partition requested: 1 (new adjacency) or 2

(recovered adjacency).

Copyright 2014, Juniper Networks, Inc.

detail

Chapter 15: ANCP Operational Commands

Table 78: show ancp neighbor Output Fields (continued)

Field Name

Field Description

Level of Outp

Partition Identifier

Number that associates the ANCP message with a specific partition.

detail

Partition
Adjacencies

Number of adjacencies that share the partition.

detail

Dead Timer

Remaining period that the edge device waits for adjacency packets from a
neighbor before declaring the neighbor to be down. The maximum dead time
value is three times the configured adjacency timer value. This field displays
the current value based on the time that the last adjacency packet was received.

detail

Received Syn Count

Number of synchronization messages received from neighbors to maintain

adjacencies.

detail

Received Synack
Count

Number of synchronization acknowledgment messages received from neighbors

in response to the nodes synchronization messages.

detail

Received Rstack
Count

Number of messages received from neighbors indicating that the link to the
neighbor needs to be reset.

detail

Received Ack Count

Number of acknowledgment messages periodically received from neighbors

after an adjacency has been established.

detail

Received Port Up
Count

Number of status messages received from neighbors indicating that a port has
transitioned to the up state.

detail

Received Port
Down Count

Number of status messages received from neighbors indicating that a port has
transitioned to the down state.

detail

Received Generic
Resp Count

Number of generic response messages received from neighbors.

detail

Received Adjacency
Update Count

Number of adjacency update messages received from neighbors.

detail

Received OAM
Count

Number of OAM responses received from neighbors in reply to request

commands.

detail

Received Other
Count

Number of all other ANCP message packets received from neighbors that do
not fit into one of the other categories.

detail

Sent Syn Count

Number of synchronization messages sent to neighbors to maintain adjacencies.

detail

Sent Synack Count

Number of synchronization acknowledgment messages sent to neighbors in

response to the their synchronization messages.

detail

Sent Rstack Count

Number of messages sent to neighbors indicating that the link to the neighbor
needs to be reset.

detail

Sent Ack Count

Number of acknowledgment messages periodically sent to neighbors after an

adjacency has been established.

detail

Copyright 2014, Juniper Networks, Inc.

1427

Interfaces Fundamentals for Routing Devices

Table 78: show ancp neighbor Output Fields (continued)

Field Name

Field Description

Level of Outp

Sent Generic Resp

Count

Number of generic response messages sent to neighbors.

detail

Sent OAM Count

Number of OAM request commands sent to neighbors.

detail

Max Discovery Limit

Exceed Count

Number of times that the maximum number of discovery table entries accepted
from the neighbor has been exceeded.

detail

Result Codes

Number of generic response messages sent to neighbors that include each of

the following result codes:

detail

Invalid Request Message CountA properly formed request message violated

the protocol because of timing (such as a race condition) or direction of

transmission.

Specified Port(s) Down CountOne or more of the specified ports are down

because of a state mismatch between the router and an ANCP control

application.

Out of Resources CountANCP is out of resources, probably not related to

the access lines. This result code is sent only by an access node.

Request Msg Not Implemented Count

Malformed Msg CountMessage is malformed because it was corrupted in

transit or there was an implementation error at either end of the connection.

TLV Missing CountOne or more mandatory TLVs was missing from a request.

Invalid TLV Contents CountThe contents of one or more TLVs in the request

do not match its required specification.

Non-Existent Port(s) CountOne or more of the ports specified in a request

do not exist, possibly because of a configuration mismatch between the

access node and the router or AAA.

Sample Output
show ancp neighbor
user@host> show ancp neighbor
Version IP Address
PartID
Capabilities

State

Time

Subscriber

0x31
0x31
* 0x0
* 0x0
* 0x0

Established
Not Estblshd
Establishing
Configured
Configured

11:24
2:45
0
0
0

Count
2
2
0
0
0

10.0.1.3
10.0.1.5
100.0.0.2
192.0.1.0
192.0.22.1

0
0
0
0
0

Topo
Topo

show ancp neighbor detail

user@host> show ancp neighbor detail
Neighbor Information
Version
: 0x31
IP Address
: 192.85.1.5
System Name
: 00:10:94:00:00:01
Up Time
: 26
TCP Port
: 32666

1428

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

State
:
Subscriber Count
:
Capabilities
:
System Instance
:
Peer Instance
:
Adjacency Timer (in 100ms)
:
Peer Adjacency Timer (in 100ms) :
Partition Type
:
Partition Flag
:
Partition Identifier
:
Partition Adjacencies
:
Dead Timer
:
Received Syn Count
:
Received Synack Count
:
Received Rstack Count
:
Received Ack Count
:
Received Port Up Count
:
Received Port Down Count
:
Received Generic Resp Count
:
Received Adjacency Update Count :
Received OAM Count
:
Received Other Count
:
Sent Syn Count
:
Sent Synack Count
:
Sent Rstack Count
:
Sent Ack Count
:
Sent Generic Resp Count
:
Sent OAM Count
:
Max Discovery Limit Exceed Count :
Result Codes:
Invalid Request Message Count
:
Specified Port(s) Down Count
:
Out of Resources Count
:
Request Msg Not Implemented Count:
Malformed Msg Count
:
TLV Missing Count
:
Invalid TLV Contents Count
:
Non-Existent Port(s) Count
:

Established
4
Topo
2
20
100
100
0
1
0
0
23
1
1
0
4
10
0
0
0
0
0
1
2
0
3
0
0
0
Received
0
0
0
0
0
0
0
0

Sent
0
0
0
0
0
0
0
0

Version
: 0x32
IP Address
: 192.168.9.1
System Name
: 00:00:64:1c:01:02
Up Time
: 36
TCP Port
: 61408
State
: Not Established
Subscriber Count
: 1
Capabilities
: Topology Discovery
System Instance
: 12
Peer Instance
: 1
Adjacency Timer (in 100ms)
: 50
Peer Adjacency Timer (in 100ms) : 100
Partition Type
: 0
Partition Flag
: 1
Partition Identifier
: 0
Partition Adjacencies
: 0
Dead Timer
: 23
Received Syn Count
: 24
Received Synack Count
: 20
Received Rstack Count
: 2
Received Ack Count
: 9

Copyright 2014, Juniper Networks, Inc.

1429

Interfaces Fundamentals for Routing Devices

Received Port Up Count

:
Received Port Down Count
:
Received Generic Resp Count
:
Received Adjacency Update Count :
Received OAM Responses Count
:
Received Other Count
:
Sent Syn Count
:
Sent Synack Count
:
Sent Rstack Count
:
Sent Generic Resp Count
:
Sent Ack Count
:
Sent OAM Requests Count
:
Max Discovery Limit Exceed Count :
Result Codes:
Invalid Request Message Count
:
Specified Port(s) Down Count
:
Out of Resources Count
:
Request Msg Not Implemented Count:
Malformed Msg Count
:
TLV Missing Count
:
Invalid TLV Contents Count
:
Non-Existent Port(s) Count
:

5
0
0
0
2
0
20
24
1
0
9
4
0
Received
0
0
0
0
0
0
0
0

Sent
0
0
0
0
0
0
0
0

show ancp neighbor ip-address

user@host> show ancp neighbor ip-address 192.85.1.5
Neighbor Information
Version
: 0x32
IP Address
: 192.85.1.5
System Name : ba:ad:be:ef:10:10
Up Time
TCP Port
State
Subscriber Count
Capabilities
System Instance
Peer Instance
Adjacency Timer (in 100ms)
Peer Adjacency Timer (in 100ms)
Partition Type
Partition Flag
Partition Identifier
Partition Adjacencies
Dead Timer
Received Syn Count
Received Synack Count
Received Rstack Count
Received Ack Count
Received Port Up Count
Received Port Down Count
Received Generic Resp Count
Received Adjacency Update Count
Received OAM Count
Received Other Count
Sent Syn Count
Sent Synack Count
Sent Rstack Count
Sent Ack Count
Sent Generic Resp Count
Sent OAM Count

1430

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

26
32666
Established
4
Topo
2
20
100
100
0
1
0
0
23
1
1
0
4
10
0
0
0
0
0
1
2
0
3
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

Max Discovery Limit Exceed Count :

Result Codes:
Invalid Request Message Count
:
Specified Port(s) Down Count
:
Out of Resources Count
:
Request Msg Not Implemented Count:
Malformed Msg Count
:
TLV Missing Count
:
Invalid TLV Contents Count
:
Non-Existent Port(s) Count
:

0
Received
0
0
0
0
0
0
0
0

Sent
0
0
0
0
0
0
0
0

show ancp neighbor system-name

user@host> show ancp neighbor ba:ad:be:ef:10:10 detail
Neighbor Information
Version
: 0x31
IP Address
: 10.100.0.1
System Name
: 00:00:64:1b:01:02
Up Time
: 19
TCP Port
: 1028
State
: Established
Subscriber Count
: 2
Capabilities
: Topology Discovery, OAM
System Instance
: 1
Peer Instance
: 10
Adjacency Timer (in 100ms)
: 100
Peer Adjacency Timer (in 100ms)
: 250
Partition Type
: 0
Partition Flag
: 1
Partition Identifier
: 0
Partition Adjacencies
: 0
Dead Timer
: 55
Received Syn Count
: 1
Received Synack Count
Received Rstack Count
Received Ack Count
Received Port Up Count
Received Port Down Count
Received Generic Resp Count
Received Adjacency Update Count
Received OAM Responses Count
Received Other Count
Sent Syn Count
Sent Synack Count
Sent Rstack Count
Sent Ack Count
Sent Generic Resp Count
Sent OAM Requests Count
Max Discovery Limit Exceed Count
Result Codes:
Invalid Request Message Count
Specified Port(s) Down Count
Out of Resources Count
Request Msg Not Implemented Count
Malformed Msg Count
TLV Missing Count
Invalid TLV Contents Count
Non-Existent Port(s) Count

Copyright 2014, Juniper Networks, Inc.

: 1
: 0
: 1
: 34
: 0
: 0
: 0
: 2
: 0
: 1
: 1
: 0
: 3
: 0
: 4
: 3
Received
: 0
: 0
: 0
: 0
: 0
: 0
: 0
: 0

Sent
0
0
0
0
0
0
0
0

1431

Interfaces Fundamentals for Routing Devices

1432

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

show ancp statistics

Syntax

Release Information
Description
Options

show ancp statistics

<ip-address ip-address>
<system-name mac-address>

Command introduced in Junos OS Release 13.3.

Display statistics for all ANCP neighbors (access nodes) or the specified ANCP neighbor.
noneDisplay statistics for all ANCP neighbors, including global statistics not show for

individual neighbors.
ip-address ip-address(Optional) Display statistics for only the neighbor with the specified

IP address.
system-name mac-address(Optional) Display statistics for only the neighbor with the

specified MAC address.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show ancp cos on page 1420

show ancp neighbor on page 1425

show ancp subscriber on page 1438

show ancp statistics on page 1435

show ancp statistics ip-address on page 1436
show ancp statistics system-name on page 1436
Table 79 on page 1433 lists the output fields for the show ancp statistics command. Output
fields are listed in the approximate order in which they appear.

Table 79: show ancp statistics Output Fields

Field Name

Field Description

Number of
neighbors

Total count of ANCP neighbors.

Number of
subscribers

Total count of ANCP subscribers.

Accept Count

Number of neighbor TCP/IP sessions accepted on listener socket.

Accept Fail Count

Number of neighbor TCP/IP sessions that failed due to one of the following
causes: session already exists, maximum number of ANCP connections
exceeded, creation of session or neighbor failed, or protocol start failed.

Copyright 2014, Juniper Networks, Inc.

1433

Interfaces Fundamentals for Routing Devices

Table 79: show ancp statistics Output Fields (continued)

1434

Field Name

Field Description

No Config Accept
Deny Count

Number of neighbor TCP/IP sessions that failed because the neighbor was not
configured.

Received Syn Count

Number of synchronization messages received from neighbors to maintain

adjacencies.

Received Synack
Count

Number of synchronization acknowledgment messages received from neighbors

in response to the nodes synchronization messages.

Received Rstack
Count

Number of messages received from neighbors indicating that the link to the
neighbor needs to be reset.

Received Ack Count

Number of acknowledgment messages periodically received from neighbors

after an adjacency has been established.

Received Port Up
Count

Number of status messages received from neighbors indicating that a port has
transitioned to the up state.

Received Port
Down Count

Number of status messages received from neighbors indicating that a port has
transitioned to the down state.

Received Generic
Resp Count

Number of generic response messages received from neighbors.

Received Adjacency
Update Count

Number of adjacency update messages received from neighbors.

Received OAM
Count

Number of OAM responses received from neighbors in reply to request

commands.

Received Other
Count

Number of all other ANCP message packets received from neighbors that do
not fit into one of the other categories.

Sent Syn Count

Number of synchronization messages sent to neighbors to maintain adjacencies.

Sent Synack Count

Number of synchronization acknowledgment messages sent to neighbors in

response to the their synchronization messages.

Sent Rstack Count

Number of messages sent to neighbors indicating that the link to the neighbor
needs to be reset.

Sent Ack Count

Number of acknowledgment messages periodically sent to neighbors after an

adjacency has been established.

Sent Generic Resp

Count

Number of generic response messages sent to neighbors.

Sent OAM Count

Number of OAM request commands sent to neighbors.

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

Table 79: show ancp statistics Output Fields (continued)

Field Name

Field Description

Result Codes

Number of generic response messages sent to neighbors that include each of

the following result codes:

Invalid Request Message CountA properly formed request messages violated

the protocol because of timing (such as a race condition) or direction of

transmission.

Specified Port(s) Down CountOne or more of the specified ports are down

because of a state mismatch between the router and an ANCP control

application.

Out of Resources Countthe ANCP agent is out of resources, probably not

related to the access lines. This result code is sent only by an access node.

Request Msg Not Implemented Count

Malformed Msg CountMessage is malformed because it was corrupted in

transit or there was an implementation error at either end of the connection.

TLV Missing CountOne or more mandatory TLVs was missing from a request.

Invalid TLV Contents CountThe contents of one or more TLVs in the request

do not match its required specification.

Non-Existent Port(s) CountOne or more of the ports specified in a request

do not exist, possibly because of a configuration mismatch between the

access node and the router or AAA.

Sample Output
show ancp statistics
user@host> show ancp statistics
Statistics
Number of neighbors
: 4
Number of subscribers
: 6
Accept Count
: 0
Accept Fail Count
: 0
No Config Accept Deny Count
: 0
Received Syn Count
: 2
Received Synack Count
: 1
Received Rstack Count
: 0
Received Ack Count
: 8
Received Port Up Count
: 7
Received Port Down Count
: 0
Received Generic Resp Count
: 0
Received Adjacency Update Count : 0
Received OAM Count
: 0
Received Other Count
: 0
Sent Syn Count
: 1
Sent Synack Count
: 1
Sent Rstack Count
: 0
Sent Ack Count
: 17
Sent Generic Resp Count
: 0
Sent OAM Count
: 4
Result Codes:
Received
Invalid Request Message Count
: 0
Specified Port(s) Down Count
: 0
Out of Resources Count
: 0
Request Msg Not Implemented Count: 0

Copyright 2014, Juniper Networks, Inc.

Sent
0
0
0
0

1435

Interfaces Fundamentals for Routing Devices

Malformed Msg Count

TLV Missing Count
Invalid TLV Contents Count
Non-Existent Port(s) Count

:
:
:
:

0
0
0
0

0
0
0
0

show ancp statistics ip-address

user@host> show ancp statistics ip-address 10.0.0.1
Statistics
Received Syn Count
: 2
Received Synack Count
: 1
Received Rstack Count
: 0
Received Ack Count
: 8
Received Port Up Count
: 7
Received Port Down Count
: 0
Received Generic Resp Count
: 0
Received Adjacency Update Count : 0
Received OAM Count
: 0
Received Other Count
: 0
Sent Syn Count
: 1
Sent Synack Count
: 1
Sent Rstack Count
: 0
Sent Ack Count
: 17
Sent Generic Resp Count
: 0
Sent OAM Count
: 4
Result Codes:
Received
Invalid Request Message Count
: 0
Specified Port(s) Down Count
: 0
Out of Resources Count
: 0
Request Msg Not Implemented Count: 0
Malformed Msg Count
: 0
TLV Missing Count
: 0
Invalid TLV Contents Count
: 0
Non-Existent Port(s) Count
: 0

Sent
0
0
0
0
0
0
0
0

show ancp statistics system-name

user@host> show ancp statistics system-name 00:00:64:1b:01:02
Statistics
Received Syn Count
: 2
Received Synack Count
: 1
Received Rstack Count
: 0
Received Ack Count
: 8
Received Port Up Count
: 7
Received Port Down Count
: 0
Received Generic Resp Count
: 0
Received Adjacency Update Count : 0
Received OAM Count
: 0
Received Other Count
: 0
Sent Syn Count
: 1
Sent Synack Count
: 1
Sent Rstack Count
: 0
Sent Ack Count
: 17
Sent Generic Resp Count
: 0
Sent OAM Count
: 4
Result Codes:
Received
Invalid Request Message Count
: 0
Specified Port(s) Down Count
: 0
Out of Resources Count
: 0

1436

Sent
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

Request Msg Not Implemented Count: 0

Malformed Msg Count
: 0
TLV Missing Count
: 0
Invalid TLV Contents Count
: 0
Non-Existent Port(s) Count
: 0

Copyright 2014, Juniper Networks, Inc.

0
0
0
0
0

1437

Interfaces Fundamentals for Routing Devices

show ancp subscriber

Syntax

Release Information
Description

Options

show ancp subscriber

<brief | detail>
<identifier identifier>
<neighbor ip-address>

Command introduced in Junos OS Release 9.4.

Display information about active subscribers regardless of the subscribers operational
state, for all subscribers (local access loops), the subscriber associated with the access
line specified by an ACI, or the subscriber associated with the specified ANCP neighbor
(access node).
brief | detail(Optional) Display the specified level of detail.
identifier identifier(Optional) Display information about the subscriber associated with

the access line specified by the access identifier.

neighbor ip-address (Optional) Display information about the subscribers connected

to the access node specified by the IP address.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

clear ancp subscriber on page 1416

show ancp cos on page 1420

show ancp neighbor on page 1425

show ancp subscriber on page 1441

show ancp subscriber brief on page 1441
show ancp subscriber detail on page 1441
show ancp subscriber identifier identifier-string detail on page 1442
Table 80 on page 1438 lists the output fields for the show ancp subscriber command. Output
fields are listed in the approximate order in which they appear.

Table 80: show ancp subscriber Output Fields

Field Name

Field Description

Level of Outp

Loop Identifier

Access loop identifier as sent by the access node and configured to map the
subscriber to an interface.

brief none

An asterisk (*) indicates that the information might be stale due to receiving a
Port Down message with a DSL Line State of Idle.
Two asterisks (**) indicate that the neighbor associated with the subscriber
has lost its adjacency. In this case, the DSL Line State might be Established.
DSL Line State

1438

State of the DSL line: Idle, Showtime, or Silent.

Copyright 2014, Juniper Networks, Inc.

brief detail

Chapter 15: ANCP Operational Commands

Table 80: show ancp subscriber Output Fields (continued)

Field Name

Field Description

Level of Outp

Type

Type of digital subscriber line employed by the access node: ADSL1, ADSL2,
ADSL2+, VDSL1, VDSL2, SDSL, or UNKNOWN.

brief none

Interface

Name of the interface set or logical interface.

brief detail non

Rate Kbps

Actual downstream data rate for this local loop.

brief none

Neighbor

IP address of ANCP neighbor (access node).

brief none

Access Loop Circuit

Identifier

Access loop circuit identifier as sent by the access node and configured to map
the subscriber to an interface.

detail

An asterisk (*) indicates that the information might be stale due to receiving a
Port Down message with a DSL Line State of Idle.
Two asterisks (**) indicate that the neighbor associated with the subscriber
has lost its adjacency. In this case, the DSL Line State might be Established.
Neighbor IP
Address

IP address of the ANCP neighbor (access node).

detail

Aggregate Circuit
Identifier Binary

Binary identifier for the VLAN circuit ID.

detail

DSL Type

Type of digital subscriber line employed by the access node: ADSL1, ADSL2,
ADSL2+, VDSL1, VDSL2, SDSL, or UNKNOWN.

detail

DSL Line Data Link

Data link protocol employed on the access loop: AAL5 or Ethernet.

detail

DSL Line
Encapsulation

Encapsulation type on the access loop, for Ethernet only:

detail

DSL Line
Encapsulation
Payload

Interface Type

Copyright 2014, Juniper Networks, Inc.

0NA, type not conveyed

1Untagged Ethernet

2Single-tagged Ethernet

Payload carried across the access loop:

0NA, type not conveyed

1PPPoA LLC

2PPPoA null

3IPoA LLC

4IPoA null

5Ethernet over AAL5 LLC with FCS

6Ethernet over AAL5 LLC without FCS

7Ethernet over AAL5 null with FCS

8Ethernet over AAL5 null without FCS

detail

Type of interface employed for subscriber traffic: ifl for a single VLAN or
interface-set for a configured group of VLANs.

detail

1439

Interfaces Fundamentals for Routing Devices

Table 80: show ancp subscriber Output Fields (continued)

1440

Field Name

Field Description

Level of Outp

Actual Net Data

Upstream

Actual upstream data rate for this local loop, in Kbps.

detail

Actual Net Data

Downstream

Actual downstream data rate for this local loop, in Kbps.

detail

Minimum Net Data

Upstream

Minimum upstream data rate desired by the operator for this local loop, in Kbps.

detail

Minimum Net Data

Downstream

Minimum downstream data rate desired by the operator for this local loop, in
Kbps.

detail

Maximum Net Data

Upstream

Maximum upstream data rate desired by the operator for this local loop, in Kbps.

detail

Maximum Net Data

Downstream

Maximum downstream data rate desired by the operator for this local loop, in
Kbps.

detail

Attainable Net Data

Upstream

Maximum attainable upstream data rate for this local loop, in Kbps.

detail

Attainable Net Data

Downstream

Maximum attainable downstream data rate for this local loop, in Kbps.

detail

Minimum Low
Power Data
Downstream

Minimum downstream data rate desired by the operator for this local loop in
low power state, in Kbps.

detail

Minimum Low
Power Data
Upstream

Minimum upstream data rate desired by the operator for this local loop in low
power state, in Kbps.

detail

Maximum
Interleave Delay
Downstream

Maximum interleaving delay for downstream data, in milliseconds.

detail

Maximum
Interleave Delay
Upstream

Maximum interleaving delay for upstream data, in milliseconds.

detail

Actual Interleave
Delay Downstream

Actual interleaving delay for downstream data, in milliseconds.

detail

Actual Interleave
Delay Upstream

Actual interleaving delay for upstream data, in milliseconds.

detail

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

Sample Output
show ancp subscriber
user@host> show ancp subscriber
Loop Identifier
DSL Line
State
**circuit 101
Idle
**circuit 102
Idle
circuit 301
Showtime
circuit 302
Showtime

Type

Interface

ADSL1
ADSL1
ADSL1
ADSL1

-------------

Rate
Kbps
32
32
32
32

Neighbor
10.0.1.3
10.0.1.3
10.0.1.5
10.0.1.5

show ancp subscriber brief

user@host> show ancp subscriber brief
Loop Identifier

Type

Interface
set-ge-10410

Rate
Kbps
64

port-1-10

VDSL2

port-1-11
port-2-10
port-2-11

Neighbor
10.10.10.2

VDSL2

set-ge-10411

64

11.11.11.2

VDSL2
VDSL2

ge-1/0/4.12
ge-1/0/4.13

64
64

10.12.12.2
10.13.13.2

show ancp subscriber detail

user@host> show ancp subscriber detail
Subscriber Information
* Access Loop Circuit Identifier : circuit 101
Neighbor IP Address
: 10.0.1.3
Aggregate Circuit Identifier Binary : 0/0
DSL Type
: ADSL1
DSL Line State
: Idle
DSL Line Data Link
: Data link 2
DSL Line Encapsulation
: N/A
DSL Line Encapsulation Payload
: N/A
Interface Type
: N/A
Interface
: ---Actual Net Data Upstream
: 32
Actual Net Data Downstream
: 32
Minimum Net Data Upstream
: 0
Minimum Net Data Downstream
: 0
Maximum Net Data Upstream
: 0
Maximum Net Data Downstream
: 0
Attainable Net Data Upstream
: 1024
Attainable Net Data Downstream
: 8192
Minimum Low Power Data Downstream
: 32
Minimum Low Power Data Upstream
: 32
Maximum Interleave Delay Downstream : 20
Maximum Interleave Delay Upstream
: 20
Actual Interleave Delay Downstream
: 20
Actual Interleave Delay Upstream
: 20
* Access Loop Circuit Identifier: circuit 102
Neighbor IP Address
: 10.0.1.3
Aggregate Circuit Identifier Binary : 0/0
DSL Type
: ADSL1
DSL Line State
: Idle
DSL Line Data Link
: Data link 2
DSL Line Encapsulation
: N/A
DSL Line Encapsulation Payload
: N/A

Copyright 2014, Juniper Networks, Inc.

1441

Interfaces Fundamentals for Routing Devices

Interface Type
Interface
Actual Net Data Upstream
Actual Net Data Downstream
Minimum Net Data Upstream
Minimum Net Data Downstream
Maximum Net Data Upstream
Maximum Net Data Downstream
Attainable Net Data Upstream
Attainable Net Data Downstream
Minimum Low Power Data Downstream
Minimum Low Power Data Upstream
Maximum Interleave Delay Downstream
Maximum Interleave Delay Upstream
Actual Interleave Delay Downstream
Actual Interleave Delay Upstream

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

N/A
---32
32
0
0
0
0
1024
8192
32
32
20
20
20
20

...

show ancp subscriber identifier identifier-string detail

user@host> show ancp subscriber identifier port-1-11 detail

Access Loop Identifier : port-1-11

Neighbor IP Address
Aggregate Circuit Identifier Binary
DSL Type
Interface Type
Interface
DSL Line State
Actual Net Data Upstream
Actual Net Data Downstream
DSL Line Data Link
DSL Line Encapsulation
DSL Line Encapsulation Payload
Minimum Net Data Upstream
Minimum Net Data Downstream
Maximum Net Data Upstream
Maximum Net Data Downstream
Attainable Net Data Upstream
Attainable Net Data Downstream
Minimum Low Power Data Downstream
Minimum Low Power Data Upstream
Maximum Interleave Delay Downstream
Maximum Interleave Delay Upstream
Actual Interleave Delay Downstream
Actual Interleave Delay Upstream

1442

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

10.11.11.2
0/0
DSL 0
interface-set
set-ge-10411
Show Time
64
64
AAL5
N/A
N/A
64
64
64
64
64
64
64
64
50
50
50
50

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

show ancp summary

Syntax
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show ancp summary

Command introduced in Junos OS Release 13.1.

Display a summary of the counts and states for all ANCP neighbors and subscribers.
This command has no options.
view

show ancp neighbor on page 1425

show ancp summary neighbor on page 1445

show ancp subscriber on page 1438

show ancp summary subscriber on page 1447

show ancp summary on page 1444

Table 81 on page 1443 lists the output fields for the show ancp summary command. Output
fields are listed in the approximate order in which they appear.

Table 81: show ancp summary Output Fields

Field Name

Field Description

Configured

Number of ANCP neighbors in the Configured state; that is, that have been
configured but never established.

Establishing

Number of ANCP neighbors in the Establishing state; that is, where negotiations
are in progress.

Established

Number of ANCP neighbors in the Established state; that is, where negotiations
have succeeded and the ANCP session has been established.

Not Estblshd

Number of ANCP neighbors in the Not Estblshd state; that is, that have lost a
previously established adjacency and are ready to begin negotiations.

Total

Total number of ANCP neighbors; sum of neighbors in the Configured,

Establishing, Established, and Not Estblshd states.

Showtime

Number of DSL lines in Showtime state.

Idle

Number of DSL lines in Idle state.

Silent

Number of DSL lines in Silent state.

Unknown

Number of DSL lines where the state is not Showtime, Idle, or Silent.

Copyright 2014, Juniper Networks, Inc.

1443

Interfaces Fundamentals for Routing Devices

Table 81: show ancp summary Output Fields (continued)

Field Name

Field Description

Total

Total number of DSL lines (ANCP subscribers); sum of DSL lines in the Showtime,
Idle, Silent, and Unknown states.

Sample Output
show ancp summary
user@host> show ancp summary
Neighbors Summary:
Configured Establishing
---------- -----------22
0

Established
----------2

Not Established
--------------0

Total
---------24

Subscribers Summary:
Showtime
Idle
Silent
Unknown
Total
---------- ---------- ----------- ---------- ---------4
0
0
0
4

1444

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

show ancp summary neighbor

Syntax

Release Information
Description

Options

show ancp summary neighbor

<ip-address ip-address | system-name mac-address>

Command introduced in Junos OS Release 13.1.

Display a summary of the counts and states for all ANCP neighbors and of the neighbors
subscribers when you specify a particular neighbor.
ip-address ip-address(Optional) IP address of the ANCP neighbor (access node).
system-name mac-address(Optional) MAC address of the ANCP neighbor (access

node).
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show ancp summary on page 1443

show ancp subscriber on page 1438

show ancp summary subscriber on page 1447

show ancp summary neighbor on page 1446

show ancp summary neighbor (IP Address) on page 1446
show ancp summary neighbor (MAC Address) on page 1446
Table 82 on page 1445 lists the output fields for the show ancp summary command. Output
fields are listed in the approximate order in which they appear.

Table 82: show ancp summary neighbor Output Fields

Field Name

Field Description

Configured

Number of ANCP neighbors in the Configured state; that is, that have been
configured but never established.

Establishing

Number of ANCP neighbors in the Establishing state; that is, where negotiations
are in progress.

Established

Number of ANCP neighbors in the Established state; that is, where negotiations
have succeeded and the ANCP session has been established.

Not Estblshd

Number of ANCP neighbors in the Not Estblshd state; that is, that have lost a
previously established adjacency and are ready to begin negotiations.

Total

Total number of ANCP neighbors; sum of neighbors in the Configured,

Establishing, Established, and Not Estblshd states.

Showtime

Number of DSL lines for the neighbor in Showtime state.

Copyright 2014, Juniper Networks, Inc.

1445

Interfaces Fundamentals for Routing Devices

Table 82: show ancp summary neighbor Output Fields (continued)

Field Name

Field Description

Idle

Number of DSL lines for the neighbor in Idle state.

Silent

Number of DSL lines for the neighbor in Silent state.

Unknown

Number of DSL lines for the neighbor where the state is not Showtime, Idle, or
Silent.

Total

Total number of DSL lines (ANCP subscribers); sum of DSL lines in the Showtime,
Idle, Silent, and Unknown states.

Sample Output
show ancp summary neighbor
user@host> show ancp summary neighbor
Neighbors Summary:
Configured Establishing
---------- -----------22
0

Established
----------2

Not Established
--------------0

Total
---------24

show ancp summary neighbor (IP Address)

user@host> show ancp summary neighbor ip-address 192.168.10.1
Neighbor Summary:192.168.10.1 status Established
Subscribers Summary:
Show Time
Idle
Silent
Unknown
Total
---------- ---------- ----------- ---------- ---------6
0
0
0
6

show ancp summary neighbor (MAC Address)

user@host> show ancp summary neighbor system-name 00:00:64:1b:01:02
Neighbor Summary:00:00:64:1b:01:02 status Established
Subscribers Summary:
Show Time
Idle
Silent
Unknown
Total
---------- ---------- ----------- ---------- ---------5
1
2
0
8

1446

Copyright 2014, Juniper Networks, Inc.

Chapter 15: ANCP Operational Commands

show ancp summary subscriber

Syntax
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show ancp summary subscriber

Command introduced in Junos OS Release 13.1.

Display a summary of the counts and states for all ANCP subscribers.
This command has no options.
view

show ancp summary on page 1443

show ancp neighbor on page 1425

show ancp summary neighbor on page 1445

show ancp summary subscriber on page 1447

Table 83 on page 1447 lists the output fields for the show ancp summary subscriber
command. Output fields are listed in the approximate order in which they appear.

Table 83: show ancp summary subscriber Output Fields

Field Name

Field Description

Showtime

Number of DSL lines in Showtime state.

Idle

Number of DSL lines in Idle state.

Silent

Number of DSL lines in Silent state.

Unknown

Number of DSL lines where the state is not Showtime, Idle, or Silent.

Total

Total number of DSL lines (ANCP subscribers); sum of DSL lines in the Showtime,
Idle, Silent, and Unknown states.

Sample Output
show ancp summary subscriber
user@host> show ancp summary subscriber
Subscribers Summary:
Show Time
Idle
Silent
Unknown
Total
---------- ---------- ----------- ---------- ---------8
1
0
1
10

Copyright 2014, Juniper Networks, Inc.

1447

Interfaces Fundamentals for Routing Devices

1448

Copyright 2014, Juniper Networks, Inc.

CHAPTER 16

BFD Operational Commands

clear bfd adaptation

clear bfd session

show bfd session

Copyright 2014, Juniper Networks, Inc.

1449

Interfaces Fundamentals for Routing Devices

clear bfd adaptation

Syntax

Release Information
Description

clear bfd adaptation

<address session-address>
<discriminator discr-number>

Command introduced before Junos OS Release 7.4.

Clear adaptation for Bidirectional Forwarding Detection (BFD) sessions. BFD is a simple
hello mechanism that detects failures in a network. Configured BFD interval timers can
change, adapting to network situations. Use this command to return BFD interval timers
to their configured values.
The clear bfd adaptation command is hitless, meaning that the command does not affect
traffic flow on the routing device.

Options

noneClear adaptation for all BFD sessions.

address session-address(Optional) Clear adaptation for all BFD sessions matching the

specified address.
discriminator discr-number(Optional) Clear adaptation for the local BFD session

matching the specified discriminator.

Additional Information

Required Privilege
Level
List of Sample Output
Output Fields

For more information, see the description of the bfd-liveness-detection configuration

statement in the Junos Routing Protocols Configuration Guide.
clear

clear bfd adaptation on page 1450

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear bfd adaptation
user@host> clear bfd adaptation

1450

Copyright 2014, Juniper Networks, Inc.

Chapter 16: BFD Operational Commands

clear bfd session

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1451

Syntax (EX Series Switch and QFX Series) on page 1451
clear bfd session
<address session-address>
<discriminator discr-number>
<logical-system (all | logical-system-name)>
clear bfd session
<address session-address>
<discriminator discr-number>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.
Drop one or more Bidirectional Forwarding Detection (BFD) sessions.
noneDrop all BFD sessions.
address session-address(Optional) Drop all BFD sessions matching the specified address.
discriminator discr-number(Optional) Drop the local BFD session matching the specified

discriminator.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show bfd session on page 1452

clear bfd session on page 1451

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear bfd session
user@host> clear bfd session

Copyright 2014, Juniper Networks, Inc.

1451

Interfaces Fundamentals for Routing Devices

show bfd session

List of Syntax

Syntax on page 1452

Syntax (EX Series Switch and QFX Series) on page 1452

Syntax

show bfd session

<brief | detail | extensive | summary>
<address address>
<client rsvp-oam (brief | detail | extensive | summary) | vpls-oam (brief | detail | extensive |
instance instance-name | summary)>
<discriminator discriminator>
<logical-system (all | logical-system-name)>
<prefix address>

Syntax (EX Series

Switch and QFX
Series)

show bfd session

<brief | detail | extensive | summary>
<address address>
<client rsvp-oam (brief | detail | extensive | summary) | vpls-oam (brief | detail | extensive |
instance instance-name | summary)>
<discriminator discriminator>
<prefix address>

Release Information

Description
Options

Command introduced before Junos OS Release 7.4.

Options discriminator and address introduced in Junos OS Release 8.2.
Option prefix introduced in Junos OS Release 9.0.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Option client introduced in Junos OS Release 12.3R3.
Display information about active Bidirectional Forwarding Detection (BFD) sessions.
none(Same as brief) Display information about active BFD sessions.
brief | detail | extensive | summary(Optional) Display the specified level of output.
address address(Optional) Display information about the BFD session for the specified

neighbor address.
client rsvp-oam
(brief | detail | extensive | summary)
| vpls-oam
(brief | detail | extensive | instance instance-name | summary)(Optional) Display

information about RSVP-OAM or VPLS-OAM BFD sessions in the specified level of

output. For VPLS-OAM, display the specified level of output or display information
about all of the BFD sessions for the specified VPLS routing instance.
discriminator discriminator(Optional) Display information about the BFD session using

the specified local discriminator.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

1452

Copyright 2014, Juniper Networks, Inc.

Chapter 16: BFD Operational Commands

prefix address(Optional) Display information about all of the BFD sessions for the

specified LDP forwarding equivalence class (FEC).

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

clear bfd session on page 1451

Examples: Configuring BFD for Static Routes

Example: Configuring BFD for OSPF

Example: Configuring BFD for BGP

Configuring PIM and the Bidirectional Forwarding Detection (BFD) Protocol

Example: Configuring BFD for IS-IS

show bfd session on page 1456

show bfd session brief on page 1457
show bfd session detail on page 1457
show bfd session detail (with Authentication) on page 1457
show bfd session address extensive on page 1457
show bfd session client rsvp-oam on page 1458
show bfd session client vpls-oam summary on page 1458
show bfd session client vpls-oam instance instance-name on page 1458
show bfd session extensive on page 1458
show bfd session extensive (with Authentication) on page 1459
show bfd session summary on page 1459
Table 84 on page 1453 describes the output fields for the show bfd session command.
Output fields are listed in the approximate order in which they appear.

Table 84: show bfd session Output Fields

Field Name

Field Description

Level of Output

Address

Address on which the BFD session is active.

brief detail extensive

none
State

State of the BFD session: Up, Down, Init (initializing), or Failing.

brief detail extensive

none
Interface

Interface on which the BFD session is active.

brief detail extensive

none
Detect Time

Negotiated time interval, in seconds, used to detect BFD control packets.

brief detail extensive

none
Transmit Interval

Multiplier

Time interval, in seconds, used by the transmitting system to send BFD control
packets.

brief detail extensive

Negotiated multiplier by which the time interval is multiplied to determine the

detection time for the transmitting system.

detail extensive

Copyright 2014, Juniper Networks, Inc.

none

1453

Interfaces Fundamentals for Routing Devices

Table 84: show bfd session Output Fields (continued)

Field Name

Field Description

Level of Output

Session up time

How long a BFD session has been established.

detail extensive

Client

Protocol for which the BFD session is active: ISIS, OSPF, or Static.

detail extensive

TX interval

Time interval, in seconds, used by the host system to transmit BFD control
packets.

brief detail extensive

Time interval, in seconds, used by the host system to receive BFD

control packets.

brief detail extensive

Authenticate

Indicates that BFD authentication is configured.

detail extensive

keychain

Name of the security authentication keychain being used by a specific client.

extensive

RX interval

none

none

BFD authentication information for a client is provided in a single line and

includes the keychain, algo, and mode parameters. Multiple clients can be
configured on a BFD session.
algo

BFD authentication algorithm being used for a specific client: keyed-md5,

keyed-sha-1, meticulous-keyed-md5, meticulous-keyed-sha-1, or simple-password.

extensive

BFD authentication information for a client is provided in a single line and

includes the keychain, algo, and mode parameters. Multiple clients can be
configured on a BFD session.
mode

Level of BFD authentication enforcement being used by a specific client: strict

or loose. Strict enforcement indicates that authentication is configured at both
ends of the session (the default). Loose enforcement indicates that one end of
the session might not be authenticated.

extensive

BFD authentication information for a client is provided in a single line and

includes the keychain, algo, and mode parameters. Multiple clients can be
configured on a BFD session.
Local diagnostic

Local diagnostic information about failing BFD sessions.

detail extensive

Remote diagnostic

Remote diagnostic information about failing BFD sessions.

detail extensive

Remote state

Reports whether the remote system's BFD packets have been received and
whether the remote system is receiving transmitted control packets.

detail extensive

Version

BFD version: 0 or 1.

extensive

Replicated

The replicated flag appears when nonstop routing or graceful Routing Engine
switchover is configured and the BFD session has been replicated to the backup
Routing Engine.

detail extensive

Min async interval

Minimum amount of time, in seconds, between asynchronous control packet

transmissions across the BFD session.

extensive

1454

Copyright 2014, Juniper Networks, Inc.

Chapter 16: BFD Operational Commands

Table 84: show bfd session Output Fields (continued)

Field Name

Field Description

Level of Output

Min slow interval

Minimum amount of time, in seconds, between synchronous control packet

transmissions across the BFD session.

extensive

Adaptive async TX
interval

Transmission interval being used because of adaptation.

extensive

RX interval

Minimum required receive interval.

extensive

Local min TX
interval

Minimum amount of time, in seconds, between control packet transmissions

on the local system.

extensive

Local min RX
interval

Minimum amount of time, in seconds, between control packet detections on

the local system.

extensive

Remote min TX
interval

Minimum amount of time, in seconds, between control packet transmissions

on the remote system.

extensive

Remote min TX
interval

Minimum amount of time, in seconds, between control packet detections on

the remote system.

extensive

Threshold
transmission
interval

Threshold for notification if the transmission interval increases.

extensive

Threshold for
detection time

Threshold for notification if the detection time increases.

extensive

Local discriminator

Authentication code used by the local system to identify that BFD session.

extensive

Remote
discriminator

Authentication code used by the remote system to identify that BFD session.

extensive

Echo mode

Information about the state of echo transmissions on the BFD session.

extensive

Prefix

LDP FEC address associated with the BFD session.

All levels

Egress, Destination

Displays the LDP FEC destination address. This field is displayed only on a router
at the egress of an LDP FEC, where the BFD session has an LDP Operation,
Administration, and Maintenance (OAM) client.

All levels

Remote is
control-plane
independent

The BFD session on the remote peer is running on its Packet Forwarding Engine.
In this case, when the remote node undergoes a graceful restart, the local peer
can help the remote peer with the graceful restart.

extensive

The following BFD sessions are not distributed to the Packet Forwarding Engine:
tunnel-encapsulated sessions, and sessions over integrated routing and bridging
(IRB) interfaces.

Copyright 2014, Juniper Networks, Inc.

1455

Interfaces Fundamentals for Routing Devices

Table 84: show bfd session Output Fields (continued)

Field Name

Field Description

Level of Output

Authentication

Summary status of BFD authentication:

extensive

statusenabled/active indicates authentication is configured and active.

enabled/inactive indicates authentication is configured but not active. This

only occurs when the remote end of the session does not support
authentication and loose checking is configured.

keychainName of the security authentication keychain associated with the

specified BFD session.

algoBFD authentication algorithm being used: keyed-md5, keyed-sha-1,

meticulous-keyed-md5, meticulous-keyed-sha-1, or simple-password.

modeLevel of BFD authentication enforcement: strict or loose. Strict

enforcement indicates authentication is configured at both ends of the session

(the default). Loose enforcement indicates that one end of the session might
not be authenticated.
This information is only shown if BFD authentication is configured.
Session ID

The BFD session ID number that represents the protection using MPLS fast
reroute (FRR) and loop-free alternate (LFA).

detail extensive

sessions

Total number of active BFD sessions.

All levels

clients

Total number of clients that are hosting active BFD sessions.

All levels

Cumulative
transmit rate

Total number of BFD control packets transmitted per second on all

active sessions.

All levels

Cumulative receive
rate

Total number of BFD control packets received per second on all active sessions.

All levels

Multi-hop,
min-recv-TTL

Minimum time to live (TTL) accepted if the session is configured for multihop.

extensive

route table

Route table used if the session is configured for multihop.

extensive

local address

Local address of the source used if the session is configured for multihop.

extensive

The source IP address for outgoing BFD packets from the egress side of an
MPLS BFD session is based on the outgoing interface IP address.

Sample Output
show bfd session
user@host> show bfd session
Address
10.9.1.33
10.9.1.29

State
Up
Up

Interface
so-7/1/0.0
ge-4/0/0.0

Detect Time
0.600
0.600

Transmit
Interval
0.200
0.200

Multiplier
3
3

2 sessions, 2 clients
Cumulative transmit rate 10.0 pps, cumulative receive rate 10.0 pps

1456

Copyright 2014, Juniper Networks, Inc.

Chapter 16: BFD Operational Commands

show bfd session brief

The output for the show bfd session brief command is identical to that for the show bfd
session command. For sample output, see show bfd session on page 1456.
show bfd session detail
user@host> show bfd session detail
Transmit
Address
State
Interface
Detect Time Interval Multiplier
10.9.1.33
Up
so-7/1/0.0
0.600
0.200
3
Client OSPF, TX interval 0.200, RX interval 0.200, multiplier 3
Session up time 3d 00:34
Local diagnostic None, remote diagnostic None
Remote state Up, version 1
Replicated
10.9.1.29
Up
ge-4/0/0.0
0.600
0.200
3
Client ISIS L2, TX interval 0.200, RX interval 0.200, multiplier 3
Session up time 3d 00:29, previous down time 00:00:01
Local diagnostic NbrSignal, remote diagnostic AdminDown
Remote state Up, version 1
2 sessions, 2 clients
Cumulative transmit rate 10.0 pps, cumulative receive rate 10.0 pps

show bfd session detail (with Authentication)

user@host> show bfd session detail
Transmit
Address
State
Interface
Detect Time Interval Multiplier
10.9.1.33
Up
so-7/1/0.0
0.600
0.200
3
Client OSPF, TX interval 0.200, RX interval 0.200, multiplier 3, Authenticate
Session up time 3d 00:34
Local diagnostic None, remote diagnostic None
Remote state Up, version 1
Replicated
10.9.1.29
Up
ge-4/0/0.0
0.600
0.200
3
Client ISIS L2, TX interval 0.200, RX interval 0.200, multiplier 3
Session up time 3d 00:29, previous down time 00:00:01
Local diagnostic NbrSignal, remote diagnostic AdminDown
Remote state Up, version 1
2 sessions, 2 clients
Cumulative transmit rate 10.0 pps, cumulative receive rate 10.0 pps

show bfd session address extensive

user@host> show bfd session 10.255.245.212 extensive
Transmit
Address
State
Interface
Detect Time Interval Multiplier
10.255.245.212
Up
1.200
0.400
3
Client Static, TX interval 0.400, RX interval 0.400, multiplier 3
Session up time 00:17:03, previous down time 00:00:14
Local diagnostic CtlExpire, remote diagnostic NbrSignal
Remote state Up, version 1
Replicated
Min async interval 0.400, min slow interval 1.000
Adaptive async tx interval 0.400, rx interval 0.400
Local min tx interval 0.400, min rx interval 0.400, multiplier 3
Remote min tx interval 0.400, min rx interval 0.400, multiplier 3

Copyright 2014, Juniper Networks, Inc.

1457

Interfaces Fundamentals for Routing Devices

Threshold transmission interval 0.000, Threshold for detection time 0.000

Local discriminator 6, remote discriminator 16
Echo mode disabled/inactive
Multi-hop, min-recv-TTL 255, route-table 0, local-address 10.255.245.205

1 sessions, 1 clients
Cumulative transmit rate 2.5 pps, cumulative receive rate 2.5 pps

show bfd session client rsvp-oam

user@host> show bfd session client rsvp-oam
Address

State

192.168.0.223

Up

Detect
Transmit
Interface
Time
Interval
540.000

180.000

Multiplier
3

1 Up sessions, 0 Down sessions

1 sessions, 1 clients
Cumulative transmit rate 0.0 pps, cumulative receive rate 0.0 pps

show bfd session client vpls-oam summary

user@host> show bfd session client vpls-oam summary
1 Up sessions, 1 Down sessions
2 sessions, 2 clients
Cumulative transmit rate 2.0 pps, cumulative receive rate 1.0 pps

show bfd session client vpls-oam instance instance-name

user@host> show bfd session client vpls-oam instance vpls
Detect
Transmit
Address
State
Interface
Time
Interval
127.0.0.1

Up

ae9.0

3.000

1.000

Multiplier
3

1 Up Sessions, 0 Down Sessions

1 sessions, 1 clients
Cumulative transmit rate 1.0 pps, cumulative receive rate 1.0 pps

show bfd session extensive

user@host> show bfd session extensive
10.31.1.2
Up
ge-2/1/8.0
0.030
0.010
3
Client OSPF realm ospf-v2 Area 0.0.0.0, TX interval 0.010, RX interval 0.010
Session up time 00:10:13
Local diagnostic None, remote diagnostic None
Remote state Up, version 1
Replicated
Min async interval 0.010, min slow interval 1.000
Adaptive async TX interval 0.010, RX interval 0.010
Local min TX interval 0.010, minimum RX interval 0.010, multiplier 3
Remote min TX interval 0.010, min RX interval 0.010, multiplier 3
Local discriminator 12, remote discriminator 4
Echo mode disabled/inactive
Remote is control-plane independent
Session ID: 0x201
Micro-BFD Session
Detect
Transmit
Address
State
Interface
Time
Interval Multiplier
10.31.2.2
Up
ge-2/1/4.0
0.030
0.010
3
Client OSPF realm ospf-v2 Area 0.0.0.0, TX interval 0.010, RX interval 0.010

1458

Copyright 2014, Juniper Networks, Inc.

Chapter 16: BFD Operational Commands

Session up time 00:10:14

Local diagnostic None, remote diagnostic NbrSignal
Remote state Up, version 1
Replicated
Min async interval 0.010, min slow interval 1.000
Adaptive async TX interval 0.010, RX interval 0.010
Local min TX interval 0.010, minimum RX interval 0.010, multiplier 3
Remote min TX interval 0.010, min RX interval 0.010, multiplier 3
Local discriminator 13, remote discriminator 5
Echo mode disabled/inactive
Remote is control-plane independent
Session ID: 0x202
2 sessions, 2 clients
Cumulative transmit rate 200.0 pps, cumulative receive rate 200.0 pps

show bfd session extensive (with Authentication)

user@host> show bfd session extensive
Detect
Transmit
Address
State
Interface
Time
Interval Multiplier
192.168.208.26
Up
so-1/0/0.0
2.400
0.800
10
Client Static, TX interval 0.600, RX interval 0.600, Authenticate
keychain bfd, algo keyed-md5, mode loose
Session up time 00:18:07
Local diagnostic None, remote diagnostic NbrSignal
Remote state Up, version 1
Replicated
Min async interval 0.600, min slow interval 1.000
Adaptive async TX interval 0.600, RX interval 0.600
Local min TX interval 0.600, minimum RX interval 0.600, multiplier 10
Remote min TX interval 0.800, min RX interval 0.800, multiplier 3
Local discriminator 2, remote discriminator 3
Echo mode disabled/inactive
Authentication enabled/active, keychain bfd, algo keyed-md5, mode loose

1 sessions, 1 clients
Cumulative transmit rate 1.2 pps, cumulative receive rate 1.2 pps

show bfd session summary

user@host> show bfd session summary
2 sessions, 2 clients
Cumulative transmit rate 10.0 pps, cumulative receive rate 10.0 pps

Copyright 2014, Juniper Networks, Inc.

1459

Interfaces Fundamentals for Routing Devices

1460

Copyright 2014, Juniper Networks, Inc.

CHAPTER 17

BGP Operational Commands

clear bgp damping

clear bgp neighbor

clear bgp table

show bgp bmp

show bgp group

show bgp group traffic-statistics

show bgp neighbor

show bgp replication

show bgp summary

show policy damping

Copyright 2014, Juniper Networks, Inc.

1461

Interfaces Fundamentals for Routing Devices

clear bgp damping

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1462

Syntax (EX Series Switch and QFX Series) on page 1462
clear bgp damping
<logical-system (all | logical-system-name)>
<prefix>
clear bgp damping
<prefix>

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.3 for the QFX Series.
Clear BGP route flap damping information.
noneClear all BGP route flap damping information.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

prefix(Optional) Clear route flap damping information for only the specified destination

prefix.
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

clear

show policy damping on page 1501

show route damping on page 1970

clear bgp damping on page 1462

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear bgp damping
user@host> clear bgp damping

1462

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

clear bgp neighbor

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)

Release Information

Description

Options

Syntax on page 1463

Syntax (EX Series Switch and QFX Series) on page 1463
clear bgp neighbor
<as as-number>
<instance instance-name>
<logical-system (all | logical-system-name)>
<malformed-route>
<neighbor>
<soft | soft-inbound>
<soft-minimum-igp>
clear bgp neighbor
<as as-number>
<instance instance-name>
<malformed-route>
<neighbor>
<soft | soft-inbound>
<soft-minimum-igp>

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.3 for the QFX Series.
malformed-route option introduced in Junos OS Release 13.2.
Perform one of the following tasks:

Change the state of one or more BGP neighbors to IDLE. For neighbors in the
ESTABLISHED state, this command drops the TCP connection to the neighbors and
then reestablishes the connection.

(soft keyword only) Reapply export policies or import policies, respectively, to one or
more BGP neighbors without changing their state.

(soft-inbound keyword only) Reapply export policies or import policies, respectively,

and send refresh updates to one or more BGP neighbors without changing their state.

noneChange the state of all BGP neighbors to IDLE.

as as-number(Optional) Apply this command only to neighbors in the specified

autonomous system (AS).

instance instance-name(Optional) Apply this command only to neighbors for the

specified routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

malformed-route(Optional) Remove malformed routes. If a specific neighbor is provided,

Junos OS removes malformed routes for that particular neighbor. Otherwise, Junos
OS removes malformed routes for all BGP neighbors. To find routes that have

Copyright 2014, Juniper Networks, Inc.

1463

Interfaces Fundamentals for Routing Devices

malformed attributes, run the show route hidden command, and look for routes
marked with MalformedAttr in the AS path field.
neighbor(Optional) IP address of a BGP peer. Apply this command only to the specified

neighbor.
soft(Optional) Reapply any export policies and send refresh updates to neighbors

without clearing the state.

soft-inbound(Optional) Reapply any import policies and send refresh updates to

neighbors without clearing the state.

soft-minimum-igp(Optional) Provides soft refresh of the outbound state when the

interior gateway protocol (IGP) metric is reset.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show bgp neighbor on page 1478

clear bgp neighbor on page 1464

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear bgp neighbor
user@host> clear bgp neighbor

1464

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

clear bgp table

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

clear bgp table table-name

<logical-system (all | logical-system-name)>
clear bgp table table-name

Command introduced in Junos OS Release 9.0.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Request that BGP refresh routes in a specified routing table.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

table-nameRequest that BGP refresh routes in the specified table.

Additional Information

Required Privilege
Level
List of Sample Output

Output Fields

In some cases, a prefix limit is associated with a routing table for a VPN instance. When
this limit is exceeded (for example, because of a network misconfiguration), some routes
might not be inserted in the table. Such routes need to be added to the table after the
network issue is resolved. Use the clear bgp table command to request that BGP refresh
routes in a VPN instance table.
clear

clear bgp table private.inet.0 on page 1465

clear bgp table inet.6 logical-system all on page 1465
clear bgp table private.inet.6 logical-system ls1 on page 1465
clear bgp table logical-system all inet.0 on page 1465
clear bgp table logical-system ls2 private.inet.0 on page 1466
This command produces no output.

Sample Output
clear bgp table private.inet.0
user@host> clear bgp table private.inet.0

clear bgp table inet.6 logical-system all

user@host> clear bgp table inet.6 logical-system all

clear bgp table private.inet.6 logical-system ls1

user@host> clear bgp table private.inet.6 logical-system ls1

clear bgp table logical-system all inet.0

user@host> clear bgp table logical-system all inet.0

Copyright 2014, Juniper Networks, Inc.

1465

Interfaces Fundamentals for Routing Devices

clear bgp table logical-system ls2 private.inet.0

user@host> clear bgp table logical-system ls2 private.inet.0

1466

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

show bgp bmp

Syntax
Release Information

Description
Options
Required Privilege
Level
List of Sample Output
Output Fields

show bgp bmp

Command introduced in Junos OS Release 9.5.

Command introduced in Junos OS Release 9.5 for EX Series switches.
Command introduced in Junos OS Release 13.2X51-D15 for the QFX Series.
Display information about the BGP Monitoring Protocol (BMP).
This command has no options.
view

show bgp bmp on page 1467

Table 85 on page 1467 lists the output fields for the show bgp bmp command. Output fields
are listed in the approximate order in which they appear.

Table 85: show bgp bmp Output Fields

Field Name

Field Description

BMP station address/port

IP address and port number of the monitoring station to which BGP

Monitoring Protocol (BMP) statistics are sent.

BMP session state

Status of the BMP session: UP or DOWN.

Memory consumed by BMP

Memory used by the active BMP session.

Statistics timeout

Amount of time, in seconds, between transmissions of BMP data

to the monitoring station.

Memory limit

Threshold, in bytes, at which the routing device stops collecting

BMP data.

Memory-connect retry
timeout

Amount of time, in seconds, after which the routing device attempts

to resume a BMP session that was ended after the configured
memory threshold was exceeded.

Sample Output
show bgp bmp
user@host> show bgp bmp
BMP station address/port: 172.24.24.157+5454
BMP session state: DOWN
Memory consumed by BMP: 0
Statistics timeout: 15
Memory limit: 10485760
Memory connect retry timeout: 600

Copyright 2014, Juniper Networks, Inc.

1467

Interfaces Fundamentals for Routing Devices

1468

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

show bgp group

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)

Release Information

Description
Options

Syntax on page 1469

Syntax (EX Series Switch and QFX Series) on page 1469
show bgp group
<brief | detail | summary>
<group-name>
<exact-instance instance-name>
<instance instance-name>
<logical-system (all | logical-system-name)>
<rtf>
show bgp group
<brief | detail | summary>
<group-name>
<exact-instance instance-name>
<instance instance-name>

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.3 for the QFX Series.
exact-instance option introduced in Junos OS Release 11.4.
Display information about the configured BGP groups.
noneDisplay group information about all BGP groups.
brief | detail | summary(Optional) Display the specified level of output.
group-name(Optional) Display group information for the specified group.
exact-instance instance-name(Optional) Display information for the specified instance

only.
instance instance-name(Optional) Display information about BGP groups for all routing

instances whose name begins with this string (for example, cust1, cust11, and cust111
are all displayed when you run the show bgp group instance cust1 command). The
instance name can be master for the main instance, or any valid configured instance
name or its prefix.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

rtf(Optional) Display BGP group route targeting information.

Required Privilege
Level
List of Sample Output

view

show bgp group on page 1473

show bgp group brief on page 1473
show bgp group detail on page 1474

Copyright 2014, Juniper Networks, Inc.

1469

Interfaces Fundamentals for Routing Devices

show bgp group rtf detail on page 1475

show bgp group summary on page 1475
Output Fields

Table 86 on page 1470 describes the output fields for the show bgp group command. Output
fields are listed in the approximate order in which they appear.

Table 86: show bgp group Output Fields

Field Name

Field Description

Level of
Output

Group Type or Group

Type of BGP group: Internal or External.

All levels

group-index

Index number for the BGP peer group. The index number
differentiates between groups when a single BGP group is split
because of different configuration options at the group and peer
levels.

rtf detail

AS

AS number of the peer. For internal BGP (IBGP), this number is the
same as Local AS.

brief detail

AS number of the local routing device.

brief detail

Local AS

none

none
Name

Name of a specific BGP group.

brief detail

none
Index

Unique index number of a BGP group.

brief detail

none
Flags associated with the BGP group. This field is used by Juniper
Networks customer support.

brief detail

BGP-Static Advertisement Policy

Policies configured for the BGP group with the advertise-bgp-static

policy statement.

brief none

Remove-private options

Options associated with the remove-private statement.

brief detail

Flags

none

none
Maximum number of seconds allowed to elapse between successive
keepalive or update messages that BGP receives from a peer in the
BGP group, after which the connection to the peer is closed and
routing devices through that peer become unavailable.

brief detail

Export policies configured for the BGP group with the export
statement.

brief detail

MED tracks IGP metric update delay

Time, in seconds, that updates to multiple exit discriminator (MED)

are delayed. Also displays the time remaining before the interval is
set to expire

All levels

Traffic Statistics Interval

Time between sample periods for labeled-unicast traffic statistics,

in seconds.

brief detail

Holdtime

Export

1470

none

none

none

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Table 86: show bgp group Output Fields (continued)

Field Name

Field Description

Level of
Output

Total peers

Total number of peers in the group.

brief detail

none
Established

Number of peers in the group that are in the established state.

All levels

Active/Received/Accepted/Damped

Multipurpose field that displays information about BGP peer

sessions. The fields contents depend upon whether a session is
established and whether it was established in the main routing device
or in a routing instance.

summary

If a peer is not established, the field shows the state of the peer
session: Active, Connect, or Idle.

If a BGP session is established in the main routing device, the field

shows the number of active, received, accepted, and damped
routes that are received from a neighbor and appear in the inet.0
(main) and inet.2 (multicast) routing tables. For example,
8/10/10/2 and 2/4/4/0 indicate the following:

8 active routes, 10 received routes, 10 accepted routes, and 2

damped routes from a BGP peer appear in the inet.0 routing
table.

2 active routes, 4 received routes, 4 accepted routes, and no

damped routes from a BGP peer appear in the inet.2 routing
table.

ip-addresses

List of peers who are members of the group. The address is followed
by the peers port number.

All levels

Route Queue Timer

Number of seconds until queued routes are sent. If this time has
already elapsed, this field displays the number of seconds by which
the updates are delayed.

detail

Route Queue

Number of prefixes that are queued up for sending to the peers in

the group.

detail

inet.number

Number of active, received, accepted, and damped routes in the

routing table. For example, inet.0: 7/10/9/0 indicates the following:

none

Copyright 2014, Juniper Networks, Inc.

7 active routes, 10 received routes, 9 accepted routes, and no

damped routes from a BGP peer appear in the inet.0 routing table.

1471

Interfaces Fundamentals for Routing Devices

Table 86: show bgp group Output Fields (continued)

Field Name

Field Description

Level of
Output

Table inet.number

Information about the routing table.

detail

Received prefixesTotal number of prefixes from the peer, both

active and inactive, that are in the routing table.

Active prefixesNumber of prefixes received from the peer that

are active in the routing table.

Suppressed due to dampingNumber of routes currently inactive

because of damping or other reasons. These routes do not appear

in the forwarding table and are not exported by routing protocols.

Advertised prefixesNumber of prefixes advertised to a peer.

Received external prefixesTotal number of prefixes from the

external BGP (EBGP) peers, both active and inactive, that are in
the routing table.

Active external prefixesNumber of prefixes received from the

EBGP peers that are active in the routing table.

Externals suppressedNumber of routes received from EBGP

peers currently inactive because of damping or other reasons.

Received internal prefixesTotal number of prefixes from the IBGP

peers, both active and inactive, that are in the routing table.

Active internal prefixesNumber of prefixes received from the

IBGP peers that are active in the routing table.

Internals suppressedNumber of routes received from IBGP peers

currently inactive because of damping or other reasons.

RIB StateStatus of the graceful restart process for this routing

table: BGP restart is complete, BGP restart in progress, VPN restart
in progress, or VPN restart is complete.

Groups

Total number of groups.

All levels

Peers

Total number of peers.

All levels

External

Total number of external peers.

All levels

Internal

Total number of internal peers.

All levels

Down peers

Total number of unavailable peers.

All levels

Flaps

Total number of flaps that occurred.

All levels

Table

Name of a routing table.

brief, none

Tot Paths

Total number of routes.

brief, none

Act Paths

Number of active routes.

brief, none

Suppressed

Number of routes currently inactive because of damping or other

reasons. These routes do not appear in the forwarding table and are
not exported by routing protocols.

brief, none

1472

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Table 86: show bgp group Output Fields (continued)

Level of
Output

Field Name

Field Description

History

Number of withdrawn routes stored locally to keep track of damping

history.

brief, none

Damp State

Number of active routes with a figure of merit greater than zero, but
lower than the threshold at which suppression occurs.

brief, none

Pending

Routes being processed by the BGP import policy.

brief, none

Group

Group the peer belongs to in the BGP configuration.

detail

Receive mask

Mask of the received target included in the advertised route.

detail

Entries

Number of route entries received.

detail

Target

Route target that is to be passed by route-target filtering. If a route

advertised from the provider edge (PE) routing device matches an
entry in the route-target filter, the route is passed to the peer.

detail

Mask

Mask which specifies that the peer receive routes with the given
route target.

detail

Sample Output
show bgp group
user@host> show bgp group
Groups: 2
Table

Peers: 2
External: 1
Internal: 2
Tot Paths Act Paths Suppressed

Down peers: 1
Flaps: 0
History Damp State
Pending

inet.0
0

bgp.l3vpn.0

bgp.rtarget.0

show bgp group brief

user@host> show bgp group brief
Groups: 2 Peers: 2
External: 0
Internal: 2
Down peers: 1
Flaps: 0
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
inet.0
0

bgp.l3vpn.0

Copyright 2014, Juniper Networks, Inc.

1473

Interfaces Fundamentals for Routing Devices

bgp.rtarget.0
2

show bgp group detail

user@host> show bgp group detail
Group Type: Internal
AS: 1
Name: ibgp
Index: 0
Holdtime: 0
Total peers: 3
Established: 0
22.0.0.2
22.0.0.8
22.0.0.5
Groups: 1 Peers: 3
External: 0
Internal: 3
Table bgp.l3vpn.0
Received prefixes:
0
Accepted prefixes:
0
Active prefixes:
0
Suppressed due to damping:
0
Received external prefixes:
0
Active external prefixes:
0
Externals suppressed:
0
Received internal prefixes:
0
Active internal prefixes:
0
Internals suppressed:
0
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Table bgp.mdt.0
Received prefixes:
0
Accepted prefixes:
0
Active prefixes:
0
Suppressed due to damping:
0
Received external prefixes:
0
Active external prefixes:
0
Externals suppressed:
0
Received internal prefixes:
0
Active internal prefixes:
0
Internals suppressed:
0
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Table VPN-A.inet.0
Received prefixes:
0
Accepted prefixes:
0
Active prefixes:
0
Suppressed due to damping:
0
Received external prefixes:
0
Active external prefixes:
0
Externals suppressed:
0
Received internal prefixes:
0
Active internal prefixes:
0
Internals suppressed:
0
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Table VPN-A.mdt.0
Received prefixes:
0
Accepted prefixes:
0
Active prefixes:
0
Suppressed due to damping:
0
Received external prefixes:
0
Active external prefixes:
0

1474

Local AS: 1
Flags: <Export Eval>

Down peers: 3

Flaps: 3

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Externals suppressed:
0
Received internal prefixes:
0
Active internal prefixes:
0
Internals suppressed:
0
RIB State: BGP restart is complete
RIB State: VPN restart is complete

show bgp group rtf detail

user@host> show bgp group rtf detail
Group: internal (group-index: 0)
Receive mask: 00000002
Table: bgp.rtarget.0
Target
100:100/64
200:201/64
Group: internal (group-index: 1)
Table: bgp.rtarget.0
Target
200:201/64

Entries: 2
Mask
00000002
(Group)
Entries: 1
Mask
(Group)

show bgp group summary

user@host> show bgp group summary
Group
Type
Peers
Established
ibgp
Internal
3
0

Active/Received/Accepted/Damped

Groups: 1 Peers: 3
External: 0
Internal: 3
Down peers: 3
bgp.l3vpn.0
: 0/0/0/0 External: 0/0/0/0 Internal: 0/0/0/0
bgp.mdt.0
: 0/0/0/0 External: 0/0/0/0 Internal: 0/0/0/0
VPN-A.inet.0
: 0/0/0/0 External: 0/0/0/0 Internal: 0/0/0/0
VPN-A.mdt.0
: 0/0/0/0 External: 0/0/0/0 Internal: 0/0/0/0

Copyright 2014, Juniper Networks, Inc.

Flaps: 3

1475

Interfaces Fundamentals for Routing Devices

show bgp group traffic-statistics

Syntax

Release Information
Description
Options

show bgp group traffic-statistics

<brief | detail>
<group-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display the traffic statistics for configured Border Gateway Protocol (BGP) groups.
noneDisplay traffic statistics for all BGP groups.
brief | detail(Optional) Display the specified level of output.
group-name(Optional) Display BGP traffic statistics for only the specified group.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show bgp group traffic-statistics (Per-Group-Label Not Configured) on page 1477

show bgp group traffic-statistics (Per-Group-Label Configured) on page 1477
Table 87 on page 1476 describes the output fields for the show bgp group traffic-statistics
command. Output fields are listed in the approximate order in which they appear.

Table 87: show bgp group traffic-statistics Output Fields

1476

Field Name

Field Description

Group name

Name of a specific BGP group.

Group Index

Index number for the BGP group.

NLRI

Network layer reachability information (NLRI) indicating the source of the traffic
statistics for the BGP group.

FEC

Forwarding equivalence classes (FECs) associated with the BGP group.

Packets

Number of packets sent through each FEC.

Bytes

Number of bytes transmitted through each FEC.

EgressAS

Autonomous system (AS) number of the egress router.

AdvLabel

Label associated with each FEC.

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Sample Output
show bgp group traffic-statistics (Per-Group-Label Not Configured)
user@host> show bgp group traffic-statistics
Group Name: ext1
Group Index: 0
FEC
Packets
10.255.245.55
0
10.255.245.57
0
100.101.0.0
550
100.102.0.0
550
100.103.0.0
550
100.104.0.0
550
192.168.25.0
0

NLRI: inet-labeled-unicast
Bytes
EgressAS
AdvLabel
0
I
100224
0
I
100240
48400
25
100256
48400
25
100256
48400
25
100272
48400
25
100272
0
I
100288

Group Name: ext2

FEC
10.255.245.55
10.255.245.57
100.101.0.0
100.102.0.0
100.103.0.0
100.104.0.0
192.168.25.0

NLRI: inet-labeled-unicast
Bytes
EgressAS
AdvLabel
0
I
100224
0
I
100240
48400
25
100256
48400
25
100256
48400
25
100272
48400
25
100272
0
I
100288

Group Index: 1
Packets
0
0
550
550
550
550
0

show bgp group traffic-statistics (Per-Group-Label Configured)

user@host> show bgp group traffic-statistics
Group Name: ext1
Group Index: 0
FEC
Packets
10.255.245.55
0
10.255.245.57
0
100.101.0.0
101
100.102.0.0
101
100.103.0.0
0
100.104.0.0
0
192.168.25.0
0

NLRI: inet-labeled-unicast
Bytes
EgressAS
AdvLabel
0
I
100384
0
I
100400
8888
25
100416
8888
25
100416
0
25
100432
0
25
100432
0
I
100448

Group Name: ext2

FEC
10.255.245.55
10.255.245.57
100.101.0.0
100.102.0.0
100.103.0.0
100.104.0.0
192.168.25.0

NLRI: inet-labeled-unicast
Bytes
EgressAS
AdvLabel
0
I
100304
0
I
100320
0
25
100336
0
25
100336
8888
25
100352
8888
25
100352
0
I
100368

Copyright 2014, Juniper Networks, Inc.

Group Index: 1
Packets
0
0
0
0
101
101
0

1477

Interfaces Fundamentals for Routing Devices

show bgp neighbor

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)

Release Information

Description
Options

Syntax on page 1478

Syntax (EX Series Switch and QFX Series) on page 1478
show bgp neighbor
<exact-instance instance-name>
<instance instance-name>
<logical-system (all | logical-system-name)>
<neighbor-address>
<orf (detail | neighbor-address)
show bgp neighbor
<instance instance-name>
<exact-instance instance-name>
<neighbor-address>
<orf (neighbor-address | detail)

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.3 for the QFX Series.
orf option introduced in Junos OS Release 9.2.
exact-instance option introduced in Junos OS Release 11.4.
Display information about BGP peers.
noneDisplay information about all BGP peers.
exact-instance instance-name(Optional) Display information for the specified instance

only.
instance instance-name(Optional) Display information about BGP peers for all routing

instances whose name begins with this string (for example, cust1, cust11, and cust111
are all displayed when you run the show bgp neighbor instance cust1 command).
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor-address(Optional) Display information for only the BGP peer at the specified

IP address.
orf (detail | neighbor-address)(Optional) Display outbound route-filtering information

for all BGP peers or only for the BGP peer at the specified IP address. The default is
to display brief output. Use the detail option to display detailed output.
Additional Information

Required Privilege
Level

1478

For information about the local-address, nlri, hold-time, and preference statements, see
the Junos OS Routing Protocols Library for Routing Devices.
view

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Related
Documentation

List of Sample Output

clear bgp neighbor on page 1463

show bgp neighbor on page 1485

show bgp neighbor (CLNS) on page 1486
show bgp neighbor (Layer 2 VPN) on page 1487
show bgp neighbor (Layer 3 VPN) on page 1489
show bgp neighbor neighbor-address on page 1490
show bgp neighbor neighbor-address on page 1490
show bgp neighbor orf neighbor-address detail on page 1491

Output Fields

Table 88 on page 1479 describes the output fields for the show bgp neighbor command.
Output fields are listed in the approximate order in which they appear.

Table 88: show bgp neighbor Output Fields

Field Name

Field Description

Peer

Address of the BGP neighbor. The address is followed by the neighbor port number.

AS

AS number of the peer.

Local

Address of the local routing device. The address is followed by the peer port number.

Type

Type of peer: Internal or External.

State

Current state of the BGP session:

ActiveBGP is initiating a transport protocol connection in an attempt to connect to a peer. If the

connection is successful, BGP sends an Open message.

ConnectBGP is waiting for the transport protocol connection to be completed.

EstablishedThe BGP session has been established, and the peers are exchanging update messages.

IdleThis is the first stage of a connection. BGP is waiting for a Start event.

OpenConfirmBGP has acknowledged receipt of an open message from the peer and is waiting

to receive a keepalive or notification message.

OpenSentBGP has sent an open message and is waiting to receive an open message from the

peer.

Copyright 2014, Juniper Networks, Inc.

1479

Interfaces Fundamentals for Routing Devices

Table 88: show bgp neighbor Output Fields (continued)

Field Name

Field Description

Flags

Internal BGP flags:

Aggregate LabelBGP has aggregated a set of incoming labels (labels received from the peer) into

a single forwarding label.

CleanUpThe peer session is being shut down.

DeleteThis peer has been deleted.

IdledThis peer has been permanently idled.

ImportEvalAt the last commit operation, this peer was identified as needing to reevaluate all

received routes.

Last state

InitializingThe peer session is initializing.

SendRtnMessages are being sent to the peer.

SyncThis peer is synchronized with the rest of the peer group.

TryConnectAnother attempt is being made to connect to the peer.

UnconfiguredThis peer is not configured.

WriteFailedAn attempt to write to this peer failed.

Previous state of the BGP session:

ActiveBGP is initiating a transport protocol connection in an attempt to connect to a peer. If the

connection is successful, BGP sends an Open message.

ConnectBGP is waiting for the transport protocol connection to be completed.

EstablishedThe BGP session has been established, and the peers are exchanging update messages.

IdleThis is the first stage of a connection. BGP is waiting for a Start event.

OpenConfirmBGP has acknowledged receipt of an open message from the peer and is waiting

to receive a keepalive or notification message.

OpenSentBGP has sent an open message and is waiting to receive an open message from the

peer.
Last event

Last activity that occurred in the BGP session:

ClosedThe BGP session closed.

ConnectRetryThe transport protocol connection failed, and BGP is trying again to connect.

HoldTimeThe session ended because the hold timer expired.

KeepAliveThe local routing device sent a BGP keepalive message to the peer.

OpenThe local routing device sent a BGP open message to the peer.

OpenFailThe local routing device did not receive an acknowledgment of a BGP open message

from the peer.

1480

RecvKeepAliveThe local routing device received a BGP keepalive message from the peer.

RecvNotifyThe local routing device received a BGP notification message from the peer.

RecvOpenThe local routing device received a BGP open message from the peer.

RecvUpdateThe local routing device received a BGP update message from the peer.

StartThe peering session started.

StopThe peering session stopped.

TransportErrorA TCP error occurred.

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Table 88: show bgp neighbor Output Fields (continued)

Field Name

Field Description

Last error

Last error that occurred in the BGP session:

CeaseAn error occurred, such as a version mismatch, that caused the session to close.

Finite State Machine ErrorIn setting up the session, BGP received a message that it did not

understand.

Hold Time ExpiredThe session's hold time expired.

Message Header ErrorThe header of a BGP message was malformed.

Open Message ErrorA BGP open message contained an error.

NoneNo errors occurred in the BGP session.

Update Message ErrorA BGP update message contained an error.

Export

Name of the export policy that is configured on the peer.

Import

Name of the import policy that is configured on the peer.

Options

Configured BGP options:

AddressFamilyConfigured address family: inet or inet-vpn.

AdvertiseBGPStaticConfigured BGP static routes are advertised.

AutheKeyChainAuthentication key change is enabled.

DropPathAttributesCertain path attributes are configured to be dropped from neighbor updates

during inbound processing.

GracefulRestartGraceful restart is configured.

HoldTimeHold time configured with the hold-time statement. The hold time is three times the

interval at which keepalive messages are sent.

IgnorePathAttributesCertain path attributes are configured to be ignored in neighbor updates

during inbound processing.

Local AddressAddress configured with the local-address statement.

MultihopAllow BGP connections to external peers that are not on a directly connected network.

NLRIConfigured MBGP state for the BGP group: multicast, unicast, or both if you have configured
nlri any.

Peer ASConfigured peer autonomous system (AS).

PreferencePreference value configured with the preference statement.

RefreshConfigured to refresh automatically when the policy changes.

Rib-groupConfigured routing table group.

Path-attributes
dropped

Path attribute codes that are dropped from neighbor updates.

Path-attributes ignored

Path attribute codes that are ignored during neighbor updates.

Authentication key
change

(appears only if the authentication-keychain statement has been configured) Name of the
authentication keychain enabled.

Authentication
algorithm

(appears only if the authentication-algorithm statement has been configured) Type of authentication
algorithm enabled: hmac or md5.

Copyright 2014, Juniper Networks, Inc.

1481

Interfaces Fundamentals for Routing Devices

Table 88: show bgp neighbor Output Fields (continued)

Field Name

Field Description

Address families
configured

Names of configured address families for the VPN.

BGP-Static
Advertisement Policy

Name of the bgp static policy that is configured on the peer.

Local Address

Address of the local routing device.

Remove-private options

Options associated with the remove-private statement.

Holdtime

Hold time configured with the hold-time statement. The hold time is three times the interval at which
keepalive messages are sent.

Flags for NLRI

inet-label-unicast

Flags related to labeled-unicast:

Traffic statistics

TrafficStatisticsCollection of statistics for labeled-unicast traffic is enabled.

Information about labeled-unicast traffic statistics:

OptionsOptions configured for collecting statistics about labeled-unicast traffic.

FileName and location of statistics log files.

sizeSize of all the log files, in bytes.

filesNumber of log files.

Traffic Statistics
Interval

Time between sample periods for labeled-unicast traffic statistics, in seconds.

Preference

Preference value configured with the preference statement.

Outbound Timer

Time for which the route is available in Junos OS routing table before it is exported to BGP. This field
is displayed in the output only if the out-delay parameter is configured to a non-zero value.

Number of flaps

Number of times the BGP session has gone down and then come back up.

Peer ID

Router identifier of the peer.

Group index

Index number for the BGP peer group. The index number differentiates between groups when a single
BGP group is split because of different configuration options at the group and peer levels.

Peer index

Index that is unique within the BGP group to which the peer belongs.

Local ID

Router identifier of the local routing device.

Local Interface

Name of the interface on the local routing device.

Active holdtime

Hold time that the local routing device negotiated with the peer.

Keepalive Interval

Keepalive interval, in seconds.

1482

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Table 88: show bgp neighbor Output Fields (continued)

Field Name

Field Description

BFD

Status of BFD failure detection.

Local Address

Name of directly connected interface over which direct EBGP peering is established.

NLRI for restart

configured on peer

Names of address families configured for restart.

NLRI advertised by peer

Address families supported by the peer: unicast or multicast.

NLRI for this session

Address families being used for this session.

Peer supports Refresh

capability

Remote peers ability to send and request full route table readvertisement (route refresh capability).
For more information, see RFC 2918, Route Refresh Capability for BGP-4.

Restart time configured

on peer

Configured time allowed for restart on the neighbor.

Stale routes from peer

are kept for

When graceful restart is negotiated, the maximum time allowed to hold routes from neighbors after
the BGP session has gone down.

Peer does not support

Restarter functionality

Graceful restart restarter-mode is disabled on the peer.

Peer does not support

Receiver functionality

Graceful restart helper-mode is disabled on the peer.

Restart time requested

by this peer

Restart time requested by this neighbor during capability negotiation.

Restart flag received

from the peer

When this field appears, the BGP speaker has restarted (Restarting), and this peer should not wait
for the end-of-rib marker from the speaker before advertising routing information to the speaker.

NLRI that peer supports

restart for

Neighbor supports graceful restart for this address family.

NLRI peer can save

forwarding state

Neighbor supporting this address family saves all forwarding states.

NLRI that peer saved

forwarding for

Neighbor saves all forwarding states for this address family.

NLRI that restart is

negotiated for

Router supports graceful restart for this address family.

NLRI of received
end-of-rib markers

Address families for which end-of-routing-table markers are received from the neighbor.

NLRI of all end-of-rib

markers sent

Address families for which end-of-routing-table markers are sent to the neighbor.

Copyright 2014, Juniper Networks, Inc.

1483

Interfaces Fundamentals for Routing Devices

Table 88: show bgp neighbor Output Fields (continued)

Field Name

Field Description

Peer supports 4 byte AS

extension (peer-as 1)

Peer understands 4-byte AS numbers in BGP messages. The peer is running Junos OS Release 9.1 or
later.

NLRIs for which peer

can receive multiple
paths

Appears in the command output of the local router if the downstream peer is configured to receive
multiple BGP routes to a single destination, instead of only receiving the active route.
Possible value is inet-unicast.

NLRIs for which peer

can send multiple
paths: inet-unicast

Appears in the command output of the local router if the upstream peer is configured to send multiple
BGP routes to a single destination, instead of only sending the active route.
Possible value is inet-unicast.

Table inet.number

Information about the routing table:

RIB StateBGP is in the graceful restart process for this routing table: restart is complete or restart
in progress.

BitNumber that represents the entry in the routing table for this peer.

Send stateState of the BGP group: in sync, not in sync, or not advertising.

Active prefixesNumber of prefixes received from the peer that are active in the routing table.

Received prefixesTotal number of prefixes from the peer, both active and inactive, that are in the

routing table.

Accepted prefixesTotal number of prefixes from the peer that have been accepted by a routing

policy.

Suppressed due to dampingNumber of routes currently inactive because of damping or other

reasons. These routes do not appear in the forwarding table and are not exported by routing
protocols.
Last traffic (seconds)

Last time any traffic was received from the peer or sent to the peer, and the last time the local routing
device checked.

Input messages

Messages that BGP has received from the receive socket buffer, showing the total number of messages,
number of update messages, number of times a policy is changed and refreshed, and the buffer size
in octets. The buffer size is 16 KB.

Output messages

Messages that BGP has written to the transmit socket buffer, showing the total number of messages,
number of update messages, number of times a policy is changed and refreshed, and the buffer size
in octets. The buffer size is 16 KB.

Input dropped path

attributes

Information about dropped path attributes:

Input ignored path

attributes

1484

CodePath attribute code.

CountPath attribute count.

Information about ignored path attributes:

CodePath attribute code.

CountPath attribute count.

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Table 88: show bgp neighbor Output Fields (continued)

Field Name

Field Description

Output queue

Number of BGP packets that are queued to be transmitted to a particular neighbor for a particular
routing table. Output queue 0 is for unicast NLRIs, and queue 1 is for multicast NLRIs.
It also specifies the routing table name and the NLRI that the table was advertised through, in the
format (routing table name, NLRI).
NOTE: The output queue of routing tables that are not advertised, will only show up at extensive
output level.

Trace options

Configured tracing of BGP protocol packets and operations.

Trace file

Name of the file to receive the output of the tracing operation.

Filter Updates recv

(orf option only) Number of outbound-route filters received for each configured address family.
NOTE: The counter is cumulative. For example, the counter is increased after the remote peer either
resends or clears the outbound route filtering prefix list.

Immediate

(orf option only) Number of route updates received with the immediate flag set. The immediate flag
indicates that the BGP peer should readvertise the updated routes.
NOTE: The counter is cumulative. For example, the counter is increased after the remote peer either
resends or clears the outbound route filtering prefix list.

Filter

(orf option only) Type of prefix filter received: prefix-based or extended-community.

Received filter entries

(orf option only) List of received filters displayed.

seq

(orf option only) Numerical order assigned to this prefix entry among all the received outbound route
filter prefix entries.

prefix

(orf option only) Address for the prefix entry that matches the filter.

minlength

(orf option only) Minimum prefix length, in bits, required to match this prefix.

maxlength

(orf option only) Maximum prefix length, in bits, required to match this prefix.

match

(orf option only) For this prefix match, whether to permit or deny route updates.

Sample Output
show bgp neighbor
user@host > show bgp neighbor
Peer: 10.255.7.250+179 AS 10
Local: 10.255.7.248+63740 AS 10
Type: Internal
State: Established
Flags: <Sync>
Last State: OpenConfirm
Last Event: RecvKeepAlive
Last Error: None
Export: [ redist_static ]
Options: <Preference LocalAddress PeerAS Refresh>
Options: <AdvertiseBGPStatic>

Copyright 2014, Juniper Networks, Inc.

1485

Interfaces Fundamentals for Routing Devices

Local Address: 10.255.7.248 Holdtime: 90 Preference: 170 Outbound Timer: 50

Number of flaps: 0
Peer ID: 10.255.7.250
Local ID: 10.255.7.248
Active Holdtime: 90
Keepalive Interval: 30
Group index: 0
Peer index: 0
BFD: disabled, down
NLRI for restart configured on peer: inet-unicast
NLRI advertised by peer: inet-unicast
NLRI for this session: inet-unicast
Peer supports Refresh capability (2)
Stale routes from peer are kept for: 300
Peer does not support Restarter functionality
NLRI that restart is negotiated for: inet-unicast
NLRI of received end-of-rib markers: inet-unicast
NLRI of all end-of-rib markers sent: inet-unicast
Peer supports 4 byte AS extension (peer-as 10)
Peer does not support Addpath
Table inet.0 Bit: 10000
RIB State: BGP restart is complete
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Accepted prefixes:
1
Suppressed due to damping:
0
Advertised prefixes:
1
Last traffic (seconds): Received 9
Sent 5
Checked 5
Input messages: Total 36
Updates 2
Refreshes 0
Octets 718
Output messages: Total 37
Updates 1
Refreshes 0
Octets 796
Output Queue[0]: 0 (inet.0, inet-unicast)
Peer: 10.255.162.214+52193 AS 100 Local: 10.255.167.205+179 AS 100
Type: Internal
State: Established (route reflector client)Flags: <Sync>
Last State: OpenConfirm
Last Event: RecvKeepAlive
Last Error: None
Options: <Preference LocalAddress Cluster AddressFamily Rib-group Refresh>
Address families configured: inet-unicast inet-vpn-unicast route-target
Local Address: 10.255.167.205 Holdtime: 90 Preference: 170
Number of flaps: 0
Peer ID: 10.255.162.214 Local ID: 10.255.167.205
Active Holdtime: 90
Keepalive Interval: 30
Group index: 0
Peer index: 1

show bgp neighbor (CLNS)

user@host> show bgp neighbor
Peer: 10.245.245.1+179 AS 200 Local: 10.245.245.3+3770 AS 100
Type: External
State: Established
Flags: <ImportEval Sync>
Last State: OpenConfirm
Last Event: RecvKeepAlive
Last Error: None
Options: <Multihop Preference LocalAddress HoldTime AddressFamily PeerAS
Rib-group Refresh>
Address families configured: iso-vpn-unicast
Local Address: 10.245.245.3 Holdtime: 90 Preference: 170
Number of flaps: 0
Peer ID: 10.245.245.1
Local ID: 10.245.245.3
Active Holdtime: 90
Keepalive Interval: 30
Peer index: 0
NLRI advertised by peer: iso-vpn-unicast
NLRI for this session: iso-vpn-unicast
Peer supports Refresh capability (2)
Table bgp.isovpn.0 Bit: 10000
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: in sync
Active prefixes:
3

1486

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Received prefixes:
3
Suppressed due to damping:
0
Advertised prefixes:
3
Table aaaa.iso.0
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: not advertising
Active prefixes:
3
Received prefixes:
3
Suppressed due to damping:
0
Last traffic (seconds): Received 6
Sent 5
Checked 5
Input messages: Total 1736
Updates 4
Refreshes 0
Output messages: Total 1738
Updates 3
Refreshes 0
Output Queue[0]: 0 (bgp.isovpn.0, iso-vpn-unicast)
Output Queue[1]: 0 (aaaa.iso.0, iso-vpn-unicast)

Octets 33385
Octets 33305

show bgp neighbor (Layer 2 VPN)

user@host> show bgp neighbor
Peer: 10.69.103.2
AS 65100 Local: 10.69.103.1
AS 65103
Type: External
State: Active
Flags: <ImportEval>
Last State: Idle
Last Event: Start
Last Error: None
Export: [ BGP-INET-import ]
Options: <Preference LocalAddress HoldTime GracefulRestart AddressFamily
PeerAS
Refresh>
Address families configured: inet-unicast
Local Address: 10.69.103.1 Holdtime: 90 Preference: 170
Number of flaps: 0
Peer: 10.69.104.2
AS 65100 Local: 10.69.104.1
AS 65104
Type: External
State: Active
Flags: <ImportEval>
Last State: Idle
Last Event: Start
Last Error: None
Export: [ BGP-L-import ]
Options: <Preference LocalAddress HoldTime GracefulRestart AddressFamily PeerAS
Refresh>
Address families configured: inet-labeled-unicast
Local Address: 10.69.104.1 Holdtime: 90 Preference: 170
Number of flaps: 0
Peer: 10.255.14.182+179 AS 69
Local: 10.255.14.176+2131 AS 69
Type: Internal
State: Established
Flags: <ImportEval>
Last State: OpenConfirm
Last Event: RecvKeepAlive
Last Error: None
Options: <Preference LocalAddress HoldTime GracefulRestart AddressFamily
Rib-group Refresh>
Address families configured: inet-vpn-unicast l2vpn
Local Address: 10.255.14.176 Holdtime: 90 Preference: 170
Number of flaps: 0
Peer ID: 10.255.14.182
Local ID: 10.255.14.176
Active Holdtime: 90
Keepalive Interval: 30
NLRI for restart configured on peer: inet-vpn-unicast l2vpn
NLRI advertised by peer: inet-vpn-unicast l2vpn
NLRI for this session: inet-vpn-unicast l2vpn
Peer supports Refresh capability (2)
Restart time configured on the peer: 120
Stale routes from peer are kept for: 300
Restart time requested by this peer: 120
NLRI that peer supports restart for: inet-vpn-unicast l2vpn
NLRI peer can save forwarding state: inet-vpn-unicast l2vpn
NLRI that peer saved forwarding for: inet-vpn-unicast l2vpn
NLRI that restart is negotiated for: inet-vpn-unicast l2vpn

Copyright 2014, Juniper Networks, Inc.

1487

Interfaces Fundamentals for Routing Devices

NLRI of received end-of-rib markers: inet-vpn-unicast l2vpn

Table bgp.l3vpn.0 Bit: 10000
RIB State: BGP restart in progress
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
10
Received prefixes:
10
Suppressed due to damping: 0
Table bgp.l2vpn.0 Bit: 20000
RIB State: BGP restart in progress
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Suppressed due to damping: 0
Table BGP-INET.inet.0 Bit: 30000
RIB State: BGP restart in progress
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Suppressed due to damping: 0
Table BGP-L.inet.0 Bit: 40000
RIB State: BGP restart in progress
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Suppressed due to damping: 0
Table LDP.inet.0 Bit: 50000
RIB State: BGP restart is complete
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Suppressed due to damping: 0
Table OSPF.inet.0 Bit: 60000
RIB State: BGP restart is complete
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Suppressed due to damping: 0
Table RIP.inet.0 Bit: 70000
RIB State: BGP restart is complete
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Suppressed due to damping: 0
Table STATIC.inet.0 Bit: 80000
RIB State: BGP restart is complete
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Suppressed due to damping: 0
Table L2VPN.l2vpn.0 Bit: 90000
RIB State: BGP restart is complete
RIB State: VPN restart in progress
Send state: in sync

1488

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Active prefixes:
1
Received prefixes:
1
Suppressed due to damping: 0
Last traffic (seconds): Received 0
Sent 0
Checked 0
Input messages: Total 14
Updates 13
Refreshes 0
Output messages: Total 3
Updates 0
Refreshes 0
Output Queue[0]: 0 (bgp.l3vpn.0, inet-vpn-unicast)
Output Queue[1]: 0 (bgp.l2vpn.0, inet-vpn-unicast)
Output Queue[2]: 0 (BGP-INET.inet.0, inet-vpn-unicast)
Output Queue[3]: 0 (BGP-L.inet.0, inet-vpn-unicast)
Output Queue[4]: 0 (LDP.inet.0, inet-vpn-unicast)
Output Queue[5]: 0 (OSPF.inet.0, inet-vpn-unicast)
Output Queue[6]: 0 (RIP.inet.0, inet-vpn-unicast)
Output Queue[7]: 0 (STATIC.inet.0, inet-vpn-unicast)
Output Queue[8]: 0 (L2VPN.l2vpn.0, inet-vpn-unicast)

Octets 1053
Octets 105

show bgp neighbor (Layer 3 VPN)

user@host> show bgp neighbor
Peer: 4.4.4.4+179
AS 10045 Local: 5.5.5.5+1214
AS 10045
Type: Internal
State: Established
Flags: <ImportEval>
Last State: OpenConfirm
Last Event: RecvKeepAlive
Last Error: None
Export: [ match-all ] Import: [ match-all ]
Options: <Preference LocalAddress HoldTime GracefulRestart AddressFamily
Rib-group Refresh>
Address families configured: inet-vpn-unicast
Local Address: 5.5.5.5 Holdtime: 90 Preference: 170
Flags for NLRI inet-labeled-unicast: TrafficStatistics
Traffic Statistics: Options: all File: /var/log/bstat.log
size 131072 files 10
Traffic Statistics Interval: 60
Number of flaps: 0
Peer ID: 192.168.1.110
Local ID: 192.168.1.111
Active Holdtime: 90
Keepalive Interval: 30
NLRI for restart configured on peer: inet-vpn-unicast
NLRI advertised by peer: inet-vpn-unicast
NLRI for this session: inet-vpn-unicast
Peer supports Refresh capability (2)
Restart time configured on the peer: 120
Stale routes from peer are kept for: 300
Restart time requested by this peer: 120
NLRI that peer supports restart for: inet-vpn-unicast
NLRI peer can save forwarding state: inet-vpn-unicast
NLRI that peer saved forwarding for: inet-vpn-unicast
NLRI that restart is negotiated for: inet-vpn-unicast
NLRI of received end-of-rib markers: inet-vpn-unicast
NLRI of all end-of-rib markers sent: inet-vpn-unicast
Table bgp.l3vpn.0 Bit: 10000
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Suppressed due to damping: 0
Table vpn-green.inet.0 Bit: 20001
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: in sync
Active prefixes:
2
Received prefixes:
2

Copyright 2014, Juniper Networks, Inc.

1489

Interfaces Fundamentals for Routing Devices

Suppressed due to damping: 0

Last traffic (seconds): Received 15
Sent 20
Checked 20
Input messages: Total 40
Updates 2
Refreshes 0
Output messages: Total 44
Updates 2
Refreshes 0
Output Queue[0]: 0 (bgp.l3vpn.0, inet-vpn-unicast)
Output Queue[1]: 0 (vpn-green.inet.0, inet-vpn-unicast)
Trace options: detail packets
Trace file: /var/log/bgpgr.log size 131072 files 10

Octets 856
Octets 1066

show bgp neighbor neighbor-address

user@host> show bgp neighbor 192.168.1.111
Peer: 10.255.245.12+179 AS 35 Local: 10.255.245.13+2884 AS 35
Type: Internal
State: Established (route reflector client)Flags: <Sync>
Last State: OpenConfirm
Last Event: RecvKeepAlive
Last Error: None
Options: <Preference LocalAddress HoldTime Cluster AddressFamily Rib-group
Refresh>
Address families configured: inet-vpn-unicast inet-labeled-unicast
Local Address: 10.255.245.13 Holdtime: 90 Preference: 170
Flags for NLRI inet-vpn-unicast: AggregateLabel
Flags for NLRI inet-labeled-unicast: AggregateLabel
Number of flaps: 0
Peer ID: 10.255.245.12
Local ID: 10.255.245.13
Active Holdtime: 90
Keepalive Interval: 30
BFD: disabled
NLRI advertised by peer: inet-vpn-unicast inet-labeled-unicast
NLRI for this session: inet-vpn-unicast inet-labeled-unicast
Peer supports Refresh capability (2)
Restart time configured on the peer: 300
Stale routes from peer are kept for: 60
Restart time requested by this peer: 300
NLRI that peer supports restart for: inet-unicast inet6-unicast
NLRI that restart is negotiated for: inet-unicast inet6-unicast
NLRI of received end-of-rib markers: inet-unicast inet6-unicast
NLRI of all end-of-rib markers sent: inet-unicast inet6-unicast
Table inet.0 Bit: 10000
RIB State: restart is complete
Send state: in sync
Active prefixes: 4
Received prefixes: 6
Suppressed due to damping: 0
Table inet6.0 Bit: 20000
RIB State: restart is complete
Send state: in sync
Active prefixes: 0
Received prefixes: 2
Suppressed due to damping: 0
Last traffic (seconds): Received 3
Sent 3
Checked 3
Input messages: Total 9
Updates 6
Refreshes 0
Octets 403
Output messages: Total 7
Updates 3
Refreshes 0
Octets 365
Output Queue[0]: 0 (inet.0, inet-unicast)
Output Queue[1]: 0 (inet6.0, inet6-unicast)
Trace options: detail packets
Trace file: /var/log/bgpgr size 131072 files 10

show bgp neighbor neighbor-address

user@host> show bgp neighbor 192.168.4.222
Peer: 192.168.4.222+4902 AS 65501 Local: 192.168.4.221+179 AS 65500
Type: External
State: Established
Flags: <Sync>

1490

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Last State: OpenConfirm

Last Event: RecvKeepAlive
Last Error: Cease
Export: [ export-policy ] Import: [ import-policy ]
Options: <Preference HoldTime AddressFamily PeerAS PrefixLimit Refresh>
Address families configured: inet-unicast inet-multicast
Holdtime: 60000 Preference: 170
Number of flaps: 4
Last flap event: RecvUpdate
Error: 'Cease' Sent: 5 Recv: 0
Peer ID: 10.255.245.6
Local ID: 10.255.245.5
Active Holdtime: 60000
Keepalive Interval: 20000
Peer index: 0
BFD: disabled, down
Local Interface: fxp0.0
NLRI advertised by peer: inet-unicast inet-multicast
NLRI for this session: inet-unicast inet-multicast
Peer supports Refresh capability (2)
Table inet.0 Bit: 10000
RIB State: BGP restart is complete
Send state: in sync
Active prefixes:
8
Received prefixes:
10
Accepted prefixes:
10
Suppressed due to damping:
0
Advertised prefixes:
3
Table inet.2 Bit: 20000
RIB State: BGP restart is complete
Send state: in sync
Active prefixes:
0
Received prefixes:
0
Accepted prefixes:
0
Suppressed due to damping:
0
Advertised prefixes:
0
Last traffic (seconds): Received 357 Sent 357 Checked 357
Input messages: Total 4 Updates 2 Refreshes 0 Octets 211
Output messages: Total 4 Updates 1 Refreshes 0 Octets 147
Output Queue[0]: 0 (inet.0, inet-unicast)
Output Queue[1]: 0 (inet.2, inet-multiicast)
Trace options: all
Trace file: /var/log/bgp size 10485760 files 10

show bgp neighbor orf neighbor-address detail

user@host > show bgp neighbor orf 192.168.165.56 detail
Peer: 192.168.165.56+179 Type: External
Group: ext1
inet-unicast
Filter updates recv:
1 Immediate:
1
Filter: prefix-based receive
Received filter entries:
seq 1: prefix 2.2.2.2/32: minlen 32: maxlen 32: match deny:
inet6-unicast
Filter updates recv:
0 Immediate:
Filter: prefix-based receive
Received filter entries:
*:*

Copyright 2014, Juniper Networks, Inc.

1491

Interfaces Fundamentals for Routing Devices

show bgp replication

Syntax

show bgp replication

Release Information

Command introduced in JUNOS Release 8.5.

Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for logical-system option introduced in Junos OS Release 13.3

Description

Displays the status of BGP state replication between the master and backup Routing
Engines on devices that have nonstop active routing configured on them.

Options

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level

view

Related
Documentation

List of Sample Output

show bgp replication logical-system

show bgp replication (for Master) on page 1493

show bgp replication (for Backup) on page 1493

Output Fields

Table 89 on page 1492 lists the output fields for the show bgp replication command. Output
fields are listed in the approximate order in which they appear.

Table 89: show bgp replication Output Fields

Field Name

Field Description

session state

State of the current internal BGP state replication session, Up or Down, and the duration for which
the session has been in the indicated state.

flaps

Total number of flaps that occurred.

protocol state

Current state of the protocol operation, Active, Connect, Idle, and the duration for which the protocol
has been in the indicated state.

synchronization state

Synchronization state at the time of executing the command. The states can be:

1492

Idle

NeighborIndicates that the neighbor state synchronization is in progress.

AckWaitIndicates that the request processing is over.

ORFIndicates that the outbound routing filter synchronization is in progress.

RIBIndicates that the routing table synchronization is in progress.

Complete

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Table 89: show bgp replication Output Fields (continued)

Field Name

Field Description

number of peers waiting

Total number of peers waiting for various messages:

AckWaitNumber of peers waiting for a connection establishment or completed acknowledgment

messages.

messages sent

messages received

SoWaitNumber of peers waiting for TCP socket-related operations.

ScheduledNumber of peers being synchronized.

Number of various types of messages that have been sent since internal replication session became
active:

OpenNumber of Open messages sent.

EstablishNumber of connection establishment acknowledgment messages sent.

UpdateNumber of update messages sent.

ErrorNumber of error messages sent.

CompleteNumber of connection complete acknowledgment messages sent.

Total number of messages received:

OpenNumber of Open messages received.

RequestNumber of request messages received:

WildcardNumber of requests received that used wildcards in the target address.

TargetedNumber of requests received that used a specific address.

EstablishAckNumber of connection establishment acknowledgement messages received.

CompleteAckNumber of connection completed acknowledgement messages received.

Sample Output
show bgp replication (for Master)
user@host> show bgp replication
Synchronization master:
Session state: Up, Since: 44:07
Flaps: 0
Protocol state: Idle, Since: 14
Synchronization state: Complete
Number of peers waiting: AckWait: 0, SoWait: 0, Scheduled: 0
Messages sent: Open 1, Establish 924, Update 381, Error 60, Complete 114
Messages received: Open 1, Request 1 wildcard 113 targeted, EstablishAck 924,
CompleteAck 114

show bgp replication (for Backup)

user@host> show bgp replication
Synchronization backup:
State: Established 13 ago
, Unsync timer: 2
Unsync entry queue:
Instance: 0 Neighbor: 30.30.30.1 elapsed: 7
Instance: 0 Neighbor: 40.40.40.3 elapsed: 7
Instance: 0 Neighbor: 40.40.40.4 elapsed: 7

Copyright 2014, Juniper Networks, Inc.

1493

Interfaces Fundamentals for Routing Devices

Instance:
Instance:
Instance:
Instance:

1494

0
0
0
0

Neighbor:
Neighbor:
Neighbor:
Neighbor:

40.40.40.5
40.40.40.6
40.40.40.1
40.40.40.2

elapsed:
elapsed:
elapsed:
elapsed:

7
7
7
7

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

show bgp summary

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1495

Syntax (EX Series Switch and QFX Series) on page 1495
show bgp summary
<exact-instance instance-name>
<group group-name>
<instance instance-name>
<logical-system (all | logical-system-name)>
show bgp summary
<exact-instance instance-name>
<instance instance-name>

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.3 for the QFX Series.
exact-instance option introduced in Junos OS Release 11.4.
group option introduced in Junos OS Release 13.3.
Display BGP summary information.
noneDisplay BGP summary information for all routing instances.
exact-instance instance-name(Optional) Display information for the specified instance

only.
groupDisplay overview of bgp information for a particular group
instance instance-name(Optional) Display information for all routing instances whose

name begins with this string (for example, cust1, cust11, and cust111 are all displayed
when you run the show bgp summary instance cust1 command). The instance name
can be master for the main instance, or any valid configured instance name or its
prefix.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show bgp summary (When a Peer Is Not Established) on page 1498

show bgp summary (When a Peer Is Established) on page 1498
show bgp summary (CLNS) on page 1498
show bgp summary (Layer 2 VPN) on page 1499
show bgp summary (Layer 3 VPN) on page 1499
show bgp summary group on page 1499
Table 90 on page 1496 describes the output fields for the show bgp summary command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1495

Interfaces Fundamentals for Routing Devices

Table 90: show bgp summary Output Fields

Field Name

Field Description

Groups

Number of BGP groups.

Peers

Number of BGP peers.

Down peers

Number of down BGP peers.

Table

Name of routing table.

Tot Paths

Total number of paths.

Act Paths

Number of active routes.

Suppressed

Number of routes currently inactive because of damping or other reasons. These routes do not appear
in the forwarding table and are not exported by routing protocols.

History

Number of withdrawn routes stored locally to keep track of damping history.

Damp State

Number of routes with a figure of merit greater than zero, but still active because the value has not
reached the threshold at which suppression occurs.

Pending

Routes in process by BGP import policy.

Peer

Address of each BGP peer. Each peer has one line of output.

AS

Peer's AS number.

InPkt

Number of packets received from the peer.

OutPkt

Number of packets sent to the peer.

OutQ

Number of BGP packets that are queued to be transmitted to a particular neighbor. It normally is 0
because the queue usually is emptied quickly.

Flaps

Number of times the BGP session has gone down and then come back up.

Last Up/Down

Last time since the neighbor transitioned to or from the established state.

1496

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

Table 90: show bgp summary Output Fields (continued)

Field Name

Field Description

State|#Active
/Received/Accepted
/Damped

Multipurpose field that displays information about BGP peer sessions. The fields contents depend
upon whether a session is established and whether it was established on the main routing device or
in a routing instance.

If a peer is not established, the field shows the state of the peer session: Active, Connect, or Idle.
In general, the Idle state is the first stage of a connection. BGP is waiting for a Start event. A session
can be idle for other reasons as well. The reason that a session is idle is sometimes displayed. For
example: Idle (Removal in progress) or Idle (LicenseFailure).

If a BGP session is established on the main routing device, the field shows the number of active,
received, accepted, and damped routes that are received from a neighbor and appear in the inet.0
(main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the
following:

8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer
appear in the inet.0 routing table.

2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer
appear in the inet.2 routing table.

If a BGP session is established in a routing instance, the field indicates the established (Establ)
state, identifies the specific routing table that receives BGP updates, and shows the number of
active, received, and damped routes that are received from a neighbor. For example, Establ
VPN-AB.inet.0: 2/4/0 indicates the following:

The BGP session is established.

Routes are received in the VPN-AB.inet.0 routing table.

The local routing device has two active routes, four received routes, and no damped routes from
a BGP peer.

When a BGP session is established, the peers are exchanging update messages.

Copyright 2014, Juniper Networks, Inc.

1497

Interfaces Fundamentals for Routing Devices

Sample Output
show bgp summary (When a Peer Is Not Established)
user@host> show bgp summary
Groups: 2 Peers: 4 Down peers: 1
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
inet.0
6
4
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
State|#Active/Received/Damped...
10.0.0.3
65002
86
90
0
2
42:54 0/0/0
0/0/0
10.0.0.4

65002

90

91

42:54 0/2/0

0/0/0
10.0.0.6
10.1.12.1

65002
65001

87
89

90
89

0
0

3
1

3 Active
42:54 4/4/0

0/0/0

show bgp summary (When a Peer Is Established)

user@host> show bgp summary
Groups: 1 Peers: 3 Down peers: 0
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
inet.0
6
4
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
State|#Active/Received/Damped...
10.0.0.2
65002
88675
88652
0
2
42:38 2/4/0
0/0/0
10.0.0.3

65002

54528

54532

2w4d22h 0/0/0

0/0/0
10.0.0.4

65002

51597

51584

2w3d22h 2/2/0

0/0/0
user@host> show bgp summary logical-system R3
Groups: 2 Peers: 2 Down peers: 0
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
bgp.l3vpn.0
2
2
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
State|#Active/Received/Accepted/Damped...
1.1.1.2
2
204
206
0
0
1:30:59
Establ
bgp.l3vpn.0: 2/2/2/0
red.inet.0: 2/2/2/0
10.1.1.10
3
206
207
0
0
1:31:36
Establ
red.inet.0: 2/2/2/0

show bgp summary (CLNS)

user@host> show bgp summary
Groups: 1 Peers: 1 Down peers: 0
Peer
AS
InPkt
State|#Active/Received/Damped...
10.245.245.1
200
1735

1498

OutPkt

OutQ

1737

Flaps Last Up/Dwn

0

14:26:12 Establ

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

bgp.isovpn.0: 3/3/0
aaaa.iso.0: 3/3/0

show bgp summary (Layer 2 VPN)

user@host> show bgp summary
Groups: 1 Peers: 5 Down peers: 0
Table
Tot Paths Act Paths Suppressed
History Damp State
bgp.l2vpn.0
1
1
0
0
0
inet.0
0
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last
Up/Dwn State|#Active/Received/Damped...
10.255.245.35
65299
72
74
0
1
19:00
bgp.l2vpn.0: 1/1/0
frame-vpn.l2vpn.0: 1/1/0
10.255.245.36
65299
2164
2423
0
4
19:50
bgp.l2vpn.0: 0/0/0
frame-vpn.l2vpn.0: 0/0/0
10.255.245.37
65299
36
37
0
4
17:07
inet.0: 0/0/0
10.255.245.39
65299
138
168
0
6
53:48
bgp.l2vpn.0: 0/0/0
frame-vpn.l2vpn.0: 0/0/0
10.255.245.69
65299
134
140
0
6
53:42
inet.0: 0/0/0

Pending
0
0

Establ

Establ

Establ
Establ

Establ

show bgp summary (Layer 3 VPN)

user@host> show bgp summary
Groups: 2 Peers: 2 Down peers: 0
Table
Tot Paths Act Paths Suppressed
History Damp State Pending
bgp.l3vpn.0
2
2
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
State|#Active/Received/Damped...
10.39.1.5
2
21
22
0
0
6:26 Establ
VPN-AB.inet.0: 1/1/0
10.255.71.15
1
19
21
0
0
6:17 Establ
bgp.l3vpn.0: 2/2/0
VPN-A.inet.0: 1/1/0
VPN-AB.inet.0: 2/2/0
VPN-B.inet.0: 1/1/0

show bgp summary group

user@host> show bgp summary group Group2
Groups: 3 Peers: 3 Down peers: 3
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
inet.0
0
0
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
State|#Active/Received/Accepted/Damped...
10.0.0.1
56
0
0
0
0
51
Idle
user@host> show bgp summary logical-system R3 group toR4
Groups: 2 Peers: 2 Down peers: 0
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
bgp.l3vpn.0
2
2
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
State|#Active/Received/Accepted/Damped...
10.1.1.10
3
207
207
0
0
1:31:40

Copyright 2014, Juniper Networks, Inc.

1499

Interfaces Fundamentals for Routing Devices

Establ
red.inet.0: 2/2/2/0

Sample Output

1500

Copyright 2014, Juniper Networks, Inc.

Chapter 17: BGP Operational Commands

show policy damping

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1501

Syntax (EX Series Switch and QFX Series) on page 1501
show policy damping
<logical-system (all | logical-system-name)>
show policy damping

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.3 for the QFX Series.
Display information about BGP route flap damping parameters.
noneDisplay information about BGP route flap damping parameters.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Additional Information

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

In the output from this command, figure-of-merit values correlate with the probability
of future instability of a routing device. Routes with higher figure-of-merit values are
suppressed for longer periods of time. The figure-of-merit value decays exponentially
over time. A figure-of-merit value of zero is assigned to each new route. The value is
increased each time the route is withdrawn or readvertised, or when one of its path
attributes changes.
view

Configuring BGP Flap Damping Parameters in the Routing Policies, Firewall Filters,
and Traffic Policers Feature Guide for Routing Devices

clear bgp damping on page 1462

show route damping on page 1970

show policy damping on page 1502

Table 91 on page 1502 describes the output fields for the show policy damping command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1501

Interfaces Fundamentals for Routing Devices

Table 91: show policy damping Output Fields

Field Name

Field Description

Halflife

Decay half-life, in minutes. The value represents the period during which the accumulated
figure-of-merit value is reduced by half if the route remains stable. If a route has flapped, but then
becomes stable, the figure-of-merit value for the route decays exponentially. For example, for a route
with a figure-of-merit value of 1500, if no incidents occur, its figure-of-merit value is reduced to 750
after 15 minutes and to 375 after another 15 minutes.

Reuse merit

Figure-of-merit value below which a suppressed route can be used again. A suppressed route becomes
reusable when its figure-of-merit value decays to a value below a reuse threshold, and the route once
again is considered usable and can be installed in the forwarding table and exported from the routing
table.

Suppress/cutoff merit

Figure-of-merit value above which a route is suppressed for use or inclusion in advertisements. When
a route's figure-of-merit value reaches a particular level, called the cutoff or suppression threshold,
the route is suppressed. When a route is suppressed, the routing table no longer installs the route into
the forwarding table and no longer exports this route to any of the routing protocols.

Maximum suppress
time

Maximum hold-down time, in minutes. The value represents the maximum time that a route can be
suppressed no matter how unstable it has been before this period of stability.

Computed values

Merit ceilingMaximum merit that a flapping route can collect.

Maximum decayMaximum decay half-life, in minutes.

Sample Output
show policy damping
user@host> show policy damping
Default damping information:
Halflife: 15 minutes
Reuse merit: 750 Suppress/cutoff merit: 3000
Maximum suppress time: 60 minutes
Computed values:
Merit ceiling: 12110
Maximum decay: 6193
Damping information for "standard-damping":
Halflife: 10 minutes
Reuse merit: 4000 Suppress/cutoff merit: 8000
Maximum suppress time: 30 minutes
Computed values:
Merit ceiling: 32120
Maximum decay: 12453

1502

Copyright 2014, Juniper Networks, Inc.

CHAPTER 18

ES-IS Operational Commands

clear esis adjacency

clear esis statistics

show esis adjacency

show esis interface

show esis statistics

Copyright 2014, Juniper Networks, Inc.

1503

Interfaces Fundamentals for Routing Devices

clear esis adjacency

Syntax

Release Information
Description
Options

clear esis adjacency

<instance instance-name>
<interface interface-name)>
<neighbor>

Command introduced before Junos OS Release 7.4.

Clear End System-to-Intermediate System (ES-IS) adjacencies.
noneClear all ES-IS adjacencies.
instance instance-name(Optional) Clear adjacencies for the specified routing instance

only.
interface interface-name(Optional) Clear adjacencies for the specified interface only.
neighbor(Optional) Clear adjacencies for the specified neighbor only.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show esis adjacency on page 1506

clear esis adjacency on page 1504

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear esis adjacency
user@host> clear esis adjacency

1504

Copyright 2014, Juniper Networks, Inc.

Chapter 18: ES-IS Operational Commands

clear esis statistics

Syntax

Release Information
Description
Options

clear esis statistics

<instance instance-name>

Command introduced before Junos OS Release 7.4.

Clear End System-to-Intermediate System (ES-IS) packet statistics.
noneClear ES-IS packet statistics for all routing instances.
instance instance-name(Optional) Clear ES-IS packet statistics for the specified routing

instance only.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show esis statistics on page 1510

clear esis statistics on page 1505

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear esis statistics
user@host> clear esis statistics

Copyright 2014, Juniper Networks, Inc.

1505

Interfaces Fundamentals for Routing Devices

show esis adjacency

Syntax

Release Information
Description

Options

show esis adjacency

<brief | detail | extensive>
<esis-neighbor-id>
<instance instance-name>
<interface interface-name)>

Command introduced before Junos OS Release 7.4.

(J Series and PTX Series routers only) Display End System-to-Intermediate System
(ES-IS) adjacencies.
none(Same as brief) Display all ES-IS adjacencies.
brief | detail | extensive(Optional) Display the specified level of output.
esis-neighbor-id(Optional) Display adjacencies for the specified neighbor's network

service access point (NSAP) only.

instance instance-name(Optional) Display adjacencies for the specified routing instance

only.
interface interface-name(Optional) Display adjacencies for the specified interface only.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear esis adjacency on page 1504

show esis adjacency on page 1507

show esis adjacency brief on page 1507
show esis adjacency detail on page 1507
show esis adjacency extensive on page 1507
Table 92 on page 1506 describes the output fields for the show esis adjacency command.
Output fields are listed in the approximate order in which they appear.

Table 92: show esis adjacency Output Fields

Field Name

Field Description

Level of Output

Nbr Type

Type of network service access point (NSAP) of this neighbor.

brief none

NSAP/NET

NSAP of this neighbor.

All levels

Type

Type of NSAP of this neighbor.

detail extensive

Hold (secs)

Holdtime interval advertised by this neighbor.

brief none

Interface

Interface through which the neighbor is reachable.

All levels

1506

Copyright 2014, Juniper Networks, Inc.

Chapter 18: ES-IS Operational Commands

Table 92: show esis adjacency Output Fields (continued)

Field Name

Field Description

Level of Output

Advertised
holdtime

Holdtime interval advertised by this neighbor.

detail extensive

Expires in

How long until the adjacency expires, in seconds.

detail extensive

SNPA

Subnetwork point of attachment (MAC address of the neighbor).

detail extensive

Transition log

List of recent transitions.

extensive

WhenTime of advertisement from this neighbor.

StateState of the adjacency: Up, Down, New, One-way, Initializing, or

Rejected.

EventEvent causing the state.

Down reasonReason the adjacency is down.

Sample Output
show esis adjacency
user@host> show esis adjacency
Nbr NSAP/NET
Hold Interface
Type
(secs)
IS
47.0005.80ff.f800.0000.0108.0001.0102.5501.6008
135 fe-0/0/0.0

show esis adjacency brief

The output for the show esis adjacency brief command is identical to that for the show
esis adjacency command. For sample output, see show esis adjacency on page 1507.
show esis adjacency detail
user@host> show esis adjacency detail
NSAP/NET: 47.0005.80ff.f800.0000.0108.0001.0102.5501.6008, Type: IS
Interface: fe-0/0/0.0, Advertised hold time: 180 secs, Expires in: 173 secs
SNPA: 0:5:85:c1:73:71

show esis adjacency extensive

user@host> show esis adjacency extensive
NSAP/NET: 47.0005.80ff.f800.0000.0108.0001.0102.5501.6008, Type: IS
Interface: fe-0/0/0.0, Advertised hold time: 180 secs, Expires in: 167 secs
SNPA: 0:5:85:c1:73:71
Transition log:
When
State
Event
Down reason
Sun Nov 26 22:07:35
Up
Received ISH

Copyright 2014, Juniper Networks, Inc.

1507

Interfaces Fundamentals for Routing Devices

show esis interface

Syntax

Release Information
Description

Options

show esis interface

<brief | detail | extensive>
<instance instance-name>
<interface interface-name)>

Command introduced before Junos OS Release 7.4.

(J Series and PTX Series routers only) Display End System-to-Intermediate System
(ES-IS) interface information.
none(Same as brief) Display information for all configured ES-IS interfaces.
brief | detail | extensive(Optional) Display the specified level of output.
instance instance-name(Optional) Display configured interfaces for the specified routing

instance only.
interface interface-name(Optional) Display information about the specified interface

only.
Required Privilege
Level
List of Sample Output

Output Fields

view

show esis interface on page 1509

show esis interface brief on page 1509
show esis interface detail on page 1509
show esis interface extensive on page 1509
Table 93 on page 1508 describes the output fields for the show esis interface command.
Output fields are listed in the approximate order in which they appear.

Table 93: show esis interface Output Fields

Field Name

Field Description

Level of Output

Interface

Interface through which the adjacency is made.

All levels

Receives

Types of hello messages that are received.

All levels

Sends

Types of hello messages that are sent.

All levels

Hello interval

Interface's hello interval, in seconds.

All levels

Adjacencies or Num
Adj

Number of adjacencies established on this interface.

All levels

Holdtime

Interface's hold time, in seconds.

detail extensive

State

Internal implementation information.

detail extensive

1508

Copyright 2014, Juniper Networks, Inc.

Chapter 18: ES-IS Operational Commands

Table 93: show esis interface Output Fields (continued)

Field Name

Field Description

Level of Output

End system
configuration timer

Time, in seconds, for the end system to configure itself for ES-IS.

detail extensive

Interface index

Index value.

detail extensive

NET used in hello

Network entity title used in hello messages.

detail extensive

Sample Output
show esis interface
user@host> show esis interface
Interface
Receives
fe-0/0/0.0
ISH
lo0.0
ISH

Sends
ISH
-

Hello Interval
60.00
60.00

Num Adj
1
0

show esis interface brief

The output for the show esis interface brief command is identical to that for the show
esis interface command. For sample output, see show esis interface on page 1509.
show esis interface detail
user@host> show esis interface detail
Interface: fe-0/0/0.0
Receives: ISH, Sends: ISH, Hello interval: 60.00
Adjacencies: 1, Holdtime: 180, End system configuration timer: 180
Interface index: 68, State: 0x2
NET used in hello: 47.0005.80ff.f800.0000.0108.0001.0102.5501.6007
Interface: lo0.0
Receives: ISH, Sends: - , Hello interval: 60.00
Adjacencies: 0, Holdtime: 180, End system configuration timer: 180
Interface index: 64, State: 0x2
NET used in hello: 47.0005.80ff.f800.0000.0108.0001.0102.5501.6007

show esis interface extensive

The output for the show esis interface extensive command is identical to that for the
show esis interface detail command. For sample output, see show esis interface detail
on page 1509.

Copyright 2014, Juniper Networks, Inc.

1509

Interfaces Fundamentals for Routing Devices

show esis statistics

Syntax

Release Information
Description

Options

show esis statistics

<instance instance-name>

Command introduced before Junos OS Release 7.4.

(J Series and PTX Series routers only) Display End System-to-Intermediate System
(ES-IS) packet statistics.
noneDisplay ES-IS packet statistics for all routing instances.
instance instance-name(Optional) Display ES-IS statistics for the specified routing

instance only.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

clear esis statistics on page 1505

show esis statistics on page 1510

Table 94 on page 1510 describes the output fields for the show esis statistics command.
Output fields are listed in the approximate order in which they appear.

Table 94: show esis statistics Output Fields

Field Name

Field Description

PDU type

Protocol data unit type.

Received

Number of PDUs received since IS-IS started or since the statistics

were set to zero.

Processed

Number of PDUs received less the number dropped.

Drops

Number of PDUs dropped.

Sent

Number of PDUs transmitted since IS-IS started or since the

statistics were set to zero.

Total packets received/sent

Total number of PDUs received and transmitted since IS-IS started

or since the statistics were set to zero.

Sample Output
show esis statistics
user@host> show esis statistics
PDU type Received Processed Drops
ESH
3
3
0

1510

Sent
8

Copyright 2014, Juniper Networks, Inc.

Chapter 18: ES-IS Operational Commands

ISH
11
10
RD
0
0
Unknown
0
0
Totals
14
13
Total packets received: 14 sent:

Copyright 2014, Juniper Networks, Inc.

1
0
0
1
0

4
0
0
12

1511

Interfaces Fundamentals for Routing Devices

1512

Copyright 2014, Juniper Networks, Inc.

CHAPTER 19

IP Multicast Operational Commands

clear amt statistics

clear amt tunnel

clear igmp membership

clear igmp snooping membership

clear igmp snooping statistics

clear igmp statistics

clear mld membership

clear mld statistics

clear msdp cache

clear msdp statistics

clear multicast bandwidth-admission

clear multicast forwarding-cache

clear multicast scope

clear multicast sessions

clear multicast snooping statistics

clear multicast statistics

clear pgm negative-acknowledgments

clear pgm source-path-messages

clear pgm statistics

clear pim join

clear pim join-distribution

clear pim register

clear pim snooping join

clear pim snooping statistics

clear pim statistics

request pim multicast-tunnel rebalance

show amt statistics

show amt summary

Copyright 2014, Juniper Networks, Inc.

1513

Interfaces Fundamentals for Routing Devices

1514

show amt tunnel

show dvmrp interfaces

show dvmrp neighbors

show dvmrp prefix

show dvmrp prunes

show igmp group

show igmp interface

show igmp snooping interface

show igmp snooping membership

show igmp snooping statistics

show igmp statistics

show mld group

show mld interface

show mld statistics

show msdp

show msdp source

show msdp source-active

show msdp statistics

show multicast backup-pe-groups

show multicast flow-map

show multicast forwarding-cache statistics

show multicast interface

show multicast mrinfo

show multicast next-hops

show multicast pim-to-igmp-proxy

show multicast pim-to-mld-proxy

show multicast route

show multicast rpf

show multicast scope

show multicast snooping next-hops

show multicast sessions

show multicast snooping route

show multicast statistics

show multicast usage

show pgm negative-acknowledgments

show pgm source-path-messages

show pgm statistics

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim bootstrap

show pim interfaces

show pim join

show pim mdt

show pim mdt data-mdt-joins

show pim mdt data-mdt-limit

show pim neighbors

show pim rps

show pim snooping interfaces

show pim snooping join

show pim snooping neighbors

show pim snooping statistics

show pim source

show pim statistics

show sap listen

test msdp

Copyright 2014, Juniper Networks, Inc.

1515

Interfaces Fundamentals for Routing Devices

clear amt statistics

Syntax

Release Information
Description
Options

clear amt statistics

<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced in JUNOS Release 10.2.

Clear Automatic Multicast Tunneling (AMT) statistics.
noneClear the multicast statistics for all AMT tunnel interfaces.
instance instance-name(Optional) Clear AMT multicast statistics for the specified

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show amt statistics on page 1553

clear amt statistics on page 1516

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear amt statistics
user@host> clear amt statistics

1516

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear amt tunnel

Syntax

Release Information
Description

Options

clear amt tunnel

<gateway gateway-ip-addr> <port port-number>
<instance instance-name>
<logical-system (all | logical-system-name)>
<statistics>
<tunnel-interface interface-name>

Command introduced in JUNOS Release 10.2.

Clear the Automatic Multicast Tunneling (AMT) multicast state. Optionally, clear AMT
protocol statistics.
noneClear multicast state for all AMT tunnel interfaces.
gateway gateway-ip-addr port port-number(Optional) Clear the AMT multicast state

for the specified gateway address. If no port is specified, clear the AMT multicast
state for all AMT gateways with the given IP address.
instance instance-name(Optional) Clear the AMT multicast state for the specified

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

statistics(Optional) Clear multicast statistics for all AMT tunnels or for specified tunnels.
tunnel-interface interface-name(Optional) Clear the AMT multicast state for the specified

AMT tunnel interface.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

clear

show amt tunnel on page 1558

clear amt tunnel on page 1517

clear amt tunnel statistics gateway-address on page 1517
When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear amt tunnel
user@host> clear amt tunnel

clear amt tunnel statistics gateway-address

user@host> clear amt tunnel statistics gateway-address 100.31.1.21 port 4000

Copyright 2014, Juniper Networks, Inc.

1517

Interfaces Fundamentals for Routing Devices

clear igmp membership

List of Syntax

Syntax

Syntax on page 1518

Syntax (EX Series Switch and the QFX Series) on page 1518
clear igmp membership
<group address-range>
<interface interface-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

clear igmp membership

<group address-range>
<interface interface-name>

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.3 for the QFX Series.

Description
Options

Clear Internet Group Management Protocol (IGMP) group members.

noneClear all IGMP members on all interfaces and for all address ranges.
group address-range(Optional) Clear all IGMP members that are in a particular address

range. An example of a range is 224.2/16. If you omit the destination prefix length,
the default is /32.
interface interface-name(Optional) Clear all IGMP group members on an interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

clear

show igmp group on page 1569

show igmp interface on page 1573

clear igmp membership on page 1518

clear igmp membership interface on page 1519
clear igmp membership group on page 1520
See show igmp group for an explanation of output fields.

Sample Output
clear igmp membership
The following sample output displays IGMP group information before and after the clear
igmp membership command is entered:
user@host> show igmp group

1518

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Interface
so-0/0/0
so-0/0/0
so-0/0/0
so-0/0/0
local
local
local
local
local
local

Group
224.2.127.253
224.2.127.254
239.255.255.255
224.1.127.255
224.0.0.6
224.0.0.5
224.2.127.254
239.255.255.255
224.0.0.2
224.0.0.13

Last Reported
10.1.128.1
10.1.128.1
10.1.128.1
10.1.128.1
(null)
(null)
(null)
(null)
(null)
(null)

Timeout
186
186
187
188
0
0
0
0
0
0

user@host> clear igmp membership

Clearing Group Membership Info for so-0/0/0
Clearing Group Membership Info for so-1/0/0
Clearing Group Membership Info for so-2/0/0

user@host> show igmp group

Interface
Group
local
224.0.0.6
local
224.0.0.5
local
224.2.127.254
local
239.255.255.255
local
224.0.0.2
local
224.0.0.13

Last Reported
(null)
(null)
(null)
(null)
(null)
(null)

Timeout
0
0
0
0
0
0

clear igmp membership interface

The following sample output displays IGMP group information before and after the clear
igmp membership interface command is issued:
user@host> show igmp group
Interface
Group
so-0/0/0
224.2.127.253
so-0/0/0
239.255.255.255
so-0/0/0
224.1.127.255
so-0/0/0
224.2.127.254
local
224.0.0.6
local
224.0.0.5
local
224.2.127.254
local
239.255.255.255
local
224.0.0.2
local
224.0.0.13

Last Reported
10.1.128.1
10.1.128.1
10.1.128.1
10.1.128.1
(null)
(null)
(null)
(null)
(null)
(null)

Timeout
210
210
215
216
0
0
0
0
0
0

user@host> clear igmp membership interface so-0/0/0

Clearing Group Membership Info for so-0/0/0

user@host> show igmp group

Interface
Group
local
224.0.0.6
local
224.0.0.5
local
224.2.127.254
local
239.255.255.255
local
224.0.0.2
local
224.0.0.13

Copyright 2014, Juniper Networks, Inc.

Last Reported
(null)
(null)
(null)
(null)
(null)
(null)

Timeout
0
0
0
0
0
0

1519

Interfaces Fundamentals for Routing Devices

clear igmp membership group

The following sample output displays IGMP group information before and after the clear
igmp membership group command is entered:
user@host> show igmp group
Interface
Group
so-0/0/0
224.2.127.253
so-0/0/0
239.255.255.255
so-0/0/0
224.1.127.255
so-0/0/0
224.2.127.254
local
224.0.0.6
local
224.0.0.5
local
224.2.127.254
local
239.255.255.255
local
224.0.0.2
local
224.0.0.13

Last Reported
10.1.128.1
10.1.128.1
10.1.128.1
10.1.128.1
(null)
(null)
(null)
(null)
(null)
(null)

Timeout
210
210
215
216
0
0
0
0
0
0

user@host> clear igmp membership group 239.225/16

Clearing Group Membership Range 239.225.0.0/16 on so-0/0/0
Clearing Group Membership Range 239.225.0.0/16 on so-1/0/0
Clearing Group Membership Range 239.225.0.0/16 on so-2/0/0

user@host> show igmp group

Interface
Group
so-0/0/0
224.1.127.255
so-0/0/0
224.2.127.254
so-0/0/0
224.2.127.253
local
224.0.0.6
local
224.0.0.5
local
224.2.127.254
local
239.255.255.255
local
224.0.0.2
local
224.0.0.13

1520

Last Reported
10.1.128.1
10.1.128.1
10.1.128.1
(null)
(null)
(null)
(null)
(null)
(null)

Timeout
231
233
236
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear igmp snooping membership

Syntax

Release Information
Description
Options

clear igmp snooping membership

<group | source address>
<instance instance-name>
<interface interface-name>
<learning-domain learning-domain-name>
<logical-system logical-system-name>
<vlan-id vlan-identifier>

Command introduced in Junos OS Release 8.5.

Clear IP IGMP snooping membership information.
noneClear IGMP snooping membership for all supported address families on all

interfaces.
group | source address(Optional) Clear IGMP snooping membership for the specified

multicast group or source address.

instance instance-name(Optional) Clear IGMP snooping membership for the specified

instance.
interface interface-name(Optional) Clear IGMP snooping membership on a specific

interface.
learning-domain learning-domain-name(Optional) Perform this operation on all learning

domains or on a particular learning domain.

logical-system logical-system-name(Optional) Display information about a particular

logical system, or for all logical systems.

vlan-id vlan-identifier(Optional) Perform this operation on a particular VLAN.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show igmp snooping membership on page 1582

clear igmp snooping membership on page 1521

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear igmp snooping membership
user@host> clear igmp snooping membership

Copyright 2014, Juniper Networks, Inc.

1521

Interfaces Fundamentals for Routing Devices

clear igmp snooping statistics

Syntax

clear igmp snooping statistics

<instance instance-name>
<interface interface-name>
<learning-domain (all | learning-domain-name)>
<logical-system logical-system-name>

Release Information

Command introduced in Junos OS Release 8.5.

Description
Options

Clear IP IGMP snooping statistics.

noneClear IGMP snooping statistics for all supported address families on all interfaces.
instance instance-name(Optional) Clear IGMP snooping statistics for the specified

instance.
interface interface-name(Optional) Clear IGMP snooping statistics on a specific interface.
learning-domain (all | learning-domain-name)(Optional) Perform this operation on all

learning domains or on a particular learning domain.

logical-system logical-system-name(Optional) Delete the IGMP snooping statistics for

a given logical system or for all logical systems.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show igmp snooping statistics on page 1586

clear igmp snooping statistics on page 1522

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear igmp snooping statistics
user@host> clear igmp snooping statistics

1522

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear igmp statistics

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description
Options

Syntax on page 1523

Syntax (EX Series Switches) on page 1523
clear igmp statistics
<interface interface-name>
<logical-system (all | logical-system-name)>
clear igmp statistics
<interface interface-name>

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.3 for the QFX Series.
Clear Internet Group Management Protocol (IGMP) statistics.
noneClear IGMP statistics on all interfaces.
interface interface-name(Optional) Clear IGMP statistics for the specified interface

only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show igmp statistics on page 1591

clear igmp statistics on page 1523

See show igmp statistics for an explanation of output fields.

Sample Output
clear igmp statistics
The following sample output displays IGMP statistics information before and after the
clear igmp statistics command is entered:
user@host> show igmp statistics
IGMP packet statistics for all interfaces
IGMP Message type
Received
Sent
Membership Query
8883
459
V1 Membership Report
0
0
DVMRP
19784
35476
PIM V1
18310
0
Cisco Trace
0
0
V2 Membership Report
0
0
Group Leave
0
0
Mtrace Response
0
0

Copyright 2014, Juniper Networks, Inc.

Rx errors
0
0
0
0
0
0
0
0

1523

Interfaces Fundamentals for Routing Devices

Mtrace Request
0
Domain Wide Report
0
V3 Membership Report
0
Other Unknown types
IGMP v3 unsupported type
IGMP v3 source required for SSM
IGMP v3 mode not applicable for SSM
IGMP Global Statistics
Bad Length
Bad Checksum
Bad Receive If
Rx non-local

0
0
0

0
0
0
1227

user@host> clear igmp statistics

user@host> show igmp statistics
IGMP packet statistics for all interfaces
IGMP Message type
Received
Sent
Membership Query
0
0
V1 Membership Report
0
0
DVMRP
0
0
PIM V1
0
0
Cisco Trace
0
0
V2 Membership Report
0
0
Group Leave
0
0
Mtrace Response
0
0
Mtrace Request
0
0
Domain Wide Report
0
0
V3 Membership Report
0
0
Other Unknown types
IGMP v3 unsupported type
IGMP v3 source required for SSM
IGMP v3 mode not applicable for SSM
IGMP Global Statistics
Bad Length
0
Bad Checksum
0
Bad Receive If
0
Rx non-local
0

1524

0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear mld membership

Syntax

Release Information
Description
Options

clear mld membership

<group group-name> | <interface interface-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Clear Multicast Listener Discovery (MLD) group membership.
noneClear all MLD memberships.
group group-name(Optional) Clear MLD membership for the specified group.
interface interface-name(Optional) Clear MLD group membership for the specified

interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

show mld group on page 1594

clear mld membership on page 1525

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear mld membership
user@host> clear mld membership

Copyright 2014, Juniper Networks, Inc.

1525

Interfaces Fundamentals for Routing Devices

clear mld statistics

Syntax

clear mld statistics

<interface interface-name>
<logical-system (all | logical-system-name)>

Release Information

Command introduced before Junos OS Release 7.4.

Description

Clear Multicast Listener Discovery (MLD) statistics.

Options

none(Same as logical-system all) Clear MLD statistics for all interfaces.

interface interface-name(Optional) Clear MLD statistics for the specified interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show mld statistics on page 1602

clear mld statistics on page 1526

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear mld statistics
user@host> clear mld statistics

1526

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear msdp cache

Syntax

Release Information

Description
Options

clear msdp cache

<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.
Clear the entries in the Multicast Source Discovery Protocol (MSDP) source-active cache.
noneClear entries in the MSDP source-active cache for all instances, logical systems,

and peers.
instance instance-name(Optional) Clear entries for a specific MSDP instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

peer peer-address(Optional) Clear the MSDP source-active cache entries learned from

a specific peer.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show msdp source-active on page 1609

clear msdp cache on page 1527

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear msdp cache
user@host> clear msdp cache

Copyright 2014, Juniper Networks, Inc.

1527

Interfaces Fundamentals for Routing Devices

clear msdp statistics

Syntax

clear msdp statistics

<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.

Description

Clear Multicast Source Discovery Protocol (MSDP) peer statistics.

Options

noneClear MSDP statistics for all peers.

instance instance-name(Optional) Clear statistics for the specified instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

peer peer-address(Optional) Clear the statistics for the specified peer.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show msdp statistics on page 1612

clear msdp statistics on page 1528

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear msdp statistics
user@host> clear msdp statistics

1528

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear multicast bandwidth-admission

Syntax

Release Information

Description
Options

clear multicast bandwidth-admission

<group group-address>
<inet | inet6>
<instance instance-name>
<interface interface-name>
<source source-address>

Command introduced in Junos OS Release 8.3.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Reapply IP multicast bandwidth admissions.
noneReapply multicast bandwidth admissions for all IPv4 forwarding entries in the

master routing instance.

group group-address(Optional) Reapply multicast bandwidth admissions for the

specified group.
inet(Optional) Reapply multicast bandwidth admission settings for IPv4 flows.
inet6(Optional) Reapply multicast bandwidth admission settings for IPv6 flows.
instance instance-name(Optional) Reapply multicast bandwidth admission settings

for the specified instance. If you do not specify an instance, the command applies
to the master routing instance.
interface interface-name(Optional) Examines the corresponding outbound interface in

the relevant entries and acts as follows:

If the interface is congested, and it was admitted previously, it is removed.

If the interface was rejected previously, the clear multicast bandwidth-admission

command enables the interface to be admitted as long as enough bandwidth
exists on the interface.

If you do not specify an interface, issuing the clear multicast bandwidth-admission

command readmits any previously rejected interface for the relevant entries as
long as enough bandwidth exists on the interface.

To manually reject previously admitted outbound interfaces, you must specify the
interface.
source source-address(Optional) Use with the group option to reapply multicast

bandwidth admission settings for the specified (source, group) entry.

Required Privilege
Level

clear

Copyright 2014, Juniper Networks, Inc.

1529

Interfaces Fundamentals for Routing Devices

Related
Documentation
List of Sample Output
Output Fields

show multicast interface on page 1622

clear multicast bandwidth-admission on page 1530

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear multicast bandwidth-admission
user@host> clear multicast bandwidth-admission

1530

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear multicast forwarding-cache

Syntax

Release Information
Description

clear multicast forwarding-cache

<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced in Junos OS Release 12.2.

Clear IP multicast forwarding cache entries.
This command is not supported for next-generation multiprotocol BGP multicast VPNs
(MVPNs).

Options

none(Same as logical-system all) Clear multicast forwarding cache entries.

inet(Optional) Clear multicast forwarding cache entries for IPv4 family addresses.
inet6(Optional) Clear multicast forwarding cache entries for IPv6 family addresses.
instance instance-name(Optional) Clear multicast forwarding cache entries on a specific

routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show multicast forwarding-cache statistics on page 1620

clear multicast forwarding-cache on page 1531

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear multicast forwarding-cache
user@host> clear multicast forwarding-cache

Copyright 2014, Juniper Networks, Inc.

1531

Interfaces Fundamentals for Routing Devices

clear multicast scope

List of Syntax

Syntax

Syntax on page 1532

Syntax (EX Series Switch and the QFX Series) on page 1532
clear multicast scope
<inet | inet6>
<interface interface-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

clear multicast scope

<inet | inet6>
<interface interface-name>

Release Information

Command introduced in Junos OS Release 7.6.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 option introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Clear IP multicast scope statistics.

none(Same as logical-system all) Clear multicast scope statistics.
inet(Optional) Clear multicast scope statistics for IPv4 family addresses.
inet6(Optional) Clear multicast scope statistics for IPv6 family addresses.
interface interface-name(Optional) Clear multicast scope statistics on a specific

interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show multicast scope on page 1644

clear multicast scope on page 1532

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear multicast scope
user@host> clear multicast scope

1532

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear multicast sessions

List of Syntax

Syntax

Syntax on page 1533

Syntax (EX Series Switch and the QFX Series) on page 1533
clear multicast sessions
<logical-system (all | logical-system-name)>
<regular-expression>

Syntax (EX Series

Switch and the QFX
Series)

clear multicast sessions

<regular-expression>

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.3 for the QFX Series.

Description
Options

Clear IP multicast sessions.

none(Same as logical-system all) Clear multicast sessions.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

regular-expression(Optional) Clear only multicast sessions that contain the specified

regular expression.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show multicast sessions on page 1648

clear multicast sessions on page 1533

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear multicast sessions
user@host> clear multicast sessions

Copyright 2014, Juniper Networks, Inc.

1533

Interfaces Fundamentals for Routing Devices

clear multicast snooping statistics

Syntax

Release Information
Description
Options

clear multicast snooping statistics

<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>

Command introduced in Junos OS Release 8.5.

Clear IP multicast snooping statistics.
noneClear multicast snooping statistics for all supported address families on all

interfaces.
instance instance-name(Optional) Clear multicast snooping statistics for the specified

instance.
interface interface-name(Optional) Clear multicast snooping statistics on a specific

interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

clear

clear multicast snooping statistics on page 1534

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear multicast snooping statistics
user@host> clear multicast snooping statistics

1534

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear multicast statistics

List of Syntax

Syntax

Syntax on page 1535

Syntax (EX Series Switch and the QFX Series) on page 1535
clear multicast statistics
<inet | inet6>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

clear multicast statistics

<inet | inet6>
<instance instance-name>
<interface interface-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Clear IP multicast statistics.

noneClear multicast statistics for all supported address families on all interfaces.
inet(Optional) Clear multicast statistics for IPv4 family addresses.
inet6(Optional) Clear multicast statistics for IPv6 family addresses.
instance instance-name(Optional) Clear multicast statistics for the specified instance.
interface interface-name(Optional) Clear multicast statistics on a specific interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show multicast statistics on page 1655

clear multicast statistics on page 1535

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear multicast statistics
user@host> clear multicast statistics

Copyright 2014, Juniper Networks, Inc.

1535

Interfaces Fundamentals for Routing Devices

clear pgm negative-acknowledgments

Syntax

clear pgm negative-acknowledgments

Release Information

NOTE: Support for the Pragmatic General Multicast protocol (PGM) is being
removed from Junos. In Junos OS release 14.2 PGM functionality is still
available, but the commands are hidden, that is, they no longer appear in the
CLI.

Command introduced before Junos OS Release 7.4.

Description

Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

Clear the Pragmatic General Multicast (PGM) negative acknowledgment (NAK) state
received.
This command has no options.
clear

show pgm negative-acknowledgments on page 1661

clear pgm negative-acknowledgments on page 1536

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear pgm negativeacknowledgments
user@host> clear pgm negative-acknowledgments

1536

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear pgm source-path-messages

Syntax

clear pgm source-path-messages

Release Information

NOTE: Support for the Pragmatic General Multicast protocol (PGM) is being
removed from Junos. In Junos OS release 14.2 PGM functionality is still
available, but the commands are hidden, that is, they no longer appear in the
CLI.

Command introduced before Junos OS Release 7.4.

Description
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

Clear Pragmatic General Multicast (PGM) source-path messages.

This command has no options.
clear

show pgm source-path-messages on page 1664

clear pgm source-path-messages on page 1537

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear pgm source-path-messages
user@host> clear pgm source-path-messages

Copyright 2014, Juniper Networks, Inc.

1537

Interfaces Fundamentals for Routing Devices

clear pgm statistics

Syntax

clear pgm statistics

Release Information

NOTE: Support for the Pragmatic General Multicast protocol (PGM) is being
removed from Junos. In Junos OS release 14.2 PGM functionality is still
available, but the commands are hidden, that is, they no longer appear in the
CLI.

Command introduced before Junos OS Release 7.4.

Description
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

Clear Pragmatic General Multicast (PGM) statistics.

This command has no options.
clear

show pgm statistics on page 1666

clear pgm statistics on page 1538

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear pgm statistics
user@host> clear pgm statistics

1538

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear pim join

List of Syntax

Syntax on page 1539

Syntax (EX Series Switch and the QFX Series) on page 1539

Syntax

clear pim join

<group-address>
<bidirectional | dense | sparse>
<exact>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<rp ip-address/prefix | source ip-address/prefix>
<sg | star-g>

Syntax (EX Series

Switch and the QFX
Series)

clear pim join

<group-address>
<dense | sparse>
<exact>
<inet | inet6>
<instance instance-name>
<rp ip-address/prefix | source ip-address/prefix>
<sg | star-g>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Multiple new filter options introduced in Junos OS Release 13.2.

Description
Options

Clear the Protocol Independent Multicast (PIM) join and prune states.
noneClear the PIM join and prune states for all groups, family addresses, and instances.
group-address(Optional) Clear the PIM join and prune states for a group address.
bidirectional | dense | sparse(Optional) Clear PIM bidirectional mode, dense mode, or

sparse and source-specific multicast (SSM) mode entries.

exact(Optional) Clear only the group that exactly matches the specified group address.
inet | inet6(Optional) Clear the PIM entries for IPv4 or IPv6 family addresses, respectively.
instance instance-name(Optional) Clear the entries for a specific PIM-enabled routing

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

rp ip-address/prefix | source ip-address/prefix(Optional) Clear the PIM entries with a

specified rendezvous point (RP) address and prefix or with a specified source address
and prefix. You can omit the prefix.

Copyright 2014, Juniper Networks, Inc.

1539

Interfaces Fundamentals for Routing Devices

sg | star-g(Optional) Clear PIM (S,G) or (*,G) entries.

Additional Information

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

The clear pim join command cannot be used to clear the PIM join and prune state on a
backup Routing Engine when nonstop active routing is enabled.
clear

show pim join on page 1675

clear pim join on page 1540

clear pim join inet6 on page 1540
clear pim join inet6 star-g on page 1540
When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear pim join
user@host> clear pim join
Cleared 8 Join/Prune states

clear pim join inet6

user@host> clear pim join inet6
Cleared 4 Join/Prune states

clear pim join inet6 star-g

user@host> clear pim join inet6 star-g
Cleared 1 Join/Prune states

1540

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear pim join-distribution

Syntax

Release Information
Description

clear pim join-distribution

<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced in Junos OS Release 10.0.

Redistribute the Protocol Independent Multicast (PIM) join states.
You can find out if there are multiple paths available for a source (for example, an RP)
with the output of the show pim source command.
When you include the join-load-balance statement in the configuration, the PIM join
states are distributed evenly on available equal-cost multipath links. When an upstream
neighbor link fails, Junos OS redistributes the PIM join states to the remaining links.
However, when new links are added or the failed link is restored, the existing PIM joins
are not redistributed to the new link. New flows will be distributed to the new links.
However, in a network without new joins and prunes, the new link is not used for multicast
traffic. The clear pim join-distribution command redistributes the existing flows to the
new upstream neighbors. Redistributing the existing flows causes traffic to be disrupted,
so we recommend that you run the clear pim join-distribution command during a
maintenance window.

Options

noneRedistribute the PIM join states for the default master instance.
instance instance-name(Optional) Redistribute the join states for a specific PIM-enabled

routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Additional Information

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

The clear pim join-distribution command cannot be used to redistribute the PIM join states
on a backup Routing Engine when nonstop active routing is enabled.
clear

show pim neighbors on page 1705

show pim join on page 1675

join-load-balance

clear pim join-distribution on page 1542

When you enter this command, you are provided no feedback on the status of your
request. You can enter the show pim join command before and after distributing the join
state to verify the operation.

Copyright 2014, Juniper Networks, Inc.

1541

Interfaces Fundamentals for Routing Devices

Sample Output
clear pim join-distribution
user@host> clear pim join-distribution

1542

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear pim register

List of Syntax

Syntax

Syntax on page 1543

Syntax (EX Series Switch and the QFX Series) on page 1543
Syntax (PTX Series) on page 1543
clear pim register
<inet | inet6>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

clear pim register

<inet | inet6>
<instance instance-name>
<interface interface-name>

Syntax (PTX Series)

clear pim register

<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>

Release Information

Command introduced in Junos OS Release 7.6.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Clear Protocol Independent Multicast (PIM) register message counters.

noneClear PIM register message counters for all family addresses, instances, and
interfaces.
inet | inet6(Optional) Clear PIM register message counters for IPv4 or IPv6 family

addresses, respectively.
instance instance-name(Optional) Clear register message counters for a specific

PIM-enabled routing instance.

interface interface-name(Optional) Clear PIM register message counters for a specific

interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Additional Information

Required Privilege
Level

The clear pim register command cannot be used to clear the PIM register state on a
backup Routing Engine when nonstop active routing is enabled.
clear

Copyright 2014, Juniper Networks, Inc.

1543

Interfaces Fundamentals for Routing Devices

Related
Documentation
List of Sample Output
Output Fields

show pim statistics on page 1736

clear pim register on page 1544

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear pim register
user@host> clear pim register

1544

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear pim snooping join

Syntax

Release Information

Description
Options

clear pim snooping join

<instance instance-name>
<logical-system logical-system-name>
<vlan-id vlan-id>

Command introduced in Junos OS Release 12.3 for MX Series 3D Universal Edge devices.
Command introduced in Junos OS Release 13.2 for M Series Multiservice Edge devices.
Clear information about Protocol Independent Multicast (PIM) snooping joins.
noneDisplay detailed information.
instance instance-name(Optional) Clear PIM snooping join information for the specified

routing instance.
logical-system logical-system-name(Optional) Delete the IGMP snooping statistics for

a given logical system or for all logical systems.

vlan-id vlan-identifier(Optional) Clear PIM snooping join information for the specified

VLAN.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

PIM Snooping for VPLS

clear pim snooping join on page 1545

See show pim snooping join for an explanation of the output fields.

Sample Output
clear pim snooping join
The following sample output displays information about PIM snooping joins before and
after the clear pim snooping join command is entered:
user@host> show pim snooping join extensive
Instance: vpls1
Learning-Domain: vlan-id 10
Learning-Domain: vlan-id 20
Group: 225.1.1.2
Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.120.5, port: ge-1/3/7.20
Downstream port: ge-1/3/1.20
Downstream neighbors:
20.0.120.2 State: Join Flags: SRW Timeout: 185
Group: 225.1.1.3

Copyright 2014, Juniper Networks, Inc.

1545

Interfaces Fundamentals for Routing Devices

Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.120.4, port: ge-1/3/5.20
Downstream port: ge-1/3/3.20
Downstream neighbors:
20.0.120.3 State: Join Flags: SRW Timeout: 175
user@host> clear pim snooping join
Clearing the Join/Prune state for 224.0.0.0/4
Clearing the Join/Prune state for 224.0.0.0/4
user@host> show pim snooping join extensive
Instance: vpls1
Learning-Domain: vlan-id 10
Learning-Domain: vlan-id 20

1546

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear pim snooping statistics

Syntax

Release Information

Description
Options

clear pim snooping statistics

<instance instance-name>
<interface interface-name>
<logical-system logical-system-name>
<vlan-id vlan-id>

Command introduced in Junos OS Release 12.3 for MX Series 3D Universal Edge devices.
Command introduced in Junos OS Release 13.2 for M Series Multiservice Edge devices.
Clear Protocol Independent Multicast (PIM) snooping statistics.
noneClear PIM snooping statistics for all family addresses, instances, and interfaces.
instance instance-name(Optional) Clear statistics for a specific PIM-snooping-enabled

routing instance.
interface interface-name(Optional) Clear PIM snooping statistics for a specific interface.
logical-system logical-system-name(Optional) Delete the IGMP snooping statistics for

a given logical system or for all logical systems.

vlan-id vlan-identifier(Optional) Clear PIM snooping statistics information for the

specified VLAN.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

PIM Snooping for VPLS

clear pim snooping statistics on page 1547

See show pim snooping statistics for an explanation of the output fields.

Sample Output
clear pim snooping statistics
The following sample output displays PIM snooping statistics before and after the clear
pim snooping statistics command is entered:
user@host> show pim snooping statistics
Instance: vpls1
Learning-Domain: vlan-id 10
Tx
RX
Rx
Rx
Rx
Rx
Rx

J/P messages 0
J/P messages 660
J/P messages -- seen 0
J/P messages -- received 660
Hello messages 1396
Version Unknown 0
Neighbor Unknown 0

Copyright 2014, Juniper Networks, Inc.

1547

Interfaces Fundamentals for Routing Devices

Rx
Rx
Rx
Rx
Rx

Upstream Neighbor Unknown 0

Bad Length 0
J/P Busy Drop 0
J/P Group Aggregate 0
Malformed Packet 0

Learning-Domain: vlan-id 20
user@host> clear pim snooping statistics
user@host> show pim snooping statistics
Instance: vpls1
Learning-Domain: vlan-id 10
Tx
RX
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx

J/P messages 0
J/P messages 0
J/P messages -- seen 0
J/P messages -- received 0
Hello messages 0
Version Unknown 0
Neighbor Unknown 0
Upstream Neighbor Unknown 0
Bad Length 0
J/P Busy Drop 0
J/P Group Aggregate 0
Malformed Packet 0

Learning-Domain: vlan-id 20

1548

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

clear pim statistics

List of Syntax

Syntax

Syntax on page 1549

Syntax (EX Series Switch and the QFX Series) on page 1549
clear pim statistics
<inet | inet6>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

clear pim statistics

<inet | inet6>
<instance instance-name>
<interface interface-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Clear Protocol Independent Multicast (PIM) statistics.

noneClear PIM statistics for all family addresses, instances, and interfaces.
inet | inet6(Optional) Clear PIM statistics for IPv4 or IPv6 family addresses, respectively.
instance instance-name(Optional) Clear statistics for a specific PIM-enabled routing

instance.
interface interface-name(Optional) Clear PIM statistics for a specific interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Additional Information

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

The clear pim statistics command cannot be used to clear the PIM statistics on a backup
Routing Engine when nonstop active routing is enabled.
clear

show pim statistics on page 1736

clear pim statistics on page 1550

See show pim statistics for an explanation of output fields.

Copyright 2014, Juniper Networks, Inc.

1549

Interfaces Fundamentals for Routing Devices

Sample Output
clear pim statistics
The following sample output displays PIM statistics before and after the clear pim statistics
command is entered:
user@host> show pim statistics
PIM statistics on all interfaces:
PIM Message type
Received
Sent
Hello
0
0
Register
0
0
Register Stop
0
0
Join Prune
0
0
Bootstrap
0
0
Assert
0
0
Graft
0
0
Graft Ack
0
0
Candidate RP
0
0
V1 Query
2111
4222
V1 Register
0
0
V1 Register Stop
0
0
V1 Join Prune
14200
13115
V1 RP Reachability
0
0
V1 Assert
0
0
V1 Graft
0
0
V1 Graft Ack
0
0
PIM statistics summary for all interfaces:
Unknown type
0
V1 Unknown type
0
Unknown Version
0
Neighbor unknown
0
Bad Length
0
Bad Checksum
0
Bad Receive If
0
Rx Intf disabled
2007
Rx V1 Require V2
0
Rx Register not RP
0
RP Filtered Source
0
Unknown Reg Stop
0
Rx Join/Prune no state
1040
Rx Graft/Graft Ack no state
0
...

user@host> clear pim statistics

user@host> show pim statistics
PIM statistics on all interfaces:
PIM Message type
Received
Hello
0
Register
0
Register Stop
0
Join Prune
0
Bootstrap
0
Assert
0
Graft
0
Graft Ack
0
Candidate RP
0
V1 Query
1
V1 Register
0
...

1550

Sent
0
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Copyright 2014, Juniper Networks, Inc.

1551

Interfaces Fundamentals for Routing Devices

request pim multicast-tunnel rebalance

List of Syntax

Syntax on page 1552

Syntax (EX Series Switches) on page 1552

Syntax

request pim multicast-tunnel rebalance

<instance instance-name>
<logical-system (all | logical-system-name>

Syntax (EX Series

Switches)
Release Information

Description

Options

request pim multicast-tunnel rebalance

<instance instance-name>

Command introduced in Junos OS Release 10.2.

Command introduced in Junos OS Release 10.2 for EX Series switches.
Rebalance the assignment of multicast tunnel encapsulation interfaces across available
tunnel-capable PICs or across a configured list of tunnel-capable PICs. You can determine
whether a rebalance is necessary by running the show pim interfaces instance
instance-name command.
noneRe-create and rebalance all tunnel interfaces for all routing instances.
instance instance-nameRe-create and rebalance all tunnel interfaces for a specific

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation

Output Fields

1552

maintenance

show pim interfaces on page 1672

Load Balancing Multicast Tunnel Interfaces Among Available PICs

This command produces no output. To verify the operation of the command, run the
show pim interface instance instance-name before and after running the request pim
multicast-tunnel rebalance command.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show amt statistics

Syntax

show amt statistics

<instance instance-name>
<logical-system (all | logical-system-name)>

Release Information

Command introduced in JUNOS Release 10.2.

Description

Display information about the Automatic Multicast Tunneling (AMT) protocol tunnel
statistics.

Options

noneDisplay summary information about all AMT Protocol tunnels.

instance instance-name(Optional) Display information for the specified instance only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level

view

Related
Documentation

List of Sample Output

clear amt statistics on page 1516

show amt summary on page 1556

show amt tunnel on page 1558

show amt statistics on page 1554

Output Fields

Table 95 on page 1553 describes the output fields for the show amt statistics command.
Output fields are listed in the approximate order in which they appear.

Table 95: show amt statistics Output Fields

Field Name

Field Description

AMT receive message

count

Summary of AMT statistics for messages received on all interfaces.

AMT send message

count

AMT relay discoveryNumber of AMT relay discovery messages received.

AMT membership requestNumber of AMT membership request messages received.

AMT membership updateNumber of AMT membership update messages received.

Summary of AMT statistics for messages sent on all interfaces.

AMT relay advertisementNumber of AMT relay advertisement messages sent.

AMT membership queryNumber of AMT membership query messages sent.

Copyright 2014, Juniper Networks, Inc.

1553

Interfaces Fundamentals for Routing Devices

Table 95: show amt statistics Output Fields (continued)

Field Name

Field Description

AMT error message

count

Summary of AMT statistics for error messages received on all interfaces.

AMT incomplete packetNumber of messages received with length errors so severe that further

classification could not occur.

AMT invalid macNumber of messages received with an invalid message authentication code

(MAC).

AMT unexpected typeNumber of messages received with an unknown message type specified.

AMT invalid relay discovery addressNumber of AMT relay discovery messages received with an

address other than the configured anycast address.

AMT invalid membership request addressNumber of AMT membership request messages received

with an address other than the configured AMT local address.

AMT invalid membership update addressNumber of AMT membership update messages received

with an address other than the configured AMT local address.

AMT incomplete relay discovery messagesNumber of AMT relay discovery messages received that

are not fully formed.

AMT incomplete membership request messagesNumber of AMT membership request messages

received that are not fully formed.

AMT incomplete membership update messagesNumber of AMT membership update messages

received that are not fully formed.

AMT no active gatewayNumber of AMT membership update messages received for a tunnel that

does not exist for the gateway that sent the message.

AMT invalid inner header checksumNumber of AMT membership update messages received with

an invalid IP checksum.

AMT gateways timed outNumber of gateways that timed out because of inactivity.

Sample Output
show amt statistics
user@host> show amt statistics
AMT
AMT
AMT
AMT

1554

receive message count

relay advertisement
membership request
membership update

:
:
:

2
5
5

AMT send message count

AMT relay advertisement
AMT membership query

:
:

2
5

AMT
AMT
AMT
AMT
AMT
AMT
AMT
AMT
AMT
AMT
AMT

:
:
:
:
:
:
:
:
:
:

0
0
0
0
0
0
0
0
0
0

error message count

incomplete packet
invalid mac
unexpected type
invalid relay discovery address
invalid membership request address
invalid membership update address
incomplete relay discovery messages
incomplete membership request messages
incomplete membership update messages
no active gateway

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

AMT invalid inner header checksum

AMT gateways timed out

Copyright 2014, Juniper Networks, Inc.

:
:

0
0

1555

Interfaces Fundamentals for Routing Devices

show amt summary

Syntax

Release Information
Description
Options

show amt summary

<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced in JUNOS Release 10.2.

Display summary information about the Automatic Multicast Tunneling (AMT) protocol.
noneDisplay summary information about all AMT protocol instances.
instance instance-name(Optional) Display information for the specified instance only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

clear amt tunnel on page 1517

show amt statistics on page 1553

show amt tunnel on page 1558

show amt summary on page 1557

Table 96 on page 1556 describes the output fields for the show amt summary command.
Output fields are listed in the approximate order in which they appear.

Table 96: show amt summary Output Fields

Field Name

Field Description

Level of Output

AMT anycast prefix

Prefix advertised by unicast routing protocols to route AMT discovery messages to the
router from nearby AMT gateways.

All levels

AMT anycast
address

Anycast address configured from which the anycast prefix is derived.

All levels

AMT local address

Local unique AMT relay IP address configured. Used to send AMT relay advertisement
messages, it is the IP source address of AMT control messages and the source address
of the data tunnel encapsulation.

All levels

AMT tunnel limit

Maximum number of AMT tunnels that can be created.

All levels

active tunnels

Number of active AMT tunnel interfaces.

All levels

1556

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show amt summary
user@host> show amt summary
AMT anycast prefix : 20.0.0.4/32
AMT anycast address : 20.0.0.4
AMT local address : 20.0.0.4
AMT tunnel limit : 1000, active tunnels : 2

Copyright 2014, Juniper Networks, Inc.

1557

Interfaces Fundamentals for Routing Devices

show amt tunnel

Syntax

Release Information
Description
Options

show amt tunnel

<brief | detail>
<gateway-address gateway-ip-address> <port port-number>
<instance instance-name>
<logical-system (all | logical-system-name)>
<tunnel-interface interface-name>

Command introduced in JUNOS Release 10.2.

Display information about the Automatic Multicast Tunneling (AMT) dynamic tunnels.
noneDisplay summary information about all AMT protocol instances.
brief | detail(Optional) Display the specified level of detail.
gateway-address gateway-ip-address port port-number(Optional) Display information

for the specified AMT gateway only. If no port is specified, display information for all
AMT gateways with the given IP address.
instance instance-name(Optional) Display information for the specified instance only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

tunnel-interface interface-name(Optional) Display information for the specified AMT

tunnel interface only.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

clear amt tunnel on page 1517

show amt statistics on page 1553

show amt summary on page 1556

show amt tunnel on page 1559

show amt tunnel detail on page 1559
show amt tunnel tunnel-interface on page 1560
show amt tunnel gateway-address on page 1560
show amt tunnel gateway-address detail on page 1560
Table 97 on page 1558 describes the output fields for the show amt tunnel command.
Output fields are listed in the approximate order in which they appear.

Table 97: show amt tunnel Output Fields

Field Name

Field Description

Level of Output

AMT gateway
address

Address of the AMT gateway that is being connected by the AMT tunnel.

All levels

1558

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 97: show amt tunnel Output Fields (continued)

Field Name

Field Description

Level of Output

port

Client port used by the AMT tunnel.

All levels

AMT tunnel
interface

Dynamically created AMT logical interfaces used by the AMT tunnel in the format
ud-FPC/PIC/Port.unit.

All levels

AMT tunnel state

State of the AMT tunnel. The state is normally Active.

All levels

ActiveThe tunnel is active.

PendingThe tunnel creation is pending. This is a transient state.

DownThe tunnel is in the down state.

Graceful restart pendingGraceful restart is in progress.

RevivingThe routing protocol daemon or Routing Engine was restarted (not

gracefully). The tunnel remains in the reviving state until the AMT gateway sends a
control message. When the message is received the tunnel is moved to the Active
state. If no message is received before the AMT tunnel inactivity timer expires, the
tunnel is deleted.
AMT tunnel
inactivity timeout

Number of seconds since the most recent control message was received from an AMT
gateway. If no message is received before the AMT tunnel inactivity timer expires, the
tunnel is deleted.

All levels

Number of groups

Number of multicast groups using the tunnel.

All levels

Group

Multicast group address or addresses using the tunnel.

detail

Include Source

Multicast source address for each IGMPv3 group using the tunnel.

detail

AMT message
count

Statistics for AMT messages:

All levels

AMT RequestNumber of AMT relay tunnel request messages received.

AMT membership updateNumber of AMT membership update messages received.

Sample Output
show amt tunnel
user@host> show amt tunnel
AMT gateway address : 11.11.11.2, port : 2268
AMT tunnel interface : ud-5/1/10.1120256
AMT tunnel state : Active
AMT tunnel inactivity timeout : 15
Number of groups : 1
AMT message count:
AMT Request
AMT membership update
2
2

show amt tunnel detail

user@host> show amt tunnel detail
AMT gateway address : 11.11.11.2, port : 2268
AMT tunnel interface : ud-5/3/10.1120512

Copyright 2014, Juniper Networks, Inc.

1559

Interfaces Fundamentals for Routing Devices

AMT tunnel state : Active

AMT tunnel inactivity timeout : 62
Number of groups : 1
Group: 226.2.3.2
AMT message count:
AMT Request
AMT membership update
2
2
AMT gateway address : 11.11.11.3, port : 2268
AMT tunnel interface : ud-5/2/10.1120513
AMT tunnel state : Active
AMT tunnel inactivity timeout : 214
Number of groups : 1
Group: 226.2.3.3
AMT message count:
AMT Request
AMT membership update
2
2

show amt tunnel tunnel-interface

user@host> show amt tunnel tunnel-interface ud-5/3/10.1120512
AMT gateway address : 11.11.11.2, port : 2268
AMT tunnel interface : ud-5/3/10.1120512
AMT tunnel state : Active
AMT tunnel inactivity timeout : 145
Number of groups : 1
AMT message count:
AMT Request
AMT membership update
2
2

show amt tunnel gateway-address

user@host> show amt tunnel gateway-address 11.11.11.3 port 2268
AMT gateway address : 11.11.11.3, port : 2268
AMT tunnel interface : ud-5/2/10.1120513
AMT tunnel state : Active
AMT tunnel inactivity timeout : 214
Number of groups : 1
Group: 226.2.3.3
AMT message count:
AMT Request
AMT membership update
2
2

show amt tunnel gateway-address detail

user@host> show amt tunnel gateway-address 11.11.11.2 detail
AMT gateway address : 11.11.11.2, port : 2268
AMT tunnel interface : ud-5/3/10.1120512
AMT tunnel state : Active
AMT tunnel inactivity timeout : 234
Number of groups : 1
Group: 226.2.3.2
AMT message count:
AMT Request
AMT membership update
2
2

1560

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show dvmrp interfaces

Syntax

Release Information

show dvmrp interfaces

<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Description

Display information about Distance Vector Multicast Routing Protocol (DVMRP)enabled

interfaces.

Options

none(Same as logical-system all) Display information about DVMRP-enabled interfaces.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show dvmrp interfaces on page 1562

Table 98 on page 1561 describes the output fields for the show dvmrp interfaces command.
Output fields are listed in the approximate order in which they appear.

Table 98: show dvmrp interfaces Output Fields

Field Name

Field Description

Interface

Name of the interface.

State

State of the interface: up or down.

Leaf

Whether the interface is a leaf (that is, whether it has no neighbors)

or whether it has neighbors.

Metric

Interface metric: a value from 1 through 31.

Announce

Number of routes the interface is announcing.

Mode

DVMRP mode:

ForwardingDVMRP does both the routing and the multicast

data forwarding.

Unicast-routingDVMRP does only the routing. Forwarding of

the multicast data packets can be done by enabling PIM on the

interface.

Copyright 2014, Juniper Networks, Inc.

1561

Interfaces Fundamentals for Routing Devices

Sample Output
show dvmrp interfaces
user@host> show dvmrp interfaces
Interface State Leaf Metric Announce Mode
fxp0.0
Up
N
1
4 Forwarding
fxp1.0
Up
N
1
4 Forwarding
fxp2.0
Up
N
1
3 Forwarding
lo0.0
Up
Y
1
0 Unicast-routing

1562

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show dvmrp neighbors

Syntax

show dvmrp neighbors

<logical-system (all | logical-system-name)>

Release Information

Command introduced before Junos OS Release 7.4.

Description

Display information about Distance Vector Multicast Routing Protocol (DVMRP) neighbors.

Options

none(Same as logical-system all) Display information about DVMRP neighbors.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level

view

List of Sample Output

show dvmrp neighbors on page 1564

Output Fields

Table 99 on page 1563 describes the output fields for the show dvmrp neighbors command.
Output fields are listed in the approximate order in which they appear.

Table 99: show dvmrp neighbors Output Fields

Field Name

Field Description

Neighbor

Address of the neighboring DVMRP router.

Interface

Interface through which the neighbor is reachable.

Version

Version of DVMRP that the neighbor is running, in the format majorminor.

Flags

Information about the neighbor:

1One way. The local router has seen the neighbor, but the neighbor has not seen the local router.

GNeighbor supports generation ID.

LNeighbor is a leaf router.

MNeighbor supports mtrace.

NNeighbor supports netmask in prune messages and graft messages.

PNeighbor supports pruning.

SNeighbor supports SNMP.

Routes

Number of routes learned from the neighbor.

Timeout

How long until the DVMRP neighbor information times out, in seconds.

Transitions

Number of generation ID changes that have occurred since the local router learned about the neighbor.

Copyright 2014, Juniper Networks, Inc.

1563

Interfaces Fundamentals for Routing Devices

Sample Output
show dvmrp neighbors
user@host> show dvmrp neighbors
Neighbor
Interface
192.168.1.1
ipip.0

1564

Version Flags
3.255 PGM

Routes Timeout Transitions

3
28
1

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show dvmrp prefix

Syntax

Release Information
Description
Options

show dvmrp prefix

<brief | detail>
<logical-system (all | logical-system-name)>
<prefix>

Command introduced before Junos OS Release 7.4.

Display information about Distance Vector Multicast Routing Protocol (DVMRP) prefixes.
noneDisplay standard information about all DVMRP prefixes.
brief | detail(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

prefix(Optional) Display information about specific prefixes.

Required Privilege
Level
List of Sample Output

Output Fields

view

show dvmrp prefix on page 1566

show dvmrp prefix brief on page 1566
show dvmrp prefix detail on page 1566
Table 100 on page 1565 describes the output fields for the show dvmrp prefix command.
Output fields are listed in the approximate order in which they appear.

Table 100: show dvmrp prefix Output Fields

Field Name

Field Description

Level of Output

Prefix

DVMRP route.

All levels

Next hop

Next hop from which the route was learned.

All levels

Age

Last time that the route was refreshed.

All levels

multicast-group

Multicast group address.

detail

Prunes sent

Number of prune messages sent to the multicast group.

detail

Grafts sent

Number of grafts sent to the multicast group.

detail

Cache lifetime

Lifetime of the group in the multicast cache, in seconds.

detail

Prune lifetime

Lifetime remaining and total lifetime of prune messages, in seconds.

detail

Copyright 2014, Juniper Networks, Inc.

1565

Interfaces Fundamentals for Routing Devices

Sample Output
show dvmrp prefix
user@host> show dvmrp prefix
Prefix
Next hop
10.38.0.0
/30 10.38.0.1
10.38.0.4
/30 10.38.0.5
10.38.0.8
/30 10.38.0.2
10.38.0.12
/30 10.38.0.6
10.255.14.114 /32 10.255.14.114
10.255.14.142 /32 10.38.0.2
10.255.14.144 /32 10.38.0.2
10.255.70.15
/32 10.38.0.6
192.168.14.0
/24 192.168.14.114
192.168.195.40 /30 192.168.195.41
192.168.195.92 /30 10.38.0.2

Age
00:06:17
00:06:13
00:00:04
00:00:04
00:06:17
00:00:04
00:00:04
00:00:04
00:06:17
00:06:17
00:00:04

show dvmrp prefix brief

The output for the show dvmrp prefix brief command is identical to that for the show
dvmrp prefix command.
show dvmrp prefix detail
user@host> show dvmrp prefix detail
Prefix
Next hop
10.38.0.0
/30 10.38.0.1
10.38.0.4
/30 10.38.0.5
10.38.0.8
/30 10.38.0.2
10.38.0.12
/30 10.38.0.6
10.255.14.114 /32 10.255.14.114
10.255.14.142 /32 10.38.0.2
10.255.14.144 /32 10.38.0.2
10.255.70.15
/32 10.38.0.6
192.168.14.0
/24 192.168.14.114
192.168.195.40 /30 192.168.195.41
192.168.195.92 /30 10.38.0.2

1566

Age
00:06:28
00:06:24
00:00:15
00:00:15
00:06:28
00:00:15
00:00:15
00:00:15
00:06:28
00:06:28
00:00:15

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show dvmrp prunes

Syntax

Release Information
Description

Options

show dvmrp prunes

<all | rx | tx>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display information about active Distance Vector Multicast Routing Protocol (DVMRP)
prune messages.
noneDisplay received and transmitted DVMRP prune information.
all(Optional) Display information about all received and transmitted prune messages.
rx(Optional) Display information about received prune messages.
tx(Optional) Display information about transmitted prune messages.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show dvmrp prunes on page 1567

Table 101 on page 1567 describes the output fields for the show dvmrp prunes command.
Output fields are listed in the approximate order in which they appear.

Table 101: show dvmrp prunes Output Fields

Field Name

Field Description

Group

Group address.

Source prefix

Prefix for the prune.

Timeout

How long until the prune message expires, in seconds.

Neighbor

Neighbor to which the prune was sent or from which the prune was
received.

Sample Output
show dvmrp prunes
user@host> show dvmrp prunes
Group
Source prefix
224.0.1.1
128.112.0.0
224.0.1.32
160.0.0.0
224.2.123.4
136.0.0.0
224.2.127.1
129.0.0.0

Copyright 2014, Juniper Networks, Inc.

/12
/3
/5
/8

Timeout
7077
7087
6955
7046

Neighbor
192.168.1.1
192.168.1.1
192.168.1.1
192.168.1.1

1567

Interfaces Fundamentals for Routing Devices

224.2.135.86
224.2.135.86
224.2.135.86
...

1568

128.102.128.0
129.0.0.0
130.0.0.0

/17
/8
/7

7071 192.168.1.1
7074 192.168.1.1
7071 192.168.1.1

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show igmp group

List of Syntax

Syntax

Syntax on page 1569

Syntax (EX Series Switch and the QFX Series) on page 1569
show igmp group
<brief | detail>
<group-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show igmp group

<brief | detail>
<group-name>

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.3 for the QFX Series.

Description
Options

Display Internet Group Management Protocol (IGMP) group membership information.

noneDisplay standard information about membership for all IGMP groups.
brief | detail(Optional) Display the specified level of output.
group-name(Optional) Display group membership for the specified IP address only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear igmp membership on page 1518

show igmp group (Include Mode) on page 1570

show igmp group (Exclude Mode) on page 1571
show igmp group brief on page 1571
show igmp group detail on page 1571
Table 102 on page 1569 describes the output fields for the show igmp group command.
Output fields are listed in the approximate order in which they appear.

Table 102: show igmp group Output Fields

Field Name

Field Description

Level of Output

Interface

Name of the interface that received the IGMP membership report. A name of
local indicates that the local routing device joined the group itself.

All levels

Group

Group address.

All levels

Group Mode

Mode the SSM group is operating in: Include or Exclude.

All levels

Copyright 2014, Juniper Networks, Inc.

1569

Interfaces Fundamentals for Routing Devices

Table 102: show igmp group Output Fields (continued)

Field Name

Field Description

Level of Output

Source

Source address.

All levels

Source timeout

Time remaining until the group traffic is no longer forwarded. The timer is
refreshed when a listener in include mode sends a report. A group in exclude
mode or configured as a static group displays a zero timer.

detail

Last reported by

Address of the host that last reported membership in this group.

All levels

Timeout

Time remaining until the group membership is removed.

brief none

Group timeout

Time remaining until a group in exclude mode moves to include mode. The timer
is refreshed when a listener in exclude mode sends a report. A group in include
mode or configured as a static group displays a zero timer.

detail

Type

Type of group membership:

All levels

DynamicHost reported the membership.

StaticMembership is configured.

Sample Output
show igmp group (Include Mode)
user@host> show igmp group
Interface: t1-0/1/0.0
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.2
Last reported by: 10.9.5.2
Timeout:
24 Type: Dynamic
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.3
Last reported by: 10.9.5.2
Timeout:
24 Type: Dynamic
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.4
Last reported by: 10.9.5.2
Timeout:
24 Type: Dynamic
Group: 232.1.1.2
Group mode: Include
Source: 10.0.0.4
Last reported by: 10.9.5.2
Timeout:
24 Type: Dynamic
Interface: t1-0/1/1.0
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Interface: local
Group: 224.0.0.2
Source: 0.0.0.0
Last reported by: Local
Timeout:
0 Type: Dynamic

1570

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Group: 224.0.0.22
Source: 0.0.0.0
Last reported by: Local
Timeout:
0 Type: Dynamic

show igmp group (Exclude Mode)

user@host> show igmp group
Interface: t1-0/1/0.0
Interface: t1-0/1/1.0
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Interface: local
Group: 224.0.0.2
Source: 0.0.0.0
Last reported by: Local
Timeout:
0 Type: Dynamic
Group: 224.0.0.22
Source: 0.0.0.0
Last reported by: Local
Timeout:
0 Type: Dynamic

show igmp group brief

The output for the show igmp group brief command is identical to that for the show igmp
group command.
show igmp group detail
user@host> show igmp group detail
Interface: t1-0/1/0.0
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.2
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout:
0 Type:
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.3
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout:
0 Type:
Group: 232.1.1.1
Group mode: Include
Source: 10.0.0.4
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout:
0 Type:
Group: 232.1.1.2
Group mode: Include
Source: 10.0.0.4
Source timeout: 12
Last reported by: 10.9.5.2
Group timeout:
0 Type:
Interface: t1-0/1/1.0
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Interface: local
Group: 224.0.0.2
Group mode: Exclude

Copyright 2014, Juniper Networks, Inc.

Dynamic

Dynamic

Dynamic

Dynamic

1571

Interfaces Fundamentals for Routing Devices

Source: 0.0.0.0
Source timeout: 0
Last reported by: Local
Group timeout:
0 Type: Dynamic
Group: 224.0.0.22
Group mode: Exclude
Source: 0.0.0.0
Source timeout: 0
Last reported by: Local
Group timeout:
0 Type: Dynamic

1572

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show igmp interface

List of Syntax

Syntax

Syntax (EX Series

Switches and the QFX
Series)
Release Information

Description

Options

Syntax on page 1573

Syntax (EX Series Switches and the QFX Series) on page 1573
show igmp interface
<brief | detail>
<interface-name>
<logical-system (all | logical-system-name)>
show igmp interface
<brief | detail>
<interface-name>

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.3 for the QFX Series.
Display information about Internet Group Management Protocol (IGMP)-enabled
interfaces.
noneDisplay standard information about all IGMP-enabled interfaces.
brief | detail(Optional) Display the specified level of output.
interface-name(Optional) Display information about the specified IGMP-enabled

interface only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear igmp membership on page 1518

show igmp interface on page 1575

show igmp interface brief on page 1576
show igmp interface detail on page 1576
show igmp interface <interface-name> on page 1576
Table 103 on page 1573 describes the output fields for the show igmp interface command.
Output fields are listed in the approximate order in which they appear.

Table 103: show igmp interface Output Fields

Field Name

Field Description

Level of Output

Interface

Name of the interface.

All levels

Querier

Address of the routing device that has been elected to send membership queries.

All levels

Copyright 2014, Juniper Networks, Inc.

1573

Interfaces Fundamentals for Routing Devices

Table 103: show igmp interface Output Fields (continued)

Field Name

Field Description

Level of Output

State

State of the interface: Up or Down.

All levels

SSM Map Policy

Name of the source-specific multicast (SSM) map policy that has been applied to the
IGMP interface.

All levels

Timeout

How long until the IGMP querier is declared to be unreachable, in seconds.

All levels

Version

IGMP version being used on the interface: 1 , 2 , or 3.

All levels

Groups

Number of groups on the interface.

All levels

Group limit

Maximum number of groups allowed on the interface. Any joins requested after the limit
is reached are rejected.

All levels

Group threshold

Configured threshold at which a warning message is generated.

All levels

This threshold is based on a percentage of groups received on the interface. If the number
of groups received reaches the configured threshold, the device generates a warning
message.
Group log-interval

Time (in seconds) between consecutive log messages.

All levels

Immediate Leave

State of the immediate leave option:

All levels

OnIndicates that the router removes a host from the multicast group as soon as the

router receives a leave group message from a host associated with the interface.

OffIndicates that after receiving a leave group message, instead of removing a host

from the multicast group immediately, the router sends a group query to determine if
another receiver responds.
Promiscuous Mode

State of the promiscuous mode option:

All levels

OnIndicates that the router can accept IGMP reports from subnetworks that are not

associated with its interfaces.

OffIndicates that the router can accept IGMP reports only from subnetworks that

are associated with its interfaces.

Passive

State of the passive mode option:

All levels

OnIndicates that the router can run IGMP on the interface but not send or receive

control traffic such as IGMP reports, queries, and leaves.

OffIndicates that the router can run IGMP on the interface and send or receive control

traffic such as IGMP reports, queries, and leaves.

The passive statement enables you to selectively activate up to two out of a possible
three available query or control traffic options. When enabled, the following options
appear after the on state declaration:

send-general-queryThe interface sends general queries.

send-group-queryThe interface sends group-specific and group-source-specific

queries.

1574

allow-receiveThe interface receives control traffic.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 103: show igmp interface Output Fields (continued)

Field Name

Field Description

Level of Output

OIF map

Name of the OIF map (if configured) associated with the interface.

All levels

SSM map

Name of the source-specific multicast (SSM) map (if configured) used on the interface.

All levels

Configured
Parameters

Information configured by the user:

All levels

IGMP Query IntervalInterval (in seconds) at which this router sends membership

queries when it is the querier.

IGMP Query Response IntervalTime (in seconds) that the router waits for a report in

response to a general query.

IGMP Last Member Query IntervalTime (in seconds) that the router waits for a report

in response to a group-specific query.

Derived Parameters

IGMP Robustness CountNumber of times the router retries a query.

Derived information:

All levels

IGMP Membership TimeoutTimeout period (in seconds) for group membership. If no

report is received for these groups before the timeout expires, the group membership
is removed.

IGMP Other Querier Present TimeoutTime (in seconds) that the router waits for the

IGMP querier to send a query.

Sample Output
show igmp interface
user@host> show igmp interface
Interface: at-0/3/1.0
Querier: 10.111.30.1
State:
Up Timeout:
SSM Map Policy: ssm-policy-A
Interface: so-1/0/0.0
Querier: 10.111.10.1
State:
Up Timeout:
SSM Map Policy: ssm-policy-B
Interface: so-1/0/1.0
Querier: 10.111.20.1
State:
Up Timeout:
SSM Map Policy: ssm-policy-C
Immediate Leave: On
Promiscuous Mode: Off

None Version:

2 Groups:

None Version:

2 Groups:

None Version:

2 Groups:

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Derived Parameters:
IGMP Membership Timeout: 260.0
IGMP Other Querier Present Timeout: 255.0

Copyright 2014, Juniper Networks, Inc.

1575

Interfaces Fundamentals for Routing Devices

show igmp interface brief

The output for the show igmp interface brief command is identical to that for the show
igmp interface command. For sample output, see show igmp interface on page 1575.
show igmp interface detail
The output for the show igmp interface detail command is identical to that for the show
igmp interface command. For sample output, see show igmp interface on page 1575.
show igmp interface <interface-name>
user@host# show igmp interface ge-3/2/0.0
Interface: ge-3/2/0.0
Querier: 20.1.1.1
State: Up Timeout:
None Version: 3 Groups:
Group limit: 8
Group threshold: 60
Group log-interval: 10
Immediate leave: Off
Promiscuous mode: Off

1576

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show igmp snooping interface

Syntax

Release Information
Description
Options

show igmp snooping interface interface-name

<brief | detail>
<bridge-domain bridge-domain-name>
<logical-system logical-system-name>
<virtual-switch virtual-switch-name>
<vlan-id vlan-identifier>

Command introduced in Junos OS Release 8.5.

Display IGMP snooping interface information.
none Display detailed information.
brief | detail(Optional) Display the specified level of output.
bridge-domain bridge-domain-name(Optional) Display information about a particular

bridge domain.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

virtual-switch virtual-switch-name(Optional) Display information about a particular

virtual switch.
vlan-id vlan-identifier(Optional) Display information about a particular VLAN.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show igmp snooping membership on page 1582

show igmp snooping statistics on page 1586

show igmp snooping interface on page 1578

show igmp snooping interface (Group Limit Configured) on page 1580
Table 104 on page 1577 lists the output fields for the show igmp snooping interface
command. Output fields are listed in the approximate order in which they appear.

Table 104: show igmp snooping interface Output Fields

Field Name

Field Description

Level of Output

Routing-instance

Routing instance for IGMP snooping.

All levels

Learning Domain

Learning domain for snooping.

All levels

IGMP Query Interval

Frequency (in seconds) with which this router sends membership queries when it is
the querier.

detail

Copyright 2014, Juniper Networks, Inc.

1577

Interfaces Fundamentals for Routing Devices

Table 104: show igmp snooping interface Output Fields (continued)

Field Name

Field Description

Level of Output

IGMP Query
Response Interval

Time (in seconds) that the router waits for a response to a general query.

detail

IGMP Last Member

Query Interval

Time (in seconds) that the router waits for a report in response to a group-specific
query.

detail

IGMP Robustness
Count

Number of times the router retries a query.

detail

immediate-leave

State of immediate leave: On or Off.

All levels

router-interface

Router interfaces that are part of this learning domain.

All levels

Group limit

Maximum number of (source,group) pairs allowed per interface. When a group limit
is not configured, this field is not shown.

All levels

interface

Interfaces that are being snooped in this learning domain.

All levels

Groups

Number of groups on the interface.

none

State

State of the interface: Up or Down.

none

Up Groups

Number of active multicast groups attached to the logical interface.

All levels

IGMP Membeship
Timeout

Timeout for group membership. If no report is received for these groups before the
timeout expires, the group membership is removed.

none

IGMP Other Querier

Present Timeout

Time that the router waits for the IGMP querier to send a query.

none

Sample Output
show igmp snooping interface
user@host> show igmp snooping interface logical-system all
logical-system: default
Instance: VPLS-6
Learning-Domain: default
Interface: ge-0/2/2.601
State:
Up Groups:
10
Immediate leave: Off
Router interface: no
Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Instance: VS-4
Bridge-Domain: VS-4-BD-1

1578

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Learning-Domain: vlan-id 1041

Interface: ae2.3
State:
Up Groups:
Immediate leave: Off
Router interface: no
Interface: ge-0/2/2.1041
State:
Up Groups:
Immediate leave: Off
Router interface: no

20

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Instance: default-switch
Bridge-Domain: bd-200
Learning-Domain: default
Interface: ge-0/2/2.100
State:
Up Groups:
Immediate leave: Off
Router interface: no

20

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Bridge-Domain: bd0
Learning-Domain: default
Interface: ae0.0
State:
Up Groups:
Immediate leave: Off
Router interface: yes
Interface: ae1.0
State:
Up Groups:
Immediate leave: Off
Router interface: no
Interface: ge-0/2/2.0
State:
Up Groups:
Immediate leave: Off
Router interface: no

32

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Instance: VPLS-1
Learning-Domain: default
Interface: ge-0/2/2.502
State:
Up Groups:
Immediate leave: Off
Router interface: no

11

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0

Copyright 2014, Juniper Networks, Inc.

1579

Interfaces Fundamentals for Routing Devices

IGMP Last Member Query Interval: 1.0

IGMP Robustness Count: 2
Instance: VS-1
Bridge-Domain: VS-BD-1
Learning-Domain: default
Interface: ae2.0
State:
Up Groups:
Immediate leave: Off
Router interface: no
Interface: ge-0/2/2.1010
State:
Up Groups:
Immediate leave: Off
Router interface: no

20

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Bridge-Domain: VS-BD-2
Learning-Domain: default
Interface: ae2.0
State:
Up Groups:
Immediate leave: Off
Router interface: no
Interface: ge-0/2/2.1011
State:
Up Groups:
Immediate leave: Off
Router interface: no

20

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2
Instance: VPLS-p2mp
Learning-Domain: default
Interface: ge-0/2/2.3001
State:
Up Groups:
Immediate leave: Off
Router interface: no

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2

show igmp snooping interface (Group Limit Configured)

user@host> show igmp snooping interface instance vpls1
Instance: vpls1
Learning-Domain: default
Interface: ge-1/3/9.0
State:
Up Groups:
Immediate leave: Off
Router interface: yes

1580

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Interface: ge-1/3/8.0
State:
Up Groups:
Immediate leave: Off
Router interface: yes
Group limit:
1000

Configured Parameters:
IGMP Query Interval: 125.0
IGMP Query Response Interval: 10.0
IGMP Last Member Query Interval: 1.0
IGMP Robustness Count: 2

Copyright 2014, Juniper Networks, Inc.

1581

Interfaces Fundamentals for Routing Devices

show igmp snooping membership

Syntax

Release Information
Description
Options

show igmp snooping membership

<brief | detail>
<bridge-domain bridge-domain-name>
<group group-name>
<logical-system logical-system-name>
<virtual-switch virtual-switch-name>
<vlan-id vlan-identifier>

Command introduced in Junos OS Release 8.5.

Display IGMP snooping membership information.
noneDisplay detailed information.
brief | detail(Optional) Display the specified level of output.
bridge-domain bridge-domain-name(Optional) Display information about a particular

bridge domain.
group group-name (Optional) Display information about this group address.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

virtual-switch virtual-switch-name(Optional) Display information about a particular

virtual switch.
vlan-id vlan-identifier(Optional) Display information about a particular VLAN.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show igmp snooping interface on page 1577

show igmp snooping statistics on page 1586

clear igmp snooping membership on page 1521

show igmp snooping membership on page 1583

show igmp snooping membership (Exclude Mode) on page 1584
show igmp snooping membership interface ge-0/1/2.200 on page 1584
show igmp snooping membership vlan-id 1 on page 1584
Table 105 on page 1582 lists the output fields for the show igmp snooping membership
command. Output fields are listed in the approximate order in which they appear.

Table 105: show igmp snooping membership Output Fields

Field Name

Field Description

Level of Output

Instance

Routing instance for IGMP snooping.

All levels

1582

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 105: show igmp snooping membership Output Fields (continued)

Field Name

Field Description

Level of Output

Learning Domain

Learning domain for snooping.

All levels

Interface

Interface on which this router is a proxy.

detail

Up Groups

Number of active multicast groups attached to the logical interface.

All levels

Group

Multicast group address in the membership database.

All levels

Group Mode

Mode the SSM group is operating in: Include or Exclude.

All levels

Source

Source address used on queries.

detail

Last reported by

Address of source last replying to the query.

detail

Group Timeout

Time remaining until a group in exclude mode moves to include mode. The timer
is refreshed when a listener in exclude mode sends a report. A group in include
mode or configured as a static group displays a zero timer.

All levels

Timeout

Length of time (in seconds) left until the entry is purged.

detail

Type

Way that the group membership information was learned:

detail

Include receiver

DynamicGroup membership was learned by the IGMP protocol.

StaticGroup membership was learned by configuration.

Source address of receiver included in membership with timeout (in seconds).

detail

Sample Output
show igmp snooping membership
user@host> show igmp snooping membership
Instance: vpls2
Learning-Domain: vlan-id 2
Interface: ge-3/0/0.2
Up Groups:
0
Interface: ge-3/1/0.2
Up Groups:
0
Interface: ge-3/1/5.2
Up Groups:
0
Instance: vpls1
Learning-Domain: vlan-id 1
Interface: ge-3/0/0.1
Up Groups:
0
Interface: ge-3/1/0.1
Up Groups:
0
Interface: ge-3/1/5.1
Up Groups:
1

Copyright 2014, Juniper Networks, Inc.

1583

Interfaces Fundamentals for Routing Devices

Group: 225.10.10.1
Group mode: Exclude
Source: 0.0.0.0
Last reported by: 100.6.85.2
Group timeout:
173 Type: Dynamic

show igmp snooping membership (Exclude Mode)

user@host> show igmp snooping membership
Instance: vpls2
Learning-Domain: vlan-id 2
Interface: ge-3/0/0.2
Up Groups:
0
Interface: ge-3/1/0.2
Up Groups:
0
Interface: ge-3/1/5.2
Up Groups:
0
Instance: vpls1
Learning-Domain: vlan-id 1
Interface: ge-3/0/0.1
Up Groups:
0
Interface: ge-3/1/0.1
Up Groups:
0
Interface: ge-3/1/5.1
Up Groups:
1
Group: 225.10.10.1
Group mode: Exclude
Source: 0.0.0.0
Last reported by: 100.6.85.2
Group timeout:
173 Type: Dynamic

show igmp snooping membership interface ge-0/1/2.200

user@host> show igmp snooping membership interface ge-0/1/2.200
Instance: bridge-domain bar
Learning-Domain: default
Interface: ge-0/1/2.200
Group: 225.1.1.1
Source: 0.0.0.0
Timeout:
391 Type: Static
Group: 232.1.1.1
Source: 192.168.1.1
Timeout:
0 Type: Static

show igmp snooping membership vlan-id 1

user@host> show igmp snooping membership vlanid 1
Instance: vpls2
Instance: vpls1
Learning-Domain: vlan-id 1
Interface: ge-3/0/0.1
Up Groups:
0
Interface: ge-3/1/0.1
Up Groups:
0
Interface: ge-3/1/5.1
Up Groups:
1

1584

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Group: 225.10.10.1
Group mode: Exclude
Source: 0.0.0.0
Last reported by: 100.6.85.2
Group timeout:
209 Type: Dynamic

Copyright 2014, Juniper Networks, Inc.

1585

Interfaces Fundamentals for Routing Devices

show igmp snooping statistics

Syntax

Release Information
Description
Options

show igmp snooping statistics

<brief | detail>
<bridge-domain bridge-domain-name>
<logical-system logical-system-name>
<virtual-switch virtual-switch-name>
<vlan-id vlan-identifier>

Command introduced in Junos OS Release 8.5.

Display IGMP snooping statistics.
none(Optional) Display detailed information.
brief | detail(Optional) Display the specified level of output.
bridge-domain bridge-domain-name(Optional) Display information about a particular

bridge domain.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

virtual-switch virtual-switch-name(Optional) Display information about a particular

virtual switch.
vlan-id vlan-identifier(Optional) Display information about a particular VLAN.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show igmp snooping interface on page 1577

show igmp snooping membership on page 1582

clear igmp snooping statistics on page 1522

show igmp snooping statistics on page 1587

show igmp snooping statistics logical-systems all on page 1588
show igmp snooping statistics interface (Bridge Domains Configured) on page 1589
Table 106 on page 1586 lists the output fields for the show igmp snooping statistics
command. Output fields are listed in the approximate order in which they appear.

Table 106: show igmp snooping statistics Output Fields

Field Name

Field Description

Level of Output

Routing-instance

Routing instance for IGMP snooping.

All levels

IGMP packet
statistics

Heading for IGMP snooping statistics for all interfaces or for the specified
interface.

All levels

1586

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 106: show igmp snooping statistics Output Fields (continued)

Field Name

Field Description

Level of Output

learning-domain

Appears at end of IGMP packets statistics line.

All levels

IGMP Message type

Summary of IGMP statistics:

All levels

Membership QueryNumber of membership queries sent and received.

V1 Membership ReportNumber of version 1 membership reports sent and

received.

DVMRPNumber of DVMRP messages sent or received.

PIM V1Number of PIM version 1 messages sent or received.

Cisco TraceNumber of Cisco trace messages sent or received.

V2 Membership ReportNumber of version 2 membership reports sent or

received.

Group LeaveNumber of group leave messages sent or received.

Domain Wide ReportNumber of domain-wide reports sent or received.

V3 Membership ReportNumber of version 3 membership reports sent or

received.

Other Unknown typesNumber of unknown message types received.

IGMP v3 unsupported typeNumber of messages received with unknown and

unsupported IGMP version 3 message types.

IGMP v3 source required for SSMNumber of IGMP version 3 messages

received that contained no source.

IGMP v3 mode not applicable for SSMNumber of IGMP version 3 messages

received that did not contain a mode applicable for source-specific multicast
(SSM).
Received

Number of messages received.

All levels

Sent

Number of messages sent.

All levels

Rx errors

Number of received packets that contained errors.

All levels

IGMP Global
Statistics

Summary of IGMP snooping statistics for all interfaces.

All levels

Bad LengthNumber of messages received with length errors so severe that

further classification could not occur.

Bad ChecksumNumber of messages received with a bad IP checksum. No

further classification was performed.

Rx non-localNumber of messages received from senders that are not local.

Sample Output
show igmp snooping statistics
user@host> show igmp snooping statistics
Routing-instance foo
IGMP packet statistics for all interfaces in learning-domain vlan-100
IGMP Message type

Copyright 2014, Juniper Networks, Inc.

Received

Sent

Rx errors

1587

Interfaces Fundamentals for Routing Devices

Membership Query
V1 Membership Report
DVMRP
PIM V1
Cisco Trace
V2 Membership Report
Group Leave
Domain Wide Report
V3 Membership Report
Other Unknown types
IGMP v3 unsupported type
IGMP v3 source required for
IGMP v3 mode not applicable

89
0
0
0
0
139
0
0
136

51
0
0
0
0
0
0
0
0

SSM
for SSM

IGMP Global Statistics

Bad Length
Bad Checksum
Rx non-local

0
0
0
0
0
0
0
0
0
0
0
23
0

0
0
0

Routing-instance bar
IGMP packet statistics for all interfaces in learning-domain vlan-100
IGMP Message type
Received
Membership Query
89
V1 Membership Report
0
DVMRP
0
PIM V1
0
Cisco Trace
0
V2 Membership Report
139
Group Leave
0
Domain Wide Report
0
V3 Membership Report
136
Other Unknown types
IGMP v3 unsupported type
IGMP v3 source required for SSM
IGMP v3 mode not applicable for SSM
IGMP Global Statistics
Bad Length
Bad Checksum
Rx non-local

Sent
51
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0
23
0

0
0
0

show igmp snooping statistics logical-systems all

user@host> show igmp snooping statistics logical-systems all
logical-system: default
Bridge: VPLS-6
IGMP Message type
Received
Membership Query
0
V1 Membership Report
0
DVMRP
0
PIM V1
0
Cisco Trace
0
V2 Membership Report
0
Group Leave
0
Mtrace Response
0
Mtrace Request
0
Domain Wide Report
0
V3 Membership Report
0

1588

Sent
4
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Other Unknown types

Learning-Domain: vlan-id 1041 bridge-domain VS-4-BD-1

IGMP Message type
Received
Sent Rx errors
Membership Query
0
4
0
V1 Membership Report
0
0
0
DVMRP
0
0
0
PIM V1
0
0
0
Cisco Trace
0
0
0
V2 Membership Report
0
0
0
Group Leave
0
0
0
Mtrace Response
0
0
0
Mtrace Request
0
0
0
Domain Wide Report
0
0
0
V3 Membership Report
0
0
0
Other Unknown types
0
Bridge: VPLS-p2mp
IGMP Message type
Membership Query
V1 Membership Report
DVMRP
PIM V1
Cisco Trace
V2 Membership Report
Group Leave
Mtrace Response
Mtrace Request
Domain Wide Report
V3 Membership Report
Other Unknown types

Received
0
0
0
0
0
0
0
0
0
0
0

Sent
2
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0
0

Bridge: VS-BD-1
IGMP Message type
Membership Query
V1 Membership Report
DVMRP
PIM V1
Cisco Trace
V2 Membership Report
Group Leave
Mtrace Response
Mtrace Request
Domain Wide Report
V3 Membership Report
Other Unknown types

Received
0
0
0
0
0
0
0
0
0
0
0

Sent
6
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0
0

show igmp snooping statistics interface (Bridge Domains Configured)

user@host> show igmp snooping statistics interface
Bridge: bridge-domain1
IGMP interface packet statistics for ge-2/0/8.0
IGMP Message type
Received
Sent Rx errors
Membership Query
0
2
0
V1 Membership Report
0
0
0
DVMRP
0
0
0
PIM V1
0
0
0
Cisco Trace
0
0
0
V2 Membership Report
0
0
0

Copyright 2014, Juniper Networks, Inc.

1589

Interfaces Fundamentals for Routing Devices

Group Leave
Mtrace Response
Mtrace Request
Domain Wide Report
V3 Membership Report
Other Unknown types

0
0
0
0
0

0
0
0
0
0

0
0
0
0
0
0

Bridge: bridge-domain2
IGMP interface packet statistics for ge-2/0/8.0
IGMP Message type
Received
Sent Rx errors
Membership Query
0
2
0
V1 Membership Report
0
0
0
DVMRP
0
0
0
PIM V1
0
0
0
Cisco Trace
0
0
0
V2 Membership Report
0
0
0
Group Leave
0
0
0
Mtrace Response
0
0
0
Mtrace Request
0
0
0
Domain Wide Report
0
0
0
V3 Membership Report
0
0
0
Other Unknown types
0

1590

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show igmp statistics

List of Syntax

Syntax

Syntax on page 1591

Syntax (EX Series Switch and the QFX Series) on page 1591
show igmp statistics
<brief | detail>
<interface interface-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show igmp statistics

<brief | detail>
<interface interface-name>

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.3 for the QFX Series.

Description
Options

Display Internet Group Management Protocol (IGMP) statistics.

noneDisplay IGMP statistics for all interfaces.
brief | detail(Optional) Display the specified level of output.
interface interface-name(Optional) Display IGMP statistics about the specified interface

only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear igmp statistics on page 1523

show igmp statistics on page 1592

show igmp statistics interface on page 1593
Table 107 on page 1591 describes the output fields for the show igmp statistics command.
Output fields are listed in the approximate order in which they appear.

Table 107: show igmp statistics Output Fields

Field Name

Field Description

IGMP packet statistics

Heading for IGMP packet statistics for all interfaces or for the specified interface name.

Copyright 2014, Juniper Networks, Inc.

1591

Interfaces Fundamentals for Routing Devices

Table 107: show igmp statistics Output Fields (continued)

Field Name

Field Description

IGMP Message type

Summary of IGMP statistics:

Membership QueryNumber of membership queries sent and received.

V1 Membership ReportNumber of version 1 membership reports sent and received.

DVMRPNumber of DVMRP messages sent or received.

PIM V1Number of PIM version 1 messages sent or received.

Cisco TraceNumber of Cisco trace messages sent or received.

V2 Membership ReportNumber of version 2 membership reports sent or received.

Group LeaveNumber of group leave messages sent or received.

Mtrace ResponseNumber of Mtrace response messages sent or received.

Mtrace RequestNumber of Mtrace request messages sent or received.

Domain Wide ReportNumber of domain-wide reports sent or received.

V3 Membership ReportNumber of version 3 membership reports sent or received.

Other Unknown typesNumber of unknown message types received.

IGMP v3 unsupported typeNumber of messages received with unknown and unsupported IGMP

version 3 message types.

IGMP v3 source required for SSMNumber of IGMP version 3 messages received that contained no

source.

IGMP v3 mode not applicable for SSMNumber of IGMP version 3 messages received that did not

contain a mode applicable for source-specific multicast (SSM).

Received

Number of messages received.

Sent

Number of messages sent.

Rx errors

Number of received packets that contained errors.

IGMP Global Statistics

Summary of IGMP statistics for all interfaces.

Bad LengthNumber of messages received with length errors so severe that further classification

could not occur.

Bad ChecksumNumber of messages received with a bad IP checksum. No further classification

was performed.

Bad Receive IfNumber of messages received on an interface not enabled for IGMP.

Rx non-localNumber of messages received from senders that are not local.

Timed outNumber of groups that timed out as a result of not receiving an explicit leave message.

Rejected ReportNumber of reports dropped because of the IGMP group policy.

Total InterfacesNumber of interfaces configured to support IGMP.

Sample Output
show igmp statistics
user@host> show igmp statistics
IGMP packet statistics for all interfaces
IGMP Message type
Received
Sent
Membership Query
8883
459
V1 Membership Report
0
0

1592

Rx errors
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

DVMRP
0
PIM V1
0
Cisco Trace
0
V2 Membership Report
0
Group Leave
0
Mtrace Response
0
Mtrace Request
0
Domain Wide Report
0
V3 Membership Report
0
Other Unknown types
IGMP v3 unsupported type
IGMP v3 source required for SSM
IGMP v3 mode not applicable for SSM
IGMP Global Statistics
Bad Length
Bad Checksum
Bad Receive If
Rx non-local
Timed out
Rejected Report
Total Interfaces

0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0
0
0
0

0
0
0
1227
0
0
2

show igmp statistics interface

user@host> show igmp statistics interface fe-1/0/1.0
IGMP interface packet statistics for fe-1/0/1.0
IGMP Message type
Received
Sent Rx errors
Membership Query
0
230
0
V1 Membership Report
0
0
0

Copyright 2014, Juniper Networks, Inc.

1593

Interfaces Fundamentals for Routing Devices

show mld group

Syntax

Release Information
Description
Options

show mld group

<brief | detail>
<group-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display information about Multicast Listener Discovery (MLD) group membership.
noneDisplay standard information about all MLD groups.
brief | detail(Optional) Display the specified level of output.
group-name(Optional) Display MLD information about the specified group.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear mld membership on page 1525

show mld group (Include Mode) on page 1595

show mld group (Exclude Mode) on page 1596
show mld group brief on page 1596
show mld group detail (Include Mode) on page 1596
show mld group detail (Exclude Mode) on page 1597
Table 108 on page 1594 describes the output fields for the show mld group command.
Output fields are listed in the approximate order in which they appear.

Table 108: show mld group Output Fields

Field Name

Field Description

Level of Output

Interface

Name of the interface that received the MLD membership report; local means
that the local router joined the group itself.

All levels

Group

Group address.

All levels

Source

Source address.

All levels

Group Mode

Mode the SSM group is operating in: Include or Exclude.

All levels

Last reported by

Address of the host that last reported membership in this group.

All levels

1594

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 108: show mld group Output Fields (continued)

Field Name

Field Description

Level of Output

Source timeout

Time remaining until the group traffic is no longer forwarded. The timer is
refreshed when a listener in include mode sends a report. A group in exclude
mode or configured as a static group displays a zero timer.

detail

Timeout

Time remaining until the group membership is removed.

brief none

Group timeout

Time remaining until a group in exclude mode moves to include mode. The timer
is refreshed when a listener in exclude mode sends a report. A group in include
mode or configured as a static group displays a zero timer.

detail

Type

Type of group membership:

All levels

DynamicHost reported the membership.

StaticMembership is configured.

Sample Output
show mld group
(Include Mode)
user@host> show mld group
Interface: fe-0/1/2.0
Group: ff02::1:ff05:1a67
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
245 Type: Dynamic
Group: ff02::1:ffa8:c35e
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
241 Type: Dynamic
Group: ff02::2:43e:d7f6
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
244 Type: Dynamic
Group: ff05::2
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
244 Type: Dynamic
Interface: local
Group: ff02::2
Source: ::
Last reported by: Local
Timeout:
0 Type: Dynamic
Group: ff02::16
Source: ::
Last reported by: Local
Timeout:
0 Type: Dynamic

Copyright 2014, Juniper Networks, Inc.

1595

Interfaces Fundamentals for Routing Devices

show mld group (Exclude Mode)

user@host> show mld group
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Group: ff02::6
Source: ::
Last reported by: fe80::21f:12ff:feb6:4b3a
Timeout:
245 Type: Dynamic
Group: ff02::16
Source: ::
Last reported by: fe80::21f:12ff:feb6:4b3a
Timeout:
28 Type: Dynamic
Interface: local
Group: ff02::2
Source: ::
Last reported by: Local
Timeout:
0 Type: Dynamic
Group: ff02::16
Source: ::
Last reported by: Local
Timeout:
0 Type: Dynamic

show mld group brief

The output for the show mld group brief command is identical to that for the show mld
group command. For sample output, see show mld group (Include Mode) on page 1595
show mld group (Exclude Mode) on page 1596.
show mld group detail (Include Mode)
user@host> show mld group detail
Interface: fe-0/1/2.0
Group: ff02::1:ff05:1a67
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
224 Type: Dynamic
Group: ff02::1:ffa8:c35e
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
220 Type: Dynamic
Group: ff02::2:43e:d7f6
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
223 Type: Dynamic
Group: ff05::2
Group mode: Include
Source: ::
Last reported by: fe80::2e0:81ff:fe05:1a67
Timeout:
223 Type: Dynamic
Interface: so-1/0/1.0
Group: ff02::2
Group mode: Include
Source: ::
Last reported by: fe80::280:42ff:fe15:f445
Timeout:
258 Type: Dynamic
Interface: local

1596

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Group: ff02::2
Group mode: Include
Source: ::
Last reported by: Local
Timeout:
0 Type: Dynamic
Group: ff02::16
Source: ::
Last reported by: Local
Timeout:
0 Type: Dynamic

show mld group detail (Exclude Mode)

user@host> show mld group detail
Interface: ge-0/2/2.0
Interface: ge-0/2/0.0
Group: ff02::6
Group mode: Exclude
Source: ::
Source timeout: 0
Last reported by: fe80::21f:12ff:feb6:4b3a
Group timeout:
226 Type: Dynamic
Group: ff02::16
Group mode: Exclude
Source: ::
Source timeout: 0
Last reported by: fe80::21f:12ff:feb6:4b3a
Group timeout:
246 Type: Dynamic
Interface: local
Group: ff02::2
Group mode: Exclude
Source: ::
Source timeout: 0
Last reported by: Local
Group timeout:
0 Type: Dynamic
Group: ff02::16
Group mode: Exclude
Source: ::
Source timeout: 0
Last reported by: Local
Group timeout:
0 Type: Dynamic

Copyright 2014, Juniper Networks, Inc.

1597

Interfaces Fundamentals for Routing Devices

show mld interface

Syntax

Release Information
Description
Options

show mld interface

<brief | detail>
<interface-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display information about Multicast Listener Discovery (MLD)-enabled interfaces.
noneDisplay standard information about all MLD-enabled interfaces.
brief | detail(Optional) Display the specified level of output.
interface-name(Optional) Display information about the specified interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear mld membership on page 1525

show mld interface on page 1600

show mld interface brief on page 1600
show mld interface detail on page 1601
show mld interface <interface-name> on page 1601
Table 109 on page 1598 describes the output fields for the show mld interface command.
Output fields are listed in the approximate order in which they appear.

Table 109: show mld interface Output Fields

Field Name

Field Description

Level of Output

Interface

Name of the interface.

All levels

Querier

Address of the router that has been elected to send membership queries.

All levels

State

State of the interface: Up or Down.

All levels

SSM Map Policy

Name of the source-specific multicast (SSM) map policy that has been applied
to the interface.

All levels

SSM Map Policy

Name of the source-specific multicast (SSM) map policy at the MLD interface.

All levels

Timeout

How long until the MLD querier is declared to be unreachable, in seconds.

All levels

Version

MLD version being used on the interface: 1 or 2.

All levels

1598

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 109: show mld interface Output Fields (continued)

Field Name

Field Description

Level of Output

Groups

Number of groups on the interface.

All levels

Passive

State of the passive mode option:

All levels

OnIndicates that the router can run IGMP or MLD on the interface but not

send or receive control traffic such as IGMP or MLD reports, queries, and
leaves.

OffIndicates that the router can run IGMP or MLD on the interface and send

or receive control traffic such as IGMP or MLD reports, queries, and leaves.
The passive statement enables you to selectively activate up to two out of a
possible three available query or control traffic options. When enabled, the
following options appear after the on state declaration:

send-general-queryThe interface sends general queries.

send-group-queryThe interface sends group-specific and

group-source-specific queries.

allow-receiveThe interface receives control traffic

OIF map

Name of the OIF map associated to the interface.

All levels

SSM map

Name of the source-specific multicast (SSM) map used on the interface, if

configured.

All levels

Group limit

Maximum number of groups allowed on the interface. Any memberships

requested after the limit is reached are rejected.

All levels

Group threshold

Configured threshold at which a warning message is generated.

All levels

This threshold is based on a percentage of groups received on the interface. If

the number of groups received reaches the configured threshold, the device
generates a warning message.
Group log-interval

Time (in seconds) between consecutive log messages.

All levels

Immediate Leave

State of the immediate leave option:

All levels

OnIndicates that the router removes a host from the multicast group as

soon as the router receives a multicast listener done message from a host
associated with the interface.

OffIndicates that after receiving a multicast listener done message, instead

of removing a host from the multicast group immediately, the router sends
a group query to determine if another receiver responds.

Copyright 2014, Juniper Networks, Inc.

1599

Interfaces Fundamentals for Routing Devices

Table 109: show mld interface Output Fields (continued)

Field Name

Field Description

Level of Output

Configured
Parameters

Information configured by the user.

All levels

MLD Query Interval (.1 secs)Interval at which this router sends membership

queries when it is the querier.

MLD Query Response Interval (.1 secs)Time that the router waits for a report

in response to a general query.

MLD Last Member Query Interval (.1 secs)Time that the router waits for a

report in response to a group-specific query.

Derived Parameters

MLD Robustness CountNumber of times the router retries a query.

Derived information.

All levels

MLD Membership Timeout (.1 secs)Timeout period for group membership.

If no report is received for these groups before the timeout expires, the group
membership will be removed.

MLD Other Querier Present Timeout (.1 secs)Time that the router waits for

the IGMP querier to send a query.

Sample Output
show mld interface
user@host> show mld interface
Interface: fe-0/0/0
Querier: None
State: Up
Timeout:
SSM Map Policy: ssm-policy-A
Interface: at-0/3/1.0
Querier: 8038::c0a8:c345
State: Up
Timeout:
SSM Map Policy: ssm-policy-B
Interface: fe-1/0/1.0
Querier: ::192.168.195.73
State: Up
Timeout:
SSM Map Policy: ssm-policy-C
SSM map: ipv6map1
Immediate Leave: On

Version:

Groups:

None

Version:

Groups:

None

Version:

Groups:

Configured Parameters:
MLD Query Interval (.1 secs): 1250
MLD Query Response Interval (.1 secs): 100
MLD Last Member Query Interval (.1 secs): 10
MLD Robustness Count: 2
Derived Parameters:
MLD Membership Timeout (.1secs): 2600
MLD Other Querier Present Timeout (.1 secs): 2550

show mld interface brief

The output for the show mld interface brief command is identical to that for the show
mld interface command. For sample output, see show mld interface on page 1600.

1600

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show mld interface detail

The output for the show mld interface detail command is identical to that for the show
mld interface command. For sample output, see show mld interface on page 1600.
show mld interface <interface-name>
user@host# show mld interface ge-3/2/0.0
Interface: ge-3/2/0.0
Querier: 20.1.1.1
State: Up Timeout:
None Version:
Group limit: 8
Group threshold: 60
Group log-interval: 10
Immediate leave: Off
Promiscuous mode: Off

Copyright 2014, Juniper Networks, Inc.

3 Groups:

1601

Interfaces Fundamentals for Routing Devices

show mld statistics

Syntax

Release Information
Description
Options

show mld statistics

<interface interface-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display information about Multicast Listener Discovery (MLD) statistics.
noneDisplay MLD statistics for all interfaces.
interface interface-name(Optional) Display statistics about the specified interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear mld statistics on page 1526

show mld statistics on page 1603

show mld statistics interface on page 1604
Table 110 on page 1602 describes the output fields for the show mld statistics command.
Output fields are listed in the approximate order in which they appear.

Table 110: show mld statistics Output Fields

1602

Field Name

Field Description

Received

Number of received packets.

Sent

Number of transmitted packets.

Rx errors

Number of received packets that contained errors.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 110: show mld statistics Output Fields (continued)

Field Name

Field Description

MLD Message type

Summary of MLD statistics.

Listener Query (v1/v2)Number of membership queries sent and received.

Listener Report (v1)Number of version 1 membership reports sent

and received.

Listener Done (v1/v2)Number of Listener Done messages sent

and received.

Listener Report (v2)Number of version 2 membership reports sent

and received.

Other Unknown typesNumber of unknown message types received.

MLD v2 source required for SSMNumber of MLD version 2 messages

received that contained no source.

MLD v2 mode not applicable for SSMNumber of MLD version 2 messages

received that did not contain a mode applicable for source-specific

multicast (SSM).
MLD Global Statistics

Summary of MLD statistics for all interfaces.

Bad LengthNumber of messages received with length errors so severe

that further classification could not occur.

Bad ChecksumNumber of messages received with an invalid IP

checksum. No further classification was performed.

Bad Receive IfNumber of messages received on an interface not enabled

for MLD.

Rx non-localNumber of messages received from nonlocal senders.

Timed outNumber of groups that timed out as a result of not receiving

an explicit leave message.

Rejected ReportNumber of reports dropped because of the MLD group

policy.

Total InterfacesNumber of interfaces configured to support IGMP.

Sample Output
show mld statistics
user@host> show mld statistics
MLD packet statistics for all interfaces
MLD Message type
Received
Listener Query (v1/v2)
0
Listener Report (v1)
0
Listener Done (v1/v2)
0
Listener Report (v2)
0
Other Unknown types
MLD v2 source required for SSM
2
MLD v2 mode not applicable for SSM 0
MLD Global Statistics
Bad Length
Bad Checksum
Bad Receive If
Rx non-local
Timed out

Copyright 2014, Juniper Networks, Inc.

Sent
2
0
0
0

Rx errors
0
0
0
0
0

0
0
0
0
0

1603

Interfaces Fundamentals for Routing Devices

Rejected Report
Total Interfaces

0
2

show mld statistics interface

user@host> show mld statistics interface fe-1/0/1.0
MLD interface packet statistics for fe-1/0/1.0
MLD Message type
Received
Sent
Listener Query (v1/v2)
0
2
Listener Report (v1)
0
0
Listener Done (v1/v2)
0
0
Listener Report (v2)
0
0
Other Unknown types
MLD v2 source required for SSM
2
MLD v2 mode not applicable for SSM 0
MLD Global Statistics
Bad Length
Bad Checksum
Bad Receive If
Rx non-local
Timed out
Rejected Report
Total Interfaces

1604

Rx errors
0
0
0
0
0

0
0
0
0
0
0
2

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show msdp
Syntax

show msdp
<brief | detail>
<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.

Description

Display Multicast Source Discovery Protocol (MSDP) information.

Options

noneDisplay standard MSDP information for all routing instances.

brief | detail(Optional) Display the specified level of output.
instance instance-name(Optional) Display information for the specified instance only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

peer peer-address(Optional) Display information about the specified peer only,

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show msdp source on page 1607

show msdp source-active on page 1609

show msdp statistics on page 1612

show msdp on page 1606

show msdp brief on page 1606
show msdp detail on page 1606
Table 111 on page 1605 describes the output fields for the show msdp command. Output
fields are listed in the approximate order in which they appear.

Table 111: show msdp Output Fields

Field Name

Field Description

Level of Output

Peer address

IP address of the peer.

All levels

Local address

Local address of the peer.

All levels

State

Status of the MSDP connection: Listen, Established, or Inactive.

All levels

Last up/down

Time at which the most recent peer-state change occurred.

All levels

Copyright 2014, Juniper Networks, Inc.

1605

Interfaces Fundamentals for Routing Devices

Table 111: show msdp Output Fields (continued)

Field Name

Field Description

Level of Output

Peer-Group

Peer group name.

All levels

SA Count

Number of source-active cache entries advertised by each peer that were

accepted, compared to the number that were received, in the format
number-accepted/number-received.

All levels

Peer Connect Retries

Number of peer connection retries.

detail

State timer expires

Number of seconds before another message is sent to a peer.

detail

Peer Times out

Number of seconds to wait for a response from the peer before the peer is
declared unavailable.

detail

SA accepted

Number of entries in the source-active cache accepted from the peer.

detail

SA received

Number of entries in the source-active cache received by the peer.

detail

Sample Output
show msdp
user@host> show msdp
Peer address
Local address
198.32.8.193
198.32.8.195
198.32.8.194
198.32.8.195
198.32.8.196
198.32.8.195
198.32.8.197
198.32.8.195
198.32.8.198
198.32.8.195

State
Last up/down Peer-Group
Established 5d 19:25:44 North23
Established 3d 19:27:27 North23
Established 5d 19:39:36 North23
Established 5d 19:32:27 North23
Established 3d 19:33:04 North23

SA Count
120/150
300/345
10/13
5/6
2305/3000

show msdp brief

The output for the show msdp brief command is identical to that for the show msdp
command. For sample output, see show msdp on page 1606.
show msdp detail
user@host> show msdp detail
Peer: 10.255.70.15
Local address: 10.255.70.19
State: Established
Peer Connect Retries: 0
State timer expires: 22
Peer Times out: 49
SA accepted: 0
SA received: 0

1606

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show msdp source

Syntax

Release Information

Description
Options

show msdp source

<instance instance-name>
<logical-system (all | logical-system-name)>
<source-address>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.
Display multicast sources learned from Multicast Source Discovery Protocol (MSDP).
noneDisplay standard MSDP source information for all routing instances.
instance instance-name(Optional) Display information for the specified instance only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

source-address(Optional) IP address and optional prefix length. Display information

for the specified source address only.

Required Privilege
Level
Related
Documentation

List of Sample Output

view

show msdp on page 1605

show msdp source-active on page 1609

show msdp statistics on page 1612

show msdp source on page 1608

Copyright 2014, Juniper Networks, Inc.

1607

Interfaces Fundamentals for Routing Devices

Output Fields

Table 112 on page 1608 describes the output fields for the show msdp source command.
Output fields are listed in the approximate order in which they appear.

Table 112: show msdp source Output Fields

Field Name

Field Description

Source address

IP address of the source.

/Len

Length of the prefix for this IP address.

Type

Discovery method for this multicast source:

ConfiguredSource-active limit explicitly configured for this

source.

DynamicSource-active limit established when this source was

discovered.
Maximum

Source-active limit applied to this source.

Threshold

Source-active threshold applied to this source.

Exceeded

Number of source-active messages received from this source

exceeding the established maximum.

Sample Output
show msdp source
user@host> show msdp source
Source address /Len
Type
Maximum
Threshold
0.0.0.0
/0
Configured
5
none
10.1.0.0
/16
Configured
500
none
10.1.1.1
/32
Configured
10000
none
10.1.1.2
/32
Dynamic
6936
none
10.1.5.5
/32
Dynamic
500
none
10.2.1.1
/32
Dynamic
2
none

1608

Exceeded
0
0
0
0
123
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show msdp source-active

Syntax

Release Information

Description
Options

show msdp source-active

<brief | detail>
<group group>
<instance instance-name>
<local>
<logical-system (all | logical-system-name)>
<originator originator>
<peer peer-address>
<source source-address>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.
Display the Multicast Source Discovery Protocol (MSDP) source-active cache.
noneDisplay standard MSDP source-active cache information for all routing instances.
brief | detail(Optional) Display the specified level of output.
group group(Optional) Display source-active cache information for the specified group.
instance instance-name(Optional) Display information for the specified instance.
local(Optional) Display all source-active caches originated by this router.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

originator originator(Optional) Display information about the peer that originated the

source-active cache entries.

peer peer-address(Optional) Display the source-active cache of the specified peer.
source source-address(Optional) Display the source-active cache of the specified source.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show msdp on page 1605

show msdp source on page 1607

show msdp statistics on page 1612

show msdp source-active on page 1610

show msdp source-active brief on page 1610
show msdp source-active detail on page 1611
show msdp source-active source on page 1611
Table 113 on page 1610 describes the output fields for the show msdp source-active
command. Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1609

Interfaces Fundamentals for Routing Devices

Table 113: show msdp source-active Output Fields

Field Name

Field Description

Global active
source limit
exceeded

Number of times all peers have exceeded configured active source limits.

Global active
source limit
maximum

Configured number of active source messages accepted by the device.

Global active
source limit
threshold

Configured threshold for applying random early discard (RED) to drop some
but not all MSDP active source messages.

Global active
source limit
log-warning

Threshold at which a warning message is logged (percentage of the number of

active source messages accepted by the device).

Global active
source limit log
interval

Time (in seconds) between consecutive log messages.

Group address

Multicast address of the group.

Source address

IP address of the source.

Peer address

IP address of the peer.

Originator

Router ID configured on the source of the rendezvous point (RP) that originated
the message, or the loopback address when the router ID is not configured.

Flags

Flags: Accept, Reject, or Filtered.

Sample Output
show msdp source-active
user@host> show msdp source-active
Group address
Source address Peer address
230.0.0.0
192.168.195.46 local
230.0.0.1
192.168.195.46 local
230.0.0.2
192.168.195.46 local
230.0.0.3
192.168.195.46 local
230.0.0.4
192.168.195.46 local

Originator
10.255.14.30
10.255.14.30
10.255.14.30
10.255.14.30
10.255.14.30

Flags
Accept
Accept
Accept
Accept
Accept

show msdp source-active brief

The output for the show msdp source-active brief command is identical to that for the
show msdp source-active command. For sample output, see show msdp source-active
on page 1610.

1610

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show msdp source-active detail

The output for the show msdp source-active detail command is identical to that for the
show msdp source-active command. For sample output, see show msdp source-active
on page 1610.
show msdp source-active source
user@host> show msdp source-active source 192.168.215.246
Global active source limit exceeded: 0
Global active source limit maximum: 25000
Global active source limit threshold: 24000
Global active source limit log-warning: 100
Global active source limit log interval: 0
Group address
226.2.2.1
226.2.2.3
226.2.2.4
226.2.2.5
226.2.2.7
226.2.2.10
226.2.2.11
226.2.2.13
226.2.2.14
226.2.2.15

Copyright 2014, Juniper Networks, Inc.

Source address
192.168.215.246
192.168.215.246
192.168.215.246
192.168.215.246
192.168.215.246
192.168.215.246
192.168.215.246
192.168.215.246
192.168.215.246
192.168.215.246

Peer address
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140

Originator
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140
10.255.182.140

Flags
Accept
Accept
Accept
Accept
Accept
Accept
Accept
Accept
Accept
Accept

1611

Interfaces Fundamentals for Routing Devices

show msdp statistics

Syntax

Release Information

Description
Options

show msdp statistics

<instance instance-name>
<logical-system (all | logical-system-name)>
<peer peer-address>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.
Display statistics about Multicast Source Discovery Protocol (MSDP) peers.
noneDisplay statistics about all MSDP peers for all routing instances.
instance instance-name(Optional) Display statistics about a specific MSDP instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

peer peer-address(Optional) Display statistics about a particular MSDP peer.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear msdp statistics on page 1528

show msdp statistics on page 1614

show msdp statistics peer on page 1614
Table 114 on page 1612 describes the output fields for the show msdp statistics command.
Output fields are listed in the approximate order in which they appear.

Table 114: show msdp statistics Output Fields

1612

Field Name

Field Description

Global active source limit

exceeded

Number of times all peers have exceeded configured active source

limits.

Global active source limit

maximum

Configured number of active source messages accepted by the

device.

Global active source limit

threshold

Configured threshold for applying random early discard (RED) to

drop some but not all MSDP active source messages.

Global active source limit

log-warning

Threshold at which a warning message is logged (percentage of

the number of active source messages accepted by the device).

Global active source limit

log interval

Time (in seconds) between consecutive log messages.

Peer

Address of peer.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 114: show msdp statistics Output Fields (continued)

Field Name

Field Description

Last State Change

How long ago the peer state changed.

Last message received from

the peer

How long ago the last message was received from the peer.

RPF Failures

Number of reverse path forwarding (RPF) failures.

Remote Closes

Number of times the remote peer closed.

Peer Timeouts

Number of peer timeouts.

SA messages sent

Number of source-active messages sent.

SA messages received

Number of source-active messages received.

SA request messages sent

Number of source-active request messages sent.

SA request messages
received

Number of source-active request messages received.

SA response messages sent

Number of source-active response messages sent.

SA response messages
received

Number of source-active response messages received.

Active source exceeded

Number of times this peer has exceeded configured source-active

limits.

Active source Maximum

Configured number of active source messages accepted by this

peer.

Active source threshold

Configured threshold on this peer for applying random early discard

(RED) to drop some but not all MSDP active source messages.

Active source log-warning

Configured threshold on this peer at which a warning message is

logged (percentage of the number of active source messages
accepted by the device).

Active source log-interval

Time (in seconds) between consecutive log messages on this peer.

Keepalive messages sent

Number of keepalive messages sent.

Keepalive messages
received

Number of keepalive messages received.

Unknown messages
received

Number of unknown messages received.

Copyright 2014, Juniper Networks, Inc.

1613

Interfaces Fundamentals for Routing Devices

Table 114: show msdp statistics Output Fields (continued)

Field Name

Field Description

Error messages received

Number of error messages received.

Sample Output
show msdp statistics
user@host> show msdp statistics
Global active source limit exceeded: 0
Global active source limit maximum: 10
Global active source limit threshold: 8
Global active source limit log-warning: 60
Global active source limit log interval: 60
Peer: 10.255.245.39
Last State Change: 11:54:49 (00:24:59)
Last message received from peer: 11:53:32 (00:26:16)
RPF Failures: 0
Remote Closes: 0
Peer Timeouts: 0
SA messages sent: 376
SA messages received: 459
SA request messages sent: 0
SA request messages received: 0
SA response messages sent: 0
SA response messages received: 0
Active source exceeded: 0
Active source Maximum: 10
Active source threshold: 8
Active source log-warning: 60
Active source log-interval 120
Keepalive messages sent: 17
Keepalive messages received: 19
Unknown messages received: 0
Error messages received: 0

show msdp statistics peer

user@host> show msdp statistics peer 10.255.182.140
Peer: 10.255.182.140
Last State Change: 8:19:23 (00:01:08)
Last message received from peer: 8:20:05 (00:00:26)
RPF Failures: 0
Remote Closes: 0
Peer Timeouts: 0
SA messages sent: 17
SA messages received: 16
SA request messages sent: 0
SA request messages received: 0
SA response messages sent: 0
SA response messages received: 0
Active source exceeded: 20
Active source Maximum: 10
Active source threshold: 8
Active source log-warning: 60
Active source log-interval: 120
Keepalive messages sent: 0

1614

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Keepalive messages received: 0

Unknown messages received: 0
Error messages received: 0

Copyright 2014, Juniper Networks, Inc.

1615

Interfaces Fundamentals for Routing Devices

show multicast backup-pe-groups

Syntax

Release Information
Description

Options

show multicast backup-pe-groups

<address pe-address>
<group group-name>
<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced in Junos OS Release 9.0.

Display backup PE router group information when ingress PE redundancy is configured.
Ingress PE redundancy provides a backup resource when point-to-multipoint LSPs are
configured for multicast distribution.
noneDisplay standard information about all backup PE groups.
address pe-address(Optional) Display the groups that a PE address is associated with.
group group(Optional) Display the backup PE group information for a particular group.
instance instance-name(Optional) Display backup PE group information for a specific

multicast instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show multicast backup-pe-groups on page 1617

Table 115 on page 1616 describes the output fields for the show multicast backup-pe-groups
command. Output fields are listed in the approximate order in which they appear.

Table 115: show multicast backup-pe-groups Output Fields

Field Name

Field Description

Backup PE Group

Group name.

Designated PE

Primary PE router. Address of the PE router that is currently forwarding traffic on the static route.

Transitions

Number of times that the designated PE router has transitioned from the most eligible PE router
to a backup PE router and back again to the most eligible PE router.

Last Transition

Time of the most recent transition.

Local Address

Address of the local PE router.

Backup PE List

List of PE routers that are configured to be backups for the group.

1616

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show multicast backup-pe-groups
user@host> show multicast backup-pe-groups
Instance: master
Backup PE group: b1
Designated PE:
Transitions:
Last Transition:
Local Address:
Backup PE List:

10.255.165.7
1
03:15:01
10.255.165.7
10.255.165.8

Backup PE group: b2
Designated PE:
Transitions:
Last Transition:
Local Address:
Backup PE List:

10.255.165.7
2
02:58:20
10.255.165.7
10.255.165.9
10.255.165.8

Copyright 2014, Juniper Networks, Inc.

1617

Interfaces Fundamentals for Routing Devices

show multicast flow-map

List of Syntax

Syntax

Syntax on page 1618

Syntax (EX Series Switch and the QFX Series) on page 1618
show multicast flow-map
<brief | detail>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show multicast flow-map

<brief | detail>

Release Information

Command introduced in Junos OS Release 8.2.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Display configuration information about IP multicast flow maps.

noneDisplay configuration information about IP multicast flow maps on all systems.
brief | detail(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show multicast flow-map on page 1619

show multicast flow-map detail on page 1619
Table 116 on page 1618 describes the output fields for the show multicast flow-map
command. Output fields are listed in the approximate order in which they appear.

Table 116: show multicast flow-map Output Fields

Field Name

Field Description

Levels of Output

Name

Name of the flow map.

All levels

Policy

Name of the policy associated with the flow map.

All levels

Cache-timeout

Cache timeout value assigned to the flow map.

All levels

Bandwidth

Bandwidth setting associated with the flow map.

All levels

Adaptive

Whether or not adaptive mode is enabled for the flow map.

none

Flow-map

Name of the flow map.

detail

1618

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 116: show multicast flow-map Output Fields (continued)

Field Name

Field Description

Levels of Output

Adaptive
Bandwidth

Whether or not adaptive mode is enabled for the flow map.

detail

Redundant Sources

Redundant sources defined for the same destination group.

detail

Sample Output
show multicast flow-map
user@host> show multicast flow-map
Instance: master
Name
Policy
map2
policy2
map1
policy1

Cache timeout
never
60 seconds

Bandwidth Adaptive
2000000 no
2000000 no

Sample Output
show multicast flow-map detail
user@host> show multicast flow-map detail
Instance: master
Flow-map: map1
Policy:
policy1
Cache Timeout:
600 seconds
Bandwidth:
2000000
Adaptive Bandwidth: yes
Redundant Sources: 11.11.11.11
Redundant Sources: 11.11.11.12
Redundant Sources: 11.11.11.13

Copyright 2014, Juniper Networks, Inc.

1619

Interfaces Fundamentals for Routing Devices

show multicast forwarding-cache statistics

Syntax

show multicast forwarding-cache statistics

<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>

Release Information

Command introduced in Junos OS Release 12.2.

Description

Display IP multicast forwarding cache statistics.

Options

noneDisplay multicast forwarding cache statistics for all supported address families

for all routing instances.

inet | inet6(Optional) Display multicast forwarding cache statistics for IPv4 or IPv6

family addresses, respectively.

instance instance-name(Optional) Display multicast forwarding cache statistics for a

specific routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear multicast forwarding-cache on page 1531

show multicast forwarding-cache statistics on page 1621

show multicast forwarding-cache statistics instance on page 1621
Table 117 on page 1620 describes the output fields for the show multicast forwarding-cache
statistics command. Output fields are listed in the approximate order in which they
appear.

Table 117: show multicast forwarding-cache statistics Output Fields

Field Name

Field Description

Instance

Name of the routing instance for which multicast forwarding cache statistics are displayed.

Family

Protocol family for which multicast forwarding cache statistics are displayed: ALL, INET, or INET6.

Suppress Threshold

Maximum number of multicast forwarding cache entries that can be added to the cache. When the
number of entries reaches the configured threshold, the device suspends adding new multicast
forwarding cache entries.

Reuse Value

Number of multicast forwarding cache entries that must be reached before the device creates new
multicast forwarding cache entries. When the total number of multicast forwarding cache entries is
below the reuse value, the device resumes adding new multicast forwarding cache entries.

1620

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 117: show multicast forwarding-cache statistics Output Fields (continued)

Field Name

Field Description

Warning Threshold

Threshold at which a warning message is logged (percentage of the suppress threshold).

Currently Used Entries

Number of currently used multicast forwarding cache entries.

Sample Output
show multicast forwarding-cache statistics
user@host> show multicast forwarding-cache statistics
Instance: master Family: INET
Suppress Threshold
100
Reuse Value
80
Warning Threshold
90
Currently Used Entries
101
Instance: master Family: INET6
Suppress Threshold
Reuse Value
Warning Threshold
Currently Used Entries

50
50
80
3

show multicast forwarding-cache statistics instance

user@host> show multicast forwarding-cache statistics instance VPN-A
Instance: VPN-A Family: ALL
Suppress Threshold
20
Reuse Value
16
Warning Threshold
50
Currently Used Entries
17

Copyright 2014, Juniper Networks, Inc.

1621

Interfaces Fundamentals for Routing Devices

show multicast interface

List of Syntax

Syntax

Syntax on page 1622

Syntax (EX Series Switch and the QFX Series) on page 1622
show multicast interface
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show multicast interface

Release Information

Command introduced in Junos OS Release 8.3.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Display bandwidth information about IP multicast interfaces.

noneDisplay all interfaces that have multicast configured.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show multicast interface on page 1623

Table 118 on page 1622 describes the output fields for the show multicast interface command.
Output fields are listed in the approximate order in which they appear.

Table 118: show multicast interface Output Fields

Field Name

Field Description

Interface

Name of the multicast interface.

Maximum bandwidth (bps)

Maximum bandwidth setting, in bits per second, for this interface.

Remaining bandwidth (bps)

Amount of bandwidth, in bits per second, remaining on the interface.

Mapped bandwidth
deduction (bps)

Amount of bandwidth, in bits per second, used by any flows that

are mapped to the interface.
NOTE: Adding the mapped bandwidth deduction value to the local
bandwidth deduction value results in the total deduction value for
the interface.
This field does not appear in the output when the no QoS
adjustment feature is disabled.

1622

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 118: show multicast interface Output Fields (continued)

Field Name

Field Description

Local bandwidth deduction

(bps)

Amount of bandwidth, in bits per second, used by any mapped flows

that are traversing the interface.
NOTE: Adding the mapped bandwidth deduction value to the local
bandwidth deduction value results in the total deduction value for
the interface.
This field does not appear in the output when the no QoS
adjustment feature is disabled.

Reverse OIF mapping

State of the reverse OIF mapping feature (on or off).

NOTE: This field does not appear in the output when the no QoS
adjustment feature is disabled.

Reverse OIF mapping no

QoS adjustment

State of the no QoS adjustment feature (on or off) for interfaces

that are using reverse OIF mapping.
NOTE: This field does not appear in the output when the no QoS
adjustment feature is disabled.

Leave timer

Amount of time a mapped interface remains active after the last

mapping ends.
NOTE: This field does not appear in the output when the no QoS
adjustment feature is disabled.

No QoS adjustment

State (on) of the no QoS adjustment feature when this feature is

enabled.
NOTE: This field does not appear in the output when the no QoS
adjustment feature is disabled.

Sample Output
show multicast interface
user@host> show multicast interface
Interface
Maximum bandwidth (bps) Remaining bandwidth (bps)
fe-0/0/3
10000000
0
fe-0/0/3.210
10000000
2000000
fe-0/0/3.220
100000000
100000000
fe-0/0/3.230
20000000
18000000
fe-0/0/2.200
100000000
100000000

Copyright 2014, Juniper Networks, Inc.

1623

Interfaces Fundamentals for Routing Devices

show multicast mrinfo

Syntax

show multicast mrinfo

<host>

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.3 for the QFX Series.

Description

Display configuration information about IP multicast networks, including neighboring

multicast router addresses.

Options

noneDisplay configuration information about all multicast networks.

host(Optional) Display configuration information about a particular host. Replace host

with a hostname or IP address.

Required Privilege
Level

view

List of Sample Output

show multicast mrinfo on page 1625

Output Fields

Table 119 on page 1624 describes the output fields for the show multicast mrinfo command.
Output fields are listed in the approximate order in which they appear.

Table 119: show multicast mrinfo Output Fields

Field Name

Field Description

source-address

Query address, hostname (DNS name or IP address of the source address), and multicast protocol
version or the software version of another vendor.

ip-address-1--->ip-address-2

Queried router interface address and directly attached neighbor interface address, respectively.

(name or ip-address)

Name or IP address of neighbor.

[metric/threshold/type/
flags]

Neighbor's multicast profile:

1624

metricAlways has a value of 1, because mrinfo queries the directly connected interfaces of a device.

thresholdMulticast threshold time-to-live (TTL). The range of values is 0 through 255.

typeMulticast connection type: pim or tunnel.

flagsFlags for this route:

querierQueried router is the designated router for the neighboring session.

leafLink is a leaf in the multicast network.

downLink status indicator.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show multicast mrinfo
user@host> show multicast mrinfo 10.35.4.1
10.35.4.1 (10.35.4.1) [version 12.0]:
192.168.195.166 -> 0.0.0.0 (local) [1/0/pim/querier/leaf]
10.38.20.1 -> 0.0.0.0 (local) [1/0/pim/querier/leaf]
10.47.1.1 -> 10.47.1.2 (10.47.1.2) [1/5/pim]
0.0.0.0 -> 0.0.0.0 (local) [1/0/pim/down]

Copyright 2014, Juniper Networks, Inc.

1625

Interfaces Fundamentals for Routing Devices

show multicast next-hops

List of Syntax

Syntax

Syntax on page 1626

Syntax (EX Series Switch and the QFX Series) on page 1626
show multicast next-hops
<brief | detail>
<identifier-number>
<inet | inet6>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show multicast next-hops

<brief | detail>
<identifier-number>
<inet | inet6>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 option introduced in Junos OS Release 10.0 for EX Series switches.
detail option display of next-hop ID number introduced in Junos OS Release 11.1 for M Series
and T Series routers and EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.

Description
Options

Display the entries in the IP multicast next-hop table.

noneDisplay standard information about all entries in the multicast next-hop table for

all supported address families.

brief | detail(Optional) Display the specified level of output.

When you include the detail option on M Series and T Series routers and EX Series
switches, the downstream interface name includes the next-hop ID number in
parentheses, in the form fe-0/1/2.0-(1048574) where 1048574 is the next-hop ID
number.
identifier-number(Optional) Show a particular next hop by ID number. The range of

values is 1 through 65,535.

inet | inet6(Optional) Display entries for IPv4 or IPv6 family addresses, respectively.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

1626

view

show multicast next-hops on page 1627

show multicast next-hops (Bidirectional PIM on page 1627
show multicast next-hops brief on page 1628
show multicast next-hops detail on page 1628

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Output Fields

Table 120 on page 1627 describes the output fields for the show multicast next-hops
command. Output fields are listed in the approximate order in which they appear.

Table 120: show multicast next-hops Output Fields

Field Name

Field Description

Family

Protocol family (such as INET).

ID

Next-hop identifier of the prefix. The identifier is returned by the routing device's
Packet Forwarding Engine.

Refcount

Number of cache entries that are using this next hop.

KRefcount

Kernel reference count for the next hop.

Downstream
interface

Interface names associated with each multicast next-hop ID.

Incoming interface
list

List of interfaces that accept incoming traffic. Only shown for routes that do
not use strict RPF-based forwarding, for example for bidirectional PIM.

Sample Output
show multicast next-hops
user@host> show multicast next-hops
Family: INET
ID
Refcount KRefcount Downstream interface
262142
4
2 so-1/0/0.0
262143
2
1 mt-1/1/0.49152
262148
2
1 mt-1/1/0.32769

show multicast next-hops (Bidirectional PIM

user@host> show multicast next-hops
Family: INET
ID
Refcount KRefcount Downstream interface
2097151
8
4 ge-0/0/1.0
Family: INET6
ID
Refcount KRefcount Downstream interface
2097157
2
1 ge-0/0/1.0
Family: Incoming interface list
ID
Refcount KRefcount Downstream interface
513
5
2 lo0.0
ge-0/0/1.0
514
5
2 lo0.0
ge-0/0/1.0
xe-4/1/0.0
515
3
1 lo0.0
ge-0/0/1.0
xe-4/1/0.0
544
1
0 lo0.0
xe-4/1/0.0

Copyright 2014, Juniper Networks, Inc.

1627

Interfaces Fundamentals for Routing Devices

show multicast next-hops brief

The output for the show multicast next-hops brief command is identical to that for the
show multicast next-hops command. For sample output, see show multicast next-hops
on page 1627.
show multicast next-hops detail
user@host> show multicast next-hops detail
Family: INET
ID
Refcount KRefcount Downstream interface
1048577
2
1 fe-0/1/2.0-(1048574)
ge-0/2/3.0-(1048576)

1628

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show multicast pim-to-igmp-proxy

List of Syntax

Syntax

Syntax on page 1629

Syntax (EX Series Switch and the QFX Series) on page 1629
show multicast pim-to-igmp-proxy
<instance instance-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show multicast pim-to-igmp-proxy

<instance instance-name>

Release Information

Command introduced in Junos OS Release 9.6.

Command introduced in Junos OS Release 9.6 for EX Series switches.
instance option introduced in Junos OS Release 10.3.
instance option introduced in Junos OS Release 10.3 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Display configuration information about PIM-to-IGMP message translation, also known

as PIM-to-IGMP proxy.

Options

noneDisplay configuration information about PIM-to-IGMP message translation for all

routing instances.
instance instance-name(Optional) Display configuration information about PIM-to-IGMP

message translation for a specific multicast instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Configuring PIM-to-IGMP and PIM-to-MLD Message Translation

show multicast pim-to-igmp-proxy on page 1630

show multicast pim-to-igmp-proxy instance on page 1630
Table 121 on page 1629 describes the output fields for the show multicast pim-to-igmp-proxy
command. Output fields are listed in the order in which they appear.

Table 121: show multicast pim-to-igmp-proxy Output Fields

Field Name

Field Description

Instance

Routing instance. Default instance is master (inet.0 routing table).

Proxy state

State of PIM-to-IGMP message translation, also known as

PIM-to-IGMP proxy, on the configured upstream interfaces: enabled
or disabled.

Copyright 2014, Juniper Networks, Inc.

1629

Interfaces Fundamentals for Routing Devices

Table 121: show multicast pim-to-igmp-proxy Output Fields (continued)

Field Name

Field Description

interface-name

Name of upstream interface (no more than two allowed) on which

PIM-to-IGMP message translation is configured.

Sample Output
show multicast pim-to-igmp-proxy
user@host> show multicast pim-to-igmp-proxy
Instance: master Proxy state: enabled
ge-0/1/0.1
ge-0/1/0.2

show multicast pim-to-igmp-proxy instance

user@host> show multicast pim-to-igmp-proxy instance VPN-A
Instance: VPN-A Proxy state: enabled
ge-0/1/0.1

1630

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show multicast pim-to-mld-proxy

List of Syntax

Syntax

Syntax on page 1631

Syntax (EX Series Switch and the QFX Series) on page 1631
show multicast pim-to-mld-proxy
<instance instance-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show multicast pim-to-mld-proxy

<instance instance-name>

Release Information

Command introduced in Junos OS Release 9.6.

Command introduced in Junos OS Release 9.6 for EX Series switches.
instance option introduced in Junos OS Release 10.3.
instance option introduced in Junos OS Release 10.3 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Options

Display configuration information about PIM-to-MLD message translation, also known

as PIM-to-MLD proxy.
noneDisplay configuration information about PIM-to-MLD message translation for all

routing instances.
instance instance-name(Optional) Display configuration information about PIM-to-MLD

message translation for a specific multicast instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show multicast pim-to-mld-proxy on page 1632

show multicast pim-to-mld-proxy instance on page 1632
Table 122 on page 1631 describes the output fields for the show multicast pim-to-mld-proxy
command. Output fields are listed in the order in which they appear.

Table 122: show multicast pim-to-mld-proxy Output Fields

Field Name

Field Description

Proxy state

State of PIM-to-MLD message translation, also known as

PIM-to-MLD proxy, on the configured upstream interfaces: enabled
or disabled.

interface-name

Name of upstream interface (no more than two allowed) on which

PIM-to-MLD message translation is configured.

Copyright 2014, Juniper Networks, Inc.

1631

Interfaces Fundamentals for Routing Devices

Sample Output
show multicast pim-to-mld-proxy
user@host> show multicast pim-to-mld-proxy
Instance: master Proxy state: enabled
ge-0/5/0.1
ge-0/5/0.2

show multicast pim-to-mld-proxy instance

user@host> show multicast pim-to-mld-proxy instance VPN-A
Instance: VPN-A Proxy state: enabled
ge-0/5/0.1

1632

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show multicast route

List of Syntax

Syntax

Syntax on page 1633

Syntax (EX Series Switch and the QFX Series) on page 1633
show multicast route
<brief | detail | extensive | summary>
<active | all | inactive>
<group group>
<inet | inet6>
<instance instance name>
<logical-system (all | logical-system-name)>
<regular-expression>
<source-prefix source-prefix>

Syntax (EX Series

Switch and the QFX
Series)

show multicast route

<brief | detail | extensive | summary>
<active | all | inactive>
<group group>
<inet | inet6>
<instance instance name>
<regular-expression>
<source-prefix source-prefix>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.

Description

Options

Display the entries in the IP multicast forwarding table. You can display similar information
with the show route table inet.1 command.
noneDisplay standard information about all entries in the multicast forwarding table

for all routing instances.

brief | detail | extensive | summary(Optional) Display the specified level of output.
active | all | inactive(Optional) Display all active entries, all entries, or all inactive entries,

respectively, in the multicast forwarding table.

group group(Optional) Display the cache entries for a particular group.
inet | inet6(Optional) Display multicast forwarding table entries for IPv4 or IPv6 family

addresses, respectively.
instance instance-name(Optional) Display entries in the multicast forwarding table for

a specific multicast instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Copyright 2014, Juniper Networks, Inc.

1633

Interfaces Fundamentals for Routing Devices

regular-expression(Optional) Display information about the multicast forwarding table

entries that match a UNIX OS-style regular expression.

source-prefix source-prefix(Optional) Display the cache entries for a particular source

prefix.
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Example: Configuring Multicast-Only Fast Reroute in a PIM Domain

show multicast route on page 1635

show multicast route (Bidirectional PIM) on page 1636
show multicast route brief on page 1636
show multicast route detail on page 1637
show multicast route extensive (Bidirectional PIM) on page 1637
show multicast route extensive (Multicast-Only Fast Reroute) on page 1638
show multicast route instance <instance-name> on page 1638
show multicast route summary on page 1639
Table 123 on page 1634 describes the output fields for the show multicast route command.
Output fields are listed in the approximate order in which they appear.

Table 123: show multicast route Output Fields

Field Name

Field Description

Level of Output

family

IPv4 address family (INET) or IPv6 address family (INET6).

All levels

Group

Group address.

All levels

For any-source multicast routes, for example for bidirectional PIM, the group
address includes the prefix length.
Source

Prefix and length of the source as it is in the multicast forwarding table.

All levels

Incoming interface
list

List of interfaces that accept incoming traffic. Only shown for routes that do
not use strict RPF-based forwarding, for example for bidirectional PIM.

All levels

Upstream interface

Name of the interface on which the packet with this source prefix is expected
to arrive.

All levels

Upstream rpf
interface list

When multicast-only fast reroute (MoFRR) is enabled, a PIM router propagates

join messages on two upstream RPF interfaces to receive multicast traffic on
both links for the same join request.

All levels

Downstream
interface list

List of interface names to which the packet with this source prefix is forwarded.

All levels

Number of
outgoing interfaces

Total number of outgoing interfaces for each (S,G) entry.

extensive

1634

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 123: show multicast route Output Fields (continued)

Field Name

Field Description

Level of Output

Session description

Name of the multicast session.

detail extensive

Statistics

Rate at which packets are being forwarded for this source and group entry (in
Kbps and pps), and number of packets that have been forwarded to this prefix.
If one or more of the kilobits per second packet forwarding statistic queries fails
or times out, the statistics field displays Forwarding statistics are not available.

detail extensive

NOTE: On QFX Series switches, this field does not report valid statistics.
Next-hop ID

Next-hop identifier of the prefix. The identifier is returned by the routing devices
Packet Forwarding Engine and is also displayed in the output of the show
multicast nexthops command.

detail extensive

Incoming interface
list ID

For bidirectional PIM, incoming interface list identifier.

detail extensive

Identifiers for interfaces that accept incoming traffic. Only shown for routes
that do not use strict RPF-based forwarding, for example for bidirectional PIM.
Upstream protocol

The protocol that maintains the active multicast forwarding route for this group
or source.

detail extensive

When the show multicast route extensive command is used with the
display-origin-protocol option, the field name is only Protocol and not Upstream
Protocol. However, this field also displays the protocol that installed the active
route.
Route type

Type of multicast route. Values can be (S,G) or (*,G).

summary

Route state

Whether the group is Active or Inactive.

summary extensive

Route count

Number of multicast routes.

summary

Forwarding state

Whether the prefix is pruned or forwarding.

extensive

Cache
lifetime/timeout

Number of seconds until the prefix is removed from the multicast forwarding
table. A value of never indicates a permanent forwarding entry. A value of forever
indicates routes that do not have keepalive times.

extensive

Wrong incoming
interface
notifications

Number of times that the upstream interface was not available.

extensive

Uptime

Time since the creation of a multicast route.

extensive

Sample Output
show multicast route
user@host> show multicast route
Family: INET

Copyright 2014, Juniper Networks, Inc.

1635

Interfaces Fundamentals for Routing Devices

Group: 228.0.0.0
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Group: 239.1.1.1
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Group: 239.1.1.1
Source: 10.255.70.15/32
Upstream interface: so-1/0/0.0
Downstream interface list:
mt-1/1/0.1081344
Family: INET6

show multicast route (Bidirectional PIM)

user@host> show multicast route
Family: INET
Group: 224.1.1.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0
Downstream interface list:
ge-0/0/1.0
Group: 224.1.3.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0 xe-4/1/0.0
Downstream interface list:
ge-0/0/1.0
Group: 225.1.1.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0
Downstream interface list:
ge-0/0/1.0
Group: 225.1.3.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0 xe-4/1/0.0
Downstream interface list:
ge-0/0/1.0
Family: INET6

show multicast route brief

The output for the show multicast route brief command is identical to that for the show
multicast route command. For sample output, see show multicast route on page 1635 or
show multicast route (Bidirectional PIM) on page 1636.

1636

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show multicast route detail

user@host> show multicast route detail
Family: INET
Group: 228.0.0.0
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Session description: Unknown
Statistics: 8 kBps, 100 pps, 45272 packets
Next-hop ID: 262142
Upstream protocol: PIM
Group: 239.1.1.1
Source: 10.255.14.144/32
Upstream interface: local
Downstream interface list:
so-1/0/0.0
Session description: Administratively Scoped
Statistics: 0 kBps, 0 pps, 13404 packets
Next-hop ID: 262142
Upstream protocol: PIM
Group: 239.1.1.1
Source: 10.255.70.15/32
Upstream interface: so-1/0/0.0
Downstream interface list:
mt-1/1/0.1081344
Session description: Administratively Scoped
Statistics: 46 kBps, 1000 pps, 921077 packets
Next-hop ID: 262143
Upstream protocol: PIM
Family: INET6

show multicast route extensive (Bidirectional PIM)

user@host> show multicast route extensive
Family: INET
Group: 224.1.1.0/24
Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0
Downstream interface list:
ge-0/0/1.0
Number of outgoing interfaces: 1
Session description: NOB Cross media facilities
Statistics: 0 kBps, 0 pps, 0 packets
Next-hop ID: 2097153
Incoming interface list ID: 585
Upstream protocol: PIM
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 0
Group: 224.1.3.0/24

Copyright 2014, Juniper Networks, Inc.

1637

Interfaces Fundamentals for Routing Devices

Source: *
Incoming interface list:
lo0.0 ge-0/0/1.0 xe-4/1/0.0
Downstream interface list:
ge-0/0/1.0
Number of outgoing interfaces: 1
Session description: NOB Cross media facilities
Statistics: 0 kBps, 0 pps, 0 packets
Next-hop ID: 2097153
Incoming interface list ID: 589
Upstream protocol: PIM
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: forever
Wrong incoming interface notifications: 0
Family: INET6

show multicast route extensive (Multicast-Only Fast Reroute)

user@host> show multicast route extensive
Instance: master Family: INET
Group: 225.1.1.1
Source: 10.0.0.1/32
Upstream rpf interface list:
fe-1/2/13.0 (P) fe-1/2/14.0 (B)
Downstream interface list:
fe-1/2/15.0
Session description: Unknown
Forwarding statistics are not available
RPF Next-hop ID: 836
Next-hop ID: 1048585
Upstream protocol: PIM
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: 171 seconds
Wrong incoming interface notifications: 0
Uptime: 00:03:09

show multicast route instance <instance-name>

user@host> show multicast route instance v1 extensive
Instance: v1 Family: INET
Group: 224.1.1.1
Source: (null)/0
Upstream interface: fe-1/3/0.111
Downstream interface list:
lt-0/3/0.42 lt-0/3/0.46 lt-0/3/0.43
Number of outgoing interfaces: 3
Group: 224.1.1.2
Source: (null)/0
Upstream interface: fe-1/3/0.111
Downstream interface list:
lt-0/3/0.42 lt-0/3/0.46 lt-0/3/0.43
Number of outgoing interfaces: 3
Group: 224.1.1.3

1638

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Source: (null)/0
Upstream interface: fe-1/3/0.111
Downstream interface list:
lt-0/3/0.42 lt-0/3/0.46 lt-0/3/0.43
Number of outgoing interfaces: 3
Instance: v1 Family: INET6

show multicast route summary

user@host>show multicast route summary
Instance: master Family: INET
Route type
(S,G)
(S,G)

Route state
Active
Inactive

Route count
2
3

Instance: master Family: INET6

Copyright 2014, Juniper Networks, Inc.

1639

Interfaces Fundamentals for Routing Devices

show multicast rpf

List of Syntax

Syntax

Syntax on page 1640

Syntax (EX Series Switch and the QFX Series) on page 1640
show multicast rpf
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<prefix>
<summary>

Syntax (EX Series

Switch and the QFX
Series)

show multicast rpf

<inet | inet6>
<instance instance-name>
<prefix>
<summary>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Display information about multicast reverse-path-forwarding (RPF) calculations.

noneDisplay RPF calculation information for all supported address families.
inet | inet6(Optional) Display the RPF calculation information for IPv4 or IPv6 family

addresses, respectively.
instance instance-name(Optional) Display information about multicast RPF calculations

for a specific multicast instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

prefix(Optional) Display the RPF calculation information for the specified prefix.
summary(Optional) Display a summary of all multicast RPF information.

Required Privilege
Level
List of Sample Output

1640

view

show multicast rpf on page 1641

show multicast rpf inet6 on page 1642
show multicast rpf prefix on page 1643
show multicast rpf summary on page 1643

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Output Fields

Table 124 on page 1641 describes the output fields for the show multicast rpf command.
Output fields are listed in the approximate order in which they appear.

Table 124: show multicast rpf Output Fields

Field Name

Field Description

Instance

Name of the routing instance. (Displayed when multicast is

configured within a routing instance.)

Source prefix

Prefix and length of the source as it exists in the multicast forwarding

table.

Protocol

How the route was learned.

Interface

Upstream RPF interface.

NOTE: The displayed interface information does not apply to
bidirectional PIM RP addresses. This is because the show multicast
rpf command does not take into account equal-cost paths or the
designated forwarder. For accurate upstream RPF interface
information, always use the show pim join extensive command when
bidirectional PIM is configured.

Neighbor

Upstream RPF neighbor.

NOTE: The displayed neighbor information does not apply to
bidirectional PIM. This is because the show multicast rpf command
does not take into account equal-cost paths or the designated
forwarder. For accurate upstream RPF neighbor information, always
use the show pim join extensive command when bidirectional PIM
is configured.

Sample Output
show multicast rpf
user@host> show multicast rpf
Multicast RPF table: inet.0, 12 entries
0.0.0.0/0
Protocol: Static
10.255.14.132/32
Protocol: Direct
Interface: lo0.0
10.255.245.91/32
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: 192.168.195.21
127.0.0.1/32
Inactive172.16.0.0/12
Protocol: Static
Interface: fxp0.0

Copyright 2014, Juniper Networks, Inc.

1641

Interfaces Fundamentals for Routing Devices

Neighbor: 192.168.14.254
192.168.0.0/16
Protocol: Static
Interface: fxp0.0
Neighbor: 192.168.14.254
192.168.14.0/24
Protocol: Direct
Interface: fxp0.0
192.168.14.132/32
Protocol: Local
192.168.195.20/30
Protocol: Direct
Interface: so-1/1/1.0
192.168.195.22/32
Protocol: Local
192.168.195.36/30
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: 192.168.195.21

show multicast rpf inet6

user@host> show multicast rpf inet6
Multicast RPF table: inet6.0, 12 entries
::10.255.14.132/128
Protocol: Direct
Interface: lo0.0
::10.255.245.91/128
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: fe80::2a0:a5ff:fe28:2e8c
::192.168.195.20/126
Protocol: Direct
Interface: so-1/1/1.0
::192.168.195.22/128
Protocol: Local
::192.168.195.36/126
Protocol: IS-IS
Interface: so-1/1/1.0
Neighbor: fe80::2a0:a5ff:fe28:2e8c
::192.168.195.76/126
Protocol: Direct
Interface: fe-2/2/0.0
::192.168.195.77/128
Protocol: Local

1642

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

fe80::/64
Protocol: Direct
Interface: so-1/1/1.0
fe80::290:69ff:fe0c:993a/128
Protocol: Local
fe80::2a0:a5ff:fe12:84f/128
Protocol: Direct
Interface: lo0.0
ff02::2/128
Protocol: PIM
ff02::d/128
Protocol: PIM

show multicast rpf prefix

user@host> show multicast rpf ff02::/16
Multicast RPF table: inet6.0, 13 entries
ff02::2/128
Protocol: PIM
ff02::d/128
Protocol: PIM
...

show multicast rpf summary

user@host> show multicast rpf summary
Multicast RPF table: inet.0, 16 entries
Multicast RPF table: inet6.0, 12 entries

Copyright 2014, Juniper Networks, Inc.

1643

Interfaces Fundamentals for Routing Devices

show multicast scope

List of Syntax

Syntax

Syntax on page 1644

Syntax (EX Series Switch and the QFX Series) on page 1644
show multicast scope
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show multicast scope

<inet | inet6>
<instance instance-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Display administratively scoped IP multicast information.

noneDisplay standard information about administratively scoped multicast information

for all supported address families in all routing instances.

inet | inet6(Optional) Display scoped multicast information for IPv4 or IPv6 family

addresses, respectively.
instance instance-name(Optional) Display administratively scoped information for a

specific multicast instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show multicast scope on page 1645

show multicast scope inet on page 1645
show multicast scope inet6 on page 1645
Table 125 on page 1644 describes the output fields for the show multicast scope command.
Output fields are listed in the approximate order in which they appear.

Table 125: show multicast scope Output Fields

1644

Field Name

Field Description

Scope name

Name of the multicast scope.

Group Prefix

Range of multicast groups that are scoped.

Interface

Interface that is the boundary of the administrative scope.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 125: show multicast scope Output Fields (continued)

Field Name

Field Description

Resolve Rejects

Number of kernel resolve rejects.

Sample Output
show multicast scope
user@host> show multicast scope
Scope name
232-net
local
local
larry

Group Prefix
232.232.0.0/16
239.255.0.0/16
ff05::/16
ff05::1234/128

Interface
fe-0/0/0.1
fe-0/0/0.1
fe-0/0/0.1
fe-0/0/0.1

Resolve
Rejects
0
0
0
0

Interface
fe-0/0/0.1
fe-0/0/0.1

Resolve
Rejects
0
0

Interface
fe-0/0/0.1
fe-0/0/0.1

Resolve
Rejects
0
0

show multicast scope inet

user@host> show multicast scope inet
Scope name
232-net
local

Group Prefix
232.232.0.0/16
239.255.0.0/16

show multicast scope inet6

user@host> show multicast scope inet6
Scope name
local
larry

Copyright 2014, Juniper Networks, Inc.

Group Prefix
ff05::/16
ff05::1234/128

1645

Interfaces Fundamentals for Routing Devices

show multicast snooping next-hops

Syntax

Release Information
Description
Options

show multicast snooping next-hops

<brief | detail>
<identifier next-hop-ID>
<inet>
<inet6>
<logical-system logical-system-name>

Command introduced in Junos OS Release 11.2.

Display information about the IP multicast snooping next-hops.
brief | detail(Optional) Display the specified level of output.
inet(Optional) Display information for IPv4 multicast next hops only. If a family is not

specified, both IPv4 and IPv6 results will be shown.

inet6(Optional) Display information for IPv6 multicast next hops only. If a family is not

specified, both IPv4 and IPv6 results will be shown.

logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

Required Privilege
Level
List of Sample Output
Output Fields

view

show multicast snooping next-hops on page 1647

Table 126 on page 1646 describes the output fields for the show multicast snooping next-hops
command. Output fields are listed in the approximate order in which they appear.

Table 126: show multicast snooping next-hops Output Fields

Field Name

Field Description

Family

Protocol family for which multicast snooping next hops are displayed: INET or INET6.

Refcount

Number of cache entries that are using this next hop.

KRefcount

Kernel reference count for the next hop.

Downstream interface

Interface names associated with each multicast next-hop ID.

Nexthop Id

Identifier for the next-hop.

1646

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show multicast snooping next-hops
user@host> show multicast snooping next-hops
Family: INET
ID
Refcount KRefcount Downstream interface Nexthop Id
1048574
4
1 ge-0/1/0.1000
ge-0/1/2.1000
ge-0/1/3.1000
1048574

1 ge-0/1/0.1000-(2000)
1048575
1048576

1048575

0 ge-0/1/2.1000-(2001)
ge-0/1/3.1000-(2002)

1048576

0 lsi.1048578-(2003)
lsi.1048579-(2004)

Copyright 2014, Juniper Networks, Inc.

1647

Interfaces Fundamentals for Routing Devices

show multicast sessions

List of Syntax

Syntax

Syntax on page 1648

Syntax (EX Series Switch and the QFX Series) on page 1648
show multicast sessions
<brief | detail | extensive>
<logical-system (all | logical-system-name)>
<regular-expression>

Syntax (EX Series

Switch and the QFX
Series)

show multicast sessions

<brief | detail | extensive>
<regular-expression>

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.3 for the QFX Series.

Description
Options

Display information about announced IP multicast sessions.

noneDisplay standard information about all multicast sessions for all routing instances.
brief | detail | extensive(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

regular-expression(Optional) Display information about announced sessions that match

a UNIX-style regular expression.

Required Privilege
Level
List of Sample Output

Output Fields

view

show multicast sessions on page 1649

show multicast sessions regular-expression detail on page 1649
Table 127 on page 1648 describes the output fields for the show multicast sessions command.
Output fields are listed in the approximate order in which they appear.

Table 127: show multicast sessions Output Fields

1648

Field Name

Field Description

session-name

Name of the known announced multicast sessions.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show multicast sessions
user@host> show multicast sessions
1-Department of Biological Sciences, LSU
...
Monterey Bay - DockCam
Monterey Bay - JettyCam
Monterey Bay - StandCam
Monterey DockCam
Monterey DockCam / ROV cam
...
NASA TV (MPEG-1)
...
UO Broadcast - NASA Videos - 25 Years of Progress
UO Broadcast - NASA Videos - Journey through the Solar System
UO Broadcast - NASA Videos - Life in the Universe
UO Broadcast - NASA Videos - Nasa and the Airplane
UO Broadcasts OPB's Oregon Story
UO DOD News Clips
UO Medical Management of Biological Casualties (1)
UO Medical Management of Biological Casualties (2)
UO Medical Management of Biological Casualties (3)
...
376 active sessions.

show multicast sessions regular-expression detail

user@host> show multicast sessions "NASA TV" detail
SDP Version: 0 Originated by: [email protected]
Session: NASA TV (MPEG-1)
Description: NASA television in MPEG-1 format, provided by Private University.
Please contact the UO if you have problems with this feed.
Email: Your Name Here <[email protected]>
Phone: Your Name Here <888/555-1212>
Bandwidth: AS:1000
Start time: permanent
Stop time: none
Attribute: type:broadcast
Attribute: tool:IP/TV Content Manager 3.4.14
Attribute: live:capture:1
Attribute: x-iptv-capture:mp1s
Media: video 54302 RTP/AVP 32 31 96 97
Connection Data: 224.2.231.45 ttl 127
Attribute: quality:8
Attribute: framerate:30
Attribute: rtpmap:96 WBIH/90000
Attribute: rtpmap:97 MP4V-ES/90000
Attribute: x-iptv-svr:video 128.223.91.191 live
Attribute: fmtp:32 type=mpeg1
Media: audio 28848 RTP/AVP 14 0 96 3 5 97 98 99 100 101 102 10 11 103 104 105 106
Connection Data: 224.2.145.37 ttl 127
Attribute: rtpmap:96 X-WAVE/8000
Attribute: rtpmap:97 L8/8000/2
Attribute: rtpmap:98 L8/8000
Attribute: rtpmap:99 L8/22050/2
Attribute: rtpmap:100 L8/22050
Attribute: rtpmap:101 L8/11025/2
Attribute: rtpmap:102 L8/11025
Attribute: rtpmap:103 L16/22050/2

Copyright 2014, Juniper Networks, Inc.

1649

Interfaces Fundamentals for Routing Devices

Attribute: rtpmap:104 L16/22050

1 matching sessions.

1650

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show multicast snooping route

Syntax

Release Information

Description

Options

show multicast snooping route

<regexp>
<active>
<all>
<bridge-domain bridge-domain-name>
<brief >
<control>
<data>
<detail >
<extensive>
<group group>
<inactive>
<inet>
<inet6>
<instance instance-name>
<logical-system logical-system-name>
<mesh-group mesh-group-name>
<qualified-vlan vlan-id>
<source-prefix source-prefix>
<vlan vlan-id>

Command introduced in Junos OS Release 8.5.

Support for control, data, qualified-vlan and vlan options introduced in Junos OS Release
13.3 for EX Series switches.
Display the entries in the IP multicast snooping forwarding table. You can display some
of this information with the show route table inet.1 command.
noneDisplay standard information about all entries in the multicast snooping table for

all virtual switches and all bridge domains.

active | all | inactive (Optional) Display all active entries, all entries, or all inactive entries,

respectively, in the multicast snooping table.

bridge-domain bridge-domain(Optional) Display the entries for a particular bridge

domain.
brief | detail | extensive(Optional) Display the specified level of output.
control(Optional) Display control route entries.
data(Optional) Display data route entries.
group group(Optional) Display the entries for a particular group.
inet(Optional) Display IPv4 information.
inet6(Optional) Display IPv6 information.
instance instance-name(Optional) Display the entries for a multicast instance.

Copyright 2014, Juniper Networks, Inc.

1651

Interfaces Fundamentals for Routing Devices

logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

mesh-group mesh-group-name(Optional) Display the entries for a particular mesh group.
qualified-vlan vlan-id(Optional) Display the entries for a particular qualified VLAN.
regexp(Optional) Display information about the multicast forwarding table entries that

match a UNIX-style regular expression.

source-prefix source-prefix(Optional) Display the entries for a particular source prefix.
vlan vlan-id(Optional) Display the entries for a particular VLAN.

Required Privilege
Level
List of Sample Output

Output Fields

view

show multicast snooping route bridge-domain on page 1653

show multicast snooping route instance vs on page 1653
show multicast snooping route extensive on page 1653
Table 128 on page 1652 describes the output fields for the show multicast snooping route
command. Output fields are listed in the approximate order in which they appear.

Table 128: show multicast snooping route Output Fields

Field Name

Field Description

Level of Output

Nexthop Bulking

Displays whether next-hop bulk updating is ON or OFF (only for routing-instance

type of virtual switch or vpls).

All levels

Family

IPv4 address family (INET) or IPv6 address family (INET6).

All levels

Group

Group address.

All levels

Source

Prefix and length of the source as it is in the multicast forwarding table. For
(*,G) entries, this field is set to "*".

All levels

Routing-instance

Name of the routing instance to which this routing information applies.

(Displayed when multicast is configured within a routing instance.)

All levels

Learning Domain

Name of the learning domain to which this routing information applies.

detail extensive

Statistics

Rate at which packets are being forwarded for this source and group entry (in
Kbps and pps), and number of packets that have been forwarded to this prefix.

detail extensive

Next-hop ID

Next-hop identifier of the prefix. The identifier is returned by the router's Packet
Forwarding Engine and is also displayed in the output of the show multicast
nexthops command.

detail extensive

Route state

Whether the group is Active or Inactive.

extensive

Forwarding state

Whether the prefix is Pruned or Forwarding.

extensive

1652

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 128: show multicast snooping route Output Fields (continued)

Field Name

Field Description

Level of Output

Cache
lifetime/timeout

Number of seconds until the prefix is removed from the multicast forwarding
table. A value of never indicates a permanent forwarding entry.

extensive

Sample Output
show multicast snooping route bridge-domain
user@host> show multicast snooping route bridge-domain br-dom-1 extensive
Family: INET
Group: 232.1.1.1
Source: 192.168.3.100/32
Downstream interface list:
ge-0/1/0.200
Statistics: 0 kBps, 0 pps, 1 packets
Next-hop ID: 1048577
Route state: Active
Forwarding state: Forwarding
Cache lifetime/timeout: 240 seconds

show multicast snooping route instance vs

user@host> show multicast snooping route instance vs
Nexthop Bulking: ON
Family: INET
Group: 224.0.0.0
Bridge-domain: vsid500
Group: 225.1.0.1
Bridge-domain: vsid500
Downstream interface list: vsid500
ge-0/3/8.500 ge-1/1/9.500 ge1/2/5.500

show multicast snooping route extensive

user@host> show multicast snooping route extensive inet6 group ff03::1
Nexthop Bulking: OFF
Family: INET6
Group: ff03::1/128
Source: ::
Bridge-domain: BD-1
Mesh-group: __all_ces__
Downstream interface list:
ae0.1 -(562) 1048576
Statistics: 2697 kBps, 3875 pps, 758819039 packets
Next-hop ID: 1048605
Route state: Active
Forwarding state: Forwarding
Group: ff03::1/128
Source: 6666::2/128
Bridge-domain: BD-1
Mesh-group: __all_ces__

Copyright 2014, Juniper Networks, Inc.

1653

Interfaces Fundamentals for Routing Devices

Downstream interface list:

ae0.1 -(562) 1048576
Statistics: 0 kBps, 0 pps, 0 packets
Next-hop ID: 1048605
Route state: Active
Forwarding state: Forwarding

1654

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show multicast statistics

Syntax

Release Information
Description
Options

show multicast statistics

<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display IP multicast statistics.
noneDisplay multicast statistics for all supported address families for all routing

instances.
inet | inet6(Optional) Display multicast statistics for IPv4 or IPv6 family addresses,

respectively.
instance instance-name(Optional) Display statistics for a specific routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Additional Information

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

The input and output interface multicast statistics are consistent, but not timely. They
are constructed from the forwarding statistics, which are gathered at 30-second intervals.
Therefore, the output from this command always lags the true count by up to 30 seconds.
view

clear multicast statistics on page 1535

show multicast statistics on page 1657

Table 129 on page 1655 describes the output fields for the show multicast statistics
command. Output fields are listed in the approximate order in which they appear.

Table 129: show multicast statistics Output Fields

Field Name

Field Description

Family

Protocol family for which multicast statistics are displayed: INET or INET6.

Interface

Name of the interface for which statistics are being reported.

Routing Protocol

Primary multicast protocol on the interface: PIM, DVMRP for INET, or PIM for INET6.

Mismatch

Number of multicast packets that did not arrive on the correct upstream interface.

Kernel Resolve

Number of resolve requests processed by the primary multicast protocol on the interface.

Copyright 2014, Juniper Networks, Inc.

1655

Interfaces Fundamentals for Routing Devices

Table 129: show multicast statistics Output Fields (continued)

Field Name

Field Description

Resolve No Route

Number of resolve requests that were ignored because there was no route to the source.

In Kbytes

Total accumulated incoming packets (in KB) since the last time the clear multicast statistics command
was issued.

Out Kbytes

Total accumulated outgoing packets (in KB) since the last time the clear multicast statistics command
was issued.

Mismatch error

Number of mismatches that were ignored because of internal errors.

Mismatch No Route

Number of mismatches that were ignored because there was no route to the source.

Routing Notify

Number of times that the multicast routing system has been notified of a new multicast source by a
multicast routing protocol .

Resolve Error

Number of resolve requests that were ignored because of internal errors.

In Packets

Total number of incoming packets since the last time the clear multicast statistics command was
issued.

Out Packets

Total number of outgoing packets since the last time the clear multicast statistics command was
issued.

Resolve requests on
interfaces not enabled
for multicast n

Number of resolve requests on interfaces that are not enabled for multicast that have accumulated
since the clear multicast statistics command was last issued.

Resolve requests with

no route to source n

Number of resolve requests with no route to the source that have accumulated since the clear multicast
statistics command was last issued.

Routing notifications on
interfaces not enabled
for multicast n

Number of routing notifications on interfaces not enabled for multicast that have accumulated since
the clear multicast statistics command was last issued.

Routing notifications
with no route to source
n

Number of routing notifications with no route to the source that have accumulated since the clear
multicast statistics command was last issued.

Interface Mismatches
on interfaces not
enabled for multicast n

Number of interface mismatches on interfaces not enabled for multicast that have accumulated
since the clear multicast statistics command was last issued.

Group Membership on
interfaces not enabled
for multicast n

Number of group memberships on interfaces not enabled for multicast that have accumulated since
the clear multicast statistics command was last issued.

1656

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show multicast statistics
user@host> show multicast statistics
Address family: INET
Interface: fe-0/0/0
Routing Protocol:
Mismatch:
Kernel Resolve:
Resolve No Route:
In Kbytes:
Out Kbytes:
Interface: so-0/1/1.0
Routing Protocol:
Mismatch:
Kernel Resolve:
Resolve No Route:
In Kbytes:
Out Kbytes:

PIM
0
10
0
4641
0

Mismatch error:
Mismatch No Route:
Routing Notify:
Resolve Error:
In Packets:
Out Packets:

0
0
0
0
50454
0

PIM
0
0
0
0
4641

Mismatch error:
Mismatch No Route:
Routing Notify:
Resolve Error:
In Packets:
Out Packets:

0
0
0
0
0
50454

Resolve requests on interfaces not enabled for multicast 0

Resolve requests with no route to source 0
Routing notifications on interfaces not enabled for multicast 0
Routing notifications with no route to source 0
Interface Mismatches on interfaces not enabled for multicast 0
Group Membership on interfaces not enabled for multicast 25
Address family: INET6
Interface: fe-0/0/0.0
Routing Protocol:
Mismatch:
Kernel Resolve:
Resolve No Route:
In Kbytes:
Out Kbytes:
Interface: so-0/1/1.0
Routing Protocol:
Mismatch:
Kernel Resolve:
Resolve No Route:
In Kbytes:
Out Kbytes:

PIM
0
0
0
0
0

Mismatch error:
Mismatch No Route:
Routing Notify:
Resolve Error:
In Packets:
Out Packets:

0
0
0
0
0
0

PIM
0
0
0
0
0

Mismatch error:
Mismatch No Route:
Routing Notify:
Resolve Error:
In Packets:
Out Packets:

0
0
0
0
0
0

Resolve requests on interfaces not enabled for multicast 0

Resolve requests with no route to source 0
Routing notifications on interfaces not enabled for multicast 0
Routing notifications with no route to source 0
Interface Mismatches on interfaces not enabled for multicast 0
Group Membership on interfaces not enabled for multicast 0

Copyright 2014, Juniper Networks, Inc.

1657

Interfaces Fundamentals for Routing Devices

show multicast usage

List of Syntax

Syntax

Syntax on page 1658

Syntax (EX Series Switch and the QFX Series) on page 1658
show multicast usage
<brief | detail>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show multicast usage

<brief | detail>
<inet | inet6>
<instance instance-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Display usage information about the 10 most active Distance Vector Multicast Routing
Protocol (DVMRP) or Protocol Independent Multicast (PIM) groups.

Options

noneDisplay multicast usage information for all supported address families for all

routing instances.
brief | detail(Optional) Display the specified level of output.
inet | inet6(Optional) Display usage information for IPv4 or IPv6 family addresses,

respectively.
instance instance-name(Optional) Display information about the most active DVMRP

or PIM groups for a specific multicast instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

1658

view

show multicast usage on page 1659

show multicast usage brief on page 1659
show multicast usage instance on page 1659
show multicast usage detail on page 1660
Table 130 on page 1659 describes the output fields for the show multicast usage command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 130: show multicast usage Output Fields

Field Name

Field Description

Instance

Name of the routing instance. (Displayed when multicast is configured within

a routing instance.)

Group

Group address.

Sources

Number of sources.

Packets

Number of packets that have been forwarded to this prefix. If one or more of
the packets forwarded statistic queries fails or times out, the packets field
displays unavailable.

Bytes

Number of bytes that have been forwarded to this prefix. If one or more of the
packets forwarded statistic queries fails or times out, the bytes field displays
unavailable.

Prefix

IP address.

/len

Prefix length.

Groups

Number of multicast groups.

Sample Output
show multicast usage
user@host> show multicast usage
Group
Sources Packets
228.0.0.0
1
52847
239.1.1.1
2
13450

Prefix
10.255.14.144
10.255.70.15

/len Groups Packets

/32 2
66254
/32 1
43

Bytes
4439148
1125530

Bytes
5561304
3374...

show multicast usage brief

The output for the show multicast usage brief command is identical to that for the show
multicast usage command. For sample output, see show multicast usage on page 1659.
show multicast usage instance
user@host> show multicast usage instance VPN-A
Group
Sources Packets
224.2.127.254
1
5538
224.0.1.39
1
13
224.0.1.40
1
13
Prefix
192.168.195.34
10.255.14.30

Copyright 2014, Juniper Networks, Inc.

/len Groups Packets

/32 1
5538
/32 1
13

Bytes
509496
624
624
Bytes
509496
624

1659

Interfaces Fundamentals for Routing Devices

10.255.245.91
...

/32

13

624

show multicast usage detail

user@host> show multicast usage detail
Group
Sources Packets
Bytes
228.0.0.0
1
53159
4465356
Source: 10.255.14.144
/32 Packets: 53159 Bytes: 4465356
239.1.1.1
2
13450
1125530
Source: 10.255.14.144
/32 Packets: 13407 Bytes: 1122156
Source: 10.255.70.15
/32 Packets: 43 Bytes: 3374

Prefix
/len Groups Packets
Bytes
10.255.14.144
/32 2
66566
5587512
Group: 228.0.0.0
Packets: 53159 Bytes: 4465356
Group: 239.1.1.1
Packets: 13407 Bytes: 1122156
10.255.70.15
/32 1
43
3374
Group: 239.1.1.1
Packets: 43 Bytes: 3374

1660

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pgm negative-acknowledgments

Syntax

show pgm negative-acknowledgments

Release Information

NOTE: Support for the Pragmatic General Multicast protocol (PGM) is being
removed from Junos. In Junos OS release 14.2 PGM functionality is still
available, but the commands are hidden, that is, they no longer appear in the
CLI.

Command introduced before Junos OS Release 7.4.

Description

Options
Required Privilege
Level
List of Sample Output
Output Fields

Display the sent or received Pragmatic General Multicast (PGM) negative

acknowledgments (NAKs), the source-path message (SPM) sequence number being
negatively acknowledged, and the current state of repair.
This command has no options.
view

show pgm negative-acknowledgments on page 1663

Table 131 on page 1661 describes the output fields for the show pgm
negative-acknowledgments command. Output fields are listed in the approximate order
in which they appear.

Table 131: show pgm negative-acknowledgments Output Fields

Field Name

Field Description

Global source id

Global source identifier (GSI), which combines with the source port to determine the transport session
identifier (TSI).

Network layer address

Network layer address of the local system.

Source port

Source port number, which is combined with the GSI to determine the TSI.

SPM sequence number

Numeric sequence identifier of the source-path message.

Window
(trailing/leading
sequence)

Range of sequence numbers used by the source for sequentially numbering and transmitting the most
recent packets. The trailing (or left) edge of the transmit window is the sequence number of the oldest
data packet available for repair from a source. The leading (or right) edge of the transmit window is
defined as the sequence number of the most recent data packet a source has transmitted.

Copyright 2014, Juniper Networks, Inc.

1661

Interfaces Fundamentals for Routing Devices

Table 131: show pgm negative-acknowledgments Output Fields (continued)

Field Name

Field Description

Outstanding NAKS

Total number of outstanding negative acknowledgments sent or received by the local system. NAK
packets indicate that a packet in the expected original data sequence has been detected as missing.

1662

Sequence numberNumeric sequence identifier of the source-path message.

GroupGroup address.

SourceMulticast source.

InterfaceInterface name.

ReceiverIP address receiving the multicast.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show pgm negativeacknowledgments
user@host> show pgm negative-acknowledgments
Global source ID: 010203040506 Source port: 1111
Network layer address: 10.38.0.1
SPM sequence number: 1
Window (trailing/leading sequence): 0/1
Outstanding NAKs:
Sequence number: 1
Group: 225.1.1.1
Source: 192.168.195.121
Interface: t3-0/2/0:0 Receiver: 10.38.0.10

Copyright 2014, Juniper Networks, Inc.

1663

Interfaces Fundamentals for Routing Devices

show pgm source-path-messages

Syntax

show pgm source-path-messages

Release Information

NOTE: Support for the Pragmatic General Multicast protocol (PGM) is being
removed from Junos. In Junos OS release 14.2 PGM functionality is still
available, but the commands are hidden, that is, they no longer appear in the
CLI.

Command introduced before Junos OS Release 7.4.

Description
Options
Required Privilege
Level
List of Sample Output
Output Fields

Display the Pragmatic General Multicast (PGM) source-path messages received.

This command has no options.
view

show pgm source-path-messages on page 1664

Table 132 on page 1664 describes the output fields for the show pgm source-path-messages
command. Output fields are listed in the approximate order in which they appear.

Table 132: show pgm source-path-messages Output Fields

Field Name

Field Description

Global source ID

Global source identifier (GSI), which combines with the source port to
determine the transport session identifier (TSI).

Port

Source port number, which combines with the GSI to determine the TSI.

SPM number

Numeric sequence identifier of the source-path message.

Trail number

Sequence number of the oldest data packet available for repair from
a source.

Lead number

Sequence number of the most recent data packet a source

has transmitted.

Network layer address

Network layer address of the local system.

Sample Output
show pgm source-path-messages
user@host> show pgm source-path-messages
Global source ID Port SPM number Trail number Lead number Network layer address
010203040506
1111
1
0
1 10.38.0.1

1664

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Copyright 2014, Juniper Networks, Inc.

1665

Interfaces Fundamentals for Routing Devices

show pgm statistics

Syntax

show pgm statistics

Release Information

NOTE: Support for the Pragmatic General Multicast protocol (PGM) is being
removed from Junos. In Junos OS release 14.2 PGM functionality is still
available, but the commands are hidden, that is, they no longer appear in the
CLI.

Command introduced before Junos OS Release 7.4.

Description

Options
Required Privilege
Level
List of Sample Output
Output Fields

1666

Display Pragmatic General Multicast (PGM) packet statistics, including general loss and
repair statistics.
This command has no options.
view

show pgm statistics on page 1669

Table 133 on page 1667 describes the output fields for the show pgm statistics command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 133: show pgm statistics Output Fields

Field Name

Field Description

PGM type, # received,

# sent

Number of packets received and sent for the following PGM packet types:

SPMNumber of total source path messages received and sent by the local system. Source path

messages (SPMs) are sent by a source to establish the source path state in network elements and
to provide the transmit-window state to receivers.

POLLTotal number of poll requests received and sent by the local system.

POLRTotal number of poll responses received and sent by the local system.

ODATATotal number of original data packets received and sent by the local system.

RDATATotal number of repair data packets received and sent by the local system. RDATA packets

are generated in response to negative acknowledgments (NAKs), which indicate a missing packet
from the original data sequence.

NAKTotal number of negative acknowledgments received and sent by the local system. NAK

packets indicate that a packet in the expected original data sequence has been detected as missing.

NULLNAKTotal number of null negative acknowledgments received and sent by the local system.

NULLNAKs are transmitted by a designated local repairer that receives NAKs redirected to it by
either receivers or network elements to provide flow-control feedback to a source.

NCFTotal number of NAK confirmations received and sent by the local system. NAK confirmations

are generated in response to NAK packets that are received.

SPMRTotal number of source path message requests (SPMRs) received and sent by the local

system. SPMRs are used to solicit a source path message from a source in a nonimplosive way.
The typical application is for late-joining receivers to solicit source path messages directly from a
source in order to be able to send NAKs for missing packets, without having to wait for a regularly
scheduled source path message from that source.

OTHERTotal number of other PGM packets received and sent by the local system.

packets shorter than

minimum PGM header
length

Total number of packets received with headers that are shorter than the minimum required PGM
header length.

packets received with

incorrect check sum

Total number of packets received with an incorrect checksum. The checksum field is the 1's
complement of the 1's complement sum of the entire PGM packet, including the header.

packets received with

zero check sum

Total number of packets received with a zero checksum. If the computed checksum is zero, it is
transmitted as all ones. A value of zero in this field means that the transmitter generated no checksum.

packets received with

TSDU length incorrect

Total number of packets received with an incorrect Transport Service Data Unit (TSDU) length (16
bits).

packets received with

SPM length incorrect

Total number of packets received with an incorrect source path message length.

packets received with

unknown SPM address
family

Total number of packets received with an unknown source path message address family indicator
(AFI).

packets received with

NAK length incorrect

Total number of packets received with an incorrect NAK length.

Copyright 2014, Juniper Networks, Inc.

1667

Interfaces Fundamentals for Routing Devices

Table 133: show pgm statistics Output Fields (continued)

Field Name

Field Description

packets received with

unknown NAK address
family

Total number of packets received with an unknown NAK address family indicator (AFI).

packets received with

NAK for unknown TSI

Total number of NAK packets received with an unknown transport session identifier (TSI).

packets received when

NAK throttled

Total number of packets received when NAK is throttled.

packets received with

NCF length incorrect

Total number of packets received with an incorrect NAK confirmation length.

packets received with

unknown NCF address
family

Total number of packets received with an unknown NAK confirmation address family indicator (AFI).

packets received with

NCF for unknown TSI

Total number of NAK confirmation packets received with an unknown transport session identifier
(TSI).

packets received with

RDATA length incorrect

Total number of packets received with an incorrect RDATA length.

packets received with

RDATA for unknown TSI

Total number of RDATA packets received with an unknown transport session identifier (TSI).

1668

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show pgm statistics
user@host> show pgm statistics
PGM type
# received
# sent
SPM
0
0
POLL
0
0
POLR
0
0
ODATA
0
0
RDATA
0
0
NAK
0
0
NULLNAK
0
0
NCF
0
0
SPMR
0
0
OTHER
0
0
packets
packets
packets
packets
packets
packets
packets
packets
packets
packets
packets
packets
packets
packets
packets

Copyright 2014, Juniper Networks, Inc.

shorter than minimum PGM header length :

received with incorrect check sum
:
received with zero check sum
:
received with TSDU length incorrect
:
received with SPM length incorrect
:
received with unknown SPM address family:
received with NAK length incorrect
:
received with unknown NAK address family:
received with NAK for unknown TSI
:
received when NAK throttled
:
received with NCF length incorrect
:
received with unknown NCF address family:
received with NCF for unknown TSI
:
received with RDATA length incorrect
:
received with RDATA for unknown TSI
:

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

1669

Interfaces Fundamentals for Routing Devices

show pim bootstrap

List of Syntax

Syntax

Syntax on page 1670

Syntax (EX Series Switch and the QFX Series) on page 1670
show pim bootstrap
<instance instance-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show pim bootstrap

<instance instance-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
instance option introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Options

For sparse mode only, display information about Protocol Independent Multicast (PIM)
bootstrap routers.
noneDisplay PIM bootstrap router information for all routing instances.
instance instance-name(Optional) Display information about bootstrap routers for a

specific PIM-enabled routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show pim bootstrap on page 1671

show pim bootstrap instance on page 1671
Table 134 on page 1670 describes the output fields for the show pim bootstrap command.
Output fields are listed in the approximate order in which they appear.

Table 134: show pim bootstrap Output Fields

1670

Field Name

Field Description

Instance

Name of the routing instance.

BSR

Bootstrap router.

Pri

Priority of the routing device as elected to be the bootstrap router.

Local address

Local routing device address.

Pri

Local routing device address priority to be elected as the bootstrap

router.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 134: show pim bootstrap Output Fields (continued)

Field Name

Field Description

State

Local routing device election state: Candidate, Elected, or Ineligible.

Timeout

How long until the local routing device declares the bootstrap router
to be unreachable, in seconds.

Sample Output
show pim bootstrap
user@host> show pim bootstrap
Instance: PIM.master
BSR
Pri Local address
Pri State
Timeout
None
0 10.255.71.46
0 InEligible
0
feco:1:1:1:1:0:aff:785c 34 feco:1:1:1:1:0:aff:7c12
0 InEligible
0

show pim bootstrap instance

user@host> show pim bootstrap instance VPN-A
Instance: PIM.VPN-A
BSR
None

Copyright 2014, Juniper Networks, Inc.

Pri Local address

Pri State
Timeout
0 192.168.196.105
0 InEligible
0

1671

Interfaces Fundamentals for Routing Devices

show pim interfaces

List of Syntax

Syntax

Syntax on page 1672

Syntax (EX Series Switch and the QFX Series) on page 1672
show pim interfaces
<inet | inet6>
<instance (instance-name | all)>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show pim interfaces

<inet | inet6>
<instance (instance-name | all)>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Commmand introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Support for the instance all option added in Junos OS Release 12.1.

Description

Options

Display information about the interfaces on which Protocol Independent Multicast (PIM)
is configured.
noneDisplay interface information for all family addresses for the main instance.
inet | inet6(Optional) Display interface information for IPv4 or IPv6 family addresses,

respectively.
instance (instance-name | all)(Optional) Display information about interfaces for a

specific PIM-enabled routing instance or for all routing instances.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show pim interfaces on page 1673

Table 135 on page 1672 describes the output fields for the show pim interfaces command.
Output fields are listed in the approximate order in which they appear.

Table 135: show pim interfaces Output Fields

Field Name

Field Description

Instance

Name of the routing instance.

Name

Interface name.

State

State of the interface. The state also is displayed in the show interfaces command.

1672

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 135: show pim interfaces Output Fields (continued)

Field Name

Field Description

Mode

PIM mode running on the interface:

BIn bidirectional mode, multicast groups are carried across the network over bidirectional shared

trees. This type of tree minimizes PIM routing state, which is especially important in networks with
numerous and dispersed senders and receivers.

SIn sparse mode, routing devices must join and leave multicast groups explicitly. Upstream routing

devices do not forward multicast traffic to this routing device unless this device has sent an explicit
request (using a join message) to receive multicast traffic.

DenseUnlike sparse mode, where data is forwarded only to routing devices sending an explicit

request, dense mode implements a flood-and-prune mechanism, similar to DVMRP (the first
multicast protocol used to support the multicast backbone). (Not supported on QFX Series.)

Sparse-DenseSparse-dense mode allows the interface to operate on a per-group basis in either

sparse or dense mode. A group specified as dense is not mapped to a rendezvous point (RP).

Instead, data packets destined for that group are forwarded using PIM-Dense Mode (PIM-DM)
rules. A group specified as sparse is mapped to an RP, and data packets are forwarded using
PIM-Sparse Mode (PIM-SM) rules. (Not supported on QFX Series.)
When sparse-dense mode is configured, the output includes both S and D. When bidirectional-sparse
mode is configured, the output includes S and B. When bidirectional-sparse-dense mode is
configured, the output includes B, S, and D.
IP

Version number of the address family on the interface: 4 (IPv4) or 6 (IPv6).

PIM version running on the interface: 1 or 2.

State

State of PIM on the interface:

ActiveBidirectional mode is enabled on the interface and on all PIM neighbors.

DRDesignated router.

NotCapBidirectional mode is not enabled on the interface. This can happen when bidirectional

PIM is not configured locally, when one of the neighbors is not configured for bidirectional PIM, or
when one of the neighbors has not implemented the bidirectional PIM protocol.

NotDRNot the designated router.

P2PPoint to point.

NbrCnt

Number of neighbors that have been seen on the interface.

JoinCnt(sg)

Number of (s,g) join messages that have been seen on the interface.

JointCnt(*g)

Number of (*,g) join messages that have been seen on the interface.

DR address

Address of the designated router.

Sample Output
show pim interfaces
user@host> show pim interfaces
Stat = Status, V = Version, NbrCnt = Neighbor Count,
S = Sparse, D = Dense, B = Bidirectional,
DR = Designated Router, P2P = Point-to-point link,

Copyright 2014, Juniper Networks, Inc.

1673

Interfaces Fundamentals for Routing Devices

Active = Bidirectional is active, NotCap = Not Bidirectional Capable

Name
ge-0/3/0.0
ge-0/3/3.50
ge-0/3/3.51
pe-1/2/0.32769

1674

Stat
Up
Up
Up
Up

Mode IP V State
NbrCnt JoinCnt(sg/*g)
S
4 2 NotDR,NotCap
1 0/0
S
4 2 DR,NotCap
1 9901/100
S
4 2 DR,NotCap
1 0/0
S
4 2 P2P,NotCap
0 0/0

DR address
40.0.0.3
50.0.0.2
51.0.0.2

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim join

List of Syntax

Syntax on page 1675

Syntax (EX Series Switch and the QFX Series) on page 1675

Syntax

show pim join

<brief | detail | extensive | summary>
<bidirectional | dense | sparse>
<exact>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<range>
<rp ip-address/prefix | source ip-address/prefix>
<sg | star-g>

Syntax (EX Series

Switch and the QFX
Series)

show pim join

<brief | detail | extensive | summary>
<dense | sparse>
<exact>
<inet | inet6>
<instance instance-name>
<range>
<rp ip-address/prefix | source ip-address/prefix>
<sg | star-g>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
summary option introduced in Junos OS Release 9.6.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Support for bidirectional PIM added in Junos OS Release 12.1.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Multiple new filter options introduced in Junos OS Release 13.2.

Description

Display information about Protocol Independent Multicast (PIM) groups for all PIM
modes.
For bidirectional PIM, display information about PIM group ranges (*,G-range) for each
active bidirectional RP group range, in addition to each of the joined (*,G) routes.

Options

noneDisplay the standard information about PIM groups for all supported family

addresses for all routing instances.

brief | detail | extensive | summary(Optional) Display the specified level of output.
bidirectional | dense | sparse(Optional) Display information about PIM bidirectional

mode, dense mode, or sparse and source-specific multicast (SSM) mode entries.
exact(Optional) Display information about only the group that exactly matches the

specified group address.

Copyright 2014, Juniper Networks, Inc.

1675

Interfaces Fundamentals for Routing Devices

inet | inet6(Optional) Display PIM group information for IPv4 or IPv6 family addresses,

respectively.
instance instance-name(Optional) Display information about groups for the specified

PIM-enabled routing instance only.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

range(Optional) Address range of the group, specified as prefix/prefix-length.
rp ip-address/prefix | source ip-address/prefix(Optional) Display information about the

PIM entries with a specified rendezvous point (RP) address and prefix or with a
specified source address and prefix. You can omit the prefix.
sg | star-g(Optional) Display information about PIM (S,G) or (*,G) entries.

Required Privilege
Level
Related
Documentation

List of Sample Output

1676

view

clear pim join on page 1539

Example: Configuring Multicast-Only Fast Reroute in a PIM Domain

Example: Configuring Bidirectional PIM

Example: Configuring PIM State Limits

show pim join summary on page 1680

show pim join (PIM Sparse Mode) on page 1680
show pim join (Bidirectional PIM) on page 1681
show pim join inet6 on page 1681
show pim join inet6 star-g on page 1682
show pim join instance <instance-name> on page 1682
show pim join detail on page 1682
show pim join extensive (PIM Sparse Mode) on page 1683
show pim join extensive (Bidirectional PIM) on page 1684
show pim join extensive (Bidirectional PIM with a Directly Connected Phantom
RP) on page 1685
show pim join instance <instance-name> extensive on page 1685
show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for
Point-to-Multipoint LSPs) on page 1686
show pim join extensive (Egress Node with Multipoint LDP Inband Signaling for
Point-to-Multipoint LSPs) on page 1687
show pim join summary on page 1689
show pim join (PIM Sparse Mode) on page 1689
show pim join (Bidirectional PIM) on page 1689
show pim join inet6 on page 1690
show pim join inet6 star-g on page 1690
show pim join instance <instance-name> on page 1690
show pim join detail on page 1691

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim join extensive (PIM Sparse Mode) on page 1691

show pim join extensive (Bidirectional PIM) on page 1692
show pim join extensive (Bidirectional PIM with a Directly Connected Phantom
RP) on page 1693
show pim join instance <instance-name> extensive on page 1694
show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for
Point-to-Multipoint LSPs) on page 1694
show pim join extensive (Multipoint LDP with Multicast-Only Fast Reroute) on page 1695
Output Fields

Table 136 on page 1677 describes the output fields for the show pim join command. Output
fields are listed in the approximate order in which they appear.

Table 136: show pim join Output Fields

Field Name

Field Description

Level of Output

Instance

Name of the routing instance.

brief detail extensive summary none

Family

Name of the address family: inet (IPv4) or inet6

(IPv6).

brief detail extensive summary none

Route type

Type of multicast route: (S,G) or (*,G).

summary

Route count

Number of (S,G) routes and number of (*,G) routes.

summary

Rendezvous Point Tree.

brief detail extensive none

Sparse.

brief detail extensive none

Wildcard.

brief detail extensive none

Group

Group address.

brief detail extensive none

Bidirectional group
prefix length

For bidirectional PIM, length of the IP prefix for RP

group ranges.

All levels

Source

Multicast source:

brief detail extensive none

RP

* (wildcard value)

ipv4-address

ipv6-address

Rendezvous point for the PIM group.

Copyright 2014, Juniper Networks, Inc.

brief detail extensive none

1677

Interfaces Fundamentals for Routing Devices

Table 136: show pim join Output Fields (continued)

Field Name

Field Description

Level of Output

Flags

PIM flags:

brief detail extensive none

bidirectionalBidirectional mode entry.

denseDense mode entry.

rptreeEntry is on the rendezvous point tree.

sparseSparse mode entry.

sptEntry is on the shortest-path tree for the

source.

Upstream interface

wildcardEntry is on the shared tree.

RPF interface toward the source address for the

source-specific state (S,G) or toward the
rendezvous point (RP) address for the
non-source-specific state (*,G).

brief detail extensive none

For bidirectional PIM, RP Link means that the

interface is directly connected to a subnet that
contains a phantom RP address.
A pseudo multipoint LDP (M-LDP) interface appears
on egress nodes in M-LDP point-to-multipoint LSPs
with inband signaling.
Upstream neighbor

Information about the upstream neighbor: Direct,

Local, Unknown, or a specific IP address.

extensive

For bidirectional PIM, Direct means that the interface

is directly connected to a subnet that contains a
phantom RP address.
The multipoint LDP (M-LDP) root appears on egress
nodes in M-LDP point-to-multipoint LSPs with
inband signaling.
Active upstream
interface

When multicast-only fast reroute (MoFRR) is

configured in a PIM domain, the upstream interface
for the active path. A PIM router propagates join
messages on two upstream RPF interfaces to
receive multicast traffic on both links for the same
join request. Preference is given to two paths that
do not converge to the same immediate upstream
router. PIM installs appropriate multicast routes
with upstream neighbors as RPF next hops with two
(primary and backup) interfaces.

extensive

Active upstream
neighbor

On the MoFRR primary path, the IP address of the

neighbor that is directly connected to the active
upstream interface.

extensive

1678

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 136: show pim join Output Fields (continued)

Field Name

Field Description

Level of Output

MoFRR Backup
upstream interface

The MoFRR upstream interface that is used when

the primary path fails.

extensive

When the primary path fails, the backup path is

upgraded to primary, and traffic is forwarded
accordingly. If there are alternate paths available,
a new backup path is calculated and the appropriate
multicast route is updated or installed.
Upstream state

Information about the upstream interface:

Join to RPSending a join to the rendezvous point.

Join to SourceSending a join to the source.

Local RPSending neither join messages nor

extensive

prune messages toward the RP, because this

routing device is the rendezvous point.

Local SourceSending neither join messages nor

prune messages toward the source, because the

source is locally attached to this routing device.

Prune to RPSending a prune to the rendezvous

point.

Prune to SourceSending a prune to the source.

NOTE: RP group range entries have None in the

Upstream state field because RP group ranges do
not trigger actual PIM join messages between
routing devices.
Downstream
neighbors

Information about downstream interfaces:

extensive

InterfaceInterface name for the downstream

neighbor.
A pseudo PIM-SM interface appears for all
IGMP-only interfaces.
A pseudo multipoint LDP (M-LDP) interface
appears on ingress root nodes in M-LDP
point-to-multipoint LSPs with inband signaling.

Interface addressAddress of the downstream

neighbor.

StateInformation about the downstream

neighbor: join or prune.

FlagsPIM join flags: R (RPtree), S (Sparse), W

(Wildcard), or zero.

UptimeTime since the downstream interface

joined the group.

Time since last JoinTime since the last join

message was received from the downstream

interface.

Time since last PruneTime since the last prune

message was received from the downstream

interface.

Copyright 2014, Juniper Networks, Inc.

1679

Interfaces Fundamentals for Routing Devices

Table 136: show pim join Output Fields (continued)

Field Name

Field Description

Level of Output

Number of
downstream
interfaces

Total number of outgoing interfaces for each (S,G)

entry.

extensive

Assert Timeout

Length of time between assert cycles on the

downstream interface. Not displayed if the assert
timer is null.

extensive

Keepalive timeout

Time remaining until the downstream join state is

updated (in seconds). If the downstream join state
is not updated before this keepalive timer reaches
zero, the entry is deleted. If there is a directly
connected host, Keepalive timeout is Infinity.

extensive

Uptime

Time since the creation of (S,G) or (*,G) state. The

uptime is not refreshed every time a PIM join
message is received for an existing (S,G) or (*,G)
state.

extensive

Bidirectional
accepting
interfaces

Interfaces on the routing device that forward

bidirectional PIM traffic.

extensive

The reasons for forwarding bidirectional PIM traffic

are that the interface is the winner of the designated
forwarder election (DF Winner), or the interface is
the reverse path forwarding (RPF) interface toward
the RP (RPF).

Sample Output
show pim join summary
user@host> show pim join summary
Instance: PIM.master Family: INET
Route type
(s,g)
(*,g)

Route count
2
1

Instance: PIM.master Family: INET6

show pim join (PIM Sparse Mode)

user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 239.1.1.1

1680

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join (Bidirectional PIM)

user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join inet6

user@host> show pim join inet6
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local

Copyright 2014, Juniper Networks, Inc.

1681

Interfaces Fundamentals for Routing Devices

Group: ff04::e000:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
Group: ff04::e800:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
Group: ff04::e800:101
Source: ::1.1.1.2
Flags: sparse
Upstream interface: unknown (no neighbor)

show pim join inet6 star-g

user@host> show pim join inet6 star-g
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local

show pim join instance <instance-name>

user@host> show pim join instance VPN-A
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Instance: PIM.VPN-A Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join detail

user@host> show pim join detail
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard

1682

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Upstream interface: Local

Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join extensive (PIM Sparse Mode)

user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
10.111.10.2 State: Join Flags: SRW Timeout: 174
Uptime: 00:03:49 Time since last Join: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: SRW Timeout: Infinity
Uptime: 00:03:49 Time since last Join: 00:01:49
Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local Source, Local RP
Keepalive timeout: 344
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
10.111.10.2 State: Join Flags: S Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: S
Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Upstream neighbor: 10.111.10.2
Upstream state: Local RP, Join to Source

Copyright 2014, Juniper Networks, Inc.

1683

Interfaces Fundamentals for Routing Devices

Keepalive timeout: 344

Uptime: 00:03:49
Downstream neighbors:
Interface: Pseudo-GMP
fe-0/0/0.0 fe-0/0/1.0 fe-0/0/3.0
Interface: so-1/0/0.0 (pruned)
10.111.10.2 State: Prune Flags: SR Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: S
Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 3
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join extensive (Bidirectional PIM)

user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Number of downstream interfaces: 0
Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Downstream neighbors:
Interface: lt-1/0/10.24
10.0.24.4 State: Join
RW Timeout: 185
Interface: lt-1/0/10.23
10.0.23.3 State: Join
RW Timeout: 184
Number of downstream interfaces: 2
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)

1684

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Upstream neighbor: Direct

Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Interface: xe-4/1/0.0
(DF Winner)
Number of downstream interfaces: 0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join extensive (Bidirectional PIM with a Directly Connected Phantom RP)
user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Upstream neighbor: Direct
Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Interface: xe-4/1/0.0
(DF Winner)
Number of downstream interfaces: 0

show pim join instance <instance-name> extensive

user@host> show pim join instance VPN-A extensive
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
Interface: mt-1/1/0.32768
10.10.47.101 State: Join Flags: SRW Timeout: 156
Uptime: 00:03:49 Time since last Join: 00:01:49
Number of downstream interfaces: 1
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Upstream neighbor: 10.111.30.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52

Copyright 2014, Juniper Networks, Inc.

1685

Interfaces Fundamentals for Routing Devices

Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Upstream neighbor: 10.111.20.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52

show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 232.1.1.1
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:55
Downstream neighbors:
Interface: Pseudo-MLDP
Interface: lt-1/2/0.25
1.2.5.2 State: Join Flags: S
Timeout: Infinity
Uptime: 11:27:55 Time since last Join: 11:27:55
Group: 232.1.1.2
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.1.1.3
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.2.2.2
Source: 1.2.7.7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:25
Downstream neighbors:

1686

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Interface: Pseudo-MLDP
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff3e::1:2
Source: abcd::1:2:7:7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:26
Downstream neighbors:
Interface: Pseudo-MLDP

show pim join extensive (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 227.1.1.1
Source: *
RP: 1.1.1.1
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 11:31:33
Downstream neighbors:
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: SRW Timeout: Infinity
Uptime: 11:31:33 Time since last Join: 11:31:32
Group: 232.1.1.1
Source: 192.168.219.11
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:32
Downstream neighbors:
Interface: so-0/1/3.0
192.168.92.9 State: Join Flags: S
Timeout: Infinity
Uptime: 11:31:30 Time since last Join: 11:31:30
Downstream neighbors:
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: S
Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32
Group: 232.1.1.2
Source: 192.168.219.11
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:

Copyright 2014, Juniper Networks, Inc.

1687

Interfaces Fundamentals for Routing Devices

Uptime: 11:31:32
Downstream neighbors:
Interface: so-0/1/3.0
192.168.92.9 State: Join Flags: S
Timeout: Infinity
Uptime: 11:31:30 Time since last Join: 11:31:30
Downstream neighbors:
Interface: lt-1/2/0.14
1.1.4.4 State: Join Flags: S Timeout: 177
Uptime: 11:30:33 Time since last Join: 00:00:33
Downstream neighbors:
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: S
Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32
Group: 232.1.1.3
Source: 192.168.219.11
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:32
Downstream neighbors:
Interface: fe-1/3/0.0
192.168.209.9 State: Join Flags: S
Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32
Group: 232.2.2.2
Source: 1.2.7.7
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:30
Downstream neighbors:
Interface: so-0/1/3.0
192.168.92.9 State: Join Flags: S
Timeout: Infinity
Uptime: 11:31:30 Time since last Join: 11:31:30
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff3e::1:2
Source: abcd::1:2:7:7
Flags: sparse,spt
Upstream protocol: MLDP
Upstream interface: Pseudo MLDP
Upstream neighbor: MLDP LSP root <1.1.1.2>
Upstream state: Join to Source
Keepalive timeout:
Uptime: 11:31:32
Downstream neighbors:
Interface: fe-1/3/0.0
fe80::21f:12ff:fea5:c4db State: Join Flags: S
Timeout: Infinity
Uptime: 11:31:32 Time since last Join: 11:31:32

1688

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show pim join summary
user@host> show pim join summary
Instance: PIM.master Family: INET
Route type
(s,g)
(*,g)

Route count
2
1

Instance: PIM.master Family: INET6

show pim join (PIM Sparse Mode)

user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join (Bidirectional PIM)

user@host> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *

Copyright 2014, Juniper Networks, Inc.

1689

Interfaces Fundamentals for Routing Devices

RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join inet6

user@host> show pim join inet6
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: ff04::e000:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
Group: ff04::e800:101
Source: ::1.1.1.1
Flags: sparse
Upstream interface: unknown (no neighbor)
Group: ff04::e800:101
Source: ::1.1.1.2
Flags: sparse
Upstream interface: unknown (no neighbor)

show pim join inet6 star-g

user@host> show pim join inet6 star-g
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff04::e000:101
Source: *
RP: ::46.0.0.13
Flags: sparse,rptree,wildcard
Upstream interface: Local

show pim join instance <instance-name>

user@host> show pim join instance VPN-A
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100

1690

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Instance: PIM.VPN-A Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join detail

user@host> show pim join detail
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join extensive (PIM Sparse Mode)

user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 239.1.1.1
Source: *
RP: 10.255.14.144
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
10.111.10.2 State: Join Flags: SRW Timeout: 174
Uptime: 00:03:49 Time since last Join: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: SRW Timeout: Infinity

Copyright 2014, Juniper Networks, Inc.

1691

Interfaces Fundamentals for Routing Devices

Uptime: 00:03:49 Time since last Join: 00:01:49

Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.14.144
Flags: sparse,spt
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local Source, Local RP
Keepalive timeout: 344
Uptime: 00:03:49
Downstream neighbors:
Interface: so-1/0/0.0
10.111.10.2 State: Join Flags: S Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: S
Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 2
Group: 239.1.1.1
Source: 10.255.70.15
Flags: sparse,spt
Upstream interface: so-1/0/0.0
Upstream neighbor: 10.111.10.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 344
Uptime: 00:03:49
Downstream neighbors:
Interface: Pseudo-GMP
fe-0/0/0.0 fe-0/0/1.0 fe-0/0/3.0
Interface: so-1/0/0.0 (pruned)
10.111.10.2 State: Prune Flags: SR Timeout: 174
Uptime: 00:03:49 Time since last Prune: 00:01:49
Interface: mt-1/1/0.32768
10.10.47.100 State: Join Flags: S
Timeout: Infinity
Uptime: 00:03:49 Time since last Prune: 00:01:49
Number of downstream interfaces: 3
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join extensive (Bidirectional PIM)

user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Number of downstream interfaces: 0

1692

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Group: 225.1.1.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.13.2
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0
Upstream neighbor: 10.10.1.2
Upstream state: None
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Downstream neighbors:
Interface: lt-1/0/10.24
10.0.24.4 State: Join
RW Timeout: 185
Interface: lt-1/0/10.23
10.0.23.3 State: Join
RW Timeout: 184
Number of downstream interfaces: 2
Group: 225.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Upstream neighbor: Direct
Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Interface: xe-4/1/0.0
(DF Winner)
Number of downstream interfaces: 0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard

show pim join extensive (Bidirectional PIM with a Directly Connected Phantom RP)
user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.3.0
Bidirectional group prefix length: 24
Source: *
RP: 10.10.1.3
Flags: bidirectional,rptree,wildcard
Upstream interface: ge-0/0/1.0 (RP Link)
Upstream neighbor: Direct
Upstream state: Local RP
Uptime: 00:03:49
Bidirectional accepting interfaces:
Interface: ge-0/0/1.0
(RPF)
Interface: lo0.0
(DF Winner)
Interface: xe-4/1/0.0
(DF Winner)
Number of downstream interfaces: 0

Copyright 2014, Juniper Networks, Inc.

1693

Interfaces Fundamentals for Routing Devices

show pim join instance <instance-name> extensive

user@host> show pim join instance VPN-A extensive
Instance: PIM.VPN-A Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 235.1.1.2
Source: *
RP: 10.10.47.100
Flags: sparse,rptree,wildcard
Upstream interface: Local
Upstream neighbor: Local
Upstream state: Local RP
Uptime: 00:03:49
Downstream neighbors:
Interface: mt-1/1/0.32768
10.10.47.101 State: Join Flags: SRW Timeout: 156
Uptime: 00:03:49 Time since last Join: 00:01:49
Number of downstream interfaces: 1
Group: 235.1.1.2
Source: 192.168.195.74
Flags: sparse,spt
Upstream interface: at-0/3/1.0
Upstream neighbor: 10.111.30.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52
Group: 235.1.1.2
Source: 192.168.195.169
Flags: sparse
Upstream interface: so-1/0/1.0
Upstream neighbor: 10.111.20.2
Upstream state: Local RP, Join to Source
Keepalive timeout: 156
Uptime: 00:14:52

show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 232.1.1.1
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:55
Downstream neighbors:
Interface: Pseudo-MLDP
Interface: lt-1/2/0.25
1.2.5.2 State: Join Flags: S
Timeout: Infinity
Uptime: 11:27:55 Time since last Join: 11:27:55
Group: 232.1.1.2
Source: 192.168.219.11
Flags: sparse,spt

1694

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Upstream interface: fe-1/3/1.0

Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.1.1.3
Source: 192.168.219.11
Flags: sparse,spt
Upstream interface: fe-1/3/1.0
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:41
Downstream neighbors:
Interface: Pseudo-MLDP
Group: 232.2.2.2
Source: 1.2.7.7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:25
Downstream neighbors:
Interface: Pseudo-MLDP
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: ff3e::1:2
Source: abcd::1:2:7:7
Flags: sparse,spt
Upstream interface: lt-1/2/0.27
Upstream neighbor: Direct
Upstream state: Local Source
Keepalive timeout:
Uptime: 11:27:26
Downstream neighbors:
Interface: Pseudo-MLDP

show pim join extensive (Multipoint LDP with Multicast-Only Fast Reroute)
user@host> show pim join 225.1.1.1 extensive sg
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 225.1.1.1
Source: 10.0.0.1
Flags: sparse,spt
Active upstream interface: fe-1/2/13.0
Active upstream neighbor: 10.0.0.9
MoFRR Backup upstream interface: fe-1/2/14.0
MoFRR Backup upstream neighbor: 10.0.0.21
Upstream state: Join to Source, No Prune to RP
Keepalive timeout: 354
Uptime: 00:00:06
Downstream neighbors:

Copyright 2014, Juniper Networks, Inc.

1695

Interfaces Fundamentals for Routing Devices

Interface: fe-1/2/15.0
10.0.0.13 State: Join Flags: S
Timeout: Infinity
Uptime: 00:00:06 Time since last Join: 00:00:06
Number of downstream interfaces: 1

1696

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim mdt

Syntax

Release Information
Description

Options

show pim mdt instance instance-name

<brief | detail | extensive>
<incoming | outgoing>
<logical-system (all | logical-system-name)>
<range>

Command introduced before Junos OS Release 7.4.

Display information about Protocol Independent Multicast (PIM) default multicast
distribution tree (MDT) and the data MDTs in a Layer 3 VPN environment for a routing
instance.
instance instance-nameDisplay information about data-MDTs for a specific PIM-enabled

routing instance.
brief | detail | extensive(Optional) Display the specified level of output.
incoming | outgoing(Optional) Display incoming or outgoing multicast data tunnels,

respectively.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

range(Optional) Display information about an IP address with optional prefix length

representing a particular multicast group.

Required Privilege
Level
List of Sample Output

Output Fields

view

show pim mdt instance on page 1698

show pim mdt instance detail on page 1699
show pim mdt instance extensive on page 1699
show pim mdt instance incoming on page 1699
show pim mdt instance outgoing on page 1699
show pim mdt instance (SSM Mode) on page 1700
Table 137 on page 1697 describes the output fields for the show pim mdt command. Output
fields are listed in the approximate order in which they appear.

Table 137: show pim mdt Output Fields

Field Name

Field Description

Level of Output

Instance

Name of the routing instance.

All levels

Tunnel direction

Direction the tunnel faces, from the router's perspective: Outgoing or Incoming.

All levels

Tunnel mode

Mode the tunnel is operating in: PIM-SSM or PIM-ASM.

All levels

Copyright 2014, Juniper Networks, Inc.

1697

Interfaces Fundamentals for Routing Devices

Table 137: show pim mdt Output Fields (continued)

Field Name

Field Description

Level of Output

Default group
address

Default multicast group address using this tunnel.

All levels

Default source
address

Default multicast source address using this tunnel.

All levels

Default tunnel
interface

Default multicast tunnel interface.

All levels

Default tunnel
source

Address used as the source address for outgoing PIM control messages.

All levels

C-Group

Customer-facing multicast group address using this tunnel. If you enable dynamic
reuse of data MDT group addresses, more than one group address can use the same
data MDT.

detail

C-Source

IP address of the multicast source in the customer's address space. If you enable
dynamic reuse of data MDT group addresses, more than one source address can use
the same data MDT.

detail

P-Group

Service provider-facing multicast group address using this tunnel.

detail

Data tunnel
interface

Multicast data tunnel interface that set up the data-MDT tunnel.

detail

Last known
forwarding rate

Last known rate, in kilobits per second, at which the tunnel was forwarding traffic.

detail

Configured
threshold rate

Rate, in kilobits per second, above which a data-MDT tunnel is created and below
which it is deleted.

detail

Tunnel uptime

Time that this data-MDT tunnel has existed. The format is hours:minutes:seconds.

detail

Sample Output
show pim mdt instance
user@host> show pim mdt instance VPN-A
Instance: PIM.VPN-A
Tunnel direction: Outgoing
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.32768
Default tunnel source: 192.168.7.1
C-group address
235.1.1.2

C-source address
192.168.195.74

P-group address
228.0.0.0

Data tunnel interface

mt-1/1/0.32769

Instance: PIM.VPN-A
Tunnel direction: Incoming
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.1081344

1698

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim mdt instance detail

user@host> show pim mdt instance VPN-A detail
Instance: PIM.VPN-A
Tunnel direction: Outgoing
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.32768
Default tunnel source: 192.168.7.1
C-Group: 235.1.1.2
C-Source: 192.168.195.74
P-Group : 228.0.0.0
Data tunnel interface
Last known forwarding rate
Configured threshold rate
Tunnel uptime

:
:
:
:

mt-1/1/0.32769
48 kbps (6 kBps)
10 kbps
00:00:34

Instance: PIM.VPN-A
Tunnel direction: Incoming
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.1081344

show pim mdt instance extensive

user@host> show pim mdt instance VPN-A extensive
Instance: PIM.VPN-A
Tunnel direction: Outgoing
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.32768
Default tunnel source: 192.168.7.1
C-Group: 235.1.1.2
C-Source: 192.168.195.74
P-Group : 228.0.0.0
Data tunnel interface
Last known forwarding rate
Configured threshold rate
Tunnel uptime

:
:
:
:

mt-1/1/0.32769
48 kbps (6 kBps)
10 kbps
00:00:41

Instance: PIM.VPN-A
Tunnel direction: Incoming
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.1081344

show pim mdt instance incoming

user@host> show pim mdt instance VPN-A incoming
Instance: PIM.VPN-A
Tunnel direction: Incoming
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.1081344

show pim mdt instance outgoing

user@host> show pim mdt instance VPN-A outgoing
Instance: PIM.VPN-A
Tunnel direction: Outgoing
Default group address: 239.1.1.1
Default tunnel interface: mt-1/1/0.32768
Default tunnel source: 192.168.7.1

Copyright 2014, Juniper Networks, Inc.

1699

Interfaces Fundamentals for Routing Devices

C-group address
235.1.1.2

C-source address
192.168.195.74

P-group address
228.0.0.0

Data tunnel interface

mt-1/1/0.32769

show pim mdt instance (SSM Mode)

user@host> show pim mdt instance vpn-a
Instance: PIM.vpn-a
Tunnel direction: Outgoing
Tunnel mode: PIM-SSM
Default group address: 232.1.1.1
Default source address: 10.255.14.216
Default tunnel interface: mt-1/3/0.32769
Default tunnel source: 192.168.7.1
Instance: PIM.vpn-a
Tunnel direction: Incoming
Tunnel mode: PIM-SSM
Default group address: 232.1.1.1
Default source address: 10.255.14.217
Default tunnel interface: mt-1/3/0.1081345
Instance: PIM.vpn-a
Tunnel direction: Incoming
Tunnel mode: PIM-SSM
Default group address: 232.1.1.1
Default source address: 10.255.14.218
Default tunnel interface: mt-1/3/0.1081345

1700

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim mdt data-mdt-joins

Syntax

Release Information

show pim mdt data-mdt-joins

<logical-system (all | logical-system-name)> instance instance-name

Command introduced in Junos OS Release 11.2.

Description

In a draft-rosen Layer 3 multicast virtual private network (MVPN) configured with service
provider tunnels, display the advertisements of new multicast distribution tree (MDT)
group addresses cached by the provider edge (PE) routers in the specified VPN routing
and forwarding (VRF) instance that is configured to use the Protocol Independent
Multicast (PIM) protocol.

Options

instance instance-nameDisplay data MDT join packets cached by PE routers in a specific

PIM instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

NOTE: Draft-rosen multicast VPNs are not supported in a logical system

environment even though the configuration statements can be configured
under the logical-systems hierarchy.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

Understanding Data MDTs

Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific

Multicast Mode

Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast
Mode

show pim mdt data-mdt-joins on page 1702

Table 138 on page 1701 describes the output fields for the show pim mdt data-mdt-joins
command. Output fields are listed in the approximate order in which they appear.

Table 138: show pim mdt data-mdt-joins Output Fields

Field Name

Field Description

C-Group

IPv4 group address in the address space of the customers VPN-specific PIM-enabled routing instance
of the multicast traffic destination. This 32-bit value is carried in the C-group field of the MDT join TLV
packet.

C-Source

IPv4 address in the address space of the customers VPN-specific PIM-enabled routing instance of the
multicast traffic source. This 32-bit value is carried in the C-source field of the MDT join TLV packet.

Copyright 2014, Juniper Networks, Inc.

1701

Interfaces Fundamentals for Routing Devices

Table 138: show pim mdt data-mdt-joins Output Fields (continued)

Field Name

Field Description

P-Group

IPv4 group address in the service providers address space of the new data MDT that the PE router will
use to encapsulate the VPN multicast traffic flow (C-Source, C-Group). This 32-bit value is carried in
the P-group field of the MDT join TLV packet.

P-Source

IPv4 address of the PE router.

Timeout

Timeout, in seconds, remaining for this cache entry. When the cache entry is created, this field is set to
180 seconds. After an entry times out, the PE router deletes the entry from its cache and prunes itself
off the data MDT.

Sample Output
show pim mdt data-mdt-joins
user@host show pim mdt data-mdt-joins instance VPN-A
C-Source
C-Group
P-Source
20.2.15.9
225.1.1.2
20.0.0.5
20.2.15.9
225.1.1.3
20.0.0.5

1702

P-Group
239.10.10.0
239.10.10.1

Timeout
172
172

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim mdt data-mdt-limit

Syntax

Release Information
Description

Options

show pim mdt data-mdt-limit instance instance-name

<logical-system (all | logical-system-name)>

Command introduced in Junos OS Release 12.2.

Display the maximum number configured and the currently active data multicast
distribution trees (MDTs) for a specific VPN routing and forwarding (VRF) instance.
instance instance-nameDisplay data MDT information for the specified VRF instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

NOTE: Draft-rosen multicast VPNs are not supported in a logical system

environment even though the configuration statements can be configured
under the logical-systems hierarchy.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

Understanding Data MDTs

Example: Configuring Data MDTs and Provider Tunnels Operating in Source-Specific

Multicast Mode

Example: Configuring Data MDTs and Provider Tunnels Operating in Any-Source Multicast
Mode

show pim mdt data-mdt-limit on page 1703

Table 139 on page 1703 describes the output fields for the show pim mdt data-mdt-limit
command. Output fields are listed in the approximate order in which they appear.

Table 139: show pim mdt data-mdt-limit Output Fields

Field Name

Field Description

Maximum Data
Tunnels

Maximum number of data MDTs created in this VRF instance. If the number is 0, no data MDTs are
created for this VRF instance.

Active Data Tunnels

Active number of data MDTs in this VRF instance.

Sample Output
show pim mdt data-mdt-limit
user@host show pim mdt data-mdt-limit instance VPN-A

Copyright 2014, Juniper Networks, Inc.

1703

Interfaces Fundamentals for Routing Devices

Maximum Data Tunnels

Active Data Tunnels

1704

10
2

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim neighbors

List of Syntax

Syntax

Syntax on page 1705

Syntax (EX Series Switch and the QFX Series) on page 1705
show pim neighbors
<brief | detail>
<inet | inet6>
<instance (instance-name | all)>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show pim neighbors

<brief | detail>
<inet | inet6>
<instance (instance-name | all)>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.
Support for the instance all option added in Junos OS Release 12.1.

Description
Options

Display information about Protocol Independent Multicast (PIM) neighbors.

none(Same as brief) Display standard information about PIM neighbors for all supported

family addresses for the main instance.

brief | detail(Optional) Display the specified level of output.
inet | inet6(Optional) Display information about PIM neighbors for IPv4 or IPv6 family

addresses, respectively.
instance (instance-name | all)(Optional) Display information about neighbors for the

specified PIM-enabled routing instance or for all routing instances.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show pim neighbors on page 1707

show pim neighbors brief on page 1707
show pim neighbors instance on page 1707
show pim neighbors detail on page 1707
show pim neighbors detail (With BFD) on page 1708
Table 140 on page 1706 describes the output fields for the show pim neighbors command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1705

Interfaces Fundamentals for Routing Devices

Table 140: show pim neighbors Output Fields

Field Name

Field Description

Level of Output

Instance

Name of the routing instance.

All levels

Interface

Interface through which the neighbor is reachable.

All levels

Neighbor addr

Address of the neighboring PIM routing device.

All levels

IP

IP version: 4 or 6.

All levels

PIM version running on the neighbor: 1 or 2.

All levels

Mode

PIM mode of the neighbor: Sparse, Dense, SparseDense, or Unknown. When the
neighbor is running PIM version 2, this mode is always Unknown.

All levels

Option

Can be one or more of the following:

brief none

BBidirectional Capable.

HHello Option Holdtime.

GGeneration Identifier.

PHello Option DR Priority.

LHello Option LAN Prune Delay.

Uptime

Time the neighbor has been operational since the PIM process was last initialized,
in the format dd:hh:mm:ss ago for less than a week and nwnd:hh:mm:ss ago for
more than a week.

All levels

Address

Address of the neighboring PIM routing device.

detail

BFD

Status and operational state of the Bidirectional Forwarding Detection (BFD)

protocol on the interface: Enabled, Operational state is up, or Disabled.

detail

Hello Option
Holdtime

Time for which the neighbor is available, in seconds. The range of values is
0 through 65,535.

detail

Hello Default
Holdtime

Default holdtime and the time remaining if the holdtime option is not in the
received hello message.

detail

Hello Option DR
Priority

Designated router election priority. The range of values is 0 through 255.

detail

Hello Option
Generation ID

9-digit or 10-digit number used to tag hello messages.

detail

Hello Option
Bi-Directional PIM
supported

Neighbor can process bidirectional PIM messages.

detail

Hello Option LAN

Prune Delay

Time to wait before the neighbor receives prune messages, in the format delay
nnn ms override nnnn ms.

detail

1706

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 140: show pim neighbors Output Fields (continued)

Field Name

Field Description

Level of Output

Join Suppression
supported

Neighbor is capable of join suppression.

detail

Rx Join

Information about joins received from the neighbor.

detail

GroupGroup addresses in the join message.

SourceAddress of the source in the join message.

TimeoutTime for which the join is valid.

Sample Output
show pim neighbors
user@host> show pim neighbors
Instance: PIM.master
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority
Interface
so-1/0/0.0

IP V Mode
4 2

Option
HPLG

Uptime Neighbor addr

00:07:10 10.111.10.2

show pim neighbors brief

The output for the show pim neighbors brief command is identical to that for the show
pim neighbors command. For sample output, see show pim neighbors on page 1707.
show pim neighbors instance
user@host> show pim neighbors instance VPN-A
Instance: PIM.VPN-A
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority
Interface
at-0/3/1.0
mt-1/1/0.32768
so-1/0/1.0

IP
4
4
4

V Mode
2
2
2

Option
HPLG
HPLG
HPLG

Uptime
00:07:54
00:07:22
00:07:50

Neighbor addr
10.111.30.2
10.10.47.101
10.111.20.2

show pim neighbors detail

user@host> show pim neighbors detail
Instance: PIM.master
Interface: ge-0/0/1.0
Address: 10.10.1.1, IPv4, PIM v2, Mode: SparseDense, sg Join Count: 0, tsg
Join Count: 2
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 2053759302
Hello Option Bi-Directional PIM supported
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported

Copyright 2014, Juniper Networks, Inc.

1707

Interfaces Fundamentals for Routing Devices

Address: 10.10.1.2, IPv4, PIM v2, sg Join Count: 0, tsg Join Count: 2
BFD: Disabled
Hello Option Holdtime: 105 seconds 93 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1734018161
Hello Option Bi-Directional PIM supported
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported
Interface: lo0.0
Address: 10.255.179.246,
IPv4, PIM v2, Mode: SparseDense, sg Join Count:
0, tsg Join Count: 0
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 1997462267
Hello Option Bi-Directional PIM supported
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Join Suppression supported

show pim neighbors detail (With BFD)

user@host> show pim neighbors detail
Instance: PIM.master
Interface: fe-1/0/0.0
Address: 192.168.11.1,
IPv4, PIM v2, Mode: Sparse
Hello Option Holdtime: 65535 seconds
Hello Option DR Priority: 1
Hello Option Generation ID: 836607909
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Address: 192.168.11.2,
IPv4, PIM v2
BFD: Enabled, Operational state is up
Hello Default Holdtime: 105 seconds 104 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1907549685
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Interface: fe-1/0/1.0
Address: 192.168.12.1,
IPv4, PIM v2
BFD: Disabled
Hello Default Holdtime: 105 seconds 80 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1971554705
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms

1708

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim rps

List of Syntax

Syntax

Syntax on page 1709

Syntax (EX Series Switch and the QFX Series) on page 1709
show pim rps
<brief | detail | extensive>
<group-address>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show pim rps

<brief | detail | extensive>
<group-address>
<inet | inet6>
<instance instance-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.

Description

Options

Display information about Protocol Independent Multicast (PIM) rendezvous points

(RPs).
noneDisplay standard information about PIM RPs for all groups and family addresses

for all routing instances.

brief | detail | extensive(Optional) Display the specified level of output.
group-address(Optional) Display the RPs for a particular group. If you specify a group

address, the output lists the routing device that is the RP for that group.
inet | inet6(Optional) Display information for IPv4 or IPv6 family addresses, respectively.
instance instance-name(Optional) Display information about RPs for a specific

PIM-enabled routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

view

Example: Configuring Bidirectional PIM

show pim rps on page 1712

show pim rps brief on page 1712
show pim rps <group-address> on page 1712

Copyright 2014, Juniper Networks, Inc.

1709

Interfaces Fundamentals for Routing Devices

show pim rps <group-address> (Bidirectional PIM) on page 1712

show pim rps <group-address> (PIM Dense Mode) on page 1713
show pim rps <group-address> (SSM Range Without asm-override-ssm
Configured) on page 1713
show pim rps <group-address> (SSM Range With asm-override-ssm Configured and
a Sparse-Mode RP) on page 1713
show pim rps <group-address> (SSM Range With asm-override-ssm Configured and
a Bidirectional RP) on page 1713
show pim rps instance on page 1713
show pim rps extensive (PIM Sparse Mode) on page 1713
show pim rps extensive (Bidirectional PIM) on page 1714
show pim rps extensive (PIM Anycast RP in Use) on page 1714
Output Fields

Table 141 on page 1710 describes the output fields for the show pim rps command. Output
fields are listed in the approximate order in which they appear.

Table 141: show pim rps Output Fields

Field Name

Field Description

Level of Output

Instance

Name of the routing instance.

All levels

Family or Address
family

Name of the address family: inet (IPv4) or inet6 (IPv6).

All levels

RP address

Address of the rendezvous point.

All levels

Type

Type of RP:

brief none

auto-rpAddress of the RP known through the Auto-RP protocol.

bootstrapAddress of the RP known through the bootstrap router protocol

(BSR).

embeddedAddress of the RP known through an embedded RP (IPv6).

staticAddress of RP known through static configuration.

Holdtime

How long to keep the RP active, with time remaining, in seconds.

All levels

Timeout

How long until the local routing device determines the RP to be unreachable,
in seconds.

All levels

Groups

Number of groups currently using this RP.

All levels

Group prefixes

Addresses of groups that this RP can span.

brief none

Learned via

Address and method by which the RP was learned.

detail extensive

Mode

The PIM mode of the RP: bidirectional or sparse.

All levels

If a sparse and bidirectional RPs are configured with the same RP address, they
appear as separate entries in both formats.
Time Active

1710

How long the RP has been active, in the format hh:mm:ss.

detail extensive

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 141: show pim rps Output Fields (continued)

Field Name

Field Description

Level of Output

Device Index

Index value of the order in which Junos OS finds and initializes the interface.

detail extensive

For bidirectional RPs, the Device Index output field is omitted because
bidirectional RPs do not require encapsulation and de-encapsulation interfaces.
Subunit

Logical unit number of the interface.

detail extensive

For bidirectional RPs, the Subunit output field is omitted because bidirectional
RPs do not require encapsulation and de-encapsulation interfaces.
Interface

Either the encapsulation or the de-encapsulation logical interface, depending

on whether this routing device is a designated router (DR) facing an RP router,
or is the local RP, respectively.

detail extensive

For bidirectional RPs, the Interface output field is omitted because bidirectional
RPs do not require encapsulation and de-encapsulation interfaces.
Group Ranges

Addresses of groups that this RP spans.

detail extensive

group-address
Active groups using
RP

Number of groups currently using this RP.

detail extensive

total

Total number of active groups for this RP.

detail extensive

Register State for

RP

Current register state for each group:

extensive

GroupMulticast group address.

SourceMulticast source address for which the PIM register is sent or received,

depending on whether this router is a designated router facing an RP router,

or is the local RP, respectively:

First HopPIM-designated routing device that sent the Register message

(the source address in the IP header).

RP AddressRP to which the Register message was sent (the destination

address in the IP header).

State:

On the designated router:

SendSending Register messages.

ProbeSent a null register. If a Register-Stop message does not arrive in

5 seconds, the designated router resumes sending Register messages.

SuppressReceived a Register-Stop message. The designated router is

waiting for the timer to resume before changing to Probe state.

On the RP:

ReceiveReceiving Register messages.

Anycast-PIM rpset

If anycast RP is configured, the addresses of the RPs in the set.

extensive

Anycast-PIM local
address used

If anycast RP is configured, the local address used by the RP.

extensive

Copyright 2014, Juniper Networks, Inc.

1711

Interfaces Fundamentals for Routing Devices

Table 141: show pim rps Output Fields (continued)

Field Name

Field Description

Level of Output

Anycast-PIM
Register State

If anycast RP is configured, the current register state for each group:

extensive

GroupMulticast group address.

SourceMulticast source address for which the PIM register is sent or received,

depending on whether this routing device is a designated router facing an RP

router, or is the local RP, respectively.

RP selected

OriginHow the information was obtained:

DIRECTFrom a local attachment

MSDPFrom the Multicast Source Discovery Protocol (MSDP)

DRFrom the designated router

For sparse mode and bidirectional mode, the identity of the RP for the specified
group address.

group-address

Sample Output
show pim rps
user@host> show pim rps
Instance: PIM.master
Address-family INET
RP address
Type
100.100.100.100 auto-rp
200.200.200.200 auto-rp

Mode
Holdtime Timeout Groups Group prefixes
sparse
150
146
0 235.0.0.0/8
235.100.100.0/24
sparse
150
146
0 224.0.0.0/4

address-family INET6

show pim rps brief

The output for the show pim rps brief command is identical to that for the show pim rps
command. For sample output, see show pim rps on page 1712.
show pim rps <group-address>
user@host> show pim rps 235.100.100.0
Instance: PIM.master
Instance: PIM.master
RP selected: 100.100.100.100

show pim rps <group-address> (Bidirectional PIM)

user@host> show pim rps 224.1.1.1
Instance: PIM.master
224.1.0.0/16
11.4.12.75 (Bidirectional)
RP selected: 11.4.12.75

1712

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim rps <group-address> (PIM Dense Mode)

user@host> show pim rps 224.1.1.1
Instance: PIM.master
Dense Mode active for group 224.1.1.1

show pim rps <group-address> (SSM Range Without asm-override-ssm Configured)

user@host> show pim rps 224.1.1.1
Instance: PIM.master
Source-specific Mode (SSM) active for group 224.1.1.1

show pim rps <group-address> (SSM Range With asm-override-ssm Configured and a Sparse-Mode RP)
user@host> show pim rps 224.1.1.1
Instance: PIM.master
Source-specific Mode (SSM) active with Sparse Mode ASM override for group 224.1.1.1
224.1.0.0/16
11.4.12.75
RP selected: 11.4.12.75

show pim rps <group-address> (SSM Range With asm-override-ssm Configured and a Bidirectional RP)
user@host> show pim rps 224.1.1.1
Instance: PIM.master
Source-specific Mode (SSM) active with Sparse Mode ASM override for group 224.1.1.1
224.1.0.0/16
11.4.12.75 (Bidirectional)
RP selected: (null)

show pim rps instance

user@host> show pim rps instance VPN-A
Instance: PIM.VPN-A
Address family INET
RP address
Type
Holdtime Timeout Groups Group prefixes
10.10.47.100
static
0
None
1 224.0.0.0/4
Address family INET6

show pim rps extensive (PIM Sparse Mode)

user@host> show pim rps extensive
Instance: PIM.master
Family: INET
RP: 10.255.245.91
Learned via: static configuration
Time Active: 00:05:48
Holdtime: 45 with 36 remaining
Device Index: 122
Subunit: 32768
Interface: pd-6/0/0.32768

Copyright 2014, Juniper Networks, Inc.

1713

Interfaces Fundamentals for Routing Devices

Group Ranges:
224.0.0.0/4, 36s remaining
Active groups using RP:
225.1.1.1
total 1 groups active
Register State for RP:
Group
Source
225.1.1.1
192.168.195.78

FirstHop
10.255.14.132

RP Address
10.255.245.91

State
Receive

Timeout
0

show pim rps extensive (Bidirectional PIM)

user@host> show pim rps extensive
Instance: PIM.master
Address family INET
RP: 10.10.1.3
Learned via: static configuration
Mode: Bidirectional
Time Active: 01:58:07
Holdtime: 150
Group Ranges:
224.1.3.0/24
225.1.3.0/24
RP: 10.10.13.2
Learned via: static configuration
Mode: Bidirectional
Time Active: 01:58:07
Holdtime: 150
Group Ranges:
224.1.1.0/24
225.1.1.0/24

show pim rps extensive (PIM Anycast RP in Use)

user@host> show pim rps extensive
Instance: PIM.master
Family: INET
RP: 10.10.10.2
Learned via: static configuration
Time Active: 00:54:52
Holdtime: 0
Device Index: 130
Subunit: 32769
Interface: pimd.32769
Group Ranges:
224.0.0.0/4
Active groups using RP:
224.10.10.10
total 1 groups active
Anycast-PIM rpset:
10.100.111.34
10.100.111.17
10.100.111.55
Anycast-PIM local address used: 10.100.111.1

1714

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Anycast-PIM Register State:

Group
Source
224.1.1.1
10.10.95.2
224.1.1.2
10.10.95.2
224.10.10.10
10.10.70.1
224.10.10.11
10.10.70.1
224.20.20.1
10.10.71.1

Origin
DIRECT
DIRECT
MSDP
MSDP
DR

Address family INET6

Anycast-PIM rpset:
ab::1
ab::2
Anycast-PIM local address used: cd::1
Anycast-PIM Register State:
Group
Source
::224.1.1.1
::10.10.95.2
::224.1.1.2
::10.10.95.2
::224.20.20.1
::10.10.71.1

Copyright 2014, Juniper Networks, Inc.

Origin
DIRECT
DIRECT
DR

1715

Interfaces Fundamentals for Routing Devices

show pim snooping interfaces

Syntax

Release Information

Description
Options

show pim snooping interfaces

<brief | detail>
<instance instance-name>
<interface interface-name>
<logical-system logical-system-name>
<vlan-id vlan-identifier>

Command introduced in Junos OS Release 12.3 for MX Series 3D Universal Edge devices.
Command introduced in Junos OS Release 13.2 for M Series Multiservice Edge devices.
Display information about PIM snooping interfaces.
noneDisplay detailed information.
brief | detail(Optional) Display the specified level of output.
instance <instance-name>(Optional) Display PIM snooping interface information for

the specified routing instance.

interface <interface-name>(Optional) Display PIM snooping information for the specified

interface only.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

vlan-id <vlan-identifier>(Optional) Display PIM snooping interface information for the

specified VLAN.
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

PIM Snooping for VPLS

show pim snooping interfaces on page 1717

show pim snooping interfaces instance vpls1 on page 1717
show pim snooping interfaces interface <interface-name> on page 1718
show pim snooping interfaces vlan-id <vlan-id> on page 1718
Table 142 on page 1716 lists the output fields for the show pim snooping interface command.
Output fields are listed in the approximate order in which they appear.

Table 142: show pim snooping interface Output Fields

Field Name

Field Description

Level of Output

Instance

Routing instance for PIM snooping.

All levels

Learning-Domain

Learning domain for snooping.

All levels

1716

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 142: show pim snooping interface Output Fields (continued)

Field Name

Field Description

Level of Output

Name

Router interfaces that are part of this learning domain.

All levels

State

State of the interface: Up, or Down.

All levels

IP-Version

Version of IP used: 4 for IPv4, or 6 for IPv6.

All levels

NbrCnt

Number of neighboring routers connected through the specified interface.

All levels

DR address

IP address of the designated router.

All levels

Sample Output
show pim snooping interfaces
user@host> show pim snooping interfaces
Instance: vpls1
Learning-Domain: vlan-id 10
Name State IP-Version NbrCnt
ge-1/3/1.10 Up 4 1
ge-1/3/3.10 Up 4 1
ge-1/3/5.10 Up 4 1
ge-1/3/7.10 Up 4 1
DR address: 20.0.110.5
DR flooding is ON
Learning-Domain: vlan-id 20
Name State IP-Version NbrCnt
ge-1/3/1.20 Up 4 1
ge-1/3/3.20 Up 4 1
ge-1/3/5.20 Up 4 1
ge-1/3/7.20 Up 4 1
DR address: 20.0.120.5
DR flooding is ON

show pim snooping interfaces instance vpls1

user@host> show pim snooping interfaces instance vpls1
Instance: vpls1
Learning-Domain: vlan-id 10
Name State IP-Version NbrCnt
ge-1/3/1.10 Up 4 1
ge-1/3/3.10 Up 4 1
ge-1/3/5.10 Up 4 1
ge-1/3/7.10 Up 4 1
DR address: 20.0.110.5
DR flooding is ON
Learning-Domain: vlan-id 20
Name State IP-Version NbrCnt
ge-1/3/1.20 Up 4 1
ge-1/3/3.20 Up 4 1
ge-1/3/5.20 Up 4 1
ge-1/3/7.20 Up 4 1

Copyright 2014, Juniper Networks, Inc.

1717

Interfaces Fundamentals for Routing Devices

DR address: 20.0.120.5
DR flooding is ON

show pim snooping interfaces interface <interface-name>

user@host> show pim snooping interfaces interface ge-1/3/1.10
Instance: vpls1
Learning-Domain: vlan-id 10
Name State IP-Version NbrCnt
ge-1/3/1.10 Up 4 1
DR address: 20.0.110.5
DR flooding is ON
Learning-Domain: vlan-id 20
DR address: 20.0.120.5
DR flooding is ON

show pim snooping interfaces vlan-id <vlan-id>

user@host> show pim snooping interfaces vlan-id 10
Instance: vpls1
Learning-Domain: vlan-id 10
Name State IP-Version NbrCnt
ge-1/3/1.10 Up 4 1
ge-1/3/3.10 Up 4 1
ge-1/3/5.10 Up 4 1
ge-1/3/7.10 Up 4 1
DR address: 20.0.110.5
DR flooding is ON

1718

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim snooping join

Syntax

Release Information

Description
Options

show pim snooping join

<brief | detail | extensive>
<instance instance-name>
<logical-system logical-system-name>
<vlan-id vlan-id>

Command introduced in Junos OS Release 12.3 for MX Series 3D Universal Edge devices.
Command introduced in Junos OS Release 13.2 for M Series Multiservice Edge devices.
Display information about Protocol Independent Multicast (PIM) snooping joins.
noneDisplay detailed information.
brief | detail | extensive(Optional) Display the specified level of output.
instance instance-name(Optional) Display PIM snooping join information for the specified

routing instance.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

vlan-id vlan-identifier(Optional) Display PIM snooping join information for the specified

VLAN.
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

PIM Snooping for VPLS

show pim snooping join on page 1721

show pim snooping join extensive on page 1721
show pim snooping join instance on page 1721
show pim snooping join vlan-id on page 1722
Table 143 on page 1719 lists the output fields for the show pim snooping join command.
Output fields are listed in the approximate order in which they appear.

Table 143: show pim snooping join Output Fields

Field Name

Field Description

Level of Output

Instance

Routing instance for PIM snooping.

All levels

Learning-Domain

Learning domain for PIM snooping.

All levels

Group

Multicast group address.

All levels

Copyright 2014, Juniper Networks, Inc.

1719

Interfaces Fundamentals for Routing Devices

Table 143: show pim snooping join Output Fields (continued)

Field Name

Field Description

Level of Output

Source

Multicast source address:

All levels

Flags

Upstream state

* (wildcard value)

<ipv4-address>

<ipv6-address>

PIM flags:

bidirectionalBidirectional mode entry.

denseDense mode entry.

rptreeEntry is on the rendezvous point tree.

sparseSparse mode entry.

sptEntry is on the shortest-path tree for the source.

wildcardEntry is on the shared tree.

All levels

Information about the upstream interface:

All levels

Join to RPSending a join to the rendezvous point.

Join to SourceSending a join to the source.

Local RPSending neither join messages nor prune messages toward the RP,

because this router is the rendezvous point.

Local SourceSending neither join messages nor prune messages toward the

source, because the source is locally attached to this routing device.

Prune to RPSending a prune to the rendezvous point.

Prune to SourceSending a prune to the source.

NOTE: RP group range entries have None in the Upstream state field because RP
group ranges do not trigger actual PIM join messages between routers.
Upstream neighbor

Information about the upstream neighbor: Direct, Local, Unknown, or a specific IP

address.

All levels

For bidirectional PIM, Direct means that the interface is directly connected to a subnet
that contains a phantom RP address.
Upstream port

RPF interface toward the source address for the source-specific state (S,G) or toward
the rendezvous point (RP) address for the non-source-specific state (*,G).

All levels

For bidirectional PIM, RP Link means that the interface is directly connected to a
subnet that contains a phantom RP address.
Downstream port

Information about downstream interfaces.

extensive

Downstream
neighbors

Address of the downstream neighbor.

extensive

Timeout

Time remaining until the downstream join state is updated (in seconds).

extensive

1720

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Sample Output
show pim snooping join
user@host> show pim snooping join
Instance: vpls1
Learning-Domain: vlan-id 10
Group: 225.1.1.2
Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.110.4, port: ge-1/3/5.10

Learning-Domain: vlan-id 20
Group: 225.1.1.3
Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.120.4, port: ge-1/3/5.20

show pim snooping join extensive

user@host> show pim snooping join extensive
Instance: vpls1
Learning-Domain: vlan-id 10
Group: 225.1.1.2
Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.110.4, port: ge-1/3/5.10
Downstream port: ge-1/3/1.10
Downstream neighbors:
20.0.110.2 State: Join Flags: SRW Timeout: 166
Learning-Domain: vlan-id 20
Group: 225.1.1.3
Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.120.4, port: ge-1/3/5.20
Downstream port: ge-1/3/3.20
Downstream neighbors:
20.0.120.3 State: Join Flags: SRW Timeout: 168

show pim snooping join instance

user@host> show pim snooping join instance vpls1
Instance: vpls1
Learning-Domain: vlan-id 10
Group: 225.1.1.2
Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.110.4, port: ge-1/3/5.10
Learning-Domain: vlan-id 20
Group: 225.1.1.3

Copyright 2014, Juniper Networks, Inc.

1721

Interfaces Fundamentals for Routing Devices

Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.120.4, port: ge-1/3/5.20

show pim snooping join vlan-id

user@host> show pim snooping join vlan-id 10
Instance: vpls1
Learning-Domain: vlan-id 10
Group: 225.1.1.2
Source: *
Flags: sparse,rptree,wildcard
Upstream state: None
Upstream neighbor: 20.0.110.4, port: ge-1/3/5.10

1722

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim snooping neighbors

Syntax

Release Information

Description
Options

show pim snooping neighbors

<brief | detail>
<instance instance-name>
<interface interface-name>
<logical-system logical-system-name>
<vlan-id vlan-identifier>

Command introduced in Junos OS Release 12.3 for MX Series 3D Universal Edge devices.
Command introduced in Junos OS Release 13.2 for M Series Multiservice Edge devices.
Display information about Protocol Independent Multicast (PIM) snooping neighbors.
noneDisplay detailed information.
brief | detail(Optional) Display the specified level of output.
instance instance-name(Optional) Display PIM snooping neighbor information for the

specified routing instance.

interface interface-name(Optional) Display information for the specified PIM snooping

neighbor interface.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

vlan-id vlan-identifier(Optional) Display PIM snooping neighbor information for the

specified VLAN.
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

Configuring Interface Priority for PIM Designated Router Selection

Modifying the PIM Hello Interval

PIM Snooping for VPLS

show pim neighbors on page 1705

show pim snooping neighbors on page 1724

show pim snooping neighbors detail on page 1725
show pim snooping neighbors instance on page 1726
show pim snooping neighbors interface on page 1726
show pim snooping neighbors vlan-id on page 1727
Table 144 on page 1724 lists the output fields for the show pim snooping neighbors command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1723

Interfaces Fundamentals for Routing Devices

Table 144: show pim snooping neighbors Output Fields

Field Name

Field Description

Level of Output

Instance

Routing instance for PIM snooping.

All levels

Learning-Domain

Learning domain for PIM snooping.

All levels

Interface

Router interface for which PIM snooping neighbor details are displayed.

All levels

Option

PIM snooping options available on the specified interface:

All levels

H = Hello Option Holdtime

P = Hello Option DR Priority

L = Hello Option LAN Prune Delay

G = Generation Identifier

T = Tracking Bit

Uptime

Time the neighbor has been operational since the PIM process was last initialized, in
the format dd:hh:mm:ss ago for less than a week and nwnd:hh:mm:ss ago for more
than a week.

All levels

Neighbor addr

IP address of the PIM snooping neighbor connected through the specified interface.

All levels

Address

IP address of the specified router interface.

All levels

Hello Option
Holdtime

Time for which the neighbor is available, in seconds. The range of values is
0 through 65,535.

detail

Hello Option DR
Priority

Designated router election priority. The range of values is 0 through 4294967295.

detail

NOTE: By default, every PIM interface has an equal probability (priority 1) of being
selected as the DR.
Hello Option
Generation ID

9-digit or 10-digit number used to tag hello messages.

detail

Hello Option LAN

Prune Delay

Time to wait before the neighbor receives prune messages, in the format delay nnn
ms override nnnn ms.

detail

Sample Output
show pim snooping neighbors
user@host> show pim snooping neighbors
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority, T = Tracking Bit
Instance: vpls1
Learning-Domain: vlan-id 10
Interface Option Uptime Neighbor addr
ge-1/3/1.10 HPLGT 00:43:33 20.0.110.2

1724

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

ge-1/3/3.10 HPLGT 00:43:33 20.0.110.3

ge-1/3/5.10 HPLGT 00:43:33 20.0.110.4
ge-1/3/7.10 HPLGT 00:43:33 20.0.110.5
Learning-Domain: vlan-id 20
Interface Option Uptime Neighbor addr
ge-1/3/1.20 HPLGT 00:43:33 20.0.120.2
ge-1/3/3.20 HPLGT 00:43:33 20.0.120.3
ge-1/3/5.20 HPLGT 00:43:33 20.0.120.4
ge-1/3/7.20 HPLGT 00:43:33 20.0.120.5

show pim snooping neighbors detail

user@host> show pim snooping neighbors detail
Instance: vpls1
Learning-Domain: vlan-id 10
Interface: ge-1/3/1.10
Address: 20.0.110.2
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 83 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 830908833
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Tracking is supported
Interface: ge-1/3/3.10
Address: 20.0.110.3
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 97 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 2056520742
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Tracking is supported
Interface: ge-1/3/5.10
Address: 20.0.110.4
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 81 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1152066227
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Tracking is supported
Interface: ge-1/3/7.10
Address: 20.0.110.5
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 96 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1113200338
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Tracking is supported
Learning-Domain: vlan-id 20
Interface: ge-1/3/1.20
Address: 20.0.120.2
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 81 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 963205167

Copyright 2014, Juniper Networks, Inc.

1725

Interfaces Fundamentals for Routing Devices

Hello Option LAN Prune Delay: delay 500 ms override 2000 ms

Tracking is supported
Interface: ge-1/3/3.20
Address: 20.0.120.3
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 104 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 166921538
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Tracking is supported
Interface: ge-1/3/5.20
Address: 20.0.120.4
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 88 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 789422835
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Tracking is supported
Interface: ge-1/3/7.20
Address: 20.0.120.5
Uptime: 00:44:51
Hello Option Holdtime: 105 seconds 88 remaining
Hello Option DR Priority: 1
Hello Option Generation ID: 1563649680
Hello Option LAN Prune Delay: delay 500 ms override 2000 ms
Tracking is supported

show pim snooping neighbors instance

user@host> show pim snooping neighbors instance vpls1
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority, T = Tracking Bit
Instance: vpls1
Learning-Domain: vlan-id 10
Interface Option Uptime Neighbor addr
ge-1/3/1.10 HPLGT 00:46:03 20.0.110.2
ge-1/3/3.10 HPLGT 00:46:03 20.0.110.3
ge-1/3/5.10 HPLGT 00:46:03 20.0.110.4
ge-1/3/7.10 HPLGT 00:46:03 20.0.110.5

Learning-Domain: vlan-id 20
Interface Option Uptime Neighbor addr
ge-1/3/1.20 HPLGT 00:46:03 20.0.120.2
ge-1/3/3.20 HPLGT 00:46:03 20.0.120.3
ge-1/3/5.20 HPLGT 00:46:03 20.0.120.4
ge-1/3/7.20 HPLGT 00:46:03 20.0.120.5

show pim snooping neighbors interface

user@host> show pim snooping neighbors interface ge-1/3/1.20
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority, T = Tracking Bit

1726

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Instance: vpls1
Learning-Domain: vlan-id 10
Learning-Domain: vlan-id 20
Interface Option Uptime Neighbor addr
ge-1/3/1.20 HPLGT 00:48:04 20.0.120.2

show pim snooping neighbors vlan-id

user@host> show pim snooping neighbors vlan-id 10
B = Bidirectional Capable, G = Generation Identifier,
H = Hello Option Holdtime, L = Hello Option LAN Prune Delay,
P = Hello Option DR Priority, T = Tracking Bit
Instance: vpls1
Learning-Domain: vlan-id 10
Interface Option Uptime Neighbor addr
ge-1/3/1.10 HPLGT 00:49:12 20.0.110.2
ge-1/3/3.10 HPLGT 00:49:12 20.0.110.3
ge-1/3/5.10 HPLGT 00:49:12 20.0.110.4
ge-1/3/7.10 HPLGT 00:49:12 20.0.110.5

Copyright 2014, Juniper Networks, Inc.

1727

Interfaces Fundamentals for Routing Devices

show pim snooping statistics

Syntax

Release Information

Description
Options

show pim snooping statistics

<instance instance-name>
<interface interface-name>
<logical-system logical-system-name>
<vlan-id vlan-id>

Command introduced in Junos OS Release 12.3 for MX Series 3D Universal Edge devices.
Command introduced in Junos OS Release 13.2 for M Series Multiservice Edge devices.
Display Protocol Independent Multicast (PIM) snooping statistics.
noneDisplay PIM statistics.
instance instance-name(Optional) Display statistics for a specific routing instance

enabled by Protocol Independent Multicast (PIM) snooping.

interface interface-name(Optional) Display statistics about the specified interface for

PIM snooping.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

vlan-id vlan-identifier(Optional) Display PIM snooping statistics information for the

specified VLAN.
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

PIM Snooping for VPLS

clear pim snooping statistics on page 1547

show pim snooping statistics on page 1729

show pim snooping statistics instance on page 1730
show pim snooping statistics interface on page 1731
show pim snooping statistics vlan-id on page 1731
Table 145 on page 1728 lists the output fields for the show pim snooping statistics command.
Output fields are listed in the approximate order in which they appear.

Table 145: show pim snooping statistics Output Fields

Field Name

Field Description

Level of Output

Instance

Routing instance for PIM snooping.

All levels

Learning-Domain

Learning domain for PIM snooping.

All levels

Tx J/P messages

Total number of transmitted join/prune packets.

All levels

1728

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 145: show pim snooping statistics Output Fields (continued)

Field Name

Field Description

Level of Output

RX J/P messages

Total number of received join/prune packets.

All levels

Rx J/P messages -seen

Number of join/prune packets seen but not received on the upstream interface.

All levels

Rx J/P messages -received

Number of join/prune packets received on the downstream interface.

All levels

Rx Hello messages

Total number of received hello packets.

All levels

Rx Version
Unknown

Number of packets received with an unknown version number.

All levels

Rx Neighbor
Unknown

Number of packets received from an unknown neighbor.

All levels

Rx Upstream
Neighbor Unknown

Number of packets received with unknown upstream neighbor information.

All levels

Rx Bad Length

Number of packets received containing incorrect length information.

All levels

Rx J/P Busy Drop

Number of join/prune packets dropped while the router is busy.

All levels

Rx J/P Group
Aggregate 0

Number of join/prune packets received containing the aggregate group information.

All levels

Rx Malformed
Packet

Number of malformed packets received.

All levels

Rx No PIM Interface

Number of packets received without the interface information.

All levels

Rx No Upstream
Neighbor

Number of packets received without upstream neighbor information.

All levels

Rx Unknown Hello
Option

Number of hello packets received with unknown options.

All levels

Sample Output
show pim snooping statistics
user@host> show pim snooping statistics
Instance: vpls1
Learning-Domain: vlan-id 10
Tx
RX
Rx
Rx
Rx

J/P messages 0
J/P messages 8
J/P messages -- seen 0
J/P messages -- received 8
Hello messages 37

Copyright 2014, Juniper Networks, Inc.

1729

Interfaces Fundamentals for Routing Devices

Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx

Version Unknown 0
Neighbor Unknown 0
Upstream Neighbor Unknown 0
Bad Length 0
J/P Busy Drop 0
J/P Group Aggregate 0
Malformed Packet 0
No PIM Interface 0
No Upstream Neighbor 0
Bad Length 0
Neighbor Unknown 0
Unknown Hello Option 0
Malformed Packet 0

Learning-Domain: vlan-id 20
Tx
RX
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx

J/P messages 0
J/P messages 2
J/P messages -- seen 0
J/P messages -- received 2
Hello messages 39
Version Unknown 0
Neighbor Unknown 0
Upstream Neighbor Unknown 0
Bad Length 0
J/P Busy Drop 0
J/P Group Aggregate 0
Malformed Packet 0
No PIM Interface 0
No Upstream Neighbor 0
Bad Length 0
Neighbor Unknown 0
Unknown Hello Option 0
Malformed Packet 0

show pim snooping statistics instance

user@host> show pim snooping statistics instance vpls1
Instance: vpls1
Learning-Domain: vlan-id 10
Tx
RX
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx

1730

J/P messages 0
J/P messages 9
J/P messages -- seen 0
J/P messages -- received 9
Hello messages 45
Version Unknown 0
Neighbor Unknown 0
Upstream Neighbor Unknown 0
Bad Length 0
J/P Busy Drop 0
J/P Group Aggregate 0
Malformed Packet 0
No PIM Interface 0
No Upstream Neighbor 0
Bad Length 0
Neighbor Unknown 0
Unknown Hello Option 0
Malformed Packet 0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Learning-Domain: vlan-id 20
Tx
RX
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx

J/P messages 0
J/P messages 3
J/P messages -- seen 0
J/P messages -- received 3
Hello messages 47
Version Unknown 0
Neighbor Unknown 0
Upstream Neighbor Unknown 0
Bad Length 0
J/P Busy Drop 0
J/P Group Aggregate 0
Malformed Packet 0
No PIM Interface 0
No Upstream Neighbor 0
Bad Length 0
Neighbor Unknown 0
Unknown Hello Option 0
Malformed Packet 0

show pim snooping statistics interface

user@host> show pim snooping statistics interface ge-1/3/1.20
Instance: vpls1
Learning-Domain: vlan-id 10
Learning-Domain: vlan-id 20
PIM Interface statistics for ge-1/3/1.20
Tx J/P messages 0
RX J/P messages 0
Rx J/P messages -- seen 0
Rx J/P messages -- received 0
Rx Hello messages 13
Rx Version Unknown 0
Rx Neighbor Unknown 0
Rx Upstream Neighbor Unknown 0
Rx Bad Length 0
Rx J/P Busy Drop 0
Rx J/P Group Aggregate 0
Rx Malformed Packet 0

show pim snooping statistics vlan-id

user@host> show pim snooping statistics vlan-id 10
Instance: vpls1
Learning-Domain: vlan-id 10
Tx
RX
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx
Rx

J/P messages 0
J/P messages 11
J/P messages -- seen 0
J/P messages -- received 11
Hello messages 64
Version Unknown 0
Neighbor Unknown 0
Upstream Neighbor Unknown 0
Bad Length 0
J/P Busy Drop 0
J/P Group Aggregate 0
Malformed Packet 0

Copyright 2014, Juniper Networks, Inc.

1731

Interfaces Fundamentals for Routing Devices

Rx
Rx
Rx
Rx

1732

No PIM Interface 0
No Upstream Neighbor 0
Bad Length 0
Neighbor Unknown 0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show pim source

List of Syntax

Syntax

Syntax on page 1733

Syntax (EX Series Switch and the QFX Series) on page 1733
show pim source
<brief | detail>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<source-prefix>

Syntax (EX Series

Switch and the QFX
Series)

show pim source

<brief | detail>
<inet | inet6>
<instance instance-name>
<source-prefix>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Options

Display information about the Protocol Independent Multicast (PIM) source reverse path
forwarding (RPF) state.
noneDisplay standard information about the PIM RPF state for all supported family

addresses for all routing instances.

brief | detail(Optional) Display the specified level of output.
inet | inet6(Optional) Display information for IPv4 or IPv6 family addresses, respectively.
instance instance-name(Optional) Display information about the RPF state for a specific

PIM-enabled routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

source-prefix(Optional) Display the state for source RPF states in the given range.

Required Privilege
Level
List of Sample Output

Output Fields

view

show pim source on page 1734

show pim source brief on page 1734
show pim source detail on page 1734
show pim source (Egress Node with Multipoint LDP Inband Signaling for
Point-to-Multipoint LSPs) on page 1735
Table 146 on page 1734 describes the output fields for the show pim source command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1733

Interfaces Fundamentals for Routing Devices

Table 146: show pim source Output Fields

Field Name

Field Description

Instance

Name of the routing instance.

Source

Address of the source or reverse path.

Prefix/length

Prefix and prefix length for the route used to reach the RPF address.

Upstream Protocol

Protocol toward the source address.

Upstream interface

RPF interface toward the source address.

A pseudo multipoint LDP (M-LDP) interface appears on egress nodes in M-LDP
point-to-multipoint LSPs with inband signaling.

Upstream Neighbor

Address of the RPF neighbor used to reach the source address.

The multipoint LDP (M-LDP) root appears on egress nodes in M-LDP
point-to-multipoint LSPs with inband signaling.

Sample Output
show pim source
user@host> show pim source
Instance: PIM.master Family: INET
Source 10.255.14.144
Prefix 10.255.14.144/32
Upstream interface Local
Upstream neighbor Local
Source 10.255.70.15
Prefix 10.255.70.15/32
Upstream interface so-1/0/0.0
Upstream neighbor 10.111.10.2
Instance: PIM.master Family: INET6

show pim source brief

The output for the show pim source brief command is identical to that for the show pim
source command. For sample output, see show pim source on page 1734.
show pim source detail
user@host> show pim source detail
Instance: PIM.master Family: INET
Source 10.255.14.144
Prefix 10.255.14.144/32
Upstream interface Local
Upstream neighbor Local
Active groups:228.0.0.0
239.1.1.1

1734

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

239.1.1.1
Source 10.255.70.15
Prefix 10.255.70.15/32
Upstream interface so-1/0/0.0
Upstream neighbor 10.111.10.2
Active groups:239.1.1.1
Instance: PIM.master Family: INET6

show pim source (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show pim source
Instance: PIM.master Family: INET
Source 1.1.1.1
Prefix 1.1.1.1/32
Upstream interface Local
Upstream neighbor Local
Source 1.2.7.7
Prefix 1.2.7.0/24
Upstream protocol MLDP
Upstream interface Pseudo MLDP
Upstream neighbor MLDP LSP root <1.1.1.2>
Source 192.168.219.11
Prefix 192.168.219.0/28
Upstream protocol MLDP
Upstream interface Pseudo MLDP
Upstream neighbor MLDP LSP root <1.1.1.2>
Instance: PIM.master Family: INET6
Source abcd::1:2:7:7
Prefix abcd::1:2:7:0/120
Upstream protocol MLDP
Upstream interface Pseudo MLDP
Upstream neighbor MLDP LSP root <1.1.1.2>

Copyright 2014, Juniper Networks, Inc.

1735

Interfaces Fundamentals for Routing Devices

show pim statistics

List of Syntax

Syntax

Syntax on page 1736

Syntax (EX Series Switch and the QFX Series) on page 1736
show pim statistics
<inet |inet6)>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and the QFX
Series)

show pim statistics

<inet |inet6)>
<instance instance-name>
<interface interface-name>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Support for bidirectional PIM added in Junos OS Release 12.1.

Description
Options

Display Protocol Independent Multicast (PIM) statistics.

noneDisplay PIM statistics.
inet | inet6(Optional) Display IPv4 or IPv6 PIM statistics, respectively.
instance instance-name(Optional) Display statistics for a specific routing instance

enabled by Protocol Independent Multicast (PIM).

interface interface-name(Optional) Display statistics about the specified interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

1736

view

clear pim statistics on page 1549

show pim statistics on page 1743

show pim statistics inet interface <interface-name> on page 1745
show pim statistics inet6 interface <interface-name> on page 1745
show pim statistics instance <instance-name> on page 1746
show pim statistics interface <interface-name> on page 1747
Table 147 on page 1737 describes the output fields for the show pim statistics command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 147: show pim statistics Output Fields

Field Name

Field Description

Instance

Name of the routing instance.

This field only appears if you specify an interface, for example:

Family

inet interface interface-name

inet6 interface interface-name

interface interface-name

Output is for IPv4 or IPv6 PIM statistics. INET indicates IPv4

statistics, and INET6 indicates IPv6 statistics.
This field only appears if you specify an interface, for example:

inet interface interface-name

inet6 interface interface-name

interface interface-name

PIM statistics

PIM statistics for all interfaces or for the specified interface.

PIM message type

Message type for which statistics are displayed.

Received

Number of received statistics.

Sent

Number of messages sent of a certain type.

Rx errors

Number of received packets that contained errors.

V2 Hello

PIM version 2 hello packets.

V2 Register

PIM version 2 register packets.

V2 Register Stop

PIM version 2 register stop packets.

V2 Join Prune

PIM version 2 join and prune packets.

V2 Bootstrap

PIM version 2 bootstrap packets.

V2 Assert

PIM version 2 assert packets.

V2 Graft

PIM version 2 graft packets.

V2 Graft Ack

PIM version 2 graft acknowledgment packets.

V2 Candidate RP

PIM version 2 candidate RP packets.

V2 State Refresh

PIM version 2 control messages related to PIM dense mode

(PIM-DM) state refresh.
State refresh is an extension to PIM-DM. It not supported in Junos
OS.

Copyright 2014, Juniper Networks, Inc.

1737

Interfaces Fundamentals for Routing Devices

Table 147: show pim statistics Output Fields (continued)

1738

Field Name

Field Description

V2 DF Election

PIM version 2 send and receive messages associated with

bidirectional PIM designated forwarder election.

V1 Query

PIM version 1 query packets.

V1 Register

PIM version 1 register packets.

V1 Register Stop

PIM version 1 register stop packets.

V1 Join Prune

PIM version 1 join and prune packets.

V1 RP Reachability

PIM version 1 RP reachability packets.

V1 Assert

PIM version 1 assert packets.

V1 Graft

PIM version 1 graft packets.

V1 Graft Ack

PIM version 1 graft acknowledgment packets.

AutoRP Announce

Auto-RP announce packets.

AutoRP Mapping

Auto-RP mapping packets.

AutoRP Unknown type

Auto-RP packets with an unknown type.

Anycast Register

Auto-RP announce packets.

Anycast Register Stop

Auto-RP announce packets.

Global Statistics

Summary of PIM statistics for all interfaces.

Hello dropped on neighbor

policy

Number of hello packets dropped because of a configured neighbor

policy.

Unknown type

Number of PIM control packets received with an unknown type.

V1 Unknown type

Number of PIM version 1 control packets received with an unknown

type.

Unknown Version

Number of PIM control packets received with an unknown version.

The version is not version 1 or version 2.

Neighbor unknown

Number of PIM control packets received (excluding PIM hello)

without first receiving the hello packet.

Bad Length

Number of PIM control packets received for which the packet size
does not match the PIM length field in the packet.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 147: show pim statistics Output Fields (continued)

Field Name

Field Description

Bad Checksum

Number of PIM control packets received for which the calculated

checksum does not match the checksum field in the packet.

Bad Receive If

Number of PIM control packets received on an interface that does

not have PIM configured.

Rx Bad Data

Number of PIM control packets received that contain data for TCP
Bad register packets.

Rx Intf disabled

Number of PIM control packets received on an interface that has

PIM disabled.

Rx V1 Require V2

Number of PIM version 1 control packets received on an interface

configured for PIM version 2.

Rx V2 Require V1

Number of PIM version 2 control packets received on an interface

configured for PIM version 1.

Rx Register not RP

Number of PIM register packets received when the routing device

is not the RP for the group.

Rx Register no route

Number of PIM register packets received when the RP does not

have a unicast route back to the source.

Rx Register no decap if

Number of PIM register packets received when the RP does not

have a de-encapsulation interface.

Null Register Timeout

Number of NULL register timeout packets.

RP Filtered Source

Number of PIM packets received when the routing device has a

source address filter configured for the RP.

Rx Unknown Reg Stop

Number of register stop messages received with an unknown type.

Rx Join/Prune no state

Number of join and prune messages received for which the routing
device has no state.

Rx Join/Prune on upstream
if

Number of join and prune messages received on the interface used

to reach the upstream routing device, toward the RP.

Rx Join/Prune for invalid

group

Number of join or prune messages received for invalid multicast

group addresses.

Rx Join/Prune messages
dropped

Number of join and prune messages received and dropped.

Rx sparse join for dense

group

Number of PIM sparse mode join messages received for a group

that is configured for dense mode.

Copyright 2014, Juniper Networks, Inc.

1739

Interfaces Fundamentals for Routing Devices

Table 147: show pim statistics Output Fields (continued)

1740

Field Name

Field Description

Rx Graft/Graft Ack no state

Number of graft and graft acknowledgment messages received for

which the router or switch has no state.

Rx Graft on upstream if

Number of graft messages received on the interface used to reach

the upstream routing device, toward the RP.

Rx CRP not BSR

Number of BSR messages received in which the PIM message type

is Candidate-RP-Advertisement, not Bootstrap.

Rx BSR when BSR

Number of BSR messages received in which the PIM message type

is Bootstrap.

Rx BSR not RPF if

Number of BSR messages received on an interface that is not the

RPF interface.

Rx unknown hello opt

Number of PIM hello packets received with options that Junos OS

does not support.

Rx data no state

Number of PIM control packets received for which the routing device
has no state for the data type.

Rx RP no state

Number of PIM control packets received for which the routing device
has no state for the RP.

Rx aggregate

Number of PIM aggregate MDT packets received.

Rx malformed packet

Number of PIM control packets received with a malformed IP unicast

or multicast address family.

No RP

Number of PIM control packets received with no RP address.

No register encap if

Number of PIM register packets received when the first-hop routing

device does not have an encapsulation interface.

No route upstream

Number of PIM control packets received when the routing device

does not have a unicast route to the the interface used to reach the
upstream routing device, toward the RP.

Nexthop Unusable

Number of PIM control packets with an unusable nexthop. A path

can be unusable if the route is hidden or the link is down.

RP mismatch

Number of PIM control packets received for which the routing device
has an RP mismatch.

RP mode mismatch

RP mode (sparse or bidirectional) mismatches encountered when

processing join and prune messages.

RPF neighbor unknown

Number of PIM control packets received for which the routing device
has an unknown RPF neighbor for the source.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 147: show pim statistics Output Fields (continued)

Field Name

Field Description

Rx Joins/Prunes filtered

The number of join and prune messages filtered because of

configured route filters and source address filters.

Tx Joins/Prunes filtered

The number of join and prune messages filtered because of

configured route filters and source address filters.

Embedded-RP invalid addr

Number of packets received with an invalid embedded RP address

in PIM join messages and other types of messages sent between
routing domains.

Embedded-RP limit exceed

Number of times the limit configured with the maximum-rps

statement is exceeded. The maximum-rps statement limits the
number of embedded RPs created in a specific routing instance.
The range is from 1 through 500. The default is 100.

Embedded-RP added

Number of packets in which the embedded RP for IPv6 is added.

The following receive events trigger extraction of an IPv6 embedded
RP address on the routing device:

Multicast Listener Discovery (MLD) report for an embedded RP

multicast group address

PIM join message with an embedded RP multicast group address

Static embedded RP multicast group address associated with

an interface

Packets sent to an embedded RP multicast group address

received on the DR

An embedded RP node discovered through these receive events is

added if it does not already exist on the routing platform.
Embedded-RP removed

Number of packets in which the embedded RP for IPv6 is removed.

The embedded RP is removed whenever all PIM join states using
this RP are removed or the configuration changes to remove the
embedded RP feature.

Rx Register msgs filtering

drop

Number of received register messages dropped because of a filter

configured for PIM register messages.

Tx Register msgs filtering

drop

Number of register messages dropped because of a filter configured

for PIM register messages.

Rx Bidir Join/Prune on
non-Bidir if

Error counter for join and prune messages received on

non-bidirectional PIM interfaces.

Rx Bidir Join/Prune on
non-DF if

Error counter for join and prune messages received on

non-designated forwarder interfaces.

V4 (S,G) Maximum

Maximum number of (S,G) IPv4 multicast routes accepted for the

VPN routing and forwarding (VRF) routing instance. If this number
is met, additional (S,G) entries are not accepted.

Copyright 2014, Juniper Networks, Inc.

1741

Interfaces Fundamentals for Routing Devices

Table 147: show pim statistics Output Fields (continued)

1742

Field Name

Field Description

V4 (S,G) Accepted

Number of accepted (S,G) IPv4 multicast routes.

V4 (S,G) Threshold

Threshold at which a warning message is logged (percentage of

the maximum number of (S,G) IPv4 multicast routes accepted by
the device).

V4 (S,G) Log Interval

Time (in seconds) between consecutive log messages.

V6 (S,G) Maximum

Maximum number of (S,G) IPv6 multicast routes accepted for the

VPN routing and forwarding (VRF) routing instance. If this number
is met, additional (S,G) entries are not accepted.

V6 (S,G) Accepted

Number of accepted (S,G) IPv6 multicast routes.

V6 (S,G) Threshold

Threshold at which a warning message is logged (percentage of

the maximum number of (S,G) IPv6 multicast routes accepted by
the device).

V6 (S,G) Log Interval

Time (in seconds) between consecutive log messages.

V4 (grp-prefix, RP)
Maximum

Maximum number of group-to-rendezvous point (RP) IPv4 multicast

mappings accepted for the VRF routing instance. If this number is
met, additional mappings are not accepted.

V4 (grp-prefix, RP)
Accepted

Number of accepted group-to-RP IPv4 multicast mappings.

V4 (grp-prefix, RP)
Threshold

Threshold at which a warning message is logged (percentage of

the maximum number of group-to-RP IPv4 multicast mappings
accepted by the device).

V4 (grp-prefix, RP) Log

Interval

Time (in seconds) between consecutive log messages.

V6 (grp-prefix, RP)
Maximum

Maximum number of group-to RP IPv6 multicast mappings

accepted for the VRF routing instance. If this number is met,
additional mappings are not accepted.

V6 (grp-prefix, RP)
Accepted

Number of accepted group-to-RP IPv6 multicast mappings.

V6 (grp-prefix, RP)
Threshold

Threshold at which a warning message is logged (percentage of

the maximum number of group-to-RP IPv6 multicast mappings
accepted by the device).

V6 (grp-prefix, RP) Log

Interval

Time (in seconds) between consecutive log messages.

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Table 147: show pim statistics Output Fields (continued)

Field Name

Field Description

V4 Register Maximum

Maximum number of IPv4 PIM registers accepted for the VRF routing
instance. If this number is met, additional PIM registers are not
accepted.
You configure the register limits on the RP.

V4 Register Accepted

Number of accepted IPv4 PIM registers.

V4 Register Threshold

Threshold at which a warning message is logged (percentage of

the maximum number of IPv4 PIM registers accepted by the device).

V4 Register Log Interval

Time (in seconds) between consecutive log messages.

V6 Register Maximum

Maximum number of IPv6 PIM registers accepted for the VRF routing
instance. If this number is met, additional PIM registers are not
accepted.
You configure the register limits on the RP.

V6 Register Accepted

Number of accepted IPv6 PIM registers.

V6 Register Threshold

Threshold at which a warning message is logged (percentage of

the maximum number of IPv6 PIM registers accepted by the device).

V6 Register Log Interval

Time (in seconds) between consecutive log messages.

(*,G) Join drop due to SSM

range check

PIM join messages that are dropped because the multicast

addresses are outside of the SSM address range of 232.0.0.0
through 232.255.255.255. You can extend the accepted SSM address
range by configuring the ssm-groups statement.

Sample Output
show pim statistics
user@host> show pim statistics
PIM Message type
Received
V2 Hello
15
V2 Register
0
V2 Register Stop
483
V2 Join Prune
18
V2 Bootstrap
0
V2 Assert
0
V2 Graft
0
V2 Graft Ack
0
V2 Candidate RP
0
V2 State Refresh
0
V2 DF Election
0
V1 Query
0
V1 Register
0
V1 Register Stop
0
V1 Join Prune
0

Copyright 2014, Juniper Networks, Inc.

Sent
32
362
0
518
0
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

1743

Interfaces Fundamentals for Routing Devices

V1 RP Reachability
V1 Assert
V1 Graft
V1 Graft Ack
AutoRP Announce
AutoRP Mapping
AutoRP Unknown type
Anycast Register
Anycast Register Stop

0
0
0
0
0
0
0
0
0

0
0
0
0
0
0

0
0
0
0
0
0

0
0

0
0

Global Statistics
Hello dropped on neighbor policy
Unknown type
V1 Unknown type
Unknown Version
ipv4 BSR pkt drop due to excessive rate
ipv6 BSR pkt drop due to excessive rate
Neighbor unknown
Bad Length
Bad Checksum
Bad Receive If
Rx Bad Data
Rx Intf disabled
Rx V1 Require V2
Rx V2 Require V1
Rx Register not RP
Rx Register no route
Rx Register no decap if
Null Register Timeout
RP Filtered Source
Rx Unknown Reg Stop
Rx Join/Prune no state
Rx Join/Prune on upstream if
Rx Join/Prune for invalid group
Rx Join/Prune messages dropped
Rx sparse join for dense group
Rx Graft/Graft Ack no state
Rx Graft on upstream if
Rx CRP not BSR
Rx BSR when BSR
Rx BSR not RPF if
Rx unknown hello opt
Rx data no state
Rx RP no state
Rx aggregate
Rx malformed packet
Rx illegal TTL
Rx illegal destination address
No RP
No register encap if
No route upstream
Nexthop Unusable
RP mismatch
RP mode mismatch
RPF neighbor unknown
Rx Joins/Prunes filtered
Tx Joins/Prunes filtered
Embedded-RP invalid addr
Embedded-RP limit exceed
Embedded-RP added

1744

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Embedded-RP removed
Rx Register msgs filtering drop
Tx Register msgs filtering drop
Rx Bidir Join/Prune on non-Bidir if
Rx Bidir Join/Prune on non-DF if
(*,G) Join drop due to SSM range check

0
0
0
0
0
0

Sample Output
show pim statistics inet interface <interface-name>
user@host> show pim statistics inet interface ge-0/3/0.0
Instance: PIM.master Family: INET
PIM Interface statistics for ge-0/3/0.0
PIM Message type
V2 Hello
V2 Register
V2 Register Stop
V2 Join Prune
V2 Bootstrap
V2 Assert
V2 Graft
V2 Graft Ack
V2 Candidate RP
V1 Query
V1 Register
V1 Register Stop
V1 Join Prune
V1 RP Reachability
V1 Assert
V1 Graft
V1 Graft Ack
AutoRP Announce
AutoRP Mapping
AutoRP Unknown type
Anycast Register
Anycast Register Stop

Received
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Sent
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

0
0

0
0

Sample Output
show pim statistics inet6 interface <interface-name>
user@host> show pim statistics inet6 interface ge-0/3/0.0
Instance: PIM.master Family: INET6
PIM Interface statistics for ge-0/3/0.0
PIM Message type
V2 Hello
V2 Register
V2 Register Stop
V2 Join Prune
V2 Bootstrap
V2 Assert
V2 Graft
V2 Graft Ack
V2 Candidate RP
Anycast Register
Anycast Register Stop

Copyright 2014, Juniper Networks, Inc.

Received
0
0
0
0
0
0
0
0
0
0
0

Sent
4
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0

1745

Interfaces Fundamentals for Routing Devices

show pim statistics instance <instance-name>

user@host> show pim statistics instance VPN-A
PIM Message type
Received
Sent Rx errors
V2 Hello
31
37
0
V2 Register
0
0
0
V2 Register Stop
0
0
0
V2 Join Prune
0
16
0
V2 Bootstrap
0
0
0
V2 Assert
0
0
0
V2 Graft
0
0
0
V2 Graft Ack
0
0
0
V2 Candidate RP
0
0
0
V2 State Refresh
0
0
0
V2 DF Election
0
0
0
V1 Query
0
0
0
V1 Register
0
0
0
V1 Register Stop
0
0
0
V1 Join Prune
0
0
0
V1 RP Reachability
0
0
0
V1 Assert
0
0
0
V1 Graft
0
0
0
V1 Graft Ack
0
0
0
AutoRP Announce
0
0
0
AutoRP Mapping
0
0
0
AutoRP Unknown type
0
Anycast Register
0
0
0
Anycast Register Stop
0
0
0
Global Statistics
Hello dropped on neighbor policy
Unknown type
V1 Unknown type
Unknown Version
Neighbor unknown
Bad Length
Bad Checksum
Bad Receive If
Rx Bad Data
Rx Intf disabled
Rx V1 Require V2
Rx V2 Require V1
Rx Register not RP
Rx Register no route
Rx Register no decap if
Null Register Timeout
RP Filtered Source
Rx Unknown Reg Stop
Rx Join/Prune no state
Rx Join/Prune on upstream if
Rx Join/Prune for invalid group
Rx Join/Prune messages dropped
Rx sparse join for dense group
Rx Graft/Graft Ack no state
Rx Graft on upstream if
Rx CRP not BSR
Rx BSR when BSR
Rx BSR not RPF if
Rx unknown hello opt
Rx data no state

1746

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

Rx RP no state
Rx aggregate
Rx malformed packet
Rx illegal TTL
Rx illegal destination address
No RP
No register encap if
No route upstream
Nexthop Unusable
RP mismatch
RP mode mismatch
RPF neighbor unknown
Rx Joins/Prunes filtered
Tx Joins/Prunes filtered
Embedded-RP invalid addr
Embedded-RP limit exceed
Embedded-RP added
Embedded-RP removed
Rx Register msgs filtering drop
Tx Register msgs filtering drop
Rx Bidir Join/Prune on non-Bidir if
Rx Bidir Join/Prune on non-DF if
V4 (S,G) Maximum
V4 (S,G) Accepted
V4 (S,G) Threshold
V4 (S,G) Log Interval
V6 (S,G) Maximum
V6 (S,G) Accepted
V6 (S,G) Threshold
V6 (S,G) Log Interval
V4 (grp-prefix, RP) Maximum
V4 (grp-prefix, RP) Accepted
V4 (grp-prefix, RP) Threshold
V4 (grp-prefix, RP) Log Interval
V6 (grp-prefix, RP) Maximum
V6 (grp-prefix, RP) Accepted
V6 (grp-prefix, RP) Threshold
V6 (grp-prefix, RP) Log Interval
V4 Register Maximum
V4 Register Accepted
V4 Register Threshold
V4 Register Log Interval
V6 Register Maximum
V6 Register Accepted
V6 Register Threshold
V6 Register Log Interval
(*,G) Join drop due to SSM range check

0
0
0
0
0
0
0
28
0
0
0
0
0
0
0
0
0
0
0
0
0
0
10
9
80
80
8
8
50
100
100
5
80
10
20
0
90
20
100
10
80
10
20
0
90
20
0

Sample Output
show pim statistics interface <interface-name>
user@host> show pim statistics interface ge-0/3/0.0
Instance: PIM.master Family: INET
PIM Interface statistics for ge-0/3/0.0
PIM Message type
V2 Hello
V2 Register
V2 Register Stop

Copyright 2014, Juniper Networks, Inc.

Received
0
0
0

Sent
3
0
0

Rx errors
0
0
0

1747

Interfaces Fundamentals for Routing Devices

V2 Join Prune
V2 Bootstrap
V2 Assert
V2 Graft
V2 Graft Ack
V2 Candidate RP
V1 Query
V1 Register
V1 Register Stop
V1 Join Prune
V1 RP Reachability
V1 Assert
V1 Graft
V1 Graft Ack
AutoRP Announce
AutoRP Mapping
AutoRP Unknown type
Anycast Register
Anycast Register Stop

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

0
0

0
0

Sent
3
0
0
0
0
0
0
0
0
0
0

Rx errors
0
0
0
0
0
0
0
0
0
0
0

Instance: PIM.master Family: INET6

PIM Interface statistics for ge-0/3/0.0
PIM Message type
V2 Hello
V2 Register
V2 Register Stop
V2 Join Prune
V2 Bootstrap
V2 Assert
V2 Graft
V2 Graft Ack
V2 Candidate RP
Anycast Register
Anycast Register Stop

1748

Received
0
0
0
0
0
0
0
0
0
0
0

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

show sap listen

Syntax

Release Information
Description

Options

show sap listen

<brief | detail>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display the addresses that the router is listening to in order to receive multicast Session
Announcement Protocol (SAP) session announcements.
noneDisplay standard information about the addresses that the router is listening to

in order to receive multicast SAP session announcements.

brief | detail(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show sap listen on page 1749

show sap listen brief on page 1749
show sap listen detail on page 1750
Table 148 on page 1749 describes the output fields for the show sap listen command. Output
fields are listed in the approximate order in which they appear.

Table 148: show sap listen Output Fields

Field Name

Field Description

Group address

Address of the group that the local router is listening to for SAP messages.

Port

UDP port number used for SAP.

Sample Output
show sap listen
user@host> show sap listen
Group address
Port
224.2.127.254
9875
239.255.255.255 9875

show sap listen brief

The output for the show sap listen brief command is identical to that for the show sap
listen command. For sample output, see show sap listen on page 1749.

Copyright 2014, Juniper Networks, Inc.

1749

Interfaces Fundamentals for Routing Devices

show sap listen detail

The output for the show sap listen detail command is identical to that for the show sap
listen command. For sample output, see show sap listen on page 1749.

1750

Copyright 2014, Juniper Networks, Inc.

Chapter 19: IP Multicast Operational Commands

test msdp
Syntax

Release Information

Description
Options

test msdp (dependent-peers prefix | rpf-peer originator)

<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.
Find Multicast Source Discovery Protocol (MSDP) peers.
dependent-peers prefixFind downstream dependent MSDP peers.
rpf-peer originatorFind the MSDP reverse-path-forwarding (RPF) peer for the originator.
instance instance-name(Optional) Find MDSP peers for the specified routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

test msdp dependent-peers on page 1751

When you enter this command, you are provided feedback on the status of your request.

Sample Output
test msdp dependent-peers
user@host> test msdp dependent-peers 10.0.0.1/24

Copyright 2014, Juniper Networks, Inc.

1751

Interfaces Fundamentals for Routing Devices

1752

Copyright 2014, Juniper Networks, Inc.

CHAPTER 20

IPv6 Operational Commands

clear ipv6 neighbors

clear ipv6 router-advertisement

show ipv6 neighbors

show ipv6 router-advertisement

Copyright 2014, Juniper Networks, Inc.

1753

Interfaces Fundamentals for Routing Devices

clear ipv6 neighbors

Syntax

Release Information

Description
Options

clear ipv6 neighbors

<all | host hostname>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.3 for EX Series switches.
Command introduced in Junos OS Release 12.2 for the QFX Series.
Clear IPv6 neighbor cache information.
noneClear all IPv6 neighbor cache information.
all(Optional) Clear all IPv6 neighbor cache information.
host hostname(Optional) Clear the information for the specified IPv6 neighbors.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

show ipv6 neighbors on page 1756

clear ipv6 neighbors on page 1754

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ipv6 neighbors
user@host> clear ipv6 neighbors

1754

Copyright 2014, Juniper Networks, Inc.

Chapter 20: IPv6 Operational Commands

clear ipv6 router-advertisement

Syntax

Release Information
Description
Options

clear ipv6 router-advertisement

<interface interface>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Clear IPv6 router advertisement counters.
noneClear IPv6 router advertisement counters for all interfaces.
interface interface(Optional) Clear IPv6 router advertisement counters for the specified

interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

show ipv6 router-advertisement on page 1758

clear ipv6 router-advertisement on page 1755

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ipv6 router-advertisement
user@host> clear ipv6 router-advertisement

Copyright 2014, Juniper Networks, Inc.

1755

Interfaces Fundamentals for Routing Devices

show ipv6 neighbors

Syntax
Release Information

Description
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

show ipv6 neighbors

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.3 for EX Series switches.
Command introduced in Junos OS Release 12.2 for the QFX Series.
Display information about the IPv6 neighbor cache.
This command has no options.
view

clear ipv6 neighbors on page 1754

show ipv6 neighbors on page 1756

Table 149 on page 1756 describes the output fields for the show ipv6 neighbors command.
Output fields are listed in the approximate order in which they appear.

Table 149: show ipv6 neighbors Output Fields

Field Name

Field Description

IPv6 Address

Name of the IPv6 interface.

Linklayer Address

Link-layer address.

State

State of the link: up, down, incomplete, reachable, stale, or

unreachable.

Exp

Number of seconds until the entry expires.

Rtr

Whether the neighbor is a routing device: yes or no.

Secure

Whether this entry was created using the Secure Neighbor Discovery
(SEND) protocol: yes or no.

Interface

Name of the interface.

Sample Output
show ipv6 neighbors
user@host> show ipv6 neighbors
IPv6 Address
Linklayer Address
Interface
2001:db8:0:1:2a0:a514:0:24c 00:05:85:8f:c8:bd
fe-1/2/0.1

1756

State

Exp Rtr Secure

stale

546 yes no

Copyright 2014, Juniper Networks, Inc.

Chapter 20: IPv6 Operational Commands

fe80::2a0:a514:0:24c
fe-1/2/0.1
fe80::2a0:a514:0:64c
fe-1/2/1.5
fe80::2a0:a514:0:a4c
fe-1/2/2.9

Copyright 2014, Juniper Networks, Inc.

00:05:85:8f:c8:bd

stale

258 yes no

00:05:85:8f:c8:bd

stale

111 yes no

00:05:85:8f:c8:bd

stale

327 yes no

1757

Interfaces Fundamentals for Routing Devices

show ipv6 router-advertisement

Syntax

Release Information

Description

Options

show ipv6 router-advertisement

<conflicts>
<interface interface>
<logical-system (all | logical-system-name)>
<prefix prefix/prefix length>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.2 for the QFX Series.
Display information about IPv6 router advertisements, including statistics about messages
sent and received on interfaces, and information received from advertisements from
other routers.
noneDisplay all IPv6 router advertisement information for all interfaces.
conflicts(Optional) Display only the IPv6 router advertisement information that is

conflicting.
interface interface(Optional) Display IPv6 router advertisement information for the

specified interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

prefix prefix/prefix length(Optional) Display IPv6 router advertisement information for

the specified prefix.

Additional Information

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

The display identifies conflicting information by enclosing the value the router is advertising
in brackets.
view

clear ipv6 router-advertisement on page 1755

show ipv6 router-advertisement on page 1759

show ipv6 router-advertisement conflicts on page 1760
show ipv6 router-advertisement prefix on page 1760
Table 150 on page 1758 describes the output fields for the show ipv6 router-advertisement
command. Output fields are listed in the approximate order in which they appear.

Table 150: show ipv6 router-advertisement Output Fields

Field Name

Field Description

Interface

Name of the interface.

Advertisements sent

Number of router advertisements sent and the elapsed time since they were sent.

1758

Copyright 2014, Juniper Networks, Inc.

Chapter 20: IPv6 Operational Commands

Table 150: show ipv6 router-advertisement Output Fields (continued)

Field Name

Field Description

Solicits received

Number of solicitation messages received.

Advertisements
received

Number of router advertisements received.

Advertisements from

Names of interfaces from which router advertisements have been received and the elapsed time
since the last one was received.

Managed

Managed address configuration flag: 0 (stateless) or 1 (stateful).

Other configuration

Other stateful configuration flag: 0 (stateless) or 1 (stateful).

Reachable time

Time that a node identifies a neighbor as reachable after receiving a reachability confirmation, in
milliseconds.

Default lifetime

Default lifetime, in seconds: from 0 seconds to 18.2 hours. A setting of 0 indicates that the router is
not a default router.

Retransmit timer

Time between retransmitted Neighbor Solicitation messages, in milliseconds.

Current hop limit

Configured current hop limit.

Prefix

Name and length of the prefix.

Valid lifetime

How long the prefix remains valid for onlink determination.

Preferred lifetime

How long the prefix generated by stateless autoconfiguration remains preferred.

On link

Onlink flag: 0 (not onlink) or 1 (onlink).

Autonomous

Autonomous address configuration flag: 0 (not autonomous) or 1 (autonomous).

Sample Output
show ipv6 router-advertisement
user@host> show ipv6 router-advertisement
Interface: fe-0/1/1.0
Advertisements sent: 0
Solicits received: 0
Advertisements received: 0
Interface: fxp0.0
Advertisements sent: 0
Solicits received: 0
Advertisements received: 1
Advertisement from fe80::2d0:b7ff:fe1e:7b0e, heard 00:00:13 ago
Managed: 0
Other configuration: 0 [1]
Reachable time: 0 ms
Default lifetime: 1800 sec

Copyright 2014, Juniper Networks, Inc.

1759

Interfaces Fundamentals for Routing Devices

Retransmit timer: 0 ms
Current hop limit: 64

show ipv6 router-advertisement conflicts

user@host> show ipv6 router-advertisement conflicts
Interface: fxp0.0
Advertisement from fe80::2d0:b7ff:fe1e:7b0e, heard 00:01:08 ago
Other configuration: 0 [1]

show ipv6 router-advertisement prefix

user@host> show ipv6 router-advertisement prefix 8040::/16
Interface: fe-0/1/3.0
Advertisements sent: 3, last sent 00:04:11 ago
Solicits received: 0
Advertisements received: 3
Advertisement from fe80::290:69ff:fe9a:5403, heard 00:00:05 ago
Managed: 0
Other configuration: 0
Reachable time: 0 ms
Default lifetime: 180 sec [1800 sec]
Retransmit timer: 0 ms
Current hop limit: 64
Prefix: 8040:1::/64
Valid lifetime: 2592000 sec
Preferred lifetime: 604800 sec
On link: 1
Autonomous: 1

1760

Copyright 2014, Juniper Networks, Inc.

CHAPTER 21

IS-IS Operational Commands

clear isis adjacency

clear isis database

clear isis overload

clear isis statistics

show isis adjacency

show isis authentication

show isis backup coverage

show isis backup label-switched-path

show isis backup spf results

show isis context-identifier

show isis database

show isis hostname

show isis interface

show isis overview

show isis route

show isis spf

show isis statistics

Copyright 2014, Juniper Networks, Inc.

1761

Interfaces Fundamentals for Routing Devices

clear isis adjacency

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Description
Options

Syntax on page 1762

Syntax (EX Series Switches and QFX Series) on page 1762
clear isis adjacency
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
<neighbor>
clear isis adjacency
<instance instance-name>
<interface interface-name>
<neighbor>

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 12.1 for the QFX Series.
Remove entries from the IS-IS adjacency database.
noneRemove all entries from the adjacency database.
instance instance-name(Optional) Clear all adjacencies for the specified routing instance

only.
interface interface-name(Optional) Clear all adjacencies for the specified interface only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor(Optional) Clear adjacencies for the specified neighbor only.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show isis adjacency on page 1770

clear isis adjacency on page 1762

See show isis adjacency for an explanation of output fields.

Sample Output
clear isis adjacency
The following sample output displays IS-IS adjacency database information before and
after the clear isis adjacency command is entered:
user@host> show isis adjacency
IS-IS adjacency database:
Interface
System
L State

1762

Hold (secs) SNPA

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

so-1/0/0.0
so-1/1/3.0
so-5/0/0.0

karakul
3 Up
1921.6800.5080 3 Up
1921.6800.5080 3 Up

26
23
19

user@host> clear isis adjacency karakul

user@host> show isis adjacency

IS-IS adjacency database:
Interface
System
so-1/0/0.0
karakul
so-1/1/3.0
1921.6800.5080
so-5/0/0.0
1921.6800.5080

Copyright 2014, Juniper Networks, Inc.

L
3
3
3

State
Hold (secs) SNPA
Initializing
26
Up
24
Up
21

1763

Interfaces Fundamentals for Routing Devices

clear isis database

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description

Options

Syntax on page 1764

Syntax (EX Series Switches and QFX Series) on page 1764
clear isis database
<entries>
<instance instance-name>
<logical-system (all | logical-system-name)>
clear isis database
<entries>
<instance instance-name>

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 12.1 for the QFX Series.
Remove the entries from the IS-IS link-state database, which contains prefixes and
topology information.
noneRemove all entries from the IS-IS link-state database for all routing instances.
entries(Optional) Name of the database entry.
instance instance-name(Optional) Clear all entries for the specified routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show isis database on page 1785

clear isis database on page 1764

See show isis database for an explanation of output fields.

Sample Output
clear isis database
The following sample output displays IS-IS link-state database information before and
after the clear isis database command is entered:
user@host> show isis database
IS-IS level 1 link-state database:
LSP ID
Sequence Checksum Lifetime (secs)
crater.00-00
0x12
0x84dd
1139
1 LSPs
IS-IS level 2 link-state database:
LSP ID
Sequence Checksum Lifetime (secs)

1764

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

crater.00-00
badlands.00-00
carlsbad.00-00
ranier.00-00
1921.6800.5066.00-00
1921.6800.5067.00-00
6 LSPs

0x19
0x16
0x33
0x2e
0x11
0x14

0xe92c
0x1454
0x220b
0xfc31
0x7313
0xd9d4

1134
985
1015
1007
566
939

user@host> clear isis database

user@host> show isis database

IS-IS level 1 link-state database:
LSP ID
Sequence Checksum Lifetime (secs)
IS-IS level 2 link-state database:
LSP ID
Sequence Checksum Lifetime (secs)

Copyright 2014, Juniper Networks, Inc.

1765

Interfaces Fundamentals for Routing Devices

clear isis overload

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description

Syntax on page 1766

Syntax (EX Series Switches and QFX Series) on page 1766
clear isis overload
<instance instance-name>
<logical-system (all | logical-system-name)>
clear isis overload
<instance instance-name>

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 12.1 for the QFX Series.
Reset the IS-IS dynamic overload bit. This command can appear to not work, continuing
to display overload after execution. The bit is reset only if the root cause is corrected by
configuration remotely or locally.
When other routers detect that the overload bit is set, they do not use this routing device
for transit traffic, but they do use it for packets destined to the overloaded routing devices
directly connected networks and IP prefixes.

Options

noneReset the IS-IS dynamic overload bit.

instance instance-name(Optional) Reset the IS-IS dynamic overload bit for the specified

routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show isis database on page 1785

clear isis overload on page 1766

See show isis database for an explanation of output fields.

Sample Output
clear isis overload
The following sample output displays IS-IS database information before and after the
clear isis overload command is entered:
user@host> show isis database
IS-IS level 1 link-state database:
LSP ID
Sequence Checksum Lifetime Attributes

1766

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

pro3-c.00-00

0x4

0x10db

1185 L1 L2 Overload

1 LSPs
IS-IS level 2 link-state database:
LSP ID
Sequence Checksum Lifetime Attributes
pro3-c.00-00
0x5
0x429f
1185 L1 L2 Overload

pro2-a.00-00
pro2-a.02-00
3 LSPs

0x91e
0x1

0x2589
0xcbc

874 L1 L2
874 L1 L2

user@host> clear isis overload

user@host> show isis database

IS-IS level 1 link-state database:
LSP ID
Sequence Checksum Lifetime Attributes
pro3-c.00-00
0xa
0x429e
1183 L1 L2
1 LSPs
IS-IS level 2 link-state database:
LSP ID
Sequence Checksum Lifetime Attributes
pro3-c.00-00
0xc
0x9c39
1183 L1 L2
pro2-a.00-00
0x91e
0x2589
783 L1 L2
pro2-a.02-00
0x1
0xcbc
783 L1 L2
3 LSPs

Copyright 2014, Juniper Networks, Inc.

1767

Interfaces Fundamentals for Routing Devices

clear isis statistics

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

Syntax on page 1768

Syntax (EX Series Switches and QFX Series) on page 1768
clear isis statistics
<instance instance-name>
<logical-system (all | logical-system-name)>
clear isis statistics
<instance instance-name>

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 12.1 for the QFX Series.
Set statistics about IS-IS traffic to zero.
noneSet IS-IS traffic statistics to zero for all routing instances.
instance instance-name(Optional) Set IS-IS traffic statistics to zero for the specified

routing instance only.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

show isis statistics on page 1815

clear isis statistics on page 1768

See show isis statistics for an explanation of output fields.

Sample Output
clear isis statistics
The following sample output displays IS-IS statistics before and after the
clear isis statistics command is entered:
user@host> show isis statistics
IS-IS statistics for merino:
PDU type
LSP
IIH
CSNP
PSNP
Unknown
Totals

1768

Received
12793
116751
203956
7356
0
340856

Processed
12793
116751
203956
7350
0
340850

Drops
0
0
0
6
0
6

Sent
8666
118834
204080
8635
0
340215

Rexmit
719
0
0
0
0
719

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Total packets received: 340856 Sent: 340934

SNP queue length:
LSP queue length:
SPF runs:
Fragments rebuilt:
LSP regenerations:
Purges initiated:

0 Drops:
0 Drops:

0
0

1064
1087
436
0

user@host> clear isis statistics

user@host> show isis statistics

IS-IS statistics for merino:
PDU type
LSP
IIH
CSNP
PSNP
Unknown
Totals

Received
0
3
2
0
0
5

Processed
0
3
2
0
0
5

Drops
0
0
0
0
0
0

Sent
0
3
4
0
0
7

Rexmit
0
0
0
0
0
0

Total packets received: 5 Sent: 7

SNP queue length:
LSP queue length:

0 Drops:
0 Drops:

SPF runs:
Fragments rebuilt:
LSP regenerations:
Purges initiated:

0
0
0
0

Copyright 2014, Juniper Networks, Inc.

0
0

1769

Interfaces Fundamentals for Routing Devices

show isis adjacency

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Description
Options

Syntax on page 1770

Syntax (EX Series Switches and QFX Series) on page 1770
show isis adjacency
<system-id>
<brief | detail | extensive>
<instance instance-name>
<logical-system (all | logical-system-name)>
show isis adjacency
<system-id>
<brief | detail | extensive>
<instance instance-name>

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 12.1 for the QFX Series.
Display information about IS-IS neighbors.
noneDisplay standard information about IS-IS neighbors for all routing instances.
system id(Optional) Display information about IS-IS neighbors for the specified

intermediate system.
brief | detail | extensive(Optional) Display standard information about IS-IS neighbors

with the specified level of output.

instance instance-name(Optional) Display information about IS-IS neighbors for the

specified routing instance.

logical-system (all | logical-system-name)(Optional) Display information about IS-IS

neighbors for all logical systems or for a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

1770

view

clear isis adjacency on page 1762

show isis adjacency on page 1772

show isis adjacency brief on page 1772
show isis adjacency detail on page 1773
show isis adjacency extensive on page 1773
Table 151 on page 1771 describes the output fields for the show isis adjacency command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 151: show isis adjacency Output Fields

Field Name

Field Description

Level of Output

Interface

Interface through which the neighbor is reachable.

All levels

System

System identifier (sysid), displayed as a name, if possible.

brief

L or Level

Level:

All levels

1Level 1 only

2Level 2 only

3Level 1 and Level 2

An exclamation point (!) preceding the level number indicates that the adjacency
is missing an IP address.
State

State of the adjacency: Up, Down, New, One-way, Initializing, or Rejected.

All levels

Hold (secs)

Remaining hold time of the adjacency.

brief

SNPA

Subnetwork point of attachment (MAC address of the next hop).

brief

Expires in

How long until the adjacency expires, in seconds.

detail

Priority

Priority to become the designated intermediate system.

detail extensive

Up/Down
transitions

Count of adjacency status changes from Up to Down or from Down to Up.

detail

Last transition

Time of the last Up/Down transition.

detail

Circuit type

Bit mask of levels on this interface: 1=Level 1 router; 2=Level 2 router; 3=both
Level 1 and Level 2 router.

detail

Speaks

Protocols supported by this neighbor.

detail extensive

MAC address

MAC address of the interface.

detail extensive

Topologies

Supported topologies.

detail extensive

Restart capable

Whether a neighbor is capable of graceful restart: Yes or No.

detail extensive

Adjacency
advertisement:
Advertise

This routing device has signaled to advertise this interface to its neighbors in
their link-state PDUs.

detail extensive

Adjacency
advertisement:
Suppress

This neighbor has signaled not to advertise the interface in the routing device's
outbound link-state PDUs.

detail extensive

IP addresses

IP address of this neighbor.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1771

Interfaces Fundamentals for Routing Devices

Table 151: show isis adjacency Output Fields (continued)

Field Name

Field Description

Level of Output

Transition log

List of recent transitions, including:

extensive

WhenTime at which an IS-IS adjacency transition occurred.

StateCurrent state of the IS-IS adjacency (up, down, or rejected).

UpAdjacency is up and operational.

DownAdjacency is down and not available.

RejectedAdjacency has been rejected.

EventType of transition that occurred.

SeenselfPossible routing loop has been detected.

Interface downIS-IS interface has gone down and is no longer available.

ErrorAdjacency error.

Down reasonReason that an IS-IS adjacency is down:

3-Way Handshake FailedConnection establishment failed.

Address MismatchAddress mismatch caused link failure.

Aged OutLink expired.

ISO Area MismatchIS-IS area mismatch caused link failure.

Bad HelloUnacceptable hello message caused link failure.

BFD Session DownBidirectional failure detection caused link failure.

Interface DisabledIS-IS interface is disabled.

Interface DownIS-IS interface is unavailable.

Interface Level DisabledIS-IS level is disabled.

Level ChangedIS-IS level has changed on the adjacency.

Level MismatchLevels on adjacency are not compatible.

MPLS LSP DownLabel-switched path (LSP) is unavailable.

MT Topology ChangedIS-IS topology has changed.

MT Topology MismatchIS-IS topology is mismatched.

Remote System ID ChangedAdjacency peer system ID changed.

Protocol ShutdownIS-IS protocol is disabled.

CLI CommandAdjacency brought down by user.

UnknownUnknown.

Sample Output
show isis adjacency
user@host> show isis adjacency
Interface
System
at-2/3/0.0
ranier

L State
3 Up

Hold (secs) SNPA

23

show isis adjacency brief

The output for the show isis adjacency brief command is identical to that for the show
isis adjacency command. For sample output, see show isis adjacency on page 1772.

1772

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

show isis adjacency detail

user@host> show isis adjacency detail
ranier
Interface: at-2/3/0.0, Level: 3, State: Up, Expires in 21 secs
Priority: 0, Up/Down transitions: 1, Last transition: 00:01:09 ago
Circuit type: 3, Speaks: IP, IPv6
Topologies: Unicast
Restart capable: Yes
IP addresses: 11.1.1.2

show isis adjacency extensive

user@host> show isis adjacency extensive
ranier
Interface: at-2/3/0.0, Level: 3, State: Up, Expires in 22 secs
Priority: 0, Up/Down transitions: 1, Last transition: 00:01:16 ago
Circuit type: 3, Speaks: IP, IPv6
Topologies: Unicast
Restart capable: Yes
IP addresses: 11.1.1.2
Transition log:
When
State
Event
Down reason
Wed Nov 8 21:24:25
Up
Seenself

Copyright 2014, Juniper Networks, Inc.

1773

Interfaces Fundamentals for Routing Devices

show isis authentication

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

Syntax on page 1774

Syntax (EX Series Switches and QFX Series) on page 1774
show isis authentication
<instance instance-name>
<logical-system (all | logical-system-name)>
show isis authentication
<instance instance-name>

Command introduced in Junos OS Release 7.5.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Support for hitless authentication key rollover introduced in Junos OS Release 11.2.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Display information about IS-IS authentication.
noneDisplay information about IS-IS authentication.
instance instance-name(Optional) Display IS-IS authentication for the specified routing

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show isis authentication on page 1775

show isis authentication (With Hitless Authentication Key Rollover
Configured) on page 1775
Table 152 on page 1774 describes the output fields for the show isis authentication
command. Output fields are listed in the approximate order in which they appear.

Table 152: show isis authentication Output Fields

Field Name

Field Description

Interface

Interface name.

Level

IS-IS level.

IIH Auth

IS-IS Hello (IIH) packet authentication type.

Displays the name of the active keychain if hitless authentication key rollover
is configured.

CSN Auth

1774

Complete sequence number authentication type.

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 152: show isis authentication Output Fields (continued)

Field Name

Field Description

PSN Auth

Partial sequence number authentication type.

L1 LSP
Authentication

Layer 1 link-state PDU authentication type.

L2 LSP
Authentication

Layer 2 link-state PDU authentication type.

Sample Output
show isis authentication
user@host> show isis authentication
Interface
Level IIH Auth
at-2/3/0.0
1
Simple
2
MD5

CSN Auth
Simple
MD5

PSN Auth
Simple
MD5

L1 LSP Authentication: Simple

L2 LSP Authentication: MD5

show isis authentication (With Hitless Authentication Key Rollover Configured)

user@host> show isis authentication
Interface
Level IIH Auth CSN Auth
so-0/1/3.0
2
hakrhello MD5

PSN Auth
MD5

L2 LSP Authentication: MD5

Copyright 2014, Juniper Networks, Inc.

1775

Interfaces Fundamentals for Routing Devices

show isis backup coverage

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

show isis backup coverage

<instance instance-name>
<logical-system (all | logical-system-name)>
show isis backup coverage
<instance instance-name>

Command introduced in Junos OS Release 9.5.

Command introduced in Junos OS Release 9.5 for EX Series switches.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Display information about the level of backup coverage available.
noneDisplay information about the level of backup coverage available for all the nodes

and prefixes in the network.

instance instance-name(Optional) Display information about the level of backup

coverage for a specific IS-IS routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

Example: Configuring Link and Node Protection for IS-IS Routes

show isis backup label-switched-path on page 1778

show isis backup coverage on page 1777

Table 153 on page 1776 lists the output fields for the show isis backup coverage command.
Output fields are listed in the approximate order in which they appear.

Table 153: show isis backup coverage Output Fields

Field Name

Field Description

Topology

Type of topology or address family: IPV4 Unicast or IPV6 Unicast.

Level

IS-IS level:

Node

1776

1Level 1

2Level 2

By topology, the percentage of all routes configured on the node that

are protected through backup coverage.

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 153: show isis backup coverage Output Fields (continued)

Field Name

Field Description

IPv4

Percentage of IPv4 unicast routes that are protected through backup

coverage.

IPv6

Percentage of IPv6 unicast routes that are protected through backup

coverage.

CLNS

Percentage of Connectionless Network Service (CLNS) routes that are

protected through backup coverage.

Sample Output
show isis backup coverage
user@host> show isis backup coverage
Backup Coverage:
Topology
Level
Node
IPV4 Unicast
2 28.57%
IPV6 Unicast
2
0.00%

Copyright 2014, Juniper Networks, Inc.

IPv4
22.22%
0.00%

IPv6
0.00%
0.00%

CLNS
0.00%
0.00%

1777

Interfaces Fundamentals for Routing Devices

show isis backup label-switched-path

Syntax

show isis backup label-switched-path

<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches and QFX
Series)

show isis backup label-switched-path

Release Information

Command introduced in Junos OS Release 9.5.

Command introduced in Junos OS Release 9.5 for EX Series switches.
Command introduced in Junos OS Release 12.1 for the QFX Series.

Description

Display information about MPLS label-switched-paths (LSPs) designated as backup

routes for IS-IS routes.

Options

noneDisplay information about MPLS LSPs designated as backup routes for IS-IS

routes.
logical-system (all | logical-system-name(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level

view

Related
Documentation

List of Sample Output

Example: Configuring Link and Node Protection for IS-IS Routes

show isis backup coverage on page 1776

show isis backup label-switched-path on page 1779

Output Fields

Table 154 on page 1778 lists the output fields for the show isis backup label-switched-path
command. Output fields are listed in the approximate order in which they appear.

Table 154: show isis backup label-switched-path Output Fields

Field Name

Field Description

Backup MPLS LSPs

List of MPLS LSPs designated as backup paths for IS-IS routes.

Egress

IP address of the egress routing device for the LSP.

Status

State of the LSP:

UpThe routing device can detect RSVP hello messages from the neighbor.

DownThe routing device has received one of the following indications:

1778

Communication failure from the neighbor.

Communication from IGP that the neighbor is unavailable.

Change in the sequence numbers in the RSVP hello messages sent by the neighbor.

DeletedLSP is no longer available as a backup path.

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 154: show isis backup label-switched-path Output Fields (continued)

Field Name

Field Description

Last change

Time elapsed since the neighbor state changed either from up to down or from down to up. The format
is hh:mm:ss.

TE-metric

Configured traffic engineering metric.

Metric

Configured metric.

Sample Output
show isis backup label-switched-path
user@host> show isis backup label-switched-path
Backup MPLS LSPs:
f-to-g, Egress: 192.168.1.4, Status: up, Last change: 06:12:03
TE-metric: 9, Metric: 0

Copyright 2014, Juniper Networks, Inc.

1779

Interfaces Fundamentals for Routing Devices

show isis backup spf results

Syntax

Syntax (EX Series

Switches)

Release Information
Description
Options

show isis backup spf results

<instance instance-name>
<level (1 | 2)>
<logical-system (all | logical-system-name)>
<no-coverage>
<topology (ipv4-unicast | ipv6-multicast | ipv6-unicast | unicast)>
show isis backup spf results
<instance instance-name>
<level (1 | 2)>
<no-coverage>
<topology (ipv4-unicast | unicast)>

Command introduced in Junos OS Release 9.5.

Display information about IS-IS shortest-path-first (SPF) calculations for backup paths.
noneDisplay information about IS-IS SPF calculations for all backup paths for all

destination nodes.
instance instance-name(Optional) Display SPF calculations for backup paths for the

specified routing instance.

level (1 | 2)(Optional) Display SPF calculations for the backup paths for the specified

IS-IS level.
logical-system logical-system-name(Optional) Display SPF calculations for the backup

paths for all logical systems or on a particular logical system.

no-coverage(Optional) Display SPF calculations only for destinations that do not have

backup coverage.
topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)(Optional) Display

SPF calculations for backup paths for the specified topology only.
Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

1780

view

Example: Configuring Link and Node Protection for IS-IS Routes

show isis backup coverage on page 1776

show isis backup spf results on page 1781

show isis backup spf results no-coverage on page 1782
Table 155 on page 1781 lists the output fields for the show isis backup spf results command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 155: show isis backup spf results Output Fields

Field Name

Field Description

node-name

Name of the destination node.

Address

Address of the destination node.

Primary next-hop

Interface and name of the node of the primary next hop to reach the
destination.

Root

Name of the next-hop neighbor.

Metric

Metric to the node.

Eligible

Indicates that the next-hop neighbor has been designated as a backup

path to the destination node.

Backup next-hop

Name of the interface of the backup next hop.

SNPA

Subnetwork point of attachment (MAC address of the next hop).

LSP

Name of the MPLS label-switched path (LSP) designated as a backup

path.

Not eligible

Indicates that the next-hop neighbor cannot function as a backup path

to the destination.

Reason

Describes why the next-hop neighbor is designated as Not eligible as

a backup path.

Sample Output
show isis backup spf results
user@host> show isis backup spf results
D.00
Primary next-hop: fe-1/0/0.0, IPV4, R2.00, SNPA: 0:12:1e:cb:cc:dc
Primary next-hop: fe-1/0/0.0, IPV6, R2.00, SNPA: 0:12:1e:cb:cc:dc
Root: R2 via Direct, Root Metric: 1, Metric: 1, Root Preference: 0x0
Not eligible, IPV4, Reason: Primary next-hop link fate sharing
Not eligible, IPV6, Reason: Primary next-hop link fate sharing
Root: S via Direct, Root Metric: 1, Metric: 3, Root Preference: 0x0
track-item: R1.00-00
Not eligible, IPV4, Reason: Path loops
Not eligible, IPV6, Reason: Path loops
Root: R4 via LDP, Root Metric: 3, Metric: 1, Root Preference: 0x0
Eligible, IPV4, Protection-Type: Node Protect, Downstream Path
Backup next-hop: fe-1/2/0.0, LSP LDP->R4(192.168.1.4)
Eligible, IPV6, Protection-Type: Node Protect, Downstream Path
Backup next-hop: fe-1/2/0.0, LSP LDP->R4(192.168.1.4)
Root: R3 via LDP, Root Metric: 2, Metric: 2, Root Preference: 0x0
Eligible, IPV4, Protection-Type: Node Protect, Downstream Path, Active
Backup next-hop: fe-1/2/0.0, LSP LDP->R3(192.168.1.3)

Copyright 2014, Juniper Networks, Inc.

1781

Interfaces Fundamentals for Routing Devices

Eligible, IPV6, Protection-Type: Node Protect, Downstream Path, Active

Backup next-hop: fe-1/2/0.0, LSP LDP->R3(192.168.1.3)

show isis backup spf results no-coverage

user@host> show isis backup spf results no-coverage
IS-IS level 1 SPF results:
pro-bng3-k.00
Primary next-hop: fe-1/3/3.0, IPV4, pro-bng3-k, SNPA: b0:c6:9a:2c:f0:de
Primary next-hop: fe-1/3/3.0, IPV6, pro-bng3-k, SNPA: b0:c6:9a:2c:f0:de
Root: pro-bng3-k, Root Metric: 10, Metric: 0, Root Preference: 0x0
Root: pro-bng3-i, Root Metric: 10, Metric: 20, Root Preference: 0x0
track-item: pro-bng3-k.00-00
track-item: pro-bng3-j.00-00
pro-bng3-i.00
Primary next-hop: fe-0/1/2.0, IPV4, pro-bng3-i, SNPA: b0:c6:9a:2a:f4:21
Primary next-hop: fe-0/1/2.0, IPV6, pro-bng3-i, SNPA: b0:c6:9a:2a:f4:21
Root: pro-bng3-i, Root Metric: 10, Metric: 0, Root Preference: 0x0
Root: pro-bng3-k, Root Metric: 10, Metric: 20, Root Preference: 0x0
track-item: pro-bng3-j.00-00
track-item: pro-bng3-i.00-00
2 nodes
IS-IS level 2 SPF results:
pro-bng3-k.00
Primary next-hop: fe-1/3/3.0, IPV4, pro-bng3-k, SNPA: b0:c6:9a:2c:f0:de
Primary next-hop: fe-1/3/3.0, IPV6, pro-bng3-k, SNPA: b0:c6:9a:2c:f0:de
Root: pro-bng3-k, Root Metric: 10, Metric: 0, Root Preference: 0x0
Root: pro-bng3-i, Root Metric: 10, Metric: 20, Root Preference: 0x0
track-item: pro-bng3-k.00-00
track-item: pro-bng3-j.00-00
pro-bng3-i.00
Primary next-hop: fe-0/1/2.0, IPV4, pro-bng3-i, SNPA: b0:c6:9a:2a:f4:21
Primary next-hop: fe-0/1/2.0, IPV6, pro-bng3-i, SNPA: b0:c6:9a:2a:f4:21
Root: pro-bng3-i, Root Metric: 10, Metric: 0, Root Preference: 0x0
Root: pro-bng3-k, Root Metric: 10, Metric: 20, Root Preference: 0x0
track-item: pro-bng3-j.00-00
track-item: pro-bng3-i.00-00
2 nodes

1782

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

show isis context-identifier

Syntax

Release Information
Description
Options

show isis context-identifier

<brief | detail | extensive>
<identifier name>
<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced in Junos OS Release 10.4.

Display IS-IS context identifier information.
brief | detail | extensive(Optional) Display the specified level of output.
identifier name(Optional) Display information about the specified context identifier.
instance instance-name(Optional) Display entries for the specified routing instance.
logical-system (all | logical-system-name)(Optional) Display the context identifier

information for all logical systems or for a particular logical system.

Required Privilege
Level
Output Fields

View

Table 156 on page 1783 lists the output fields for the show isis context-identifier command.
Output fields are listed in the approximate order in which they appear.

Table 156: show isis context-identifier Output Fields

Field Name

Field Description

Level of Output

Context

IPv4 address that defines a protection pair. The context is manually

configured on both primary and protector PEs.

detail

Owner

Protocol that requires the context.

detail

Role

Role of the PE, which is either primary or protector.

detail

Primary

Name of the primary PE.

detail

Metric

Advertised interior gateway protocol (IGP) metric.

detail

Sample Output
user@host> show isis context-identifier detail
IS-IS context database:
Context
Owner
Role
Primary
Metric
2.2.4.3
MPLS
Primary
pro3-e
1
Advertiser pro3-e, Router ID 10.255.245.198, Metric 1, Level 1
Advertiser pro3-e, Router ID 10.255.245.198, Metric 1, Level 2
Advertiser pro3-c, Router ID 10.255.245.196, Metric 11, Level 2

Copyright 2014, Juniper Networks, Inc.

1783

Interfaces Fundamentals for Routing Devices

1784

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

show isis database

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Description

Options

Syntax on page 1785

Syntax (EX Series Switches and QFX Series) on page 1785
show isis database
<system-id>
<brief | detail | extensive>
<instance instance-name>
<level (1 | 2)>
<logical-system (all | logical-system-name)>
show isis database
<system-id>
<brief | detail | extensive>
<level (1 | 2)>
<instance instance-name>

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 12.1 for the QFX Series.
Display the entries in the IS-IS link-state database, which contains data about PDU
packets.
noneDisplay standard information about IS-IS link-state database entries for all routing

instances.
system id(Optional) Display IS-IS link-state database entries for the specified

intermediate system.
brief | detail | extensive(Optional) Display the specified level of output.
instance instance-name(Optional) Display IS-IS link-state database entries for the

specified routing instance.

level (1 | 2)(Optional) Display IS-IS link-state database entries for the specified IS-IS

level.
logical-system (all | logical-system-name)(Optional) Display standard information

about IS-IS link-state database entries for all logical systems or for a particular
logical system.
Required Privilege
Level
Related
Documentation
List of Sample Output

view

clear isis database on page 1764

show isis database on page 1787

show isis database brief on page 1788
show isis database detail on page 1788

Copyright 2014, Juniper Networks, Inc.

1785

Interfaces Fundamentals for Routing Devices

show isis database extensive on page 1788

Output Fields

Table 157 on page 1786 describes the output fields for the show isis database command.
Output fields are listed in the approximate order in which they appear. Fields that contain
internal IS-IS information useful only in troubleshooting obscure problems are not
described in the table. For more details about these fields, contact your customer support
representative.

Table 157: show isis database Output Fields

Field Name

Field Description

Level of Output

Interface name

Name of the interface on which the link-state PDU has been received; always
IS-IS for this command.

All levels

level

Level of intermediate system:

All levels

1Intermediate system routes within an area; when the destination is outside

an area, it routes toward a Level 2 system.

2Intermediate system routes between areas and toward other ASs.

LSP ID

Link-state PDU identifier.

All levels

Sequence

Sequence number of the link-state PDU.

All levels

Checksum

Checksum value of the link-state PDU.

All levels

Lifetime (secs)

Remaining lifetime of the link-state PDU, in seconds.

All levels

Attributes

Attributes of the specified database: L1, L2, Overload, or Attached (L1 only).

none brief

# LSPs

Total number of link-state PDUs in the specified link-state database.

none brief

IP prefix

Prefix advertised by this link-state PDU.

detail extensive

IS neighbor

IS-IS neighbor of the advertising system.

detail extensive

ES neighbor

(J Series routers only) An ES-IS neighbor of the advertising system.

detail extensive

IP prefix

IPv4 prefix advertised by this link-state PDU.

detail extensive

V6 prefix

IPv6 prefix advertised by this link-state PDU.

detail extensive

Metric

Metric of the prefix or neighbor.

detail extensive

Header

LSP IDLink state PDU identifier of the header.

extensive

LengthHeader length.

Allocated LengthAmount of length available for the header.

Router IDAddress of the local routing device.

Remaining LifetimeRemaining lifetime of the link-state PDU, in seconds.

1786

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 157: show isis database Output Fields (continued)

Field Name

Field Description

Level of Output

Packet

LSP IDThe identifier for the link-state PDU.

extensive

LengthPacket length.

LifetimeRemaining lifetime, in seconds.

ChecksumThe checksum of the link-state PDU.

SequenceThe sequence number of the link-state PDU. Every time the

link-state PDU is updated, this number increments.

TLVs

AttributesPacket attributes.

NLPIDNetwork layer protocol identifier.

Fixed lengthSpecifies the set length for the packet.

Area AddressArea addresses that the routing device can reach.

SpeaksSupported routing protocols.

IP router idID of the routing device (usually the IP address).

IP addressIPv4 address.

HostnameAssigned name of the routing device.

IP prefixIP prefix of the routing device.

MetricIS-IS metric that measures the cost of the adjacency between the

extensive

originating routing device and the advertised routing device.

IP extended prefixExtended IP prefix of the routing device.

IS neighborDirectly attached neighbors name and metric.

IS extended neighborDirectly attached neighbors name, metric, IP address,

local interface index, and remote interface index.

The interface indexes enable Junos OS to support unnumbered extensions
for IS-IS, as described in RFC 4205.

Sample Output
show isis database
user@host> show isis database
IS-IS level 1 link-state database:
LSP ID
Sequence Checksum Lifetime Attributes
kobuk.00-00
0x3
0x3167
1057 L1 L2
camaro.00-00
0x5
0x770e
1091 L1 L2
ranier.00-00
0x4
0xaa95
1091 L1 L2
glacier.00-00
0x4
0x206f
1089 L1 L2
glacier.02-00
0x1
0xd141
1089 L1 L2
badlands.00-00
0x3
0x87a2
1093 L1 L2
6 LSPs
IS-IS level 2 link-state database:
LSP ID
Sequence Checksum Lifetime Attributes
kobuk.00-00
0x6
0x8d6b
1096 L1 L2
camaro.00-00
0x9
0x877b
1101 L1 L2
ranier.00-00
0x8
0x855d
1103 L1 L2
glacier.00-00
0x7
0xf892
1098 L1 L2
glacier.02-00
0x1
0xd141
1089 L1 L2
badlands.00-00
0x6
0x562
1105 L1 L2
6 LSPs

Copyright 2014, Juniper Networks, Inc.

1787

Interfaces Fundamentals for Routing Devices

show isis database brief

The output for the show isis database brief command is identical to that for the show isis
database command. For sample output, see show isis database on page 1787.
show isis database detail
user@host> show isis database logical-system CE3 sisira.00-00 detail
IS-IS level 1 link-state database:
sisira.00-00 Sequence: 0x11, Checksum: 0x10fc, Lifetime: 975 secs
IS neighbor: hemantha-CE3.02
Metric:
10
ES neighbor: 0015.0015.0015
Metric:
10 Down
ES neighbor: 0025.0025.0025
Metric:
10 Down
ES neighbor: 0030.0030.0030
Metric:
10 Down
ES neighbor: 0040.0040.0040
Metric:
10 Down
ES neighbor: sisira
Metric:
0
IP prefix: 1.0.0.0/24
Metric:
10 External
IP prefix: 3.0.0.0/24
Metric:
10 External
IP prefix: 4.0.0.0/24
Metric:
10 External
IP prefix: 5.0.0.0/24
Metric:
10 Internal
IP prefix: 15.15.15.15/32
Metric:
10 External
IP prefix: 25.25.25.25/32
Metric:
10 External
IP prefix: 30.30.30.30/32
Metric:
10 External
IP prefix: 40.40.40.40/32
Metric:
10 External
IP prefix: 60.60.60.60/32
Metric:
0 Internal

Down
Down
Down
Up
Down
Down
Down
Down
Up

IS-IS level 2 link-state database:

sisira.00-00 Sequence: 0x13, Checksum: 0x69ac, Lifetime: 993 secs
IS neighbor: hemantha-CE3.02
Metric:
10
IP prefix: 1.0.0.0/24
Metric:
10 External
IP prefix: 3.0.0.0/24
Metric:
10 External
IP prefix: 4.0.0.0/24
Metric:
10 External
IP prefix: 5.0.0.0/24
Metric:
10 Internal
IP prefix: 15.15.15.15/32
Metric:
10 External
IP prefix: 25.25.25.25/32
Metric:
10 External
IP prefix: 30.30.30.30/32
Metric:
10 External
IP prefix: 40.40.40.40/32
Metric:
10 External
IP prefix: 50.50.50.50/32
Metric:
10 Internal
IP prefix: 60.60.60.60/32
Metric:
0 Internal
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0015.0015.0015/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0025.0025.0025/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0030.0030.0030/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0040.0040.0040/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0060.0060.0060/152
Metric:
0 Internal

Down
Down
Down
Up
Down
Down
Down
Down
Up
Up
Down
Down
Down
Down
Up

show isis database extensive

user@host> show isis database extensive
IS-IS level 1 link-state database:
Router-A.00-00 Sequence: 0x1, Checksum: 0xf75c, Lifetime: 1116 secs

1788

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

IP prefix: 192.168.0.1/32

Metric:

0 Internal Up

Header: LSP ID: Router-A.00-00, Length: 85 bytes

Allocated length: 1492 bytes, Router ID: 192.168.0.1
Remaining lifetime: 1116 secs, Level: 1, Interface: 0
Estimated free bytes: 1353, Actual free bytes: 1407
Aging timer expires in: 1116 secs
Protocols: IP, IPv6
Packet: LSP ID: Router-A.00-00, Length: 85 bytes, Lifetime : 1200 secs
Checksum: 0xf75c, Sequence: 0x1, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 18, Packet version: 1, Max area: 0
TLVs:
Area address: 49.0002 (3)
LSP Buffer Size: 1492
Speaks: IP
Speaks: IPV6
IP router id: 192.168.0.1
IP address: 192.168.0.1
Hostname: Router-A
IP prefix: 192.168.0.1/32, Internal, Metric: default 0, Up
IP extended prefix: 192.168.0.1/32 metric 0 up
No queued transmissions
IS-IS level 2 link-state database:
Router-A.00-00 Sequence: 0x5, Checksum: 0x3196, Lifetime: 1158
IS neighbor: Router-B.02
Metric:
Two-way fragment: Router-B.02-00, Two-way first fragment:
IS neighbor: Router-E.02
Metric:
Two-way fragment: Router-E.02-00, Two-way first fragment:
IP prefix: 10.0.0.0/30
Metric:
10
IP prefix: 10.0.0.4/30
Metric:
10
IP prefix: 192.168.0.1/32
Metric:
0

secs
10
Router-B.02-00
10
Router-E.02-00
Internal Up
Internal Up
Internal Up

Header: LSP ID: Router-A.00-00, Length: 208 bytes

Allocated length: 1492 bytes, Router ID: 192.168.0.1
Remaining lifetime: 1158 secs, Level: 2, Interface: 0
Estimated free bytes: 1233, Actual free bytes: 1284
Aging timer expires in: 1158 secs
Protocols: IP, IPv6
Packet: LSP ID: Router-A.00-00, Length: 208 bytes, Lifetime : 1198 secs
Checksum: 0x3196, Sequence: 0x5, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
Area address: 49.0002 (3)
LSP Buffer Size: 1492
Speaks: IP
Speaks: IPV6
IP router id: 192.168.0.1
IP address: 192.168.0.1
Hostname: Router-A
IP prefix: 192.168.0.1/32, Internal, Metric: default 0, Up
IP prefix: 10.0.0.4/30, Internal, Metric: default 10, Up
IP prefix: 10.0.0.0/30, Internal, Metric: default 10, Up
IP extended prefix: 192.168.0.1/32 metric 0 up

Copyright 2014, Juniper Networks, Inc.

1789

Interfaces Fundamentals for Routing Devices

IP
IP
IS
IS
IS

extended prefix: 10.0.0.4/30 metric 10 up

extended prefix: 10.0.0.0/30 metric 10 up
neighbor: Router-E.02, Internal, Metric: default 10
neighbor: Router-B.02, Internal, Metric: default 10
extended neighbor: Router-E.02, Metric: default 10
IP address: 10.0.0.1
Local interface index: 101, Remote interface index: 0
IS extended neighbor: Router-B.02, Metric: default 10
IP address: 10.0.0.5
Local interface index: 102, Remote interface index: 0
No queued transmissions
Router-B.00-00 Sequence: 0x5, Checksum: 0xf8f, Lifetime: 1183 secs
IS neighbor: Router-B.02
Metric:
10
Two-way fragment: Router-B.02-00, Two-way first fragment: Router-B.02-00
IS neighbor: Router-C.02
Metric:
10
Two-way fragment: Router-C.02-00, Two-way first fragment: Router-C.02-00
IP prefix: 10.0.0.4/30
Metric:
10 Internal Up
IP prefix: 10.0.0.8/30
Metric:
10 Internal Up
IP prefix: 192.168.0.2/32
Metric:
0 Internal Up
Header: LSP ID: Router-B.00-00, Length: 208 bytes
Allocated length: 284 bytes, Router ID: 192.168.0.2
Remaining lifetime: 1183 secs, Level: 2, Interface: 102
Estimated free bytes: 114, Actual free bytes: 76
Aging timer expires in: 1183 secs
Protocols: IP, IPv6
Packet: LSP ID: Router-B.00-00, Length: 208 bytes, Lifetime : 1196 secs
Checksum: 0xf8f, Sequence: 0x5, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
Area address: 49.0002 (3)
LSP Buffer Size: 1492
Speaks: IP
Speaks: IPV6
IP router id: 192.168.0.2
IP address: 192.168.0.2
Hostname: Router-B
IP prefix: 192.168.0.2/32, Internal, Metric: default 0, Up
IP prefix: 10.0.0.4/30, Internal, Metric: default 10, Up
IP prefix: 10.0.0.8/30, Internal, Metric: default 10, Up
IP extended prefix: 192.168.0.2/32 metric 0 up
IP extended prefix: 10.0.0.4/30 metric 10 up
IP extended prefix: 10.0.0.8/30 metric 10 up
IS neighbor: Router-B.02, Internal, Metric: default 10
IS neighbor: Router-C.02, Internal, Metric: default 10
IS extended neighbor: Router-B.02, Metric: default 10
IP address: 10.0.0.6
Local interface index: 108, Remote interface index: 0
IS extended neighbor: Router-C.02, Metric: default 10
IP address: 10.0.0.9
Local interface index: 109, Remote interface index: 0
No queued transmissions
Router-B.02-00 Sequence: 0x1, Checksum: 0x3c7c, Lifetime: 1156 secs
IS neighbor: Router-A.00
Metric:
0
Two-way fragment: Router-A.00-00, Two-way first fragment: Router-A.00-00
IS neighbor: Router-B.00
Metric:
0

1790

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Two-way fragment: Router-B.00-00, Two-way first fragment: Router-B.00-00

Header: LSP ID: Router-B.02-00, Length: 76 bytes
Allocated length: 284 bytes, Router ID: 0.0.0.0
Remaining lifetime: 1156 secs, Level: 2, Interface: 102
Estimated free bytes: 208, Actual free bytes: 208
Aging timer expires in: 1156 secs
Packet: LSP ID: Router-B.02-00, Length: 76 bytes, Lifetime : 1196 secs
Checksum: 0x3c7c, Sequence: 0x1, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
IS neighbor: Router-B.00, Internal, Metric: default 0
IS neighbor: Router-A.00, Internal, Metric: default 0
IS extended neighbor: Router-B.00, Metric: default 0
IS extended neighbor: Router-A.00, Metric: default 0
No queued transmissions
Router-C.00-00 Sequence: 0x5, Checksum: 0x255b, Lifetime: 1182
IS neighbor: Router-C.02
Metric:
Two-way fragment: Router-C.02-00, Two-way first fragment:
IS neighbor: Router-D.03
Metric:
Two-way fragment: Router-D.03-00, Two-way first fragment:
IP prefix: 10.0.0.8/30
Metric:
10
IP prefix: 10.0.0.12/30
Metric:
10
IP prefix: 192.168.0.3/32
Metric:
0

secs
10
Router-C.02-00
10
Router-D.03-00
Internal Up
Internal Up
Internal Up

Header: LSP ID: Router-C.00-00, Length: 208 bytes

Allocated length: 284 bytes, Router ID: 192.168.0.3
Remaining lifetime: 1182 secs, Level: 2, Interface: 102
Estimated free bytes: 114, Actual free bytes: 76
Aging timer expires in: 1182 secs
Protocols: IP, IPv6
Packet: LSP ID: Router-C.00-00, Length: 208 bytes, Lifetime : 1196 secs
Checksum: 0x255b, Sequence: 0x5, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
Area address: 49.0002 (3)
LSP Buffer Size: 1492
Speaks: IP
Speaks: IPV6
IP router id: 192.168.0.3
IP address: 192.168.0.3
Hostname: Router-C
IP prefix: 192.168.0.3/32, Internal, Metric: default 0, Up
IP prefix: 10.0.0.8/30, Internal, Metric: default 10, Up
IP prefix: 10.0.0.12/30, Internal, Metric: default 10, Up
IP extended prefix: 192.168.0.3/32 metric 0 up
IP extended prefix: 10.0.0.8/30 metric 10 up
IP extended prefix: 10.0.0.12/30 metric 10 up
IS neighbor: Router-C.02, Internal, Metric: default 10
IS neighbor: Router-D.03, Internal, Metric: default 10
IS extended neighbor: Router-C.02, Metric: default 10
IP address: 10.0.0.10
Local interface index: 105, Remote interface index: 0
IS extended neighbor: Router-D.03, Metric: default 10

Copyright 2014, Juniper Networks, Inc.

1791

Interfaces Fundamentals for Routing Devices

IP address: 10.0.0.13
Local interface index: 106, Remote interface index: 0
No queued transmissions
Router-C.02-00 Sequence: 0x1, Checksum: 0xaa09, Lifetime: 1181 secs
IS neighbor: Router-B.00
Metric:
0
Two-way fragment: Router-B.00-00, Two-way first fragment: Router-B.00-00
IS neighbor: Router-C.00
Metric:
0
Two-way fragment: Router-C.00-00, Two-way first fragment: Router-C.00-00
Header: LSP ID: Router-C.02-00, Length: 76 bytes
Allocated length: 284 bytes, Router ID: 0.0.0.0
Remaining lifetime: 1181 secs, Level: 2, Interface: 102
Estimated free bytes: 208, Actual free bytes: 208
Aging timer expires in: 1181 secs
Packet: LSP ID: Router-C.02-00, Length: 76 bytes, Lifetime : 1194 secs
Checksum: 0xaa09, Sequence: 0x1, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
IS neighbor: Router-C.00, Internal, Metric: default 0
IS neighbor: Router-B.00, Internal, Metric: default 0
IS extended neighbor: Router-C.00, Metric: default 0
IS extended neighbor: Router-B.00, Metric: default 0
No queued transmissions
Router-D.00-00 Sequence: 0x4, Checksum: 0x8ab7, Lifetime: 1180
IS neighbor: Router-D.02
Metric:
Two-way fragment: Router-D.02-00, Two-way first fragment:
IS neighbor: Router-D.03
Metric:
Two-way fragment: Router-D.03-00, Two-way first fragment:
IP prefix: 10.0.0.12/30
Metric:
10
IP prefix: 10.0.0.20/30
Metric:
10
IP prefix: 192.168.0.4/32
Metric:
0

secs
10
Router-D.02-00
10
Router-D.03-00
Internal Up
Internal Up
Internal Up

Header: LSP ID: Router-D.00-00, Length: 208 bytes

Allocated length: 284 bytes, Router ID: 192.168.0.4
Remaining lifetime: 1180 secs, Level: 2, Interface: 102
Estimated free bytes: 114, Actual free bytes: 76
Aging timer expires in: 1180 secs
Protocols: IP, IPv6
Packet: LSP ID: Router-D.00-00, Length: 208 bytes, Lifetime : 1192 secs
Checksum: 0x8ab7, Sequence: 0x4, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
Area address: 49.0002 (3)
LSP Buffer Size: 1492
Speaks: IP
Speaks: IPV6
IP router id: 192.168.0.4
IP address: 192.168.0.4
Hostname: Router-D
IP prefix: 192.168.0.4/32, Internal, Metric: default 0, Up
IP prefix: 10.0.0.12/30, Internal, Metric: default 10, Up
IP prefix: 10.0.0.20/30, Internal, Metric: default 10, Up
IP extended prefix: 192.168.0.4/32 metric 0 up

1792

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

IP
IP
IS
IS
IS

extended prefix: 10.0.0.12/30 metric 10 up

extended prefix: 10.0.0.20/30 metric 10 up
neighbor: Router-D.02, Internal, Metric: default 10
neighbor: Router-D.03, Internal, Metric: default 10
extended neighbor: Router-D.02, Metric: default 10
IP address: 10.0.0.22
Local interface index: 115, Remote interface index: 0
IS extended neighbor: Router-D.03, Metric: default 10
IP address: 10.0.0.14
Local interface index: 114, Remote interface index: 0
No queued transmissions
Router-D.02-00 Sequence: 0x1, Checksum: 0xebbc, Lifetime: 1128 secs
IS neighbor: Router-D.00
Metric:
0
Two-way fragment: Router-D.00-00, Two-way first fragment: Router-D.00-00
IS neighbor: Router-F.00
Metric:
0
Two-way fragment: Router-F.00-00, Two-way first fragment: Router-F.00-00
Header: LSP ID: Router-D.02-00, Length: 76 bytes
Allocated length: 284 bytes, Router ID: 0.0.0.0
Remaining lifetime: 1128 secs, Level: 2, Interface: 101
Estimated free bytes: 208, Actual free bytes: 208
Aging timer expires in: 1128 secs
Packet: LSP ID: Router-D.02-00, Length: 76 bytes, Lifetime : 1160 secs
Checksum: 0xebbc, Sequence: 0x1, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
IS neighbor: Router-D.00, Internal, Metric: default 0
IS neighbor: Router-F.00, Internal, Metric: default 0
IS extended neighbor: Router-D.00, Metric: default 0
IS extended neighbor: Router-F.00, Metric: default 0
No queued transmissions
Router-D.03-00 Sequence: 0x1, Checksum: 0x129b, Lifetime: 1180 secs
IS neighbor: Router-C.00
Metric:
0
Two-way fragment: Router-C.00-00, Two-way first fragment: Router-C.00-00
IS neighbor: Router-D.00
Metric:
0
Two-way fragment: Router-D.00-00, Two-way first fragment: Router-D.00-00
Header: LSP ID: Router-D.03-00, Length: 76 bytes
Allocated length: 284 bytes, Router ID: 0.0.0.0
Remaining lifetime: 1180 secs, Level: 2, Interface: 101
Estimated free bytes: 208, Actual free bytes: 208
Aging timer expires in: 1180 secs
Packet: LSP ID: Router-D.03-00, Length: 76 bytes, Lifetime : 1192 secs
Checksum: 0x129b, Sequence: 0x1, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
IS neighbor: Router-D.00, Internal, Metric: default 0
IS neighbor: Router-C.00, Internal, Metric: default 0
IS extended neighbor: Router-D.00, Metric: default 0
IS extended neighbor: Router-C.00, Metric: default 0
No queued transmissions
Router-E.00-00 Sequence: 0x4, Checksum: 0x9da9, Lifetime: 1155 secs

Copyright 2014, Juniper Networks, Inc.

1793

Interfaces Fundamentals for Routing Devices

IS neighbor: Router-E.02
Metric:
Two-way fragment: Router-E.02-00, Two-way first fragment:
IS neighbor: Router-F.02
Metric:
Two-way fragment: Router-F.02-00, Two-way first fragment:
IP prefix: 10.0.0.0/30
Metric:
10
IP prefix: 10.0.0.16/30
Metric:
20
IP prefix: 192.168.0.5/32
Metric:
0

10
Router-E.02-00
20
Router-F.02-00
Internal Up
Internal Up
Internal Up

Header: LSP ID: Router-E.00-00, Length: 208 bytes

Allocated length: 284 bytes, Router ID: 192.168.0.5
Remaining lifetime: 1155 secs, Level: 2, Interface: 101
Estimated free bytes: 114, Actual free bytes: 76
Aging timer expires in: 1155 secs
Protocols: IP, IPv6
Packet: LSP ID: Router-E.00-00, Length: 208 bytes, Lifetime : 1185 secs
Checksum: 0x9da9, Sequence: 0x4, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
Area address: 49.0002 (3)
LSP Buffer Size: 1492
Speaks: IP
Speaks: IPV6
IP router id: 192.168.0.5
IP address: 192.168.0.5
Hostname: Router-E
IP prefix: 192.168.0.5/32, Internal, Metric: default 0, Up
IP prefix: 10.0.0.16/30, Internal, Metric: default 20, Up
IP prefix: 10.0.0.0/30, Internal, Metric: default 10, Up
IP extended prefix: 192.168.0.5/32 metric 0 up
IP extended prefix: 10.0.0.16/30 metric 20 up
IP extended prefix: 10.0.0.0/30 metric 10 up
IS neighbor: Router-E.02, Internal, Metric: default 10
IS neighbor: Router-F.02, Internal, Metric: default 20
IS extended neighbor: Router-E.02, Metric: default 10
IP address: 10.0.0.2
Local interface index: 112, Remote interface index: 0
IS extended neighbor: Router-F.02, Metric: default 20
IP address: 10.0.0.17
Local interface index: 111, Remote interface index: 0
No queued transmissions
Router-E.02-00 Sequence: 0x1, Checksum: 0xb4fa, Lifetime: 1130 secs
IS neighbor: Router-A.00
Metric:
0
Two-way fragment: Router-A.00-00, Two-way first fragment: Router-A.00-00
IS neighbor: Router-E.00
Metric:
0
Two-way fragment: Router-E.00-00, Two-way first fragment: Router-E.00-00
Header: LSP ID: Router-E.02-00, Length: 76 bytes
Allocated length: 284 bytes, Router ID: 0.0.0.0
Remaining lifetime: 1130 secs, Level: 2, Interface: 101
Estimated free bytes: 208, Actual free bytes: 208
Aging timer expires in: 1130 secs
Packet: LSP ID: Router-E.02-00, Length: 76 bytes, Lifetime : 1161 secs
Checksum: 0xb4fa, Sequence: 0x1, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0

1794

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

TLVs:
IS neighbor: Router-E.00, Internal, Metric: default 0
IS neighbor: Router-A.00, Internal, Metric: default 0
IS extended neighbor: Router-E.00, Metric: default 0
IS extended neighbor: Router-A.00, Metric: default 0
No queued transmissions
Router-F.00-00 Sequence: 0x5, Checksum: 0x94bd, Lifetime: 1153
IS neighbor: Router-D.02
Metric:
Two-way fragment: Router-D.02-00, Two-way first fragment:
IS neighbor: Router-F.02
Metric:
Two-way fragment: Router-F.02-00, Two-way first fragment:
IP prefix: 10.0.0.16/30
Metric:
10
IP prefix: 10.0.0.20/30
Metric:
10
IP prefix: 192.168.0.6/32
Metric:
0

secs
10
Router-D.02-00
10
Router-F.02-00
Internal Up
Internal Up
Internal Up

Header: LSP ID: Router-F.00-00, Length: 208 bytes

Allocated length: 284 bytes, Router ID: 192.168.0.6
Remaining lifetime: 1153 secs, Level: 2, Interface: 101
Estimated free bytes: 76, Actual free bytes: 76
Aging timer expires in: 1153 secs
Protocols: IP, IPv6
Packet: LSP ID: Router-F.00-00, Length: 208 bytes, Lifetime : 1183 secs
Checksum: 0x94bd, Sequence: 0x5, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
Area address: 49.0002 (3)
LSP Buffer Size: 1492
Speaks: IP
Speaks: IPV6
IP router id: 192.168.0.6
IP address: 192.168.0.6
Hostname: Router-F
IP prefix: 192.168.0.6/32, Internal, Metric: default 0, Up
IP prefix: 10.0.0.16/30, Internal, Metric: default 10, Up
IP prefix: 10.0.0.20/30, Internal, Metric: default 10, Up
IP extended prefix: 192.168.0.6/32 metric 0 up
IP extended prefix: 10.0.0.16/30 metric 10 up
IP extended prefix: 10.0.0.20/30 metric 10 up
IS neighbor: Router-D.02, Internal, Metric: default 10
IS neighbor: Router-F.02, Internal, Metric: default 10
IS extended neighbor: Router-D.02, Metric: default 10
IP address: 10.0.0.21
Local interface index: 94, Remote interface index: 0
IS extended neighbor: Router-F.02, Metric: default 10
IP address: 10.0.0.18
Local interface index: 93, Remote interface index: 0
No queued transmissions
Router-F.02-00 Sequence: 0x1, Checksum: 0xf5ae, Lifetime: 1153 secs
IS neighbor: Router-E.00
Metric:
0
Two-way fragment: Router-E.00-00, Two-way first fragment: Router-E.00-00
IS neighbor: Router-F.00
Metric:
0
Two-way fragment: Router-F.00-00, Two-way first fragment: Router-F.00-00
Header: LSP ID: Router-F.02-00, Length: 76 bytes
Allocated length: 284 bytes, Router ID: 0.0.0.0
Remaining lifetime: 1153 secs, Level: 2, Interface: 101

Copyright 2014, Juniper Networks, Inc.

1795

Interfaces Fundamentals for Routing Devices

Estimated free bytes: 208, Actual free bytes: 208

Aging timer expires in: 1153 secs
Packet: LSP ID: Router-F.02-00, Length: 76 bytes, Lifetime : 1183 secs
Checksum: 0xf5ae, Sequence: 0x1, Attributes: 0x3 <L1 L2>
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
IS neighbor: Router-F.00, Internal, Metric: default 0
IS neighbor: Router-E.00, Internal, Metric: default 0
IS extended neighbor: Router-F.00, Metric: default 0
IS extended neighbor: Router-E.00, Metric: default 0
No queued transmissions

1796

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

show isis hostname

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description

Syntax on page 1797

Syntax (EX Series Switches and QFX Series) on page 1797
show isis hostname
<logical-system (all | logical-system-name)>
show isis hostname

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 12.1 for the QFX Series.
Display IS-IS hostname database information.
This command displays the system ID-to-name cache. The output shows if the mapping
has been learned by receipt of a Hostname TLV #137 (type dynamic) configured in Junos
OS with the set system host-name command, or a static mapping defined in Junos OS
with the set system static-host-mapping hostname sysid command (type static). The
local router always has its type set to static even if static-host-mapping is not configured.

Options

noneDisplay IS-IS hostname database information.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show isis hostname on page 1798

Table 158 on page 1797 describes the output fields for the show isis hostname command.
Output fields are listed in the approximate order in which they appear.

Table 158: show isis hostname Output Fields

Field Name

Field Description

System Id

System identifier mapped to the hostname.

Hostname

Hostname mapped to the system identifier.

Type

Type of mapping between system identifier and hostname.

DynamicHostname mapping determined as described in

RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS.

Copyright 2014, Juniper Networks, Inc.

StaticHostname mapping configured by user.

1797

Interfaces Fundamentals for Routing Devices

Sample Output
show isis hostname
user@host> show isis hostname
IS-IS hostname database:
System Id
Hostname
1921.6800.4201 isis1
1921.6800.4202 isis2
1921.6800.4203 isis3

1798

Type
Dynamic
Static
Dynamic

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

show isis interface

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description

Syntax on page 1799

Syntax (EX Series Switches and QFX Series) on page 1799
show isis interface
<brief | detail | extensive>
<interface-name>
<logical-system (all | logical-system-name)>
show isis interface
<brief | detail | extensive>
<interface-name>

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 12.1 for the QFX Series.
Display status information about IS-IS-enabled interfaces.

NOTE: If the configured metric for an IS-IS level is above 63, and the
wide-metrics-only statement is not configured, the show isis interface detail
command and the show isis interface extensive command display 63 as the
metric value for that level. Configure the wide-metrics-only statement to
generate metric values greater than 63 on a per IS-IS level basis.
The show isis interface command displays the configured metric value for an
IS-IS level irrespective of whether is configured or not.

Options

noneDisplay standard information about all IS-IS-enabled interfaces.

brief | detail | extensive(Optional) Display the specified level of output.
interface-name(Optional) Display information about the specified interface only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

view

Example: Enabling Wide IS-IS Metrics for Traffic Engineering

show isis interface on page 1801

show isis interface brief on page 1802
show isis interface detail on page 1802
show isis interface extensive on page 1802

Copyright 2014, Juniper Networks, Inc.

1799

Interfaces Fundamentals for Routing Devices

Output Fields

Table 159 on page 1800 describes the output fields for the show isis interface command.
Output fields are listed in the approximate order in which they appear.

Table 159: show isis interface Output Fields

Field Name

Field Description

Level of Output

interface-name

Name of the interface.

detail

Designated router

Routing device selected by other routers that is responsible for sending link-state
advertisements that describe the network. Used only on broadcast networks.

detail

Index

Interface index assigned by the Junos OS kernel.

detail

State

Internal implementation information.

detail

Circuit id

Circuit identifier.

detail

Circuit type

Circuit type:

detail

1Level 1 only

2Level 2 only

3Level 1 and Level 2

LSP interval

Interval between link-state PDUs sent from the interface.

detail

CSNP interval

Interval between complete sequence number PDUs sent from the interface.

detail extensive

Sysid

System identifier.

detail

Interface

Interface through which the adjacency is made.

none brief

L or Level

Level:

All levels

1Level 1 only

2Level 2 only

3Level 1 and Level 2

NOTE: The default IS-IS level on loopback interfaces are always same as the
IS-IS level configured on other IS-IS interfaces in a router. You can also configure
IS-IS level on loopback interfaces per your requirement.
CirID

Circuit identifier.

none brief

Level 1 DR

Level 1 designated intermediate system.

none brief

Level 2 DR

Level 2 designated intermediate system.

none brief

L1/L2 Metric

Interface's metric for Level 1 and Level 2. If there is no information, the metric
is 0.

none brief

1800

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 159: show isis interface Output Fields (continued)

Field Name

Field Description

Level of Output

Adjacency
advertisement:
Advertise

This routing device has signaled to advertise this interface to its neighbors in
their label-switched paths (LSPs).

detail extensive

Adjacency
advertisement:
Suppress

This neighbor has signaled not to advertise this interface in the routing devices
outbound LSPs.

detail extensive

Adjacencies

Number of adjacencies established on this interface.

detail

Priority

Priority value for this interface.

detail

Metric

Metric value for this interface.

detail

Hello(s) / Hello
Interval

Interface's hello interval.

detail extensive

Hold(s) / Hold Time

Interface's hold time.

detail extensive

Designated Router

Router responsible for sending network link-state advertisements, which describe

all the routing devices attached to the network.

detail

Hello padding

Type of hello padding:

extensive

AdaptiveOn point-to-point connections, the hello packets are padded from

the initial detection of a new neighbor until the neighbor verifies the adjacency
as Up in the adjacency state TLV. If the neighbor does not support the
adjacency state TLV, then padding continues. On LAN connections, padding
starts from the initial detection of a new neighbor until there is at least one
active adjacency on the interface.

Loose(Default) The hello packet is padded from the initial detection of a

new neighbor until the adjacency transitions to the Up state.

StrictPadding is performed on all interface types and for all adjacency

states, and is continuous.

LDP sync state

Current LDP synchronization state: in sync, in holddown, or not supported.

extensive

reason

Reason for being in the LDP sync state.

extensive

config holdtime

Configured value of the hold timer.

extensive

remaining

If the state is not in sync and the hold time is not infinity, then this field displays
the remaining hold time in seconds.

extensive

Sample Output
show isis interface
user@host> show isis interface

Copyright 2014, Juniper Networks, Inc.

1801

Interfaces Fundamentals for Routing Devices

IS-IS interface database:

Interface
L CirID Level 1 DR
at-2/3/0.0
3
0x1 Point to Point
lo0.0
3
0x1 Passive

Level 2 DR
Point to Point
Passive

L1/L2 Metric
10/10
0/0

show isis interface brief

The output for the show isis interface brief command is identical to that for the show isis
interface command. For sample output, see show isis interface on page 1801.
show isis interface detail
user@host> show isis interface detail
IS-IS interface database:
at-2/3/0.0
Index: 66, State: 0x6, Circuit id: 0x1, Circuit type: 3
LSP interval: 100 ms, CSNP interval: 5 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1
1
64
10
9.000
27
2
1
64
10
9.000
27
lo0.0
Index: 64, State: 0x6, Circuit id: 0x1, Circuit type: 0
LSP interval: 100 ms, CSNP interval: disabled
Adjacency advertisement: Advertise
Protection Type: Node Link, No eligible Backup
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1
0
64
0 Passive
2
0
64
0 Passive

show isis interface extensive

user@host> show isis interface extensive
IS-IS interface database:
xe-6/1/0.0
Index: 75, State: 0x6, Circuit id: 0x1, Circuit type: 2
LSP interval: 100 ms, CSNP interval: 10 s, Loose Hello padding
Adjacency advertisement: Advertise
Level 1
Adjacencies: 0, Priority: 64, Metric: 10
Disabled
Level 2
Adjacencies: 1, Priority: 64, Metric: 10
Hello Interval: 20.000 s, Hold Time: 60 s
Designated Router: nemean.03

1802

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

show isis overview

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

show isis overview

<instance instance-name>
<logical-system (all | logical-system-name)>
show isis overview
<instance instance-name>

Command introduced in Junos OS Release 8.5.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 12.1 for the QFX Series.
Display IS-IS overview information.
noneDisplay standard overview information about IS-IS for all routing instances.
instance instance-name(Optional) Display overview information for the specified routing

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show isis overview on page 1805

Table 160 on page 1803 lists the output fields for the show isis overview command. Output
fields are listed in the approximate order in which they appear.

Table 160: show isis overview Output Fields

Field Name

Field Description

Instance

IS-IS routing intance.

Router ID

Router ID of the routing device.

Adjacency holddown

Adjacency holddown capability: enabled or disabled.

Maximum Areas

Maximum number of IS-IS areas advertised by the routing device.

LSP life time

Lifetime of the link-state PDU, in seconds.

Attached bit evaluation

Attached bit capability: enabled or disabled.

SPF delay

Delay before performing consecutive shortest-path-first (SPF) calculations.

SPF holddown

Delay before performing additional SPF calculations after the maximum number of consecutive SPF
calculations is reached.

Copyright 2014, Juniper Networks, Inc.

1803

Interfaces Fundamentals for Routing Devices

Table 160: show isis overview Output Fields (continued)

Field Name

Field Description

SPF rapid runs

Maximum number of SPF calculations that can be performed in succession before the holddown timer
begins.

Overload bit at startup

is set

Overload bit capability is enabled.

Overload high metrics

Overload high metrics capability: enabled or disabled.

Overload timeout

Time period after which overload is reset and the time that remains before the timer is set to expire.

Traffic engineering

Traffic engineering capability: enabled or disabled.

Restart

Graceful restart capability: enabled or disabled.

Restart duration

Time period for complete reacquisition of IS-IS neighbors.

Helper mode

Graceful restart helper capability: enabled or disabled.

Level

IS-IS level:

1Level 1 information

2Level 2 information

IPv4 is enabled

IP Protocol version 4 capability is enabled.

IPv6 is enabled

IP Protocol version 6 capability is enabled.

CLNS is enabled

(J Series routers only) OSI CLNP capability is enabled.

Internal route
preference

Preference value of internal routes.

External route
preference

Preference value of external routes.

Prefix export limit

Number of prefixes allowed to be exported, as configured by the prefix-export-limit statement.

Prefix export count

Number of prefixes exported.

Wide area metrics are

enabled

Wide area metrics capability is enabled.

Narrow metrics are

enabled

Narrow metrics capability is enabled.

1804

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Sample Output
show isis overview
user@host> show isis overview
Instance: master
Router ID: 10.255.107.183
Adjacency holddown: disabled
Maximum Areas: 3
LSP life time: 1200
Attached bit evaluation: enabled
SPF delay: 200 msec, SPF holddown: 5000 msec, SPF rapid runs: 3
IPv4 is enabled, IPv6 is enabled
Traffic engineering: enabled
Restart: Disabled
Helper mode: Enabled
Level 1
Internal route preference: 15
External route preference: 160
Wide metrics are enabled, Narrow metrics are enabled
Level 2
Internal route preference: 18
External route preference: 165
Prefix export limit: 5, Prefix export count: 5
Wide metrics are enabled

Copyright 2014, Juniper Networks, Inc.

1805

Interfaces Fundamentals for Routing Devices

show isis route

List of Syntax

Syntax on page 1806

Syntax (EX Series Switches and QFX Series) on page 1806

Syntax

show isis route

<destination>
<inet | inet6>
<instance instance-name>
<logical-system (all | logical-system-name)>
<topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)>

Syntax (EX Series

Switches and QFX
Series)

show isis route

<destination>
<inet | inet6>
<instance instance-name>
<topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)>

Release Information

Description
Options

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 12.1 for the QFX Series.
Display the routes in the IS-IS routing table.
noneDisplay all routes in the IS-IS routing table for all supported address families for

all routing instances.

destination(Optional) Destination address for the route.
inet | inet6(Optional) Display inet (IPv4) or inet6 (IPv6) routes, respectively.
instance instance-name(Optional) Display routes for the specified routing instance only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)(Optional) Display

routes for the specified topology only, or use unicast to display information, if
available, for both IPv4 and IPv6 unicast topologies.
Required Privilege
Level
List of Sample Output

Output Fields

1806

view

show isis route logical-system on page 1807

show isis route (CLNS) on page 1807
show isis route on page 1808
Table 161 on page 1807 describes the output fields for the show isis route command. Output
fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 161: show isis route Output Fields

Field Name

Field Description

Current version

Number of the current version of the IS-IS routing table.

L1

Version of Level 1 SPF that was run.

L2

Version of Level 2 SPF that was run.

Prefix

Destination of the route.

IS-IS level:

1Level 1 only

2Level 2 only

3Level 1 and Level 2

Version

Version of SPF that generated the route.

Metric

Metric value associated with the route.

Type

Metric type: int (internal) or ext (external).

Interface

Interface to the next hop.

Via

System identifier of the next hop, displayed as a name if possible.

ISO Routes

ISO routing table entries.

snpa

MAC address.

Sample Output
show isis route logical-system
user@host> show isis route logical-system ls1
IS-IS routing table
Current version: L1: 8 L2: 11
Prefix
L Version Metric Type Interface
Via
10.9.7.0/30
2
11
20 int gr-0/2/0.0
h
10.9.201.1/32
2
11
60 int gr-0/2/0.0
h
IPV6 Unicast IS-IS routing table
Current version: L1: 9 L2: 11
Prefix
L Version Metric Type Interface
Via
8009:3::a09:3200/126 2
11
20 int gr-0/2/0.0 h

show isis route (CLNS)

user@host> show isis route
IS-IS routing table
Current version: L1: 10 L2: 8
IPv4/IPv6 Routes
Prefix
L Version
Metric Type Interface
Via
0.0.0.0/0
1
10
10 int fe-0/0/1.0
ISIS.0
ISO Routes
Prefix L
Version
Metric Type Interface
Via
snpa

Copyright 2014, Juniper Networks, Inc.

1807

Interfaces Fundamentals for Routing Devices

0/0
1
10
10 int fe-0/0/1.0
isis.0 0:12:0:34:0:56
47.0005.80ff.f800.0000.0108.0001/104
1
10
0 int
47.0005.80ff.f800.0000.0108.0001.1921.6800.4001/152
1
10
10 int fe-0/0/1.0 isis.0 0:12:0:34:0:56
47.0005.80ff.f800.0000.0108.0001.1921.6800.4002/152
1
10
20 int fe-0/0/1.0 isis.0 0:12:0:34:0:56
47.0005.80ff.f800.0000.0108.0002/104
1
10
0 int
47.0005.80ff.f800.0000.0108.0002.1921.6800.4001/152
1
10
10 int fe-0/0/1.0 isis.0 0:12:0:34:0:56

show isis route

user@host> show isis route
IS-IS routing table
IPv4/IPv6 Routes
---------------Prefix
10.255.71.52/32

L
2

Version
13

10.255.71.238/32

13

10.255.71.239/32

13

Metric Type Interface

10
int ae0.0
20

20

int

int

NH
Via
IPV4 camaro

so-6/0/0.0

IPV4 olympic

as0.0

IPV4 glacier

so-6/0/0.0

IPV4 olympic

ae0.0

IPV4 camaro

10.255.71.242/32

13

10

int

as0.0

IPV4 glacier

10.255.71.243/32

13

10

int

so-6/0/0.0

IPV4 olympic

12.13.0.0/30

13

20

int

so-6/0/0.0

IPV4 olympic

12.15.0.0/30

13

20

int

so-6/0/0.0

IPV4 olympic

13.15.0.0/30

13

30

int

ae0.0

IPV4 camaro

so-6/0/0.0

IPV4 olympic

as0.0

IPV4 glacier

13.16.0.0/30

13

25

int

as0.0

IPV4 glacier

14.15.0.0/30

13

20

int

ae0.0

IPV4 camaro

192.2.1.0/30

13

30

int

so-6/0/0.0

IPV4 olympic

as0.0

IPV4 glacier

so-6/0/0.0

IPV6 olympic

as0.0

IPV6 glacier

1eee::/64

1808

Current version: L1: 4 L2: 13

13

30

int

abcd::10:255:71:52/128

13

10

int

ae0.0

IPV6 camaro

abcd::10:255:71:238/128

13

20

int

so-6/0/0.0

IPV6 olympic

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

abcd::10:255:71:239/128

13

20

int

as0.0

IPV6 glacier

so-6/0/0.0

IPV6 olympic

ae0.0

IPV6 camaro

abcd::10:255:71:242/128

13

10

int

as0.0

IPV6 glacier

abcd::10:255:71:243/128

13

10

int

so-6/0/0.0

IPV6 olympic

Copyright 2014, Juniper Networks, Inc.

1809

Interfaces Fundamentals for Routing Devices

show isis spf

List of Syntax

Syntax on page 1810

Syntax (EX Series Switches) on page 1810

Syntax

show isis spf (brief | log | results)

<instance instance-name>
<level (1 | 2)>
<logical-system (all | logical-system-name)>
<topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)>

Syntax (EX Series

Switches)

show isis spf (brief | log | results)

<instance instance-name>
<level (1 | 2)>
<topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)>

Release Information

Description
Options

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display information about IS-IS shortest-path-first (SPF) calculations.
briefDisplay an overview of SPF calculations.
instance instance instance-name(Optional) Display SPF calculations for the specified

routing instance.
level (1 | 2)(Optional) Display SPF calculations for the specified IS-IS level.
logDisplay the log of SPF calculations.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

resultsDisplay the results of SPF calculations.
topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)(Optional) Display

SPF calculations for the specified topology only.

Required Privilege
Level
List of Sample Output

Output Fields

view

show isis spf log on page 1811

show isis spf results logical-system on page 1812
show isis spf results (CLNS) on page 1813
Table 162 on page 1810 describes the output fields for the show isis spf command. Output
fields are listed in the approximate order in which they appear.

Table 162: show isis spf Output Fields

1810

Field Name

Field Description

Node

System ID of a node.

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Table 162: show isis spf Output Fields (continued)

Field Name

Field Description

Metric

Metric to the node.

Interface

Interface of the next hop.

Via

System ID of the next hop.

SNPA

Subnetwork point of attachment (MAC address of the next hop).

Start time

(log option only) Time that the SPF computation started.

Elapsed (secs)

(log option only) Length of time, in seconds, required to complete

the SPF computation.

Count

(log option only) Number of times the SPF was triggered.

Reason

(log option only) Reason that the SPF computation was completed.

Sample Output
show isis spf log
user@host> show isis spf log logical-system lsl
IS-IS level 1 SPF log:
Start time
Elapsed (secs) Count
Fri Oct 31 12:41:18
0.000069
1
Fri Oct 31 12:41:18
0.000107
3
Fri Oct 31 12:41:18
0.000050
3
Fri Oct 31 12:41:23
0.000033
1
Fri Oct 31 12:41:28
0.000178
5
Fri Oct 31 12:41:59
0.000060
1
Fri Oct 31 12:42:30
0.000161
2
Fri Oct 31 12:56:58
0.000198
1
Fri Oct 31 13:10:29
0.000209
1
IS-IS level 2 SPF log:
Start time
Elapsed (secs) Count
Fri Oct 31 12:41:18
0.000035
1
Fri Oct 31 12:41:18
0.000047
2
Fri Oct 31 12:41:18
0.000043
5
Fri Oct 31 12:41:23
0.000022
1
Fri Oct 31 12:41:59
0.000144
3
Fri Oct 31 12:42:30
0.000257
3
Fri Oct 31 12:54:37
0.000195
1
Fri Oct 31 12:55:50
0.000178
1
Fri Oct 31 12:55:55
0.000174
1
Fri Oct 31 12:55:58
0.000176
1
Fri Oct 31 13:08:14
0.000198
1
IPV6 Unicast IS-IS level 1 SPF log:

Reason
Reconfig
Updated LSP fix.00-00
Address change on so-1/2/2.0
Updated LSP fix.00-00
New adjacency scat on ge-1/1/0.0
Updated LSP fix.00-00
Multi area attachment change
Periodic SPF
Periodic SPF

Reason
Reconfig
Updated LSP fix.00-00
Address change on gr-0/2/0.0
Updated LSP fix.00-00
New adjacency h on gr-0/2/0.0
New LSP skag.00-00
Periodic SPF
Updated LSP fix.00-00
Updated LSP h.00-00
Updated LSP skag.00-00
Periodic SPF

Start time
Elapsed (secs) Count Reason
Fri Oct 31 12:41:18
0.000028
1 Reconfig
Fri Oct 31 12:41:18
0.000043
3 Updated LSP fix.00-00

Copyright 2014, Juniper Networks, Inc.

1811

Interfaces Fundamentals for Routing Devices

Fri Oct 31 12:41:18

Fri Oct 31 12:41:23
Fri Oct 31 12:41:25
Fri Oct 31 12:41:28
Fri Oct 31 12:41:59
Fri Oct 31 12:42:30
Fri Oct 31 12:56:08
Fri Oct 31 13:11:07
IPV6 Unicast IS-IS level 2
Start time
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
...

12:41:18
12:41:18
12:41:18
12:41:23
12:41:25
12:41:59
12:42:30
12:55:50
12:55:55
12:55:58
13:09:46

0.000112
0.000059
0.000041
0.000103
0.000040
0.000118
0.000289
0.000214
SPF log:

4
1
1
5
1
2
1
1

Elapsed (secs) Count

0.000027
1
0.000039
2
0.000049
6
0.000025
1
0.000023
1
0.000087
3
0.000123
3
0.000121
1
0.000121
1
0.000121
1
0.000201
1

Updated LSP fix.00-00

Updated LSP fix.00-00
Updated LSP fix.00-00
New adjacency scat on ge-1/1/0.0
Updated LSP fix.00-00
Multi area attachment change
Periodic SPF
Periodic SPF

Reason
Reconfig
Updated LSP fix.00-00
Updated LSP fix.00-00
Updated LSP fix.00-00
Updated LSP fix.00-00
New adjacency h on gr-0/2/0.0
New LSP skag.00-00
Updated LSP fix.00-00
Updated LSP h.00-00
Updated LSP skag.00-00
Periodic SPF

show isis spf results logical-system

user@host> show isis spf results logical-system ls1
IS-IS level 1 SPF results:
Node
Metric
Interface
scat.00
10
ge-1/1/0.0
20
10.9.1.0/30
fix.02
10
fix.00
0
10
10.9.1.0/30
10
10.9.5.0/30
10
10.9.6.0/30
20
10.9.7.0/30
60
10.9.201.1/32
3 nodes
IS-IS level 2 SPF results:
Node
Metric
skag.00
20
30
skag.02
20
h.00
10
20
20
60
fix.00
0
10
10
10
4 nodes

Interface
gr-0/2/0.0
10.9.7.0/30
gr-0/2/0.0
gr-0/2/0.0
10.9.6.0/30
10.9.7.0/30
10.9.201.1/32

Via
scat

Via

SNPA

h
h
h

10.9.1.0/30
10.9.5.0/30
10.9.6.0/30

IPV6 Unicast IS-IS level 1 SPF results:

Node
Metric
Interface
Via
scat.00
10
ge-1/1/0.0
scat
ge-1/1/0.0
scat
20
8009:1::a09:1400/126
fix.02
10

1812

SNPA
0:90:69:a6:48:9d

SNPA
0:90:69:a6:48:9d
0:90:69:a6:48:9d

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

fix.00

0
10
10
20
10

8009:1::a09:1400/126
8009:2::a09:1e00/126
8009:3::a09:3200/126
8009:4::a09:2800/126

3 nodes
IPV6 Unicast IS-IS level 2 SPF results:
Node
Metric
Interface
Via
skag.00
20
gr-0/2/0.0
h
gr-0/2/0.0
h
30
8009:3::a09:3200/126
skag.02
20
gr-0/2/0.0
h
gr-0/2/0.0
h
h.00
10
gr-0/2/0.0
h
gr-0/2/0.0
h
20
8009:3::a09:3200/126
20
8009:4::a09:2800/126
fix.00
0
10
8009:1::a09:1400/126
10
8009:2::a09:1e00/126
10
8009:4::a09:2800/126
4 nodes
Multicast IS-IS level 1 SPF results:
Node
Metric
Interface
scat.00
10
ge-1/1/0.0
fix.02
10
fix.00
0
3 nodes
Multicast IS-IS level 2 SPF results:
Node
Metric
Interface
skag.00
20
gr-0/2/0.0
skag.02
20
gr-0/2/0.0
h.00
10
gr-0/2/0.0
fix.00
0
4 nodes
...

Via
scat

Via

SNPA

SNPA
0:90:69:a6:48:9d

SNPA

h
h
h

show isis spf results (CLNS)

user@host> show isis spf results
IS-IS level 1 SPF results:
Node
Metric
Interface
Via
skag.00 10
fe-0/0/1.0
toothache
fe-0/0/1.0
toothache
20
192.168.37.64/29
10
1921.6800.4001
20
1921.6800.4002
pro1-a.02
10
pro1-a.00
0
0
10.255.245.1/32
10
192.168.37.64/29
0
1921.6800.4211
3 nodes
IS-IS level 2 SPF results:
Node
Metric
skag.00 10

Copyright 2014, Juniper Networks, Inc.

Interface
fe-0/0/1.0
fe-0/0/1.0

Via
toothache
toothache

SNPA
0:12:0:34:0:56
0:12:0:34:0:56

SNPA
0:12:0:34:0:56
0:12:0:34:0:56

1813

Interfaces Fundamentals for Routing Devices

pro1-a.02
pro1-a.00

20
20
20
10
0
0
10

10.255.245.1/32
192.168.37.64/29
47.0005.80ff.f800.0000.0109.0010/104

10.255.245.1/32
192.168.37.64/29

3 nodes

1814

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

show isis statistics

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

Syntax on page 1815

Syntax (EX Series Switches and QFX Series) on page 1815
show isis statistics
<instance instance-name>
<logical-system (all | logical-system-name)>
show isis statistics
<instance instance-name>

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 12.1 for the QFX Series.
Display statistics about IS-IS traffic.
noneDisplay IS-IS traffic statistics for all routing instances.
instance instance-name(Optional) Display statistics for the specified routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

clear isis statistics on page 1768

show isis statistics on page 1817

Table 163 on page 1816 describes the output fields for the show isis statistics command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1815

Interfaces Fundamentals for Routing Devices

Table 163: show isis statistics Output Fields

Field Name

Field Description

PDU type

PDU type:

CSNPComplete sequence number PDUs contain a complete list of all link-state PDUs in the IS-IS

database. CSNPs are sent periodically on all links, and the receiving systems use the information
in the CSNP to update and synchronize their link-state PDU databases. The designated router
multicasts CSNPs on broadcast links in place of sending explicit acknowledgments for each
link-state PDU.

IIHIS-IS hello packets are broadcast to discover the identity of neighboring IS-IS systems and to

determine whether the neighbors are Level 1 or Level 2 intermediate systems.

LSPLink-state PDUs contain information about the state of adjacencies to neighboring IS-IS

systems. Link-state PDUs are flooded periodically throughout an area.

PSNPPartial sequence number PDUs are sent multicast by a receiver when it detects that it is

missing a link-state PDU (when its link-state PDU database is out of date). The receiver sends a
PSNP to the system that transmitted the CSNP, effectively requesting that the missing link-state
PDU be transmitted. That routing device, in turn, forwards the missing link-state PDU to the
requesting routing device.

UnknownThe PDU type is unknown.

Received

Number of PDUs received since IS-IS started or since the statistics were set to zero.

Processed

Number of PDUs received less the number dropped.

Drops

Number of PDUs dropped.

Sent

Number of PDUs transmitted since IS-IS started or since the statistics were set to zero.

Rexmit

Number of PDUs retransmitted since IS-IS started or since the statistics were set to zero.

Total packets
received/sent

Total number of PDUs received and transmitted since IS-IS started or since the statistics were set to
zero.

SNP queue length

Number of CSPN and PSNP packets currently waiting in the queue for processing. This value is almost
always 0.

LSP queue length

Number of link-state PDUs waiting in the queue for processing. This value is almost always 0.

SPF runs

Number of shortest-path-first (SPF) calculations that have been performed. If this number is
incrementing rapidly, it indicates that the network is unstable.

Fragments rebuilt

Number of link-state PDU fragments that the local system has computed.

LSP regenerations

Number of link-state PDUs that have been regenerated. A link-state PDU is regenerated when it is
nearing the end of its lifetime and it has not changed.

Purges initiated

Number of purges that the system initiated. A purge is initiated if the software decides that a link-state
PDU must be removed from the network.

1816

Copyright 2014, Juniper Networks, Inc.

Chapter 21: IS-IS Operational Commands

Sample Output
show isis statistics
user@host> show isis statistics
IS-IS statistics for merino:
PDU type
LSP
IIH
CSNP
PSNP
Unknown
Totals

Received
12227
113808
198868
6985
0
331888

Processed
12227
113808
198868
6979
0
331882

Drops
0
0
0
6
0
6

Sent
8184
115817
198934
8274
0
331209

Rexmit
683
0
0
0
0
683

Total packets received: 331888 Sent: 331892

SNP queue length:
LSP queue length:
SPF runs:
Fragments rebuilt:
LSP regenerations:
Purges initiated:

Copyright 2014, Juniper Networks, Inc.

0 Drops:
0 Drops:

0
0

1014
1038
425
0

1817

Interfaces Fundamentals for Routing Devices

1818

Copyright 2014, Juniper Networks, Inc.

CHAPTER 22

LLDP Operational Commands

clear lldp neighbor

clear lldp statistics

show lldp

show lldp local-information

show lldp neighbors

show lldp remote-global-statistics

show lldp statistics

Copyright 2014, Juniper Networks, Inc.

1819

Interfaces Fundamentals for Routing Devices

clear lldp neighbor

Syntax

Release Information
Description

clear lldp neighbor

<interface interface-name>

Command introduced in Junos OS Release 9.6.

On MX Series and T Series routers, clear information regarding all Link Layer Discovery
Protocol (LLDP) neighbors or LLDP neighbors of the specified interface.
For information about interface names, see Interface Naming Overview on page 26. For
information about interface names for TX Matrix routers, see TX Matrix Router Chassis
and Interface Names. For information about FPC numbering on TX Matrix routers, see
Routing Matrix with a TX Matrix Router FPC Numbering.

Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

interface interface-name(Optional) Clear the LLDP neighbors on the specified interface.

clear

clear lldp statistics on page 1821

clear lldp statistics on page 1820

When you enter this command, you are provided no feedback on the status of your
request. You can enter the show lldp neighbors command before and after clearing the
LLDP neighbors to verify the clear operation.

Sample Output
clear lldp statistics
user@host> clear lldp statistics
user@host> clear lldp statistics interface ge-0/2/0

1820

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

clear lldp statistics

Syntax

Release Information
Description

clear lldpp neighbor

<interface interface-name>

Command introduced in Junos OS Release 9.6.

On MX Series and T Series routers, clear all Link Layer Discovery Protocols (LLDP)
statistics or LLDP statistics associated with the specified interface.
For information about interface names, see Interface Naming Overview on page 26. For
information about interface names for TX Matrix routers, see TX Matrix Router Chassis
and Interface Names. For information about FPC numbering on TX Matrix routers, see
Routing Matrix with a TX Matrix Router FPC Numbering.

Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

interface interface-name(Optional) Clear LLDP statistics on the specified interface.

clear

clear lldp neighbor on page 1820

clear lldp neighbor on page 1821

When you enter this command, you are provided no feedback on the status of your
request. You can enter the show lldp statistics command before and after clearing the
LLDP statistics to verify the clear operation.

Sample Output
clear lldp neighbor
user@host> clear lldp neighbors
user@host> clear lldp neighbors interface ge-0/2/2

Copyright 2014, Juniper Networks, Inc.

1821

Interfaces Fundamentals for Routing Devices

show lldp
Syntax

Release Information
Description

Options
Required Privilege
Level
List of Sample Output

Output Fields

show lldp
<detail>

Command introduced in Junos OS Release 9.6.

On MX Series and T Series routers, display information about the Link Layer Discovery
Protocol (LLDP).
detail(Optional) Display the detailed output level.

view

show lldp on page 1824

show lldp detail on page 1824
Table 164 on page 1822 describes the output fields for the show lldp command. Output
fields are listed in the approximate order in which they appear.

Table 164: show lldp Output Fields

Field Name

Field Description

LLDP

Status of LLDP: Enabled or Disabled.

Advertisement
interval

Value of the advertisement interval parameter.

Transmit delay

Value of the transmit delay parameter.

Hold timer

Value of the hold timer parameter.

Notification interval

Value of the notification interval parameter.

Config Trap Interval

Value of the configuration trap parameter.

Connection Hold
timer

Value of the connection hold timer parameter.

Interface

List of LLDP interfaces, showing status (Enabled or Disabled) and Neighbor count
(detail only).
For information about interface names, see Interface Naming Overview on
page 26. For information about interface names for TX Matrix routers, see TX
Matrix Router Chassis and Interface Names. For information about FPC numbering
on TX Matrix routers, see Routing Matrix with a TX Matrix Router FPC Numbering.

LLDP basic TLVs

supported

1822

List of basic LLDP TLVs supported by this device (detail only).

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

Table 164: show lldp Output Fields (continued)

Field Name

Field Description

LLDP 802 TLVs

supported

List of IEEE 802.1 LLDP TLVs supported by this device (detail only).

Copyright 2014, Juniper Networks, Inc.

1823

Interfaces Fundamentals for Routing Devices

Sample Output
show lldp
user@host> show lldp
LLDP
Advertisement interval
Transmit delay
Hold timer
Notification interval
Config Trap Interval
Connection Hold timer

:
:
:
:
:
:
:

Enabled
30 Second(s)
2 Second(s)
4 Second(s)
30 Second(s)
300 Second(s)
60 Second(s)

user@host> show lldp detail

LLDP
:
Advertisement interval :
Transmit delay
:
Hold timer
:
Notification interval :
Config Trap Interval
:
Connection Hold timer :

Enabled
30 Second(s)
2 Second(s)
4 Second(s)
30 Second(s)
300 Second(s)
60 Second(s)

Interface
ge-0/0/0
ge-0/0/1
ge-0/0/4

LLDP
Enabled
Enabled
Enabled

Sample Output
show lldp detail

Interface
ge-0/0/0
ge-0/0/1
ge-0/0/4

LLDP
Enabled
Enabled
Enabled

Neighbor count
0
0
0

LLDP basic TLVs supported:

Chassis identifier, Port identifier, Port description, System name, System
description, System capabilities, Management address.
LLDP 802 TLVs supported:
Link aggregation, Maximum frame size, MAC/PHY Configuration/Status, Port VLAN ID,
Port VLAN name.

1824

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

show lldp local-information

Syntax
Release Information
Description

Options
Required Privilege
Level
List of Sample Output

Output Fields

show lldp local-information

Command introduced in Junos OS Release 9.6.

On MX Series and T Series routers, display local Link Layer Discovery Protocol (LLDP)
information.
This command has no options.
view

show lldp local-information(Management Information Address Subtype is

IPv4) on page 1827
show lldp local-information(Management Information Address Subtype is
IPv6) on page 1827
Table 165 on page 1825 describes the output fields for the show lldp local-information
command. Output fields are listed in the approximate order in which they appear.

Table 165: show lldp local-information Output Fields

Field Name

Field Description

LLDP Local
Information details

Information that follows pertains to the local system.

Chassis ID

List of chassis identifiers for local information.

System name

Local system name reported by LLDP.

System descr

Local system description reported by LLDP.

System Capabilities

Capabilities (such as Bridge or Router) that are Supported or Enabled by system

on the interface.

Management
Information

Listed by Interface Name, Address Subtype (such as ipv4, ipv6), Address (such
as 192.168.168.229, 1fd::1a10), Interface Number, and Interface Numbering Subtype.

Interface Name

List of local interfaces.

For information about interface names, see Interface Naming Overview on
page 26. For information about interface names for TX Matrix routers, see TX
Matrix Router Chassis and Interface Names. For information about FPC numbering
on TX Matrix routers, see Routing Matrix with a TX Matrix Router FPC Numbering.

Parent Interface

Name of the ae interface to which the interface belongs

Interface ID

List of local interface identifiers.

Copyright 2014, Juniper Networks, Inc.

1825

Interfaces Fundamentals for Routing Devices

Table 165: show lldp local-information Output Fields (continued)

1826

Field Name

Field Description

Interface
Description

List of local interface descriptions.

Status

List of interface conditions: UP or DOWN.

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

Sample Output
show lldp local-information(Management Information Address Subtype is IPv4)
user@host> show lldp local-information
LLDP Local Information details
Chassis ID
: 64:87:88:65:37:c0
System name : apg-hp1
System descr : Juniper Networks, Inc. mx240 , version 14.1I20131231_0701_builder
[builder] Build date: 2013-12-31 07:13:42 UTC
System Capabilities
Supported
: Bridge Router
Enabled
: Bridge Router
Management Information
Interface Name : Unknown
Address Subtype : IPv4(1)
Address
: 10.216.97.103
Interface Number
: 1
Interface Numbering Subtype
: ifIndex(2)
Interface name
fxp0
me0
ge-2/0/0
ge-2/0/1

Parent Interface
ae0
ae0

Interface ID
1
33
1475
1476

Interface description
fxp0
me0
ge-2/0/0
ge-2/0/1

Status
Up
Up
Up
Up

show lldp local-information(Management Information Address Subtype is IPv6)

user@host> show lldp local-information
LLDP Local Information details
Chassis ID
: ac:4b:c8:92:67:c0
System name : apg-hp
System descr : Juniper Networks, Inc. mx240 , version 13.2-20131210.0 [builder]
Build date: 2013-12-10 06:23:15 UTC
System Capabilities
Supported
: Bridge Router
Enabled
: Bridge Router
Management Information
Interface Name : fxp0
Address Subtype : IPv6(2)
Address
: 1fd::1a20
Interface Number
Interface Numbering Subtype
Interface name
ge-1/2/4
ge-1/2/5
ge-1/2/2
ge-1/2/3

Copyright 2014, Juniper Networks, Inc.

Parent Interface
-

: 1
: ifIndex(2)
Interface ID
530
531
528
529

Interface description
ge-1/2/2
ge-1/2/3

Status
Down
Down
Up
Up

1827

Interfaces Fundamentals for Routing Devices

show lldp neighbors

Syntax

Release Information
Description

show lldp neighbors

<interface interface-name>

Command introduced in Junos OS Release 9.6.

On MX Series and T Series routers, display information about LLDP neighbors.
For information about interface names, see Interface Naming Overview on page 26. For
information about interface names for TX Matrix routers, see TX Matrix Router Chassis
and Interface Names. For information about FPC numbering on TX Matrix routers, see
Routing Matrix with a TX Matrix Router FPC Numbering.

Options

interface interface-name(Optional) Display the neighbor information about a particular

physical interface.

NOTE: Starting with Junos OS Release 14.2, you can also display LLDP
neighbor details for management interfaces, such as fxp or me, on MX
Series routers.

Required Privilege
Level
Related
Documentation

view

clear lldp neighbor on page 1820

List of Sample Output

show lldp neighbors on page 1831

show lldp neighbors interface ge-0/0/4 (Management Address is IPv4) on page 1831
show lldp neighbors interface ge-0/0/4 (Management Address is IPv6) on page 1832
show lldp neighbors (Management Ethernet Interfaces) on page 1833

Output Fields

Table 166 on page 1828 describes the output fields for the show lldp neighbors command.
Output fields are listed in the approximate order in which they appear.

Table 166: show lldp neighbors Output Fields

1828

Field Name

Field Description

LLDP Remote
Devices Information

Information about remote devices.

LocalInterface

List of local interfaces for which neighbor information is available.

ChassisId

List of chassis identifiers for neighbors.

PortInfo

List of port information gathered from neighbors. This could be the port
identifier or port description.

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

Table 166: show lldp neighbors Output Fields (continued)

Field Name

Field Description

SysName

List of system names gathered from neighbors.

LLDP Neighbor
Information

Information about both local and neighbor systems on the interface (appears
when the interface option is used).

Local Information

Information about local systems on the interface (appears when the interface
option is used).

Neighbor
Information

Information about both local and neighbor system on the interface (appears
when the interface option is used).

Index

Local interface index (appears when the interface option is used).

Time Mark

Date and timestamp of information (appears when the interface option is

used).

Time To Live

Number of seconds for which this information is valid (appears when the
interface option is used).

Local Interface

Name of the local physical interface (appears when the interface option is
used).

Parent Interface

Name of the ae interface to which the interface belongs

Local Port ID

Local port identifier (appears when the interface option is used).

Neighbor
Information

Information about neighbor systems on the interface (appears when the

interface option is used).

Chassis type

Type of chassis identifier supplied, such as MAC address (appears when the
interface option is used).

Chassis ID

Chassis identifier of type listed (appears when the interface option is used).

Port type

Type of port identifier supplied, such as local (appears when the interface
option is used).

Port ID

Port identifier of type listed (appears when the interface option is used).

Port description

Port description (appears when the interface option is used).

System name

Name supplied by the system on the interface (appears when the interface
option is used).

System Description

Description supplied by the system on the interface (appears when the

interface option is used).

System Capabilities

Capabilities (such as bridge or router) that are Supported or Enabled by the

system on the interface (appears when the interface option is used).

Copyright 2014, Juniper Networks, Inc.

1829

Interfaces Fundamentals for Routing Devices

Table 166: show lldp neighbors Output Fields (continued)

1830

Field Name

Field Description

Management
address

Details of the management address: Address Type (such as ipv4 and ipv6),
Address (such as 10.204.34.35, 1fd::1a10), Interface Number, Interface Subtype,
and Organization Identifier (OID) (appears when the interface option is used).

Organization Info

One or more entries listing remote information by Organizationally Unique

Identifier (OUI), Subtype, Index, and Info (appears when the interface option
is used).

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

Sample Output
show lldp neighbors
user@host> show lldp neighbors
Local Interface
ge-2/0/0
ge-2/0/1

Parent Interface
ae0
ae0

Chassis Id
ac:4b:c8:92:67:c0
ac:4b:c8:92:67:c0

Port info
528
529

System Name
apg-hp
apg-hp

Sample Output
show lldp neighbors interface ge-0/0/4 (Management Address is IPv4)
user@host> show lldp neighbors interface ge-0/0/4
LLDP Neighbor Information:
Local Information:
Index: 2 Time to live: 120 Time mark: Tue Dec 31 11:47:46 2013 Age: 15 secs
Local Interface
: ge-2/0/1
Parent Interface
: ae0
Local Port ID
: 1476
Ageout Count
: 0
Neighbour Information:
Chassis type
: Mac address
Chassis ID
: ac:4b:c8:92:67:c0
Port type
: Locally assigned
Port ID
: 529
Port description
: ge-1/2/3
System name
: apg-hp
System Description : Juniper Networks, Inc. mx240 , version 14.1-20131222.0
[builder] Build date: 2013-12-22 09:13:26 UTC

System capabilities
Supported: Bridge Router
Enabled : Bridge Router
Management address
Address Type
Address
Interface Number
Interface Subtype
OID

:
:
:
:
:

IPv4(1)
10.216.98.57
1
ifIndex(2)
1.3.6.1.2.1.31.1.1.1.1.1.

Organization Info
OUI
: IEEE 802.3 Private (0x00120f)
Subtype : MAC/PHY Configuration/Status (1)
Info
: Autonegotiation [supported, enabled (0x3)], PMD Autonegotiation
Capability (0x1d), MAU Type (0x0)
Index
: 1
Organization Info
OUI
:
Subtype :
Info
:
Index
:

IEEE 802.3 Private (0x00120f)

Link Aggregation (3)
Aggregation Status (0x3), Aggregation Port ID (1694498816)
2

Organization Info
OUI
: IEEE 802.3 Private (0x00120f)

Copyright 2014, Juniper Networks, Inc.

1831

Interfaces Fundamentals for Routing Devices

Subtype
Info
Index

: Maximum Frame Size (4)

: MTU Size (1518)
: 3

show lldp neighbors interface ge-0/0/4 (Management Address is IPv6)

user@host> show lldp neighbors interface ge-0/0/4
LLDP Neighbor Information:
Local Information:
Index: 1 Time to live: 120 Time mark: Thu Dec 12 07:19:45 2013 Age: 28 secs
Local Interface
: ge-1/2/2
Parent Interface
: Local Port ID
: 528
Ageout Count
: 0
Neighbour Information:
Chassis type
: Mac address
Chassis ID
: 64:87:88:65:37:c0
Port type
: Locally assigned
Port ID
: 1475
Port description
: ge-2/0/0
System name
: apg-hp1
System Description : Juniper Networks, Inc. mx240 , version 11.4R10 Build date:
2013-10-24 10:10:02 UTC

System capabilities
Supported: Bridge Router
Enabled : Bridge Router
Management address
Address Type
Address
Interface Number
Interface Subtype
OID

:
:
:
:
:

IPv6(2)
1fd::1a10
1
ifIndex(2)
1.3.6.1.2.1.31.1.1.1.1.1.

Organization Info
OUI
: IEEE 802.3 Private (0x00120f)
Subtype : MAC/PHY Configuration/Status (1)
Info
: Autonegotiation [supported, enabled (0x3)], PMD Autonegotiation
Capability (0x5), MAU Type (0x0)
Index
: 1
Organization Info
OUI
:
Subtype :
Info
:
Index
:

IEEE 802.3 Private (0x00120f)

Link Aggregation (3)
Aggregation Status (0x1), Aggregation Port ID (0)
2

Organization Info
OUI
:
Subtype :
Info
:
Index
:

IEEE 802.3 Private (0x00120f)

Maximum Frame Size (4)
MTU Size (1518)
3

Organization Info
OUI
: Ethernet Bridged (0x0080c2)
Subtype : VLAN Name (3)

1832

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

Info
Index

: VLAN ID (100), VLAN Name (vlan-100)

: 4

show lldp neighbors (Management Ethernet Interfaces)

user@host> show lldp neighbors
Local Interface
System Name
fxp0
x2-sw35
xe-0/0/0
sitara
xe-0/0/1
sitara

Copyright 2014, Juniper Networks, Inc.

Parent Interface

Chassis Id

Port info

78:fe:3d:ee:4e:00

151

a8:d0:e5:50:26:c0

512

a8:d0:e5:50:26:c0

513

1833

Interfaces Fundamentals for Routing Devices

show lldp remote-global-statistics

Syntax
Release Information
Description

Options
Required Privilege
Level
List of Sample Output
Output Fields

show lldp remote-global-statistics

Command introduced in Junos OS Release 9.6.

On MX Series and T Series routers, display remote Link Layer Discovery Protocol (LLDP)
global statistics.
This command has no options.
view

show lldp remote-global-statistics on page 1835

Table 167 on page 1834 describes the output fields for the show lldp remote-global-statistics
command. Output fields are listed in the approximate order in which they appear.

Table 167: show lldp remote-global-statistics Output Fields

1834

Field Name

Field Description

LLDP Remote
Database Table
Counters

Information about remote database table counters.

LastchangeTime

Time elapsed between LLDP agent startup and the last change to the remote
database table information.

Inserts

Number of insertions made in the remote database table.

Deletes

Number of deletions made in the remote database table.

Drops

Number of LLDP frames dropped from the remote database table because of
errors.

Ageouts

Number of remote database table entries that have aged out of the table.

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

Sample Output
show lldp remote-global-statistics
user@host> show lldp remote-global-statistics
user@host> show lldp remote-global-statistics
LLDP Remote Database Table Counters
LastchangeTime
Inserts
Deletes
00:00:76 (76 sec)
192
0

Copyright 2014, Juniper Networks, Inc.

Drops
0

Ageouts
0

1835

Interfaces Fundamentals for Routing Devices

show lldp statistics

Syntax

Release Information
Description

Options

show lldp statistics

<interface interface-name>

Command introduced in Junos OS Release 9.6.

On MX Series and T Series routers, display information about Link Layer Discovery Protocol
(LLDP) statistics.
interface interface-name(Optional) Display the statistics about a particular physical

interface.

NOTE: Starting with Junos OS Release 14.2, you can also display LLDP
statistical details for management interfaces, such as fxp or me, on MX
Series routers.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear lldp statistics on page 1821

show lldp statistics on page 1838

show lldp statistics interface ge-0/1/1 on page 1838
Table 168 on page 1836 describes the output fields for the show lldp statistics command.
Output fields are listed in the approximate order in which they appear.

Table 168: show lldp statistics Output Fields

Field Name

Field Description

Interface

Interface name.
For information about interface names, see Interface Naming Overview
on page 26. For information about interface names for TX Matrix routers,
see TX Matrix Router Chassis and Interface Names. For information about
FPC numbering on TX Matrix routers, see Routing Matrix with a TX Matrix
Router FPC Numbering.

1836

Received

Number of LLDP frames received on this interface.

Transmitted

Number of LLDP frames sent on this interface.

Unknown-TLVs

Number of LLDP frames with unsupported content received on this interface.

With-Errors

Number of LLDP frames with errors received on this interface.

Copyright 2014, Juniper Networks, Inc.

Chapter 22: LLDP Operational Commands

Table 168: show lldp statistics Output Fields (continued)

Field Name

Field Description

Discarded

Number of LLDP frames received on this interface that were discarded

because of problems.

Transmitted

Total number of LLDP frames that were transmitted on an interface.

Untransmitted

Total number of LLDP frames that were untransmitted on an interface.

Copyright 2014, Juniper Networks, Inc.

1837

Interfaces Fundamentals for Routing Devices

Sample Output
show lldp statistics
user@host> show lldp statistics
Interface
xe-3/0/0.0
xe-3/0/1.0
xe-3/0/2.0
xe-3/0/3.0
xe-3/0/4.0
xe-3/0/5.0
xe-3/0/6.0
xe-3/0/7.0
xe-5/0/6.0
xe-5/0/7.0

Parent Interface
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
-

Discarded TLVs
0
0
0
0
0
0
0
0
0
0

Transmitted
3044
3044
3044
3044
3075
3075
3075
3075
17312
17312

Received
1564
1564
1565
1566
1598
1598
1596
1597
0
0

Unknown TLVs
0
0
0
0
0
0
0
0
0
0

With Errors
0
0
0
0
0
0
0
0
0
0

Untransmitted
1
1
1
1
1
1
1
1
0
0

Sample Output
show lldp statistics interface ge-0/1/1
user@host> show lldp statistics interface ge-0/1/1
Interface Received Transmitted Unknown-TLVs With-Errors Discarded
--------- -------- ----------- ------------ ----------- --------ge-0/1/1 544
540
0
0
0

1838

Copyright 2014, Juniper Networks, Inc.

CHAPTER 23

MVRP Operational Commands

show mvrp

show mvrp applicant-state

show mvrp dynamic-vlan-memberships

show mvrp interface

show mvrp registration-state

show mvrp statistics

Copyright 2014, Juniper Networks, Inc.

1839

Interfaces Fundamentals for Routing Devices

show mvrp
Syntax

show mvrp

Release Information

Command introduced in Junos OS Release 10.1.

Command introduced in Junos OS Release 13.2X50-D10 for EX Series switches.

Description

Display Multiple VLAN Registration Protocol (MVRP) configuration information.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

show mvrp applicant-state on page 1842

show mvrp dynamic-vlan-memberships on page 1844

show mvrp interface on page 1845

show mvrp registration-state on page 1846

show mvrp statistics on page 1848

show mvrp on page 1840

Table 169 on page 1840 lists the output fields for the show mvrp command. Output fields
are listed in the approximate order in which they appear.

Table 169: show mvrp Output Fields

Field Name

Field Description

MVRP dynamic VLAN

creation

Displays whether global MVRP dynamic Virtual LAN (VLAN) creation is Enabled or Disabled.

MVRP BPDU MAC

address

Displays the multicast media access control (MAC) address for MVRP. If configured, the provider
MVRP multicast MAC address is used; otherwise, the customer MVRP multicast MAC address is
used.

MVRP timers (ms)

Displays MVRP timer information:

InterfaceThe interface on which MVRP is configured.

JoinThe maximum number of milliseconds the interfaces must wait before sending VLAN

advertisements.

LeaveThe number of milliseconds an interface must wait after receiving a Leave message to

remove the interface from the VLAN specified in the message.

LeaveAllThe interval at which LeaveAll messages are sent on interfaces. LeaveAll messages

maintain current MVRP VLAN membership information in the network.

Sample Output
show mvrp
user@host> show mvrp

1840

Copyright 2014, Juniper Networks, Inc.

Chapter 23: MVRP Operational Commands

MVRP configuration for routing instance 'default-switch'

MVRP dynamic VLAN creation : Enabled
MVRP BPDU MAC address
: Customer bridge group (01-80-C2-00-00-21)
MVRP timers (ms)
Interface
Join
Leave LeaveAll
ge-11/2/8
200
800
10000
ge-11/0/9
200
800
10000
ge-11/3/0
200
800
10000

Copyright 2014, Juniper Networks, Inc.

1841

Interfaces Fundamentals for Routing Devices

show mvrp applicant-state

Syntax
Release Information
Description

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show mvrp applicant-state

Command introduced in Junos OS Release 10.1.

For MX Series routers and EX Series switches, display Multiple VLAN Registration Protocol
(MVRP) applicant state information.
view

show mvrp on page 1840

show mvrp interface on page 1845

show mvrp registration-state on page 1846

show mvrp statistics on page 1848

show mvrp applicant-state on page 1843

Table 170 on page 1842 lists the output fields for the show mvrp applicant-state command.
Output fields are listed in the approximate order in which they appear.

Table 170: show mvrp applicant-state Output Fields

Field Name

Field Description

VLAN Id

Displays the Virtual LAN (VLAN) ID number.

Interface

Displays the interface number associated with the VLAN ID.

State

Displays one of the following MVRP registrar states:

1842

VOVery anxious observer.

VPVery anxious passive.

VAVery anxious new.

ANAnxious new.

AAAnxious active.

QAQuiet active.

LALeaving active.

AOAnxious observer.

QOQuiet observer.

LOLeaving observer.

APAnxious passive.

QAQuiet passive.

Copyright 2014, Juniper Networks, Inc.

Chapter 23: MVRP Operational Commands

Sample Output
show mvrp applicant-state
user@host> show mvrp applicant-state
MVRP applicant state for routing instance 'default-switch'
(VO) Very anxious observer, (VP) Very anxious passive, (VA) Very anxious new,
(AN) Anxious new, (AA) Anxious active, (QA) Quiet active, (LA) Leaving active,
(AO) Anxious observer, (QO) Quiet observer, (LO) Leaving observer,
(AP) Anxious passive, (QP) Quiet passive
VLAN Id
100
200
300

Copyright 2014, Juniper Networks, Inc.

Interface
ge-11/3/0
ge-11/3/0
ge-11/3/0

State
Declaring (QA)
Declaring (QA)
Declaring (QA)

1843

Interfaces Fundamentals for Routing Devices

show mvrp dynamic-vlan-memberships

Syntax
Release Information

Description

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show mvrp dynamic-vlan-memberships

Command introduced in Junos OS Release 10.1.

Command introduced in Junos OS Release 13.2X50-D10 for EX Series switches.
Display all Virtual LANs (VLANs) that have been created dynamically using Multiple
VLAN Registration Protocol (MVRP) on the router or switch.
clear

show mvrp on page 1840

show mvrp applicant-state on page 1842

show mvrp interface on page 1845

show mvrp registration-state on page 1846

show mvrp statistics on page 1848

show mvrp dynamic-vlan-memberships on page 1844

Table 171 on page 1844 lists the output fields for the show mvrp dynamic-vlan-memberships
command. Output fields are listed in the approximate order in which they appear.

Table 171: show mvrp dynamic-vlan-memberships Output Fields

Field Name

Field Description

VLAN Id

The VLAN ID of the dynamically created VLAN.

Interfaces

The interface or interfaces that are bound to the dynamically created VLAN.

Sample Output
show mvrp dynamic-vlanmemberships
user@host> show mvrp dynamic-vlan-memberships
MVRP dynamic vlans for routing instance 'default-switch'
(s) static vlan, (f) fixed registration
VLAN Id
100 (s)
200 (s)
300 (s)

1844

Interfaces
ge-11/3/0
ge-11/3/0

Copyright 2014, Juniper Networks, Inc.

Chapter 23: MVRP Operational Commands

show mvrp interface

Syntax
Release Information
Description

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show mvrp interface

Command introduced in Junos OS Release 10.1.

For MX Series routers and EX Series switches, display Multiple VLAN Registration Protocol
(MVRP) interface-specific information.
view

show mvrp on page 1840

show mvrp applicant-state on page 1842

show mvrp dynamic-vlan-memberships on page 1844

show mvrp registration-state on page 1846

show mvrp statistics on page 1848

show mvrp interface on page 1845

Table 172 on page 1845 lists the output fields for the show mvrp interface command. Output
fields are listed in the approximate order in which they appear.

Table 172: show mvrp interface Output Fields

Field Name

Field Description

Interface

Interface on which MVRP is configured.

Status

Status of the MVRP: Enabled or Disabled.

Registration Mode

Registration for the interface: Fixed, Forbidden, or Normal.

Applicant Mode

Applicant mode.

Sample Output
show mvrp interface
user@host> show mvrp interface
MVRP interface information for routing instance 'default-switch'
Interface

Status

ge-11/2/8
ge-11/0/9
ge-11/3/0

Enabled
Enabled
Enabled

Copyright 2014, Juniper Networks, Inc.

Registration
Mode
Normal
Normal
Normal

Applicant
Mode
Normal
Normal
Normal

1845

Interfaces Fundamentals for Routing Devices

show mvrp registration-state

Syntax
Release Information
Description

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show mvrp registration-state

Command introduced in Junos OS Release 10.1.

For MX Series routers and EX Series switches, display Multiple VLAN Registration Protocol
(MVRP) registration state information.
view

show mvrp on page 1840

show mvrp dynamic-vlan-memberships on page 1844

show mvrp interface on page 1845

show mvrp statistics on page 1848

show mvrp registration-state on page 1846

Table 173 on page 1846 lists the output fields for the show mvrp registration-state command.
Output fields are listed in the approximate order in which they appear.

Table 173: show mvrp registration-state Output Fields

Field Name

Field Description

VLAN Id

Displays the Virtual LAN (VLAN) ID number.

Interface

Displays the interface number associated with the VLAN ID.

Registrar State

Displays whether the registrar state is Registered or Empty.

Forced State

Displays whether the forced state is Registered or Empty.

Managed State

Displays one of the following states:

FixedVLANs always stay in a registered state and are declared as such on all other forwarding

ports.

STP State

NormalVLANs participate in the MVRP protocol and honor incoming join requests normally.

ForbiddenVLANs ignore the incoming join requests and always stay in an unregistered state.

Displays whether the Spanning Tree Protocol (STP) is Blocking or Forwarding.

Sample Output
show mvrp registration-state
user@host> show mvrp registration-state
MVRP registration state for routing instance 'default-switch'

1846

Copyright 2014, Juniper Networks, Inc.

Chapter 23: MVRP Operational Commands

VLAN Id

Interface

100

ge-11/2/8
ge-11/0/9
ge-11/3/0
ge-11/2/8
ge-11/0/9
ge-11/3/0

101

Copyright 2014, Juniper Networks, Inc.

Registrar
State
Empty
Empty
Registered
Empty
Empty
Registered

Forced
State
Registered
Empty
Registered
Registered
Empty
Registered

Managed
State
Fixed
Normal
Normal
Fixed
Normal
Normal

STP
State
Forwarding
Forwarding
Forwarding
Forwarding
Forwarding
Forwarding

1847

Interfaces Fundamentals for Routing Devices

show mvrp statistics

Syntax
Release Information
Description

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show mvrp statistics

Command introduced in Junos OS Release 10.1.

For MX Series routers and EX Series switches, display Multiple VLAN Registration Protocol
(MVRP) statistics in the form of Multiple Registration Protocol data unit (MRPDU)
messages.
view

show mvrp on page 1840

show mvrp applicant-state on page 1842

show mvrp dynamic-vlan-memberships on page 1844

show mvrp interface on page 1845

show mvrp registration-state on page 1846

show mvrp statistics on page 1848

Table 174 on page 1848 lists the output fields for the show mvrp statistics command. Output
fields are listed in the approximate order in which they appear.

Table 174: show mvrp statistics Output Fields

Field Name

Field Description

interface name

Interface for which MVRP statistics are displayed.

VLAN IDs registered

Number of Virtual LAN (VLAN) IDs registered.

Sent MVRP PDUs

Number of MRPDU messages transmitted from the router.

Received MVRP
PDUs without error

Number of MRPDU messages received on the router.

Received MVRP
PDUs with error

Number of invalid MRPDU messages received on the router.

Sample Output
show mvrp statistics
user@host> show mvrp statistics
MVRP statistics for routing instance 'default-switch'
Interface name
VLAN IDs registered
Sent MVRP PDUs

1848

: ge-11/2/8
: 0
: 1467

Copyright 2014, Juniper Networks, Inc.

Chapter 23: MVRP Operational Commands

Received MVRP PDUs without error: 0

Received MVRP PDUs with error
: 0
Interface name
:
VLAN IDs registered
:
Sent MVRP PDUs
:
Received MVRP PDUs without error:
Received MVRP PDUs with error
:

ge-11/0/9
0
1418
702
0

Interface name
:
VLAN IDs registered
:
Sent MVRP PDUs
:
Received MVRP PDUs without error:
Received MVRP PDUs with error
:

ge-11/3/0
2
1524
1366
0

Copyright 2014, Juniper Networks, Inc.

1849

Interfaces Fundamentals for Routing Devices

1850

Copyright 2014, Juniper Networks, Inc.

CHAPTER 24

OSPF Operational Commands

clear (ospf | ospf3) database

clear (ospf | ospf3) io-statistics

clear (ospf | ospf3) neighbor

clear (ospf | ospf3) overload

clear (ospf | ospf3) statistics

show (ospf | ospf3) backup coverage

show (ospf | ospf3) backup lsp

show (ospf | ospf3) backup neighbor

show (ospf | ospf3) backup spf

show ospf context-identifier

show ospf database

show ospf3 database

show (ospf | ospf3) interface

show (ospf | ospf3) io-statistics

show (ospf | ospf3) log

show (ospf | ospf3) neighbor

show (ospf | ospf3) overview

show (ospf | ospf3) route

show (ospf | ospf3) statistics

Copyright 2014, Juniper Networks, Inc.

1851

Interfaces Fundamentals for Routing Devices

clear (ospf | ospf3) database

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)

Release Information

1852

Syntax on page 1852

Syntax (EX Series Switch and QFX Series) on page 1852
clear (ospf | ospf3) database
<advertising-router (router-id | self)>
<area area-id>
<asbrsummary>
<external>
<instance instance-name>
<inter-area-prefix>
<inter-area-router>
<intra-area-prefix>
<link-local>
<logical-system (all | logical-system-name)>
<lsa-id lsa-id>
<netsummary>
<network>
<nssa>
<opaque-area>
<purge>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
<router>
clear (ospf | ospf3) database
<advertising-router (router-id | self)>
<area area-id>
<asbrsummary>
<external>
<instance instance-name>
<inter-area-prefix>
<inter-area-router>
<intra-area-prefix>
<link-local>
<lsa-id lsa-id>
<netsummary>
<network>
<nssa>
<opaque-area>
<purge>
<router>

Command introduced before Junos OS Release 7.4.

advertising-router router-id, netsummary, network, nssa, opaque-area, and router options
added in Junos OS Release 8.3. You must use the purge command with these options.
area area-id option added in Junos OS Release 8.3.
Command introduced in Junos OS Release 9.0 for EX Series switches.
realm option added in Junos OS Release 9.2.
advertising-router (router-id | self) option added in Junos OS Release 9.5.
advertising-router (router-id | self) option introduced in Junos OS Release 9.5 for EX Series
switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

purge option (and all options that are dependent on the purge option) hidden in Junos

OS Release 13.3.
Description

With the master Routing Engine, delete entries in the Open Shortest Path First (OSPF)
link-state advertisement (LSA) database. With the backup Routing Engine, delete the
OSPF LSA database and sync the new database with the master Routing Engine.

CAUTION: You can also use the purge command with any of the options to
discard rather than delete the specified LSA entries. This command is useful
only for testing. Use it with care, because it causes significant network
disruption.

Options

noneDelete all LSAs other than the systems own LSAs, which are regenerated. To

resynchronize the database, the system destroys all adjacent neighbors that are in
the state EXSTART or higher. The neighbors are then reacquired and the databases
are synchronized.
advertising-router (router-id | self)(Hidden) Discard entries for the LSA entries advertised

by the specified routing device or by this routing device.

area area-id(Optional) Discard entries for the LSAs in the specified area.
asbrsummary(Optional) Discard summary AS boundary router LSA entries.
external(Optional) Discard external LSAs.
instance instance-name(Optional) Delete or discard entries for the specified routing

instance only.
inter-area-prefix(OSPFv3 only) (Optional) Discard interarea prefix LSAs.
inter-area-router(OSPFv3 only) (Optional) Discard interarea router LSAs.
intra-area-prefix(OSPFv3 only) (Optional) Discard intra-area prefix LSAs.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

link-local(Optional) Delete link-local LSAs.
lsa-id lsa-id(Optional) Discard the LSA entries with the specified LSA identifier.
netsummary(Hidden) Discard summary network LSAs.
network(Hidden) Discard network LSAs.
nssa(Hidden) Discard not-so-stubby area (NSSA) LSAs.
opaque-area(Hidden Discard opaque area-scope LSAs.

Copyright 2014, Juniper Networks, Inc.

1853

Interfaces Fundamentals for Routing Devices

purge(Hidden) Discard all entries in the link-state advertisement database. All link-state

advertisements are set to MAXAGE and are flooded. The database is repopulated
when the originators of the link-state advertisements receive the MAXAGE link-state
advertisements and reissue them.
realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(OSPFv3 only) (Optional) Delete

the entries for the specified OSPFv3 realm, or address family. Use the realm option
to specify an address family for OSPFv3 other than IPv6 unicast, which is the default.
router(Hidden) Discard router LSAs.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

clear

show ospf database on page 1877

show ospf3 database on page 1886

clear ospf database on page 1854

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ospf database
user@host> clear ospf database

1854

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

clear (ospf | ospf3) io-statistics

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1855

Syntax (EX Series Switch and QFX Series) on page 1855
clear (ospf | osfp3) io-statistics
<logical-system (all | logical-system-name)>
clear (ospf | osfp3) io-statistics

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.3 for the QFX Series.
Clear Open Shortest Path First (OSPF) input and output statistics.
noneClear OSPF input and output statistics.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

clear

clear ospf io-statistics on page 1855

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ospf io-statistics
user@host> clear ospf io-statistics

Copyright 2014, Juniper Networks, Inc.

1855

Interfaces Fundamentals for Routing Devices

clear (ospf | ospf3) neighbor

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)

Release Information

Description
Options

Syntax on page 1856

Syntax (EX Series Switch and QFX Series) on page 1856
clear (ospf | ospf3) neighbor
<area area-id>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
<neighbor>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
clear (ospf | ospf3) neighbor
<area area-id>
<instance instance-name>
<interface interface-name>
<neighbor>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
realm option introduced in Junos OS Release 9.2.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Tear down Open Shortest Path First (OSPF) neighbor connections.
noneTear down OSPF connections with all neighbors for all routing instances.
area area-id(Optional) Tear down neighbor connections for the specified area only.
instance instance-name(Optional) Tear down neighbor connections for the specified

routing instance only.

interface interface-name(Optional) Tear down neighbor connections for the specified

interface only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor(Optional) Clear the state of the specified neighbor only.
realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) (OSPFv3 only) Clear

the state of the specified OSPFv3 realm, or address family. Use the realm option to
specify an address family for OSPFv3 other than IPv6 unicast, which is the default.
Required Privilege
Level
Related
Documentation
List of Sample Output

1856

clear

show (ospf | ospf3) neighbor on page 1908

clear ospf neighbor on page 1857

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Output Fields

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ospf neighbor
user@host> clear ospf neighbor

Copyright 2014, Juniper Networks, Inc.

1857

Interfaces Fundamentals for Routing Devices

clear (ospf | ospf3) overload

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Options

Syntax on page 1858

Syntax (EX Series Switches) on page 1858
clear (ospf | ospf3) overload
<instance instance-name>
<logical-system (all | logical-system-name)>
clear (ospf | ospf3) overload
<instance instance-name>

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.3 for the QFX Series.
Clear the Open Shortest Path First (OSPF) overload bit and rebuild link-state
advertisements (LSAs).
noneClear the overload bit and rebuild LSAs for all routing instances.
instance instance-name(Optional) Clear the overload bit and rebuild LSAs for the

specified routing instance only.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

clear

clear ospf overload on page 1858

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ospf overload
user@host> clear ospf overload

1858

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

clear (ospf | ospf3) statistics

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1859

Syntax (EX Series Switch and QFX Series) on page 1859
clear (ospf | osfp3) statistics
<instance instance-name>
<logical-system (all | logical-system-name)>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
clear (ospf | osfp3) statistics
<instance instance-name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
realm option introduced in Junos OS Release 9.2.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Clear Open Shortest Path First (OSPF) statistics.
noneClear OSPF statistics.
instance instance-name(Optional) Clear statistics for the specified routing instance

only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) (OSPFv3 only) Clear

statistics for the specified OSPFv3 realm, or address family. Use the realm option to
specify an address family for OSPFv3 other than IPv6 unicast, which is the default.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show (ospf | ospf3) statistics on page 1925

clear ospf statistics on page 1859

See show (ospf | ospf3) statistics for an explanation of output fields.

Sample Output
clear ospf statistics
The following sample output displays OSPF statistics before and after the clear ospf
statistics command is entered:
user@host> show ospf statistics
Packet type

Copyright 2014, Juniper Networks, Inc.

Total

Last 5 seconds

1859

Interfaces Fundamentals for Routing Devices

Hello
DbD
LSReq
LSUpdate
LSAck
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs

Sent
3254
41
8
212
65

Received
2268
46
7
154
98

Sent
3
0
0
0
0

retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:

Flood queue depth

Total rexmit entries
db summaries
lsreq entries

:
:
:
:

3,
12,
0,
0,
3,
5,
19,

Received
1
0
0
0
0

last
last
last
last
last
last
last

5
5
5
5
5
5
5

seconds
seconds
seconds
seconds
seconds
seconds
seconds

:
:
:
:
:
:
:

0
0
0
0
0
0
0

0
0
0
0

Receive errors:
626 subnet mismatches

user@host> clear ospf statistics

user@host> show ospf statistics

Packet type
Total
Sent
Received
Hello
3
1
DbD
0
0
LSReq
0
0
LSUpdate
0
0
LSAck
0
0
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs

Last 5 seconds
Sent
Received
3
1
0
0
0
0
0
0
0
0

retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:

Flood queue depth

Total rexmit entries
db summaries
lsreq entries

:
:
:
:

0,
0,
0,
0,
0,
0,
0,

last
last
last
last
last
last
last

5
5
5
5
5
5
5

seconds
seconds
seconds
seconds
seconds
seconds
seconds

:
:
:
:
:
:
:

0
0
0
0
0
0
0

0
0
0
0

Receive errors:
None

1860

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show (ospf | ospf3) backup coverage

Syntax

show (ospf | ospf3) backup coverage

<instance instance-name>
< logical-system (all | logical-system-name)>
<realm (ipv4-unicast | ipv46-unicast>
<topology topology-name>

Syntax (QFX Series)

show (ospf | ospf3) backup coverage

<instance instance-name>
<topology topology-name>

Release Information

Command introduced in Junos OS Release 10.0.

Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Options

Display information about the level of backup coverage available for all the nodes and
prefixes in the network.
noneDisplay information about the level backup coverage for all OSPF routing instances

in all logical systems.

logical-system (all | logical-system-name)(Optional) Display information about the

level of backup coverage for all logical systems or for a specific logical system.
instance instance-name(Optional) Display information about the level of backup

coverage for a specific OSPF routing instance.

realm (ipv4-unicast | ipv6-unicast)(Optional) (OSPFv3 only) Display information about

the level of backup coverage for the specific OSPFv3 realm, or address family.
topology (default | topology-name)(Optional) (OSPFv2 only) Display information about

the level of backup coverage for the specific OSPF topology.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

show (ospf | ospf3) backup lsp on page 1864

show ospf backup coverage on page 1862

show ospf3 backup coverage on page 1862
Table 175 on page 1861 lists the output fields for the show (ospf | ospf3) backup coverage
command. Output fields are listed in the approximate order in which they appear.

Table 175: show (ospf | ospf3) backup coverage Output Fields

Field Name

Field Description

Node Coverage

Information about backup coverage for each OSPF node.

Area

Area number. Area 0.0.0.0 is the backbone.

Copyright 2014, Juniper Networks, Inc.

1861

Interfaces Fundamentals for Routing Devices

Table 175: show (ospf | ospf3) backup coverage Output Fields (continued)
Field Name

Field Description

Covered Nodes

Number of nodes for which backup coverage is available.

Total Nodes

Total number of OSPF nodes.

Route Coverage

Information about backup coverage for each type of OSPF route.

Path Type

Type of OSPF path: Intra, Inter, Ext1, Ext2, and All.

Covered Routes

For each path type, the number of routes for which backup coverage
is available.

Total Routes

For each path type, the total number of configured routes.

Percent Covered

For all nodes and for each path type, the percentage for which
backup coverage is available.

Sample Output
show ospf backup coverage
user@host> show ospf backup coverage
Topology default coverage:
Node Coverage:
Area

Covered
Nodes
4

0.0.0.0

Total
Nodes
5

Percent
Covered
80.00%

Route Coverage:
Path Type
Intra
Inter
Ext1
Ext2
All

Covered
Routes
8
0
0
1
9

Total
Routes
14
0
0
1
15

Percent
Covered
57.14%
100.00%
100.00%
100.00%
60.00%

show ospf3 backup coverage

user @host > show ospf3 backup coverage
show ospf3 backup coverage
Node Coverage:
Area

Covered
Nodes
4

0.0.0.0

Total
Nodes
5

Percent
Covered
80.00%

Route Coverage:
Path Type

1862

Covered
Routes

Total
Routes

Percent
Covered

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Intra
Inter
Ext1
Ext2
All

Copyright 2014, Juniper Networks, Inc.

4
0
0
1
5

6
0
0
1
7

66.67%
100.00%
100.00%
100.00%
71.43%

1863

Interfaces Fundamentals for Routing Devices

show (ospf | ospf3) backup lsp

Syntax

Release Information
Description

show (ospf | ospf3) backup lsp

<logical-system (all | logical-system-name>
<realm (ipv4-unicast | ipv6-unicast)>

Command introduced in Junos OS Release 10.0.

Display information about MPLS label-switched-paths (LSPs) designated as backup
routes for OSPF routes.

NOTE: MPLS LSPs can be used as backup routes only for routes in the default
OSPFv2 topology and not for any configured topology. Additionally, MPLS
LSPs cannot be used as backup routes for nondefault instances either for
OSPFv2 or OSPFv3.

Options

noneDisplay information all MPLS LSPs designated as backup routes.

logical-system (all | logical-system-name)(Optional) Display information about MPLS

LSPs designated as backup routes for all logical systems or a specific logical system.
realm (ipv4-unicast | ipv6-unicast)(Optional) (OSPFv3 only) Display information about

MPLS LSPs designated as backup routes for a specific realm, or address family.
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

show (ospf | ospf3) backup coverage on page 1861

show ospf backup lsp on page 1865

show ospf3 backup lsp on page 1865
Table 176 on page 1864 lists the output fields for the show (ospf | ospf3) backup lsp
command. Output fields are listed in the approximate order in which they appear.

Table 176: show (ospf | ospf3) backup lsp Output Fields

1864

Field Name

Field Description

MPLS LSP name

Name of each MPLS LSP designated as a backup path.

Egress

IP address of the egress router for the LSP.

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 176: show (ospf | ospf3) backup lsp Output Fields (continued)
Field Name

Field Description

Status

State of the LSP:

UpThe router can detect RSVP hello messages from the

neighbor.

DownThe router has received one of the following indications:

Communication failure from the neighbor.

Communication from IGP that the neighbor is unavailable.

Change in the sequence numbers in the RSVP hello messages

sent by the neighbor.

DeletedThe LSP is no longer available as a backup path.

Last change

Time elapsed since the neighbor state changed either from up or

down or from down to up. The format is hh:mm:ss.

TE-metric

Configured traffic engineering metric.

Metric

Configured metric.

Sample Output
show ospf backup lsp
user@host> show ospf backup lsp
tobanff
Egress: 10.255.71.239, Status: up, Last change: 00:00:23
TE-metric: 0, Metric: 0

Sample Output
show ospf3 backup lsp
user@host> show ospf3 backup lsp
tobanff
Egress: 10.255.71.239, Status: up, Last change: 00:00:45
TE-metric: 0, Metric: 0

Copyright 2014, Juniper Networks, Inc.

1865

Interfaces Fundamentals for Routing Devices

show (ospf | ospf3) backup neighbor

Syntax

show (ospf | ospf3) backup neighbor

<area area-id>
<instance (default | instance-name)>
<logical-system (default | ipv4-multicast | logical-system-name)>
<topology (default | ipv4-multicast | topology-name)>

Syntax (QFX Series)

show (ospf | ospf3) backup neighbor

<area area-id>
<instance instance-name>
<topology (default | ipv4-multicast | topology-name)>

Release Information

Command introduced in Junos OS Release 10.0.

Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Display the neighbors through which direct next hops for the backup paths are available.
noneDisplay all neighbors that have direct next hops for backup paths.
area area-id(Optional) Display the area information.
instance (default | instance-name)(Optional) Display information about the default

routing instance or a particular routing instance.

logical-system (default | ipv4-multicast | logical-system-name)(Optional) Display

information about the default logical system, IPv4 multicast logical system, or a
particular logical system.
topology (default | ipv4-multicast | topology-name)(OSPFv2 only) (Optional) Display

information about the default topology, IPv4 multicast topology, or a particular

topology.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

show (ospf | ospf3) backup spf on page 1868

show ospf backup neighbor on page 1867

Table 177 on page 1866 lists the output fields for the show (ospf |ospf3) backup neighbor
command. Output fields are listed in the approximate order in which they appear.

Table 177: show (ospf |ospf3) backup neighbor Output Fields

Field Name

Field Description

Level of Output

Neighbor to Self
Metric

Metric from the backup neighbor to the OSPF node.

All levels

Self to Neighbor
Metric

Metric from the OSPF node to the backup neighbor.

All levels

1866

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 177: show (ospf |ospf3) backup neighbor Output Fields (continued)
Field Name

Field Description

Level of Output

Direct next-hop

Interface and address of the direct next hop.

All levels

Sample Output
show ospf backup neighbor
user@host> show ospf backup neighbor
Topology default backup neighbors:
Area 0.0.0.5 backup neighbors:
10.0.0.5
Neighbor to Self Metric: 5
Self to Neighbor Metric: 5
Direct next-hop: ge-4/0/0.111 via 10.0.175.5
10.0.0.6
Neighbor to Self Metric: 5
Self to Neighbor Metric: 5
Direct next-hop: ge-4/1/0.110 via 10.0.176.6

Copyright 2014, Juniper Networks, Inc.

1867

Interfaces Fundamentals for Routing Devices

show (ospf | ospf3) backup spf

Syntax

show (ospf | ospf3) backup spf

<brief | detail>
<area area-id>
<instance instance-name>
<logical-system (all | logical-system-name>
<no-coverage>
<node-id>
<realm (ipv4unicast | ipv6unicast)>
<topology (default | ipv4-multicast | topology-name)>

Syntax (QFX Series)

show (ospf | ospf3) backup spf

<brief | detail>
<area area-id>
<instance instance-name>
<no-coverage>
<node-id>
<topology (default | ipv4-multicast | topology-name)>

Release Information

Command introduced in JUNOS Release 10.0.

Command introduced in Junos OS Release 11.3 for the QFX Series.

Description
Options

Display information about OSPF shortest-path-first calculations for backup paths.

noneDisplay information about OSPF shortest-path-first (SPF) calculations for all

backup paths for all destination nodes.

brief | detail(Optional) Display the specified level of output.
area area-id(Optional) Display the area information.
instance instance-name(Optional) Display information about the routing instance.
logical-system (all | logical-system-name)(Optional) Display information about all

logical systems or a specific logical system.

no-coverage(Optional) Display information if there is no backup coverage.
node-id(Optional) Display information about the node specified.
realm (ipv4unicast | ipv6unicast)(Optional) Display information about the ipv4 or
ipv6 realm.
topology (default | ipv4-multicast | topology-name)(Optional) (OSPFv2 only) Display

information about the default topology, IPv4 multicast topology, or a specifc topology.
Required Privilege
Level
List of Sample Output

1868

view

show ospf backup spf on page 1869

show ospf backup spf detail on page 1869
show ospf3 backup spf on page 1872

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Output Fields

Table 178 on page 1869 lists the output fields for the show (ospf |ospf3) backup spf
command. Output fields are listed in the approximate order in which they appear.

Table 178: show (ospf |ospf3) backup spf Output Fields

Field Name

Field Description

Level of Output

Area area-id results

Area for which the results are displayed. Area 0.0.0.0 is the backbone area.

All levels

address

Address of the node for which the results are displayed.

All levels

Self to Destination
Metric

Metric from the node to the destination.

All levels

Parent Node

Address of the parent node.

All levels

Primary next-hop

Address of the next hop.

All levels

Backup Neighbor

Address of the backup neighbor or LSP endpoint and the following information:

All levels

Neighbor to Destination Metric

Neighbor to Self Metric

Self to Neighbor Metric

Status (Eligible, Not Eligible, Not Evaluated) and the reason for the status.

NOTE: If the backup neighbor is an LSP endpoint, it is indicated as such after

the neighbor address.

Sample Output
show ospf backup spf
user@host> show ospf backup spf
Topology default results:
Area 0.0.0.0 results:
pro16-d-lo0.xxx.yyyy.net
Self to Destination Metric: 1
Parent Node: pro16-b-lo0.xxx.yyyy.net
Primary next-hop: at-1/0/1.0
Backup Neighbor: pro16-c-lo0.xxx.yyyy.net (LSP endpoint)
Neighbor to Destination Metric: 4, Neighbor to Self Metric: 3
Self to Neighbor Metric: 3
Not eligible, Reason: Path loops
Backup Neighbor: pro16-d-lo0.xxx.yyyy.net
Neighbor to Destination Metric: 0, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
...

show ospf backup spf detail

user@host> show ospf backup spf detail

Copyright 2014, Juniper Networks, Inc.

1869

Interfaces Fundamentals for Routing Devices

Topology default results:

Area 0.0.0.0 results:
11.14.10.2
Self to Destination Metric: 1
Parent Node: 10.255.70.103
Primary next-hop: ae0.0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
10.255.71.52
Self to Destination Metric: 1
Parent Node: 11.14.10.2
Primary next-hop: ae0.0 via 11.14.10.2
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 0, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
10.255.71.242
Self to Destination Metric: 1
Parent Node: 10.255.70.103
Primary next-hop: as0.0
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 0, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
10.255.71.243
Self to Destination Metric: 1
Parent Node: 10.255.70.103
Primary next-hop: so-6/0/0.0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 0, Neighbor to Self Metric: 1

1870

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Self to Neighbor Metric: 1

Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
12.15.0.1
Self to Destination Metric: 2
Parent Node: 10.255.71.243
Primary next-hop: so-6/0/0.0
Backup next-hop: ae0.0 via 11.14.10.2
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 1, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 17, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered
10.255.71.238
Self to Destination Metric: 2
Parent Node: 10.255.71.243
Primary next-hop: so-6/0/0.0
Backup next-hop: as0.0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 1, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered
10.255.71.239
Self to Destination Metric: 2
Parent Node: 12.15.0.1
Primary next-hop: so-6/0/0.0
Backup next-hop: ae0.0 via 11.14.10.2
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 1, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.242

Copyright 2014, Juniper Networks, Inc.

1871

Interfaces Fundamentals for Routing Devices

Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15

Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered
14.15.0.2
Self to Destination Metric: 3
Parent Node: 10.255.71.239
Primary next-hop: so-6/0/0.0
Backup next-hop: ae0.0 via 11.14.10.2
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 17, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered

show ospf3 backup spf

user@host> show ospf3 backup spf
Area 0.0.0.0 results:
10.255.71.52;0.0.0.5
Self to Destination Metric: 1
Parent Node: 10.255.70.103
Primary next-hop: ae0.0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
10.255.71.52
Self to Destination Metric: 1
Parent Node: 10.255.71.52;0.0.0.5
Primary next-hop: ae0.0 via fe80::290:69ff:fe0f:67f0
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 0, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops

1872

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

10.255.71.242
Self to Destination Metric: 1
Parent Node: 10.255.70.103
Primary next-hop: as0.0
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 0, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
10.255.71.243
Self to Destination Metric: 1
Parent Node: 10.255.70.103
Primary next-hop: so-6/0/0.0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 0, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not eligible, Reason: Path loops
10.255.71.243;0.0.0.2
Self to Destination Metric: 2
Parent Node: 10.255.71.243
Primary next-hop: so-6/0/0.0
Backup next-hop: ae0.0 via fe80::290:69ff:fe0f:67f0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 1, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 17, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered
10.255.71.238
Self to Destination Metric: 2
Parent Node: 10.255.71.243
Primary next-hop: so-6/0/0.0
Backup next-hop: as0.0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 1, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing

Copyright 2014, Juniper Networks, Inc.

1873

Interfaces Fundamentals for Routing Devices

Backup Neighbor: 10.255.71.242

Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered
10.255.71.239
Self to Destination Metric: 2
Parent Node: 10.255.71.243;0.0.0.2
Primary next-hop: so-6/0/0.0
Backup next-hop: ae0.0 via fe80::290:69ff:fe0f:67f0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 1, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 16, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered
10.255.71.239;0.0.0.4
Self to Destination Metric: 3
Parent Node: 10.255.71.239
Primary next-hop: so-6/0/0.0
Backup next-hop: ae0.0 via fe80::290:69ff:fe0f:67f0
Backup Neighbor: 10.255.71.243
Neighbor to Destination Metric: 2, Neighbor to Self Metric: 1
Self to Neighbor Metric: 1
Not eligible, Reason: Primary next-hop link fate sharing
Backup Neighbor: 10.255.71.52
Neighbor to Destination Metric: 15, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Eligible, Reason: Contributes backup next-hop
Backup Neighbor: 10.255.71.242
Neighbor to Destination Metric: 17, Neighbor to Self Metric: 15
Self to Neighbor Metric: 1
Not evaluated, Reason: Interface is already covered

1874

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show ospf context-identifier

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Description

Options

Syntax on page 1875

Syntax (EX Series Switches and QFX Series) on page 1875
show ospf context-identifier
<brief | detail>
<area area-id>
<context-id>
<instance instance-name>
<logical-system (all | logical-system-name)>
show ospf context-identifier
<brief | detail>
<area area-id>
<context-id>
<instance instance-name>

Command introduced in Junos OS Release 10.4.

Command introduced in Junos OS Release 11.3 for the QFX Series.
Display the context identifier information processed and advertised by Open Shortest
Path First (OSPF) for egress protection.
noneDisplay information about all context identifiers.
brief | detail(Optional) Display the specified level of output.
area area-id(Optional) Display information about the context identifier for the specified

area.
context-id(Optional) Display information about the specified context identifier.
instance instance-name(Optional) Display information about the context identifier for

the specified routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

egress-protection (Layer 2 circuit) in the Junos OS VPNs Library for Routing Devices

egress-protection (MPLS) in the Junos OS VPNs Library for Routing Devices

show ospf context-identifier on page 1876

show ospf context-identifier detail on page 1876
Table 179 on page 1876 lists the output fields for the show ospf context-identifier command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1875

Interfaces Fundamentals for Routing Devices

Table 179: show ospf context-identifier Output Fields

Field Name

Field Description

Level of Output

Context

IPv4 address that defines a protection pair. The context is manually configured
on both primary and protector provider edge (PE) devices.

All levels

Status

State of the path: active or inactive.

All levels

Metric

Advertised OSPF metric.

All levels

Area

OSPF area number.

All levels

Other
Advertisements

Other advertisements received by the OSPF node:

detail

Advertising router Address of the device that sent the advertisement.

TypeType of OSPF path: inter-area and stub.

MetricAdvertised OSPF metric.

NoneNo additional advertisements were received by the OSPF node.

Sample Output
show ospf context-identifier
user@host> show ospf context-identifier
Context-id: 2.2.4.3
Status: active, Metric: 65534, PE role: protector, Area: 0.0.0.0

show ospf context-identifier detail

user@host> show ospf context-identifier detail
Context-id: 88.24.13.1
Status: inactive, Metric: 0, PE role: protector, Area: 0.0.0.13
Other Advertisements:
Advertising router: 8.8.8.103
Type: stub link
Metric: 65534

1876

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show ospf database

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Syntax on page 1877

Syntax (EX Series Switches and QFX Series) on page 1877
show ospf database
<brief | detail | extensive | summary>
<advertising-router (address | self)>
<area area-id>
<asbrsummary>
<external>
<instance instance-name>
<link-local>
<logical-system (all | logical-system-name)>
<lsa-id lsa-id>
<netsummary>
<network>
<nssa>
<opaque-area>
<router>
show ospf database
<brief | detail | extensive | summary>
<advertising-router (address | self)>
<area area-id>
<asbrsummary>
<external>
<instance instance-name>
<link-local>
<lsa-id lsa-id>
<netsummary>
<network>
<nssa>
<opaque-area>
<router>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
advertising-router self (address | self) option introduced in Junos OS Release 9.5.
advertising-router self (address | self) option introduced in Junos OS Release 9.5 for EX
Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Display the entries in the OSPF version 2 (OSPFv2) link-state database, which contains
data about link-state advertisement (LSA) packets.

Options

noneDisplay standard information about entries in the OSPFv2 link-state database for

all routing instances.

brief | detail | extensive | summary(Optional) Display the specified level of output.
advertising-router (address | self)(Optional) Display the LSAs advertised either by a

particular routing device or by this routing device.

Copyright 2014, Juniper Networks, Inc.

1877

Interfaces Fundamentals for Routing Devices

area area-id(Optional) Display the LSAs in a particular area.

asbrsummary(Optional) Display summary AS boundary router LSA entries.
external(Optional) Display external LSAs.
instance instance-name(Optional) Display all OSPF database information under the

named routing instance.

link-local(Optional) Display information about link-local LSAs.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

lsa-id lsa-id(Optional) Display the LSA with the specified LSA identifier.
netsummary(Optional) Display summary network LSAs.
network(Optional) Display information about network LSAs.
nssa(Optional) Display information about not-so-stubby area (NSSA) LSAs.
opaque-area(Optional) Display opaque area-scope LSAs.
router(Optional) Display information about router LSAs.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear (ospf | ospf3) database on page 1852

show ospf database on page 1880

show ospf database on page 1880
show ospf database brief on page 1881
show ospf database detail on page 1881
show ospf database extensive on page 1882
show ospf database summary on page 1885
Table 180 on page 1878 describes the output fields for the show ospf database command.
Output fields are listed in the approximate order in which they appear.

Table 180: show ospf database Output Fields

Field Name

Field Description

Level of Output

area

Area number. Area 0.0.0.0 is the backbone area.

All levels

Type

Type of link advertisement: ASBRSum, Extern, Network, NSSA, OpaqArea, Router,

or Summary.

All levels

ID

LSA identifier included in the advertisement. An asterisk preceding the identifier

marks database entries that originated from the local routing device.

All levels

1878

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 180: show ospf database Output Fields (continued)

Field Name

Field Description

Level of Output

Adv Rtr

Address of the routing device that sent the advertisement.

All levels

Seq

Link sequence number of the advertisement.

All levels

Age

Time elapsed since the LSA was originated, in seconds.

All levels

Opt

Optional OSPF capabilities associated with the LSA.

All levels

Cksum

Checksum value of the LSA.

All levels

Len

Length of the advertisement, in bytes.

All levels

Router

Router link-state advertisement information:

detail extensive

bitsFlags describing the routing device that generated the LSP.

link countNumber of links in the advertisement.

idID of a routing device or subnet on the link.

dataFor stub networks, the subnet mask. Otherwise, the IP address of the

routing device that generated the LSP.

Network

Summary

typeType of link. It can be PointToPoint, Transit, Stub, or Virtual.

TOS countNumber of type-of-service (ToS) entries in the advertisement.

TOS 0 metricMetric for ToS 0.

TOSType-of-service (ToS) value.

metricMetric for the ToS.

Network link-state advertisement information:

maskNetwork mask.

attached routerID of the attached neighbor.

Summary link-state advertisement information:

maskNetwork mask.

TOSType-of-service (ToS) value.

metricMetric for the ToS.

detail extensive

detail extensive

Gen timer

How long until the LSA is regenerated.

extensive

Aging timer

How long until the LSA expires.

extensive

Installed hh:mm:ss
ago

How long ago the route was installed.

extensive

expires in hh:mm:ss

How long until the route expires.

extensive

sent hh:mm:ss ago

How long ago the LSA was sent.

extensive

Copyright 2014, Juniper Networks, Inc.

1879

Interfaces Fundamentals for Routing Devices

Table 180: show ospf database Output Fields (continued)

Field Name

Field Description

Level of Output

Last changed
hh:mm:ss ago

How long ago the route was changed.

extensive

Change count

Number of times the route has changed.

extensive

Ours

Indicates that this is a local advertisement.

extensive

Router LSAs

Number of router link-state advertisements in the link-state database.

summary

Network LSAs

Number of network link-state advertisements in the link-state database.

summary

Summary LSAs

Number of summary link-state advertisements in the link-state database.

summary

NSSA LSAs

Number of not-so-stubby area link-state advertisements in the link-state

database.

summary

Sample Output
show ospf database
user@host> show ospf database
OSPF link state database, Area 0.0.0.1
Type
ID
Adv Rtr
Router
10.255.70.103
10.255.70.103
Router *10.255.71.242
10.255.71.242
Summary *23.1.1.0
10.255.71.242
Summary *24.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242

Seq
0x80000002
0x80000002
0x80000002
0x80000002
0x80000002

Age
215
214
172
177
217

Opt
0x20
0x20
0x20
0x20
0x28

Cksum Len
0x4112 48
0x11b1 48
0x6d72 28
0x607e 28
0x73bd 36

OSPF link state database, Area 0.0.0.2

Type
ID
Adv Rtr
Router
10.255.71.52
10.255.71.52
Router *10.255.71.242
10.255.71.242
Network *23.1.1.1
10.255.71.242
Summary *12.1.1.0
10.255.71.242
Summary *24.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242

Seq
0x80000004
0x80000003
0x80000002
0x80000001
0x80000002
0x80000001

Age
174
173
173
217
177
222

Opt
0x20
0x20
0x20
0x20
0x20
0x28

Cksum Len
0xd021 36
0xe191 36
0x9c76 32
0xfeec 28
0x607e 28
0xe047 36

OSPF link state database, Area 0.0.0.3

Type
ID
Adv Rtr
Router
10.255.71.238
10.255.71.238
Router *10.255.71.242
10.255.71.242
Network *24.1.1.1
10.255.71.242
Summary *12.1.1.0
10.255.71.242
Summary *23.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242

Seq
0x80000003
0x80000003
0x80000002
0x80000001
0x80000002
0x80000001

Age
179
177
177
217
172
222

Opt
0x20
0x20
0x20
0x20
0x20
0x28

Cksum Len
0x3942 36
0xf37d 36
0xc591 32
0xfeec 28
0x6d72 28
0xeb3b 36

show ospf database

The output for show ospf databse nssa with nssa-only configuration statement enabled
at [edit policy-options policy-statement policy-name term term name then external], which
clears P-bit on type 7 LSA.

1880

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

user@host> show ospf database

OSPF link state database, Area 0.0.0.1
Type
ID
Adv Rtr
Router
10.255.70.103
10.255.70.103
Router *10.255.71.242
10.255.71.242
Summary *23.1.1.0
10.255.71.242
Summary *24.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242

Seq
0x80000002
0x80000002
0x80000002
0x80000002
0x80000002

Age
215
214
172
177
217

Opt
0x20
0x20
0x20
0x20
0x20

Cksum Len
0x4112 48
0x11b1 48
0x6d72 28
0x607e 28
0x73bd 36

OSPF link state database, Area 0.0.0.2

Type
ID
Adv Rtr
Router
10.255.71.52
10.255.71.52
Router *10.255.71.242
10.255.71.242
Network *23.1.1.1
10.255.71.242
Summary *12.1.1.0
10.255.71.242
Summary *24.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242

Seq
0x80000004
0x80000003
0x80000002
0x80000001
0x80000002
0x80000001

Age
174
173
173
217
177
222

Opt
0x20
0x20
0x20
0x20
0x20
0x20

Cksum Len
0xd021 36
0xe191 36
0x9c76 32
0xfeec 28
0x607e 28
0xe047 36

OSPF link state database, Area 0.0.0.3

Type
ID
Adv Rtr
Router
10.255.71.238
10.255.71.238
Router *10.255.71.242
10.255.71.242
Network *24.1.1.1
10.255.71.242
Summary *12.1.1.0
10.255.71.242
Summary *23.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242

Seq
0x80000003
0x80000003
0x80000002
0x80000001
0x80000002
0x80000001

Age
179
177
177
217
172
222

Opt
0x20
0x20
0x20
0x20
0x20
0x20

Cksum Len
0x3942 36
0xf37d 36
0xc591 32
0xfeec 28
0x6d72 28
0xeb3b 36

show ospf database brief

The output for the show ospf database brief command is identical to that for the show
ospf database command. For sample output, see show ospf database on page 1880.
show ospf database detail
user@host> show ospf database detail
OSPF link state database, Area 0.0.0.1
Type
ID
Adv Rtr
Seq
Age
Router
10.255.70.103
10.255.70.103
0x80000002
261
bits 0x0, link count 2
id 10.255.71.242, data 12.1.1.1, Type PointToPoint (1)
TOS count 0, TOS 0 metric 1
id 12.1.1.0, data 255.255.255.0, Type Stub (3)
TOS count 0, TOS 0 metric 1
Router *10.255.71.242
10.255.71.242
0x80000002
260
bits 0x3, link count 2
id 10.255.70.103, data 12.1.1.2, Type PointToPoint (1)
TOS count 0, TOS 0 metric 1
id 12.1.1.0, data 255.255.255.0, Type Stub (3)
TOS count 0, TOS 0 metric 1
Summary *23.1.1.0
10.255.71.242
0x80000002
218
mask 255.255.255.0
TOS 0x0, metric 1
Summary *24.1.1.0
10.255.71.242
0x80000002
223
mask 255.255.255.0
TOS 0x0, metric 1
NSSA
*33.1.1.1
10.255.71.242
0x80000002
263
mask 255.255.255.255
Type 2, TOS 0x0, metric 0, fwd addr 12.1.1.2, tag 0.0.0.0
OSPF link state database, Area 0.0.0.2
Type
ID
Adv Rtr

Copyright 2014, Juniper Networks, Inc.

Seq

Age

Opt Cksum Len

0x20 0x4112 48

0x20 0x11b1

48

0x20 0x6d72

28

0x20 0x607e

28

0x28 0x73bd

36

Opt

Cksum

Len

1881

Interfaces Fundamentals for Routing Devices

Router
10.255.71.52
10.255.71.52
0x80000004
220
bits 0x0, link count 1
id 23.1.1.1, data 23.1.1.2, Type Transit (2)
TOS count 0, TOS 0 metric 1
Router *10.255.71.242
10.255.71.242
0x80000003
219
bits 0x3, link count 1
id 23.1.1.1, data 23.1.1.1, Type Transit (2)
TOS count 0, TOS 0 metric 1
Network *23.1.1.1
10.255.71.242
0x80000002
219
mask 255.255.255.0
attached router 10.255.71.242
attached router 10.255.71.52
Summary *12.1.1.0
10.255.71.242
0x80000001
263
mask 255.255.255.0
TOS 0x0, metric 1
Summary *24.1.1.0
10.255.71.242
0x80000002
223
mask 255.255.255.0
TOS 0x0, metric 1
NSSA
*33.1.1.1
10.255.71.242
0x80000001
268
mask 255.255.255.255
Type 2, TOS 0x0, metric 0, fwd addr 23.1.1.1, tag 0.0.0.0
OSPF link state database, Area 0.0.0.3
Type
ID
Adv Rtr
Seq
Age
Router
10.255.71.238
10.255.71.238
0x80000003
225
bits 0x0, link count 1
id 24.1.1.1, data 24.1.1.2, Type Transit (2)
TOS count 0, TOS 0 metric 1
Router *10.255.71.242
10.255.71.242
0x80000003
223
bits 0x3, link count 1
id 24.1.1.1, data 24.1.1.1, Type Transit (2)
TOS count 0, TOS 0 metric 1
Network *24.1.1.1
10.255.71.242
0x80000002
223
mask 255.255.255.0
attached router 10.255.71.242
attached router 10.255.71.238
Summary *12.1.1.0
10.255.71.242
0x80000001
263
mask 255.255.255.0
TOS 0x0, metric 1
Summary *23.1.1.0
10.255.71.242
0x80000002
218
mask 255.255.255.0
TOS 0x0, metric 1
NSSA
*33.1.1.1
10.255.71.242
0x80000001
268
mask 255.255.255.255
Type 2, TOS 0x0, metric 0, fwd addr 24.1.1.1, tag 0.0.0.0

0x20 0xd021

36

0x20 0xe191

36

0x20 0x9c76

32

0x20 0xfeec

28

0x20 0x607e

28

0x28 0xe047

36

Opt Cksum Len

0x20 0x3942 36

0x20 0xf37d

36

0x20 0xc591

32

0x20 0xfeec

28

0x20 0x6d72

28

0x28 0xeb3b

36

show ospf database extensive

user@host> show ospf database extensive
OSPF link state database, Area 0.0.0.1
Type
ID
Adv Rtr
Seq
Age
Router
10.255.70.103
10.255.70.103
0x80000002
286
bits 0x0, link count 2
id 10.255.71.242, data 12.1.1.1, Type PointToPoint (1)
TOS count 0, TOS 0 metric 1
id 12.1.1.0, data 255.255.255.0, Type Stub (3)
TOS count 0, TOS 0 metric 1
Aging timer 00:55:14
Installed 00:04:43 ago, expires in 00:55:14
Last changed 00:04:43 ago, Change count: 2
Router *10.255.71.242
10.255.71.242
0x80000002
285

1882

Opt Cksum Len

0x20 0x4112 48

0x20 0x11b1

48

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

bits 0x3, link count 2

id 10.255.70.103, data 12.1.1.2, Type PointToPoint (1)
TOS count 0, TOS 0 metric 1
id 12.1.1.0, data 255.255.255.0, Type Stub (3)
TOS count 0, TOS 0 metric 1
Gen timer 00:45:15
Aging timer 00:55:15
Installed 00:04:45 ago, expires in 00:55:15, sent 00:04:43
Last changed 00:04:45 ago, Change count: 2, Ours
Summary *23.1.1.0
10.255.71.242
0x80000002
243
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:57
Aging timer 00:55:57
Installed 00:04:03 ago, expires in 00:55:57, sent 00:04:01
Last changed 00:04:48 ago, Change count: 1, Ours
Summary *24.1.1.0
10.255.71.242
0x80000002
248
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:52
Aging timer 00:55:52
Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:06
Last changed 00:04:48 ago, Change count: 1, Ours
NSSA
*33.1.1.1
10.255.71.242
0x80000002
288
mask 255.255.255.255
Type 2, TOS 0x0, metric 0, fwd addr 12.1.1.2, tag 0.0.0.0
Gen timer 00:45:12
Aging timer 00:55:12
Installed 00:04:48 ago, expires in 00:55:12, sent 00:04:48
Last changed 00:04:48 ago, Change count: 2, Ours
OSPF link state database, Area 0.0.0.2
Type
ID
Adv Rtr
Seq
Age
Router
10.255.71.52
10.255.71.52
0x80000004
245
bits 0x0, link count 1
id 23.1.1.1, data 23.1.1.2, Type Transit (2)
TOS count 0, TOS 0 metric 1
Aging timer 00:55:55
Installed 00:04:02 ago, expires in 00:55:55
Last changed 00:04:02 ago, Change count: 2
Router *10.255.71.242
10.255.71.242
0x80000003
244
bits 0x3, link count 1
id 23.1.1.1, data 23.1.1.1, Type Transit (2)
TOS count 0, TOS 0 metric 1
Gen timer 00:45:56
Aging timer 00:55:56
Installed 00:04:04 ago, expires in 00:55:56, sent 00:04:02
Last changed 00:04:04 ago, Change count: 2, Ours
Network *23.1.1.1
10.255.71.242
0x80000002
244
mask 255.255.255.0
attached router 10.255.71.242
attached router 10.255.71.52
Gen timer 00:45:56
Aging timer 00:55:56
Installed 00:04:04 ago, expires in 00:55:56, sent 00:04:02
Last changed 00:04:04 ago, Change count: 1, Ours
Summary *12.1.1.0
10.255.71.242
0x80000001
288
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:12
Aging timer 00:55:12

Copyright 2014, Juniper Networks, Inc.

ago
0x20 0x6d72

28

ago
0x20 0x607e

28

ago
0x28 0x73bd

36

ago

Opt Cksum Len

0x20 0xd021 36

0x20 0xe191

36

ago
0x20 0x9c76

32

ago
0x20 0xfeec

28

1883

Interfaces Fundamentals for Routing Devices

Installed 00:04:48 ago, expires in 00:55:12, sent 00:04:04

Last changed 00:04:48 ago, Change count: 1, Ours
Summary *24.1.1.0
10.255.71.242
0x80000002
248
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:52
Aging timer 00:55:52
Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:04
Last changed 00:04:48 ago, Change count: 1, Ours
NSSA
*33.1.1.1
10.255.71.242
0x80000001
293
mask 255.255.255.255
Type 2, TOS 0x0, metric 0, fwd addr 23.1.1.1, tag 0.0.0.0
Gen timer 00:45:07
Aging timer 00:55:07
Installed 00:04:53 ago, expires in 00:55:07, sent 00:04:04
Last changed 00:04:53 ago, Change count: 1, Ours
OSPF link state database, Area 0.0.0.3
Type
ID
Adv Rtr
Seq
Age
Router
10.255.71.238
10.255.71.238
0x80000003
250
bits 0x0, link count 1
id 24.1.1.1, data 24.1.1.2, Type Transit (2)
TOS count 0, TOS 0 metric 1
Aging timer 00:55:50
Installed 00:04:07 ago, expires in 00:55:50
Last changed 00:04:07 ago, Change count: 2
Router *10.255.71.242
10.255.71.242
0x80000003
248
bits 0x3, link count 1
id 24.1.1.1, data 24.1.1.1, Type Transit (2)
TOS count 0, TOS 0 metric 1
Gen timer 00:45:52
Aging timer 00:55:52
Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:06
Last changed 00:04:08 ago, Change count: 2, Ours
Network *24.1.1.1
10.255.71.242
0x80000002
248
mask 255.255.255.0
attached router 10.255.71.242
attached router 10.255.71.238
Gen timer 00:45:52
Aging timer 00:55:52
Installed 00:04:08 ago, expires in 00:55:52, sent 00:04:06
Last changed 00:04:08 ago, Change count: 1, Ours
Summary *12.1.1.0
10.255.71.242
0x80000001
288
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:12
Aging timer 00:55:12
Installed 00:04:48 ago, expires in 00:55:12, sent 00:04:13
Last changed 00:04:48 ago, Change count: 1, Ours
Summary *23.1.1.0
10.255.71.242
0x80000002
243
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:57
Aging timer 00:55:57
Installed 00:04:03 ago, expires in 00:55:57, sent 00:04:01
Last changed 00:04:48 ago, Change count: 1, Ours
NSSA
*33.1.1.1
10.255.71.242
0x80000001
293
mask 255.255.255.255
Type 2, TOS 0x0, metric 0, fwd addr 24.1.1.1, tag 0.0.0.0
Gen timer 00:45:07
Aging timer 00:55:07

1884

ago
0x20 0x607e

28

ago
0x28 0xe047

36

ago

Opt Cksum Len

0x20 0x3942 36

0x20 0xf37d

36

ago
0x20 0xc591

32

ago
0x20 0xfeec

28

ago
0x20 0x6d72

28

ago
0x28 0xeb3b

36

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Installed 00:04:53 ago, expires in 00:55:07, sent 00:04:13 ago

Last changed 00:04:53 ago, Change count: 1, Ours

show ospf database summary

user@host> show ospf database summary
Area 0.0.0.1:
2 Router LSAs
2 Summary LSAs
1 NSSA LSAs
Area 0.0.0.2:
2 Router LSAs
1 Network LSAs
2 Summary LSAs
1 NSSA LSAs
Area 0.0.0.3:
2 Router LSAs
1 Network LSAs
2 Summary LSAs
1 NSSA LSAs
Externals:
Interface fe-2/2/1.0:
Interface ge-0/3/2.0:
Interface so-0/1/2.0:
Interface so-0/1/2.0:

Copyright 2014, Juniper Networks, Inc.

1885

Interfaces Fundamentals for Routing Devices

show ospf3 database

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Syntax on page 1886

Syntax (EX Series Switches and QFX Series) on page 1886
show ospf3 database
<brief | detail | extensive | summary>
<advertising-router (address | self)>
<area area-id>
<external>
<instance instance-name>
<inter-area-prefix>
<inter-area-router>
<intra-area-prefix>
<link>
<link-local>
<logical-system (all | logical-system-name)>
<lsa-id lsa-id>
<network>
<nssa>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
<router>
show ospf3 database
<brief | detail | extensive | summary>
<advertising-router (address | self)>
<area area-id>
<external>
<instance instance-name>
<inter-area-prefix>
<inter-area-router>
<intra-area-prefix>
<link>
<link-local>
<lsa-id lsa-id>
<network>
<nssa>
<router>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
realm option introduced in Junos OS Release 9.2.
advertising-router (address | self) option introduced in Junos Relase 9.5.
advertising-router (address | self) option introduced in Junos OS Release 9.5 for EX Series
switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Display the entries in the OSPF version 3 (OSPFv3) link-state database, which contains
data about link-state advertisement (LSA) packets.

Options

noneDisplay standard information about all entries in the OSPFv3 link-state database.
brief | detail | extensive | summary(Optional) Display the specified level of output.

1886

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

advertising-router (address | self)(Optional) Display the LSAs advertised either by a

particular routing device or by this routing device.

area area-id(Optional) Display the LSAs in a particular area.
external(Optional) Display external LSAs.
instance instance-name(Optional) Display all OSPF database information under the

named routing instance.

inter-area-prefix(Optional) Display information about interarea-prefix LSAs.
inter-area-router(Optional) Display information about interarea-router LSAs.
intra-area-prefix(Optional) Display information about intra-area-prefix LSAs.
link(Optional) Display information about link LSAs.
link-local(Optional) Display information about link-local LSAs.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

lsa-id lsa-id(Optional) Display the LSA with the specified LSA identifier.
network(Optional) Display information about network LSAs.
nssa(Optional) Display information about not-so-stubby area (NSSA) LSAs.
realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) Display information

about the specified OSPFv3 realm, or address family. Use the realm option to specify
an address family other than IPv6 unicast, which is the default.
router(Optional) Display information about router LSAs.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear (ospf | ospf3) database on page 1852

show ospf3 database brief on page 1892

show ospf3 database extensive on page 1892
show ospf3 database summary on page 1895
Table 181 on page 1887 lists the output fields for the show ospf3 database command. Output
fields are listed in the approximate order in which they appear.

Table 181: show ospf3 database Output Fields

Field Name

Field Description

Level of Output

OSPF link state

database, area
area-number

Entries in the link-state database for this area.

brief detail extensive

Copyright 2014, Juniper Networks, Inc.

1887

Interfaces Fundamentals for Routing Devices

Table 181: show ospf3 database Output Fields (continued)

Field Name

Field Description

Level of Output

OSPF AS SCOPE
link state database

Entries in the AS scope link-state database.

brief detail extensive

OSPF Link-Local
link state database,
interface
interface-name

Entries in the link-local link-state database for this interface.

brief detail extensive

area

Area number. Area 0.0.0.0 is the backbone area.

All levels

Type

Type of link advertisement: Extern, InterArPfx, InterArRtr, IntraArPrx , Link, Network,

NSSA, or Router.

brief detail extensive

ID

Link identifier included in the advertisement. An asterisk (*) preceding the

identifier marks database entries that originated from the local routing device.

brief detail extensive

Adv Rtr

Address of the routing device that sent the advertisement.

brief detail extensive

Seq

Link sequence number of the advertisement.

brief detail extensive

Age

Time elapsed since the LSA was originated, in seconds.

brief detail extensive

Cksum

Checksum value of the LSA.

brief detail extensive

Len

Length of the advertisement, in bytes.

brief detail extensive

Router (Router Link-State Advertisements)

bits

Flags describing the routing device that generated the LSP.

detail extensive

Options

Option bits carried in the router LSA.

detail extensive

For Each Router Link

Type

Type of interface. The value of all other output fields describing a routing device
interface depends on the interfaces type:

PointToPoint (1)Point-to-point connection to another routing device.

Transit (2)Connection to a transit network.

Virtual (4)Virtual link.

detail extensive

Loc-if-id

Local interface ID assigned to the interface that uniquely identifies the interface
with the routing device.

detail extensive

Nbr-if-id

Interface ID of the neighbor's interface for this routing device link.

detail extensive

Nbr-rtr-id

Router ID of the neighbor routing device (for type 2 interfaces, the attached
links designated router).

detail extensive

Metric

Cost of the router link.

detail extensive

1888

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 181: show ospf3 database Output Fields (continued)

Field Name

Field Description

Level of Output

Gen timer

How long until the LSA is regenerated, in the format hours:minutes:seconds.

extensive

Aging timer

How long until the LSA expires, in the format hours:minutes:seconds.

extensive

Installed nn:nn:nn
ago

How long ago the route was installed, in the format hours:minutes:seconds.

extensive

expires in nn:nn:nn

How long until the route expires, in the format hours:minutes:seconds.

extensive

sent nn:nn:nn ago

Time elapsed since the LSA was last transmitted or flooded to an adjacency
or an interface, respectively, in the format hours:minutes:seconds.

extensive

Ours

Indicates that this is a local advertisement.

extensive

Network (Network Link-State Advertisements)

Options

Option bits carried in the network LSA.

detail extensive

Attached Router

Router IDs of each of the routing devices attached to the link. Only routing
devices that are fully adjacent to the designated router are listed. The designated
router includes itself in this list.

detail extensive

InterArPfx (Interarea-Prefix Link-State Advertisements)

Prefix

IPv6 address prefix.

detail extensive

Prefix-options

Option bit associated with the prefix.

detail extensive

Metric

Cost of this route. Expressed in the same units as the interface costs in the router
LSAs. When the interarea-prefix LSA is describing a route to a range of addresses,
the cost is set to the maximum cost to any reachable component of the address
range.

detail extensive

Gen timer

How long until the LSA is regenerated, in the format hours:minutes:seconds.

extensive

Aging timer

How long until the LSA expires, in the format hours:minutes:seconds.

extensive

Installed nn:nn:nn
ago

How long ago the route was installed, in the format hours:minutes:seconds.

extensive

expires in nn:nn:nn

How long until the route expires, in the format hours:minutes:seconds.

extensive

sent nn:nn:nn ago

Time elapsed since the LSA was last transmitted or flooded to an adjacency
or an interface, respectively, in the format hours:minutes:seconds.

extensive

Ours

Indicates that this is a local advertisement.

extensive

InterArRtr (Interarea-Router Link-State Advertisements)

Dest-router-id

Router ID of the routing device described by the LSA.

Copyright 2014, Juniper Networks, Inc.

detail extensive

1889

Interfaces Fundamentals for Routing Devices

Table 181: show ospf3 database Output Fields (continued)

Field Name

Field Description

Level of Output

options

Optional capabilities supported by the routing device.

detail extensive

Metric

Cost of this route. Expressed in the same units as the interface costs in the router
LSAs. When the interarea-prefix LSA is describing a route to a range of addresses,
the cost is set to the maximum cost to any reachable component of the address
range.

detail extensive

Prefix

IPv6 address prefix.

extensive

Prefix-options

Option bit associated with the prefix.

extensive

Extern (External Link-State Advertisements)

Prefix

IPv6 address prefix.

detail extensive

Prefix-options

Option bit associated with the prefix.

detail extensive

Metric

Cost of the route, which depends on the value of Type.

detail extensive

Type n

Type of external metric: Type 1 or Type 2.

detail extensive

Aging timer

How long until the LSA expires, in the format hours:minutes:seconds.

extensive

Installed nn:nn:nn
ago

How long ago the route was installed, in the format hours:minutes:seconds.

extensive

expires in nn:nn:nn

How long until the route expires, in the format hours:minutes:seconds.

extensive

sent nn:nn:nn ago

Time elapsed since the LSA was last transmitted or flooded to an adjacency
or an interface, respectively, in the format hours:minutes:seconds.

extensive

Link (Link-State Advertisements)

IPv6-Address

IPv6 link-local address on the link for which this link LSA originated.

detail extensive

Options

Option bits carried in the link LSA.

detail extensive

priority

Router priority of the interface attaching the originating routing device to the
link.

detail extensive

Prefix-count

Number of IPv6 address prefixes contained in the LSA. The rest of the link LSA
contains a list of IPv6 prefixes to be associated with the link.

detail extensive

Prefix

IPv6 address prefix.

detail extensive

Prefix-options

Option bit associated with the prefix.

detail extensive

Gen timer

How long until the LSA is regenerated, in the format hours:minutes:seconds.

extensive

1890

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 181: show ospf3 database Output Fields (continued)

Field Name

Field Description

Level of Output

Aging timer

How long until the LSA expires, in the format hours:minutes:seconds.

extensive

Installed nn:nn:nn
ago

How long ago the route was installed, in the format hours:minutes:seconds.

extensive

expires in nn:nn:nn

How long until the route expires, in the format hours:minutes:seconds.

extensive

sent nn:nn:nn ago

Time elapsed since the LSA was last transmitted or flooded to an adjacency
or an interface, respectively, in the format hours:minutes:seconds.

extensive

Ours

Indicates that this is a local advertisement.

extensive

IntraArPfx (Intra-Area-Prefix Link-State Advertisements)

Ref-lsa-type

LSA type of the referenced LSA.

RouterAddress prefixes are associated with a router LSA.

NetworkAddress prefixes are associated with a network LSA.

detail extensive

Ref-lsa-id

Link-state ID of the referenced LSA.

detail extensive

Ref-router-id

Advertising router ID of the referenced LSA.

detail extensive

Prefix-count

Number of IPv6 address prefixes contained in the LSA. The rest of the link LSA
contains a list of IPv6 prefixes to be associated with the link.

detail extensive

Prefix

IPv6 address prefix.

detail extensive

Prefix-options

Option bit associated with the prefix.

detail extensive

Metric

Cost of this prefix. Expressed in the same units as the interface costs in the
router LSAs.

detail extensive

Gen timer

How long until the LSA is regenerated, in the format hours:minutes:seconds.

extensive

Aging timer

How long until the LSA expires, in the format hours:minutes:seconds.

extensive

Installed hh:mm:ss
ago

How long ago the route was installed, in the format hours:minutes:seconds.

extensive

expires in hh:mm:ss

How long until the route expires, in the format hours:minutes:seconds.

extensive

sent hh:mm:ss ago

Time elapsed since the LSA was last transmitted or flooded to an adjacency
or an interface, respectively, in the format hours:minutes:seconds.

extensive

n Router LSAs

Number of router LSAs in the link-state database.

summary

n Network LSAs

Number of network LSAs in the link-state database.

summary

Copyright 2014, Juniper Networks, Inc.

1891

Interfaces Fundamentals for Routing Devices

Table 181: show ospf3 database Output Fields (continued)

Field Name

Field Description

Level of Output

n InterArPfx LSAs

Number of interarea-prefix LSAs in the link-state database.

summary

n InterArRtr LSAs

Number of interarea-router LSAs in the link-state database.

summary

n IntraArPfx LSAs

Number of intra-area-prefix LSAs in the link-state database.

summary

Externals

Display of the external LSA database.

summary

n Extern LSAs

Number of external LSAs in the link-state database.

summary

Interface
interface-name

Name of the interface for which link-local LSA information is displayed.

summary

n Link LSAs

Number of link LSAs in the link-state database.

summary

Sample Output
show ospf3 database brief
user@host> show ospf3 database brief
OSPF3 link state database, area 0.0.0.0
Type
ID
Adv Rtr
Router
0.0.0.1
10.255.4.85
Router
*0.0.0.1
10.255.4.93
InterArPfx *0.0.0.2
10.255.4.93
InterArRtr *0.0.0.1
10.255.4.93
IntraArPfx *0.0.0.1
10.255.4.93

Seq
0x80000003
0x80000002
0x80000001
0x80000001
0x80000002

Age
885
953
910
910
432

Cksum Len
0xa697 40
0xc677 40
0xb96f 44
0xe159 32
0x788f 72

OSPF3 link state database, area 0.0.0.1

Type
ID
Adv Rtr
Router
*0.0.0.1
10.255.4.93
Router
0.0.0.1
10.255.4.97
Network
0.0.0.2
10.255.4.97
InterArPfx *0.0.0.1
10.255.4.93
InterArPfx *0.0.0.2
10.255.4.93
NSSA
0.0.0.1
10.255.4.97
IntraArPfx 0.0.0.1
10.255.4.97

Seq
0x80000003
0x80000006
0x80000002
0x80000002
0x80000002
0x80000002
0x80000006

Age
916
851
916
117
62
362
851

Cksum Len
0xea40 40
0xc95b 40
0x4598 32
0xa980 44
0xd47e 44
0x45ee 44
0x2f77 52

OSPF3 AS SCOPE link state database

Type
ID
Adv Rtr
Extern
0.0.0.1
10.255.4.85
Extern
*0.0.0.1
10.255.4.93

Seq
0x80000002
0x80000001

Age
63
910

Cksum Len
0x9b86 44
0x59c9 44

OSPF3 Link-Local link state database, interface ge-1/3/0.0

Type
ID
Adv Rtr
Seq
Age
Link
*0.0.0.2
10.255.4.93
0x80000003
916

Cksum Len
0x4dab 64

show ospf3 database extensive

user@host> show ospf3 database extensive
OSPF3 link state database, area 0.0.0.0
Type
ID
Adv Rtr
Router
0.0.0.1
10.255.4.85

1892

Seq
0x80000003

Age
1028

Cksum Len
0xa697 40

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

bits 0x2, Options 0x13

Type PointToPoint (1), Metric 10
Loc-If-Id 2, Nbr-If-Id 3, Nbr-Rtr-Id 10.255.4.93
Aging timer 00:42:51
Installed 00:17:05 ago, expires in 00:42:52, sent 02:37:54 ago
Router
*0.0.0.1
10.255.4.93
0x80000002 1096 0xc677 40
bits 0x3, Options 0x13
Type PointToPoint (1), Metric 10
Loc-If-Id 3, Nbr-If-Id 2, Nbr-Rtr-Id 10.255.4.85
Gen timer 00:00:40
Aging timer 00:41:44
Installed 00:18:16 ago, expires in 00:41:44, sent 00:18:14 ago
Ours
InterArPfx *0.0.0.2
10.255.4.93
0x80000001 1053 0xb96f 44
Prefix feee::10:10:2:0/126
Prefix-options 0x0, Metric 10
Gen timer 00:17:02
Aging timer 00:42:26
Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago
Ours
InterArPfx *0.0.0.3
10.255.4.93
0x80000001 1053 0x71d3 44
Prefix feee::10:255:4:97/128
Prefix-options 0x0, Metric 10
Gen timer 00:21:07
Aging timer 00:42:26
Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago
Ours
InterArRtr *0.0.0.1
10.255.4.93
0x80000001 1053 0xe159 32
Dest-router-id 10.255.4.97, Options 0x19, Metric 10
Gen timer 00:29:18
Aging timer 00:42:26
Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago
Ours
IntraArPfx 0.0.0.1
10.255.4.85
0x80000002 1028 0x2403 72
Ref-lsa-type Router, Ref-lsa-id 0.0.0.0, Ref-router-id 10.255.4.85
Prefix-count 2
Prefix feee::10:255:4:85/128
Prefix-options 0x2, Metric 0
Prefix feee::10:10:1:0/126
Prefix-options 0x0, Metric 10
Aging timer 00:42:51
Installed 00:17:05 ago, expires in 00:42:52, sent 02:37:54 ago
IntraArPfx *0.0.0.1
10.255.4.93
0x80000002
575 0x788f 72
Ref-lsa-type Router, Ref-lsa-id 0.0.0.0, Ref-router-id 10.255.4.93
Prefix-count 2
Prefix feee::10:255:4:93/128
Prefix-options 0x2, Metric 0
Prefix feee::10:10:1:0/126
Prefix-options 0x0, Metric 10
Gen timer 00:33:23
Aging timer 00:50:24
Installed 00:09:35 ago, expires in 00:50:25, sent 00:09:33 ago
OSPF3 link state database, area 0.0.0.1
Type
ID
Adv Rtr
Seq
Age Cksum Len
Router
*0.0.0.1
10.255.4.93
0x80000003 1059 0xea40 40
bits 0x3, Options 0x19
Type Transit (2), Metric 10
Loc-If-Id 2, Nbr-If-Id 2, Nbr-Rtr-Id 10.255.4.97
Gen timer 00:08:51
Aging timer 00:42:20
Installed 00:17:39 ago, expires in 00:42:21, sent 00:17:37 ago

Copyright 2014, Juniper Networks, Inc.

1893

Interfaces Fundamentals for Routing Devices

Router
0.0.0.1
10.255.4.97
0x80000006
994 0xc95b 40
bits 0x2, Options 0x19
Type Transit (2), Metric 10
Loc-If-Id 2, Nbr-If-Id 2, Nbr-Rtr-Id 10.255.4.97
Aging timer 00:43:25
Installed 00:16:31 ago, expires in 00:43:26, sent 02:37:54 ago
Network
0.0.0.2
10.255.4.97
0x80000002 1059 0x4598 32
Options 0x11
Attached router 10.255.4.97
Attached router 10.255.4.93
Aging timer 00:42:20
Installed 00:17:36 ago, expires in 00:42:21, sent 02:37:54 ago
InterArPfx *0.0.0.1
10.255.4.93
0x80000002
260 0xa980 44
Prefix feee::10:10:1:0/126
Prefix-options 0x0, Metric 10
Gen timer 00:45:39
Aging timer 00:55:39
Installed 00:04:20 ago, expires in 00:55:40, sent 00:04:18 ago
Ours
InterArPfx *0.0.0.2
10.255.4.93
0x80000002
205 0xd47e 44
Prefix feee::10:255:4:93/128
Prefix-options 0x0, Metric 0
Gen timer 00:46:35
Aging timer 00:56:35
Installed 00:03:25 ago, expires in 00:56:35, sent 00:03:23 ago
Ours
InterArPfx *0.0.0.3
10.255.4.93
0x80000001 1089 0x9bbb 44
Prefix feee::10:255:4:85/128
Prefix-options 0x0, Metric 10
Gen timer 00:04:46
Aging timer 00:41:51
Installed 00:18:09 ago, expires in 00:41:51, sent 00:17:43 ago
Ours
NSSA
0.0.0.1
10.255.4.97
0x80000002
505 0x45ee 44
Prefix feee::200:200:1:0/124
Prefix-options 0x8, Metric 10, Type 2,
Aging timer 00:51:35
Installed 00:08:22 ago, expires in 00:51:35, sent 02:37:54 ago
IntraArPfx 0.0.0.1
10.255.4.97
0x80000006
994 0x2f77 52
Ref-lsa-type Router, Ref-lsa-id 0.0.0.0, Ref-router-id 10.255.4.97
Prefix-count 1
Prefix feee::10:255:4:97/128
Prefix-options 0x2, Metric 0
Aging timer 00:43:25
Installed 00:16:31 ago, expires in 00:43:26, sent 02:37:54 ago
IntraArPfx 0.0.0.3
10.255.4.97
0x80000002 1059 0x4446 52
Ref-lsa-type Network, Ref-lsa-id 0.0.0.2, Ref-router-id 10.255.4.97
Prefix-count 1
Prefix feee::10:10:2:0/126
Prefix-options 0x0, Metric 0
Aging timer 00:42:20
Installed 00:17:36 ago, expires in 00:42:21, sent 02:37:54 ago
OSPF3 AS SCOPE link state database
Type
ID
Adv Rtr
Seq
Age Cksum Len
Extern
0.0.0.1
10.255.4.85
0x80000002
206 0x9b86 44
Prefix feee::100:100:1:0/124
Prefix-options 0x0, Metric 20, Type 2,
Aging timer 00:56:34
Installed 00:03:23 ago, expires in 00:56:34, sent 02:37:54 ago
Extern
*0.0.0.1
10.255.4.93
0x80000001 1053 0x59c9 44
Prefix feee::200:200:1:0/124

1894

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Prefix-options 0x0, Metric 10, Type 2,

Gen timer 00:25:12
Aging timer 00:42:26
Installed 00:17:33 ago, expires in 00:42:27, sent 00:17:31 ago
OSPF3 Link-Local link state database, interface ge-1/3/0.0
Type
ID
Adv Rtr
Seq
Age Cksum Len
Link
*0.0.0.2
10.255.4.93
0x80000003 1059 0x4dab 64
fe80::290:69ff:fe39:1cdb
Options 0x11, priority 128
Prefix-count 1
Prefix feee::10:10:2:0/126 Prefix-options 0x0
Gen timer 00:12:56
Aging timer 00:42:20
Installed 00:17:39 ago, expires in 00:42:21, sent 00:17:37 ago
Link
0.0.0.2
10.255.4.97
0x80000003
205 0xa87d 64
fe80::290:69ff:fe38:883e
Options 0x11, priority 128
Prefix-count 1
Prefix feee::10:10:2:0/126 Prefix-options 0x0
Aging timer 00:56:35
Installed 00:03:22 ago, expires in 00:56:35, sent 02:37:54 ago
OSPF3 Link-Local link state database, interface so-2/2/0.0
Type
ID
Adv Rtr
Seq
Age Cksum Len
Link
0.0.0.2
10.255.4.85
0x80000002
506 0x42bb 64
fe80::280:42ff:fe10:f169
Options 0x13, priority 128
Prefix-count 1
Prefix feee::10:10:1:0/126 Prefix-options 0x0
Aging timer 00:51:34
Installed 00:08:23 ago, expires in 00:51:34, sent 02:37:54 ago
Link
*0.0.0.3
10.255.4.93
0x80000002
505 0x6b7a 64
fe80::280:42ff:fe10:f177
Options 0x13, priority 128
Prefix-count 1
Prefix feee::10:10:1:0/126 Prefix-options 0x0
Gen timer 00:37:28
Aging timer 00:51:35
Installed 00:08:25 ago, expires in 00:51:35, sent 00:08:23 ago
Ours

show ospf3 database summary

user@host> show ospf3 database summary
Area 0.0.0.0:
2 Router LSAs
1 InterArPfx LSAs
1 InterArRtr LSAs
1 IntraArPfx LSAs
Area 0.0.0.1:
2 Router LSAs
1 Network LSAs
2 InterArPfx LSAs
1 NSSA LSAs
1 IntraArPfx LSAs
Externals:
2 Extern LSAs
Interface ge-1/3/0.0:
1 Link LSAs
Interface lo0.0:

Copyright 2014, Juniper Networks, Inc.

1895

Interfaces Fundamentals for Routing Devices

Interface so-2/2/0.0:
1 Link LSAs

1896

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show (ospf | ospf3) interface

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Description
Options

Syntax on page 1897

Syntax (EX Series Switches and QFX Series) on page 1897
show (ospf | ospf3) interface
<brief | detail | extensive>
<area area-id>
<interface-name>
<instance instance-name>
<logical-system (all | logical-system-name)>
<realm (ip4-multicast | ipv4-unicast | ipv6-multicast)>
show (ospf | ospf3) interface
<brief | detail | extensive>
<area area-id>
<interface-name>
<instance instance-name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
area option introduced in Junos OS Release 9.2.
area option introduced in Junos OS Release 9.2 for EX Series switches.
realm option introduced in Junos OS Release 9.2.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Display the status of OSPF interfaces.
noneDisplay standard information about the status of all OSPF interfaces for all routing

instances
brief | detail | extensive(Optional) Display the specified level of output.
area area-id(Optional) Display information about the interfaces that belong to the

specified area.
interface-name(Optional) Display information for the specified interface.
instance instance-name(Optional) Display all OSPF interfaces under the named routing

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(OSPFv3 only) (Optional) Display

information about the interfaces for the specified OSPFv3 realm, or address family.
Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast,
which is the default.
Required Privilege
Level

view

Copyright 2014, Juniper Networks, Inc.

1897

Interfaces Fundamentals for Routing Devices

List of Sample Output

show ospf interface brief on page 1900

show ospf interface detail on page 1900
show ospf3 interface detail on page 1900
show ospf interface detail(When Multiarea Adjacency Is Configured) on page 1900
show ospf interface area area-id on page 1902
show ospf interface extensive (When Flooding Reduction Is Enabled) on page 1902
show ospf interface extensive (When LDP Synchronization Is Configured) on page 1902

Output Fields

Table 182 on page 1898 lists the output fields for the show (ospf | ospf3) interface command.
Output fields are listed in the approximate order in which they appear.

Table 182: show (ospf | ospf3) interface Output Fields

Field Name

Field Description

Level of Output

Interface

Name of the interface running OSPF version 2 or OSPF version 3.

All levels

State

State of the interface: BDR, Down, DR, DRother, Loop, PtToPt, or Waiting.

All levels

Area

Number of the area that the interface is in.

All levels

DR ID

Address of the area's designated router.

All levels

BDR ID

Backup designated router for a particular subnet.

All levels

Nbrs

Number of neighbors on this interface.

All levels

Type

Type of interface: LAN, NBMA, P2MP, P2P, or Virtual.

detail extensive

Address

IP address of the neighbor.

detail extensive

Mask

Netmask of the neighbor.

detail extensive

Prefix-length

(OSPFv3) IPv6 prefix length, in bits.

detail extensive

OSPF3-Intf-Index

(OSPFv3) OSPF version 3 interface index.

detail extensive

MTU

Interface maximum transmission unit (MTU).

detail extensive

Cost

Interface cost (metric).

detail extensive

DR addr

Address of the designated router.

detail extensive

BDR addr

Address of the backup designated router.

detail extensive

Adj count

Number of adjacent neighbors.

detail extensive

Secondary

Indicates that this interface is configured as a secondary interface for this area.
This interface can belong to more than one area, but can be designated as a
primary interface for only one area.

detail extensive

1898

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 182: show (ospf | ospf3) interface Output Fields (continued)

Field Name

Field Description

Level of Output

Flood Reduction

Indicates that this interface is configured with flooding reduction. All

self-originated LSAs from this interface are initially sent with the DoNotAge bit
set. As a result, LSAs are refreshed only when a change occurs.

extensive

Priority

Router priority used in designated router (DR) election on this interface.

detail extensive

Flood list

List of link-state advertisements (LSAs) that might be about to flood this

interface.

extensive

Ack list

Acknowledgment list. List of pending acknowledgments on this interface.

extensive

Descriptor list

List of packet descriptors.

extensive

Hello

Configured value for the hello timer.

detail extensive

Dead

Configured value for the dead timer.

detail extensive

Auth type

(OSPFv2) Authentication mechanism for sending and receiving OSPF protocol

packets:

detail extensive

MD5The MD5 mechanism is configured in accordance with RFC 2328.

NoneNo authentication method is configured.

PasswordA simple password (RFC 2328) is configured.

Topology

(Multiarea adjacency) Name of topology: default or name.

LDP sync state

(OSPFv2 and LDP synchronization) Current state of LDP synchronization: in

sync, in holddown, and not supported.

extensive

reason

(OSPFv2 and LDP synchronization) Reason for the current state of LDP
synchronization. The LDP session might be up or down, or adjacency might be
up or down.

extensive

config holdtime

(OSPFv2 and LDP synchronization) Configured value of the hold timer.

extensive

If the state is not synchronized, and the hold time is not infinity, the remaining
field displays the number of seconds that remain until the configured hold timer
expires.
IPSec SA name

(OSPFv2) Name of the IPSec security association name.

detail extensive

Active key ID

(OSPFv2 and MD5) Number from 0 to 255 that uniquely identifies an MD5 key.

detail extensive

Start time

(OSPFv2 and MD5) Time at which the routing device starts using an MD5 key
to authenticate OSPF packets transmitted on the interface on which this key
is configured. To authenticate received OSPF protocol packets, the key becomes
effective immediately after the configuration is committed. If the start time
option is not configured, the key is effective immediately for send and receive
and is displayed as Start time 1970 Jan 01 00:00:00 PST.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1899

Interfaces Fundamentals for Routing Devices

Table 182: show (ospf | ospf3) interface Output Fields (continued)

Field Name

Field Description

Level of Output

ReXmit

Configured value for the Retransmit timer.

detail extensive

Stub, Not Stub, or

Stub NSSA

Type of area.

detail extensive

Sample Output
show ospf interface brief
user@host> show ospf interface brief
Intf
State
Area
at-5/1/0.0
PtToPt
0.0.0.0
ge-2/3/0.0
DR
0.0.0.0
lo0.0
DR
0.0.0.0
so-0/0/0.0
Down
0.0.0.0
so-6/0/1.0
PtToPt
0.0.0.0
so-6/0/2.0
Down
0.0.0.0
so-6/0/3.0
PtToPt
0.0.0.0

DR ID
0.0.0.0
192.168.4.16
192.168.4.16
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0

BDR ID
0.0.0.0
192.168.4.15
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0

Nbrs
1
1
0
0
1
0
1

show ospf interface detail

user@host> show ospf interface detail
Interface
State
Area
DR ID
BDR ID Nbrs
fe-0/0/1.0
BDR
0.0.0.0
192.168.37.12
10.255.245.215 1
Type LAN, address 192.168.37.11, Mask 255.255.255.248, MTU 4460, Cost 40
DR addr 192.168.37.12, BDR addr 192.168.37.11, Adj count 1, Priority 128
Hello 10, Dead 40, ReXmit 5, Not Stub
t1-0/2/1.0
PtToPt
0.0.0.0
0.0.0.0
0.0.0.0 0
Type P2P, Address 0.0.0.0, Mask 0.0.0.0, MTU 1500, Cost 2604
Adj count 0
Hello 10, Dead 40, ReXmit 5, Not Stub
Auth type: MD5, Active key ID 3, Start time 2002 Nov 19 10:00:00 PST
IPsec SA Name: sa

show ospf3 interface detail

user@host> show ospf3 interface so-0/0/3.0 detail
Interface
State
Area
DR-ID
BDR-ID
so-0/0/3.0
PtToPt
0.0.0.0
0.0.0.0
0.0.0.0
Address fe80::2a0:a5ff:fe28:1dfc, Prefix-length 64
OSPF3-Intf-index 1, Type P2P, MTU 4470, Cost 12, Adj-count 1
Hello 10, Dead 40, ReXmit 5, Not Stub

Nbrs
1

show ospf interface detail

(When Multiarea Adjacency Is Configured)
user@host> show ospf interface detail
regress@router> show ospf interface detail
Interface
State
Area
lo0.0
DR
0.0.0.0

DR ID
10.255.245.2

BDR ID
0.0.0.0

Nbrs
0

Type: LAN, Address: 127.0.0.1, Mask: 255.255.255.255, MTU: 65535, Cost: 0

DR addr: 127.0.0.1, Adj count: 0, Priority: 128
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None

1900

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Topology default (ID 0) -> Cost: 0

lo0.0
DR
0.0.0.0

10.255.245.2

0.0.0.0

Type: LAN, Address: 10.255.245.2, Mask: 255.255.255.255, MTU: 65535, Cost: 0

DR addr: 10.255.245.2, Adj count: 0, Priority: 128
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 0
so-0/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0
1
Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1
Adj count: 1
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 1
so-0/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0

Type: P2P, Address: 192.168.37.46, Mask: 255.255.255.254, MTU: 4470, Cost: 1

Adj count: 0, , Passive
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Passive, Cost: 1
so-1/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0
1
Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1
Adj count: 1
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 1
so-1/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0

Type: P2P, Address: 192.168.37.54, Mask: 255.255.255.254, MTU: 4470, Cost: 1

Adj count: 0, , Passive
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Passive, Cost: 1
so-0/0/0.0
PtToPt 1.1.1.1
0.0.0.0
0.0.0.0
1
Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1
Adj count: 1, Secondary
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 1
so-1/0/0.0
PtToPt 1.1.1.1
0.0.0.0
0.0.0.0

Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1

Adj count: 1, Secondary
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 1
so-0/0/0.0
PtToPt 2.2.2.2
0.0.0.0
0.0.0.0

Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1

Adj count: 1, Secondary
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 1
so-1/0/0.0
PtToPt 2.2.2.2
0.0.0.0
0.0.0.0

Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1

Adj count: 1, Secondary

Copyright 2014, Juniper Networks, Inc.

1901

Interfaces Fundamentals for Routing Devices

Hello: 10, Dead: 40, ReXmit: 5, Not Stub

Auth type: None
Topology default (ID 0) -> Cost: 1

show ospf interface area area-id

user@host> show ospf interface area 1.1.1.1
Interface
State
Area
so-0/0/0.0
PtToPt 1.1.1.1
so-1/0/0.0
PtToPt 1.1.1.1

DR ID
0.0.0.0
0.0.0.0

BDR ID
0.0.0.0
0.0.0.0

Nbrs
1
1

DR ID
0.0.0.0

BDR ID
0.0.0.0

Nbrs
0

show ospf interface extensive

(When Flooding Reduction Is Enabled)
user@host> show ospf interface extensive
Interface
State
Area
fe-0/0/0.0
PtToPt 0.0.0.0

Type: P2P, Address: 10.10.10.1, Mask: 255.255.255.0, MTU: 1500, Cost: 1

Adj count: 0
Secondary, Flood Reduction
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 1

show ospf interface extensive

(When LDP Synchronization Is Configured)
user@host> show ospf interface extensive
Interface
State
Area
DR ID
BDR ID
Nbrs
so-1/0/3.0
Down
0.0.0.0
0.0.0.0
0.0.0.0
0
Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 65535
Adj count: 0
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
LDP sync state: in holddown, for: 00:00:08, reason: LDP down during config
config holdtime: 10 seconds, remaining: 1

1902

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show (ospf | ospf3) io-statistics

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1903

Syntax (EX Series Switch and QFX Series) on page 1903
show (ospf | ospf3) io-statistics
<logical-system (all | logical-system-name)>
show (ospf | ospf3) io-statistics

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.3 for the QFX Series.
Display Open Shortest Path First (OSPF) input and output statistics.
noneDisplay OSPF input and output statistics.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

clear (ospf | ospf3) statistics on page 1859

show ospf io-statistics on page 1904

Table 183 on page 1903 lists the output fields for the show ospf io-statistics command.
Output fields are listed in the approximate order in which they appear.

Table 183: show (ospf | ospf3) io-statistics Output Fields

Field Name

Field Description

Packets read

Number of OSPF packets read since the last time the routing
protocol was started.

average per run

Total number of packets divided by the total number of times the

OSPF read operation is scheduled to run.

max run

Maximum number of packets for a given run among all scheduled

runs.

Receive errors

Number of faulty packets received with errors.

Copyright 2014, Juniper Networks, Inc.

1903

Interfaces Fundamentals for Routing Devices

Sample Output
show ospf io-statistics
user@host> show ospf io-statistics
Packets read: 7361, average per run: 1.00, max run: 1
Receive errors:
None

1904

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show (ospf | ospf3) log

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Syntax on page 1905

Syntax (EX Series Switch and QFX Series) on page 1905
show (ospf | osfp3) log
<instance instance-name>
<logical-system (all | logical-system-name)>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
<topology topology-name>
show (ospf | osfp3) log
<instance instance-name>
<topology topology-name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
topology option introduced in Junos OS Release 9.0.
topology option introduced in Junos OS Release 9.0 for EX Series switches.
realm option introduced in Junos OS Release 9.2.
Command introduced in Junos OS Release 11.3 for the QFX Series.

Description

Display the entries in the Open Shortest Path First (OSPF) log of SPF calculations.

Options

noneDisplay entries in the OSPF log of SPF calculations for all routing instances.
instance instance-name(Optional) Display entries for the specified routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

topology topology-name(Optional) (OSPFv2 only) Display entries for the specified

topology.
realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(OSPFv3 only) (Optional) Display

entries for the specified OSPFv3 realm, or address family. Use the realm option to
specify an address family for OSPFv3 other than IPv6 unicast, which is the default.
Required Privilege
Level
List of Sample Output

Output Fields

view

show ospf log on page 1906

show ospf log topology voice on page 1906
Table 184 on page 1905 lists the output fields for the show (ospf | ospf3) log command.
Output fields are listed in the approximate order in which they appear.

Table 184: show (ospf | ospf3) log Output Fields

Field Name

Field Description

When

Time, in weeks (w) and days (d), since the SPF calculation was
made.

Copyright 2014, Juniper Networks, Inc.

1905

Interfaces Fundamentals for Routing Devices

Table 184: show (ospf | ospf3) log Output Fields (continued)

Field Name

Field Description

Type

Type of calculation: Cleanup, External, Interarea, NSSA, Redist, SPF,

Stub, Total, or Virtuallink.

Elapsed

Amount of time, in seconds, that elapsed during the operation, or

the time required to complete the SPF calculation. The start time
is the time displayed in the When field.

Sample Output
show ospf log
user@host> show ospf log
When
Type
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
...

17:25:58
17:25:58
17:25:58
17:25:58
17:25:58
17:25:58
17:25:58
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48

Stub
SPF
Stub
Interarea
External
Cleanup
Total
SPF
Stub
SPF
Stub
Interarea
External
Cleanup
Total

Elapsed
0.000017
0.000070
0.000019
0.000054
0.000005
0.000203
0.000537
0.000125
0.000017
0.000100
0.000016
0.000056
0.000005
0.000238
0.000600

show ospf log topology voice

user@host> show ospf log topology voice
Topology voice SPF log:
Last instance of each event type
When
Type
Elapsed
00:06:11
SPF
0.000116
00:06:11
Stub
0.000114
00:06:11
Interarea
0.000126
00:06:11
External
0.000067
00:06:11
NSSA
0.000037
00:06:11
Cleanup
0.000186
Maximum length of each event type
When
Type
Elapsed
00:13:43
SPF
0.000140
00:13:33
Stub
0.000116
00:13:43
Interarea
0.000128
00:13:33
External
0.000075
00:13:38
NSSA
0.000039
00:13:53
Cleanup
0.000657
Last 100 events

1906

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

When

Type

Elapsed

00:13:53
00:13:53
00:13:53
00:13:53
00:13:53
00:13:53
00:13:53
.
.
00:06:11
00:06:11
00:06:11
00:06:11
00:06:11
00:06:11
00:06:11

SPF
Stub
Interarea
External
NSSA
Cleanup
Total

0.000090
0.000041
0.000123
0.000040
0.000038
0.000657
0.001252

SPF
Stub
Interarea
External
NSSA
Cleanup
Total

0.000116
0.000114
0.000126
0.000067
0.000037
0.000186
0.000818

Copyright 2014, Juniper Networks, Inc.

1907

Interfaces Fundamentals for Routing Devices

show (ospf | ospf3) neighbor

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Description

Syntax on page 1908

Syntax (EX Series Switches and QFX Series) on page 1908
show (ospf | ospf3) neighbor
<brief | detail | extensive>
<area area-id>
<instance (all | instance-name)>
<interface interface-name>
<logical-system (all | logical-system-name)>
<neighbor>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
show (ospf | ospf3) neighbor
<brief | detail | extensive>
<area area-id>
<instance (all | instance-name)>
<interface interface-name>
<neighbor>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
instance all option introduced in Junos OS Release 9.1.
instance all option introduced in Junos OS Release 9.1 for EX Series switches.
area, interface, and realm options introduced in Junos OS Release 9.2.
area and interface options introduced in Junos OS Release 9.2 for EX Series switches.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Display information about OSPF neighbors.
CPU utilization might increase while the device learns its OSPF neighbors. We recommend
that you use the show (ospf | ospf3) neighbor command after the device learns and
establishes OSPF neighbor adjacencies. Depending on the size of your network, this might
take several minutes. If you receive a timeout communicating with routing daemon
error when using the show (ospf | ospf3) neighbor command, wait several minutes before
attempting to use the command again. This is not a critical system error, but you might
experience a delay in using the CLI.

Options

noneDisplay standard information about all OSPF neighbors for all routing instances.
brief | detail | extensive(Optional) Display the specified level of output.
area area-id(Optional) Display information about the OSPF neighbors for the specified

area.
instance (all | instance-name)(Optional) Display all OSPF interfaces for all routing

instances or under the named routing instance.

interface interface-name(Optional) Display information about OSPF neighbors for the

specified logical interface.

1908

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor(Optional) Display information about the specified OSPF neighbor.
realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(OSPFv3 only) (Optional) Display

information about the OSPF neighbors for the specified OSPFv3 realm, or address
family. Use the realm option to specify an address family for OSPFv3 other than IPv6
unicast, which is the default.
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear (ospf | ospf3) neighbor on page 1856

show ospf neighbor brief on page 1911

show ospf neighbor detail on page 1911
show ospf neighbor extensive on page 1912
show ospf3 neighbor detail on page 1913
show ospf neighbor area area-id on page 1913
show ospf neighbor interface interface-name on page 1913
show ospf3 neighbor instance all (OSPFv3 Multiple Family Address Support
Enabled) on page 1913
Table 185 on page 1909 lists the output fields for the show (ospf | ospf3) neighbor command.
Output fields are listed in the approximate order in which they appear.

Table 185: show (ospf | ospf3) neighbor Output Fields

Field Name

Field Description

Level of Output

Address

Address of the neighbor.

All levels

Interface

Interface through which the neighbor is reachable.

All levels

Copyright 2014, Juniper Networks, Inc.

1909

Interfaces Fundamentals for Routing Devices

Table 185: show (ospf | ospf3) neighbor Output Fields (continued)

Field Name

Field Description

Level of Output

State

State of the neighbor:

All levels

AttemptValid only for neighbors attached to nonbroadcast networks. It

indicates that no recent information has been received from the neighbor,
but that a more concerted effort must be made to contact the neighbor.

DownInitial state of a neighbor conversation. It indicates that no recent

information has been received from the neighbor. Hello packets might
continue to be sent to neighbors in the Down state, although at a reduced
frequency.

ExchangeRouting device is describing its entire link-state database by

sending database description packets to the neighbor. Each packet has a

sequence number and is explicitly acknowledged.

ExStartFirst step in creating an adjacency between the two neighboring

routing devices. The goal of this step is to determine which routing device is
the master, and to determine the initial sequence number.

FullNeighboring routing devices are fully adjacent. These adjacencies appear

in router link and network link advertisements.

InitA hello packet has recently been sent by the neighbor. However,

bidirectional communication has not yet been established with the neighbor.
This state might occur, for example, because the routing device itself did not
appear in the neighbor's hello packet.

LoadingLink-state request packets are sent to the neighbor to acquire more

recent advertisements that have been discovered (but not yet received) in
the Exchange state.

2WayCommunication between the two routing devices is bidirectional. This

state has been ensured by the operation of the Hello Protocol. This is the
most advanced state short of beginning adjacency establishment. The
(backup) designated router is selected from the set of neighbors in state
2Way or greater.
ID

Router ID of the neighbor.

All levels

Pri

Priority of the neighbor to become the designated router.

All levels

Dead

Number of seconds until the neighbor becomes unreachable.

All levels

Link state
acknowledgment
list

Number of link-state acknowledgments received.

extensive

Link state
retransmission list

Total number of link-state advertisements retransmitted. For extensive output

only, the following information is also displayed:

detail extensive

TypeType of link advertisement: ASBR, Sum, Extern, Network, NSSA,

OpaqArea, Router, or Summary.

LSA IDLSA identifier included in the advertisement. An asterisk preceding

the identifier marks database entries that originated from the local routing
device.

1910

Adv rtrAddress of the routing device that sent the advertisement.

SeqLink sequence number of the advertisement.

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 185: show (ospf | ospf3) neighbor Output Fields (continued)

Field Name

Field Description

Level of Output

Neighbor-address

(OSPFv3 only) If the neighbor uses virtual links, the Neighbor-address is the
site-local, local, or global address. If the neighbor uses a physical interface, the
Neighbor-address is an IPv6 link-local address.

detail extensive

area

Area that the neighbor is in.

detail extensive

OSPF3-Intf-Index

(OSPFv3 only) Displays the OSPFv3 interface index.

detail extensive

opt

Option bits received in the hello packets from the neighbor.

detail extensive

DR or DR-ID

Address of the designated router.

detail extensive

BDR or BDR-ID

Address of the backup designated router.

detail extensive

Up

Length of time since the neighbor came up.

detail extensive

adjacent

Length of time since the adjacency with the neighbor was established.

detail extensive

Sample Output
show ospf neighbor brief
user@host> show ospf neighbor brief
Address
Intf
192.168.254.225 fxp3.0
192.168.254.230 fxp3.0
192.168.254.229 fxp3.0
10.1.1.129
fxp2.0
10.1.1.131
fxp2.0
10.1.2.1
fxp1.0
10.1.2.81
fxp0.0

State
2Way
Full
Full
Full
Full
Full
Full

ID
10.250.240.32
10.250.240.8
10.250.240.35
10.250.240.12
10.250.240.11
10.250.240.9
10.250.240.10

Pri
128
128
128
128
128
128
128

Dead
36
38
33
37
38
32
33

show ospf neighbor detail

user@host> show ospf neighbor detail
Address
Interface
State
ID
10.5.1.2
ge-1/2/0.1
Full
10.5.1.2
area 0.0.0.1, opt 0x42, DR 10.5.1.2, BDR 10.5.1.1
Up 06:09:28, adjacent 05:17:36
Link state acknowledgment list: 3 entries
Link state retransmission list:

Dead
37

128

34

128

38

9 entries

10.5.10.2
ge-1/2/0.10
ExStart
10.5.1.38
area 0.0.0.1, opt 0x42, DR 10.5.10.2, BDR 10.5.10.1
Up 06:09:28
master, seq 0xac1530f8, rexmit DBD in 3 sec
rexmit LSREQ in 0 sec
10.5.11.2
ge-1/2/0.11
Full
10.5.1.42
area 0.0.0.1, opt 0x42, DR 10.5.11.2, BDR 10.5.11.1
Up 06:09:28, adjacent 05:26:46
Link state retransmission list: 1 entries

Copyright 2014, Juniper Networks, Inc.

Pri
128

1911

Interfaces Fundamentals for Routing Devices

10.5.12.2
ge-1/2/0.12
ExStart
10.5.1.46
area 0.0.0.1, opt 0x42, DR 10.5.12.2, BDR 10.5.12.1
Up 06:09:28
master, seq 0xac188a68, rexmit DBD in 2 sec
rexmit LSREQ in 0 sec

128

33

Pri
128

Dead
33

128

38

128

33

show ospf neighbor extensive

user@host> show ospf neighbor extensive
Address
Interface
State
ID
10.5.1.2
ge-1/2/0.1
Full
10.5.1.2
area 0.0.0.1, opt 0x42, DR 10.5.1.2, BDR 10.5.1.1
Up 06:09:42, adjacent 05:17:50
Link state retransmission list:
Type

LSA ID

Adv rtr

Seq

Summary

10.8.56.0

172.25.27.82

0x8000004d

Router

10.5.1.94

10.5.1.94

0x8000005c

Network

10.5.24.2

10.5.1.94

0x80000036

Summary

10.8.57.0

172.25.27.82

0x80000024

Extern

1.10.90.0

10.8.1.2

0x80000041

Extern

1.4.109.0

10.6.1.2

0x80000041

Router

10.5.1.190

10.5.1.190

0x8000005f

Network

10.5.48.2

10.5.1.190

0x8000003d

Summary

10.8.58.0

172.25.27.82

0x8000004d

Extern

1.10.91.0

10.8.1.2

0x80000041

Extern

1.4.110.0

10.6.1.2

0x80000041

Router

10.5.1.18

10.5.1.18

0x8000005f

Network

10.5.5.2

10.5.1.18

0x80000033

Summary

10.8.59.0

172.25.27.82

0x8000003a

Summary

10.8.62.0

172.25.27.82

0x80000025

10.5.10.2
ge-1/2/0.10
ExStart
10.5.1.38
area 0.0.0.1, opt 0x42, DR 10.5.10.2, BDR 10.5.10.1
Up 06:09:42
master, seq 0xac1530f8, rexmit DBD in 2 sec
rexmit LSREQ in 0 sec
10.5.11.2
ge-1/2/0.11
Full
10.5.1.42
area 0.0.0.1, opt 0x42, DR 10.5.11.2, BDR 10.5.11.1
Up 06:09:42, adjacent 05:27:00
Link state retransmission list:
Type
Summary

1912

LSA ID
10.8.58.0

Adv rtr
172.25.27.82

Seq
0x8000004d

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Extern

1.10.91.0

10.8.1.2

0x80000041

Extern

1.1.247.0

10.5.1.2

0x8000003f

Extern

1.4.110.0

10.6.1.2

0x80000041

Router

10.5.1.18

10.5.1.18

0x8000005f

Network

10.5.5.2

10.5.1.18

0x80000033

Summary

10.8.59.0

172.25.27.82

0x8000003a

show ospf3 neighbor detail

user@host> show ospf3 neighbor detail
ID
Interface
State
10.255.71.13
fe-0/0/2.0
Full
Neighbor-address fe80::290:69ff:fe9b:e002
area 0.0.0.0, opt 0x13, OSPF3-Intf-Index 2
DR-ID 10.255.71.13, BDR-ID 10.255.71.12
Up 02:51:43, adjacent 02:51:43

Pri
128

Dead
30

show ospf neighbor area area-id

user@host >show ospf neighbor area 1.1.1.1
Address
Interface
192.168.37.47
so-0/0/0.0
Area 1.1.1.1
192.168.37.55
so-1/0/0.0
Area 1.1.1.1

State
Full

ID
10.255.245.4

Pri
128

Dead
33

Full

10.255.245.5

128

37

ID
10.255.245.4

Pri
128

Dead
37

10.255.245.4

128

33

10.255.245.4

128

32

show ospf neighbor interface interface-name

user@host >show ospf neighbor interface so-0/0/0.0
Address
Interface
State
192.168.37.47
so-0/0/0.0
Full
Area 0.0.0.0
192.168.37.47
so-0/0/0.0
Full
Area 1.1.1.1
192.168.37.47
so-0/0/0.0
Full
Area 2.2.2.2

show ospf3 neighbor instance all (OSPFv3 Multiple Family Address Support Enabled)
user @host > show ospf3 neighbor instance all
Instance: ina
Realm: ipv6-unicast
ID
Interface
State
100.1.1.1
fe-0/0/2.0
Full
Neighbor-address fe80::217:cb00:c87c:8c03
Instance: inb
Realm: ipv4-unicast
ID
Interface
State
100.1.2.1
fe-0/0/2.1
Full
Neighbor-address fe80::217:cb00:c97c:8c03

Copyright 2014, Juniper Networks, Inc.

Pri
128

Pri
128

Dead
37

Dead
33

1913

Interfaces Fundamentals for Routing Devices

show (ospf | ospf3) overview

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1914

Syntax (EX Series Switch and QFX Series) on page 1914
show (ospf | ospf3) overview
<brief | extensive>
<instance instance-name>
<logical-system (all | logical-system-name)>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
show (ospf | ospf3) overview
<brief | extensive>
<instance instance-name>

Command introduced in Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
realm option introduced in Junos OS Release 9.2.
Database protection introduced in Junos 10.2.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Display Open Shortest Path First (OSPF) overview information.
noneDisplay standard information about all OSPF neighbors for all routing instances.
brief | extensive(Optional) Display the specified level of output.
instance instance-name(Optional) Display all OSPF interfaces under the named routing

instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) (OSPFv3 only) Display

information about the specified OSPFv3 realm, or address family. Use the realm
option to specify an address family for OSPFv3 other than IPv6 unicast, which is the
default.
Required Privilege
Level
List of Sample Output

Output Fields

1914

view

show ospf overview on page 1916

show ospf overview (With Database Protection) on page 1917
show ospf3 overview (With Database Protection) on page 1917
show ospf overview extensive on page 1917
Table 186 on page 1915 lists the output fields for the show ospf overview command. Output
fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 186: show ospf overview Output Fields

Field name

Field Description

Level of Output

Instance

OSPF routing instance.

All levels

Router ID

Router ID of the routing device.

All levels

Route table index

Route table index.

All levels

Configured
overload

Overload capability is enabled. If the overload timer is also configured, display

the time that remains before it is set to expire. This field is not displayed after
the timer expires.

All levels

Toplogy

Topology identifier.

All levels

Prefix export count

Number of prefixes exported into OSPF.

All levels

Full SPF runs

Number of complete Shortest Path First calculations.

All levels

SPF delay

Delay before performing consecutive Shortest Path First calculations.

All levels

SPF holddown

Delay before performing additional Shortest Path First (SPF) calculations after
the maximum number of consecutive SPF calculations is reached.

All levels

SPF rapid runs

Maximum number of Shortest Path First calculations that can be performed in

succession before the hold-down timer begins.

All levels

LSA refresh time

Refresh period for link-state advertisement (in minutes).

All levels

Database
protection state

Current state of database protection.

All levels

Warning threshold

Threshold at which a warning message is logged (percentage of maximum LSA

count).

All levels

Non self-generated
LSAs

Number of LSAs whose router ID is not equal to the local router ID: Current,
Warning (threshold), and Allowed.

All levels

Ignore time

How long the database has been in the ignore state.

All levels

Reset time

How long the database must stay out of the ignore or isolated state before it
returns to normal operations.

All levels

Ignore count

Number of times the database has been in the ignore state: Current and Allowed.

All levels

Restart

Graceful restart capability: enabled or disabled.

All levels

Restart duration

Time period for complete reacquisition of OSPF neighbors.

All levels

Restart grace
period

Time period for which the neighbors should consider the restarting routing device
as part of the topology.

All levels

Copyright 2014, Juniper Networks, Inc.

1915

Interfaces Fundamentals for Routing Devices

Table 186: show ospf overview Output Fields (continued)

Field name

Field Description

Level of Output

Graceful restart
helper mode

(OSPFv2) Standard graceful restart helper capability (based on RFC 3623):

enabled or disabled.

All levels

Restart-signaling
helper mode

(OSPFv2) Restart signaling-based graceful restart helper capability (based on

RFC 4811, RFC 4812, and RFC 4813): enabled or disabled.

All levels

Helper mode

(OSPFv3) Graceful restart helper capability: enabled or disabled.

All levels

Trace options

OSPF-specific trace options.

extensive

Trace file

Name of the file to receive the output of the tracing operation.

extensive

Area

Area number. Area 0.0.0.0 is the backbone area.

All levels

Stub type

Stub type of area: Normal Stub, Not Stub, or Not so Stubby Stub.

All levels

Authentication
Type

Type of authentication: None, Password, or MD5.

All levels

NOTE: The Authentication Type field refers to the authentication configured at

the [edit protocols ospf area area-id] level. Any authentication configured for an
interface in this area will not affect the value of this field.
Area border routers

Number of area border routers.

All levels

Neighbors

Number of autonomous system boundary routers.

All levels

Sample Output
show ospf overview
user@host> show ospf overview
Instance: master
Router ID: 10.255.245.6
Route table index: 0
Configured overload, expires in 118 seconds
LSA refresh time: 50 minutes
Restart: Enabled
Restart duration: 20 sec
Restart grace period: 40 sec
Helper mode: enabled
Area: 0.0.0.0
Stub type: Not Stub
Authentication Type: None
Area border routers: 0, AS boundary routers: 0
Neighbors
Up (in full state): 0
Topology: default (ID 0)
Prefix export count: 0
Full SPF runs: 1
SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3

1916

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show ospf overview (With Database Protection)

user@host> show ospf overview
Instance: master
Router ID: 10.255.112.218
Route table index: 0
LSA refresh time: 50 minutes
Traffic engineering
Restart: Enabled
Restart duration: 180 sec
Restart grace period: 210 sec
Graceful restart helper mode: Enabled
Restart-signaling helper mode: Enabled
Database protection state: Normal
Warning threshold: 70 percent
Non self-generated LSAs: Current 582, Warning 700, Allowed 1000
Ignore time: 30, Reset time: 60
Ignore count: Current 0, Allowed 1
Area: 0.0.0.0
Stub type: Not Stub
Authentication Type: None
Area border routers: 0, AS boundary routers: 0
Neighbors
Up (in full state): 160
Topology: default (ID 0)
Prefix export count: 0
Full SPF runs: 70
SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3
Backup SPF: Not Needed

show ospf3 overview (With Database Protection)

user@host> show ospf3 overview
Instance: master
Router ID: 10.255.112.128
Route table index: 0
LSA refresh time: 50 minutes
Database protection state: Normal
Warning threshold: 80 percent
Non self-generated LSAs: Current 3, Warning 8, Allowed 10
Ignore time: 30, Reset time: 60
Ignore count: Current 0, Allowed 2
Area: 0.0.0.0
Stub type: Not Stub
Area border routers: 0, AS boundary routers: 0
Neighbors
Up (in full state): 1
Topology: default (ID 0)
Prefix export count: 0
Full SPF runs: 7
SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3
Backup SPF: Not Needed

show ospf overview extensive

user@host> show ospf overview extensive
Instance: master
Router ID: 1.1.1.103
Route table index: 0
Full SPF runs: 13, SPF delay: 0.200000 sec
LSA refresh time: 50 minutes

Copyright 2014, Juniper Networks, Inc.

1917

Interfaces Fundamentals for Routing Devices

Restart: Disabled
Trace options: lsa
Trace file: /var/log/ospf size 131072 files 10
Area: 0.0.0.0
Stub type: Not Stub
Authentication Type: None
Area border routers: 0, AS boundary routers: 0
Neighbors
Up (in full state): 1

1918

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show (ospf | ospf3) route

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)

Release Information

Description
Options

Syntax on page 1919

Syntax (EX Series Switch and QFX Series) on page 1919
show (ospf | ospf3) route
<brief | detail | extensive>
<abr | asbr | extern | inter | intra>
<destination>
<instance (default | ipv4-multicast | instance-name)>
<logical-system (default | ipv4-multicast | logical-system-name)>
<network>
<no-backup-coverage>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
<router>
<topology (default | ipv4-multicast | topology-name)>
<transit>
show (ospf | ospf3) route
<brief | detail | extensive>
<abr | asbr | extern | inter | intra>
<destination>
<instance instance-name
<network>
<no-backup-coverage>
<router>
<topology (default | ipv4-multicast | topology-name)>
<transit>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
topology option introduced in Junos OS Release 9.0.
realm option introduced in Junos OS Release 9.2.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Display the entries in the Open Shortest Path First (OSPF) routing table.
noneDisplay standard information about all entries in the OSPF routing table for all

routing instances and all topologies.

destinationDisplay routes to the specified IP address (with optional destination prefix

length).
brief | detail | extensive(Optional) Display the specified level of output.
abr(Optional) Display routes to area border routers.
asbr(Optional) Display routes to autonomous system border routers.
extern(Optional) Display external routes.
inter(Optional) Display interarea routes.

Copyright 2014, Juniper Networks, Inc.

1919

Interfaces Fundamentals for Routing Devices

intra(Optional) Display intra-area routes.

instance (default | ipv4-multicast | instance-name)(Optional) Display entries for the

default routing instance, the IPv4 multicast routing instance, or for the specified
routing instance.
logical-system (default | ipv4-multicast | logical-system-name)(Optional) Perform this

operation on the default logical system, the IPv4 multicast logical system, or on a
particular logical system.
network(Optional) Display routes to networks.
no-backup-coverage(Optional) Display routes with no backup coverage.
realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(OSPFv3 only) (Optional) Display

entries in the routing table for the specified OSPFv3 realm, or address family. Use
the realm option to specify an address family for OSPFv3 other than IPv6 unicast,
which is the default.
router(Optional) Display routes to all routers.
topology (default | ipv4-multicast | topology-name)(OSPFv2 only) (Optional) Display

routes for the default OSPF topology, IPv4 multicast topology, or for a particular
topology.
transit(Optional) (OSPFv3 only) Display OSPFv3 routes to pseudonodes.

Required Privilege
Level
List of Sample Output

Output Fields

view

show ospf route on page 1922

show ospf route detail on page 1922
show ospf3 route on page 1922
show ospf3 route detail on page 1923
show ospf route topology voice on page 1923
Table 187 on page 1920 list the output fields for the show (ospf | ospf3) route command.
Output fields are listed in the approximate order in which they appear.

Table 187: show (ospf | ospf3) route Output Fields

Field Name

Field Description

Output Level

Topology

Name of the topology.

All levels

Prefix

Destination of the route.

All levels

1920

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Table 187: show (ospf | ospf3) route Output Fields (continued)

Field Name

Field Description

Output Level

Path type

How the route was learned:

All levels

Route type

InterInterarea route

Ext1External type 1 route

Ext2External type 2 route

IntraIntra-area route

The type of routing device from which the route was learned:

AS BRRoute to AS border router.

Area BRRoute to area border router.

Area/AS BRRoute to router that is both an Area BR and AS BR.

NetworkNetwork router.

RouterRoute to a router that is neither an Area BR nor an AS BR.

Transit(OSPFv3 only) Route to a pseudonode representing a transit network,

All levels

LAN, or nonbroadcast multiaccess (NBMA) link.

DiscardRoute to a summary discard.

NH Type

Next-hop type: LSP or IP.

All levels

Metric

Route's metric value.

All levels

NH-interface

(OSPFv3 only) Interface through which the route's next hop is reachable.

All levels

NH-addr

(OSPFv3 only) IPv6 address of the next hop.

All levels

NextHop Interface

(OSPFv2 only) Interface through which the route's next hop is reachable.

All levels

Nexthop addr/label

(OSPFv2 only) If the NH Type is IP, then it is the address of the next hop. If the
NH Type is LSP, then it is the name of the label-switched path.

All levels

Area

Area ID of the route.

detail

Origin

Router from which the route was learned.

detail

Type 7

Route was learned through a not-so-stubby area (NSSA) link-state

advertisement (LSA).

detail

P-bit

Route was learned through NSSA LSA and the propagate bit was set.

detail

Fwd NZ

Forwarding address is nonzero. Fwd NZ is only displayed if the route is learned

through an NSSA LSA.

detail

Copyright 2014, Juniper Networks, Inc.

1921

Interfaces Fundamentals for Routing Devices

Table 187: show (ospf | ospf3) route Output Fields (continued)

Field Name

Field Description

Output Level

optional-capability

Optional capabilities propagated in the router LSA. This field is in the output for
intra-area router routes only (when Route Type is Area BR, AS BR, Area/AS BR,
or Router), not for interarea router routes or network routes. Three bits in this
field are defined as follows:

detail

priority

0x4 (V)Routing device is at the end of a virtual active link.

0x2 (E)Routing device is an autonomous system boundary router.

0x1 (B)Routing device is an area border router.

The priority assigned to the prefix:

high

medium

low

detail

NOTE: The priority field applies only to routes of type Network.

Sample Output
show ospf route
user@host> show ospf route
Prefix
Path
Type
10.255.71.12
Intra
10.255.71.13/32
Intra
192.168.222.84/30
Intra

Route
Type
Router
Network
Network

NH
Type
IP
IP
LSP

Metric
1
0
1

NextHop
Interface
fe-0/0/2.0
lo0.0
fe-0/0/2.0

Nexthop
addr/label
192.16.22.86
lsp-ab

show ospf route detail

user@host> show ospf route detail
Topology default Route Table:
Prefix
10.255.14.174
area 0.0.0.2,
10.255.14.178
area 0.0.0.2,
10.210.1.0/30
area 0.0.0.2,
100.1.1.1/32
area 0.0.0.2,
112.3.1.0/24
area 0.0.0.0,
200.3.3.0/30
area 0.0.0.2,

Path
Route
NH
Metric NextHop
Type
Type
Type
Interface
Inter AS BR
IP
210 t1-3/0/1.0
origin 10.255.14.185
Intra Router
IP
200 t3-3/1/3.0
origin 10.255.14.178, optional-capability 0x0
Intra Network
IP
10 t3-3/1/2.0
origin 10.255.14.172, priority medium
Inter Network
IP
210 t1-3/0/1.0
origin 10.255.14.185, priority low
Ext2
Network
IP
0 t1-3/0/1.0
origin 10.255.14.174, priority high
Inter Network
IP
220 t1-3/0/1.0
origin 10.255.14.185, priority high

Nexthop
addr/label

show ospf3 route

user@host> show ospf3 route
Prefix
Path
Type

1922

Route

NH

Type

Type

Metric

NextHop

Nexthop

Interface

addr/label

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

10.255.71.13
Intra Router
IP
1
NH-interface fe-0/0/2.0, NH-addr fe80::290:69ff:fe9b:e002
10.255.71.13;0.0.0.2
10.255.245.1
Intra Router
IP
40 fxp1.1

192.168.36.17

area 0.0.0.0, origin 10.255.245.1 optional-capability 0x0,

10.255.245.3
Intra AS BR
IP
1 fxp2.3

192.168.36.34

area 0.0.0.0, origin 10.255.245.3 optional-capability 0x0,

10.255.245.1/32
Intra Network
IP
40 fxp1.1

192.168.36.17

area 0.0.0.0, origin 10.255.245.1, priority high

10.255.245.2/32
Intra Network
IP
0 lo0.0
area 0.0.0.0, origin 10.255.245.2, priority medium
10.255.245.3/32
Intra Network
IP
1 fxp2.3

192.168.36.34

area 0.0.0.0, origin 10.255.245.3, priority low

Intra Transit
IP
1
NH-interface fe-0/0/2.0
192::168:222:84/126 Intra Network
IP
1
NH-interface fe-0/0/2.0
abcd::71:12/128
Intra Network
IP
0
NH-interface lo0.0
abcd::71:13/128
Intra Network
LSP
1
NH-interface fe-0/0/2.0, NH-addr lsp-cd

show ospf3 route detail

user@host> show ospf3 route detail
Prefix
10.255.14.174
NH-interface so-1/2/2.0
Area 0.0.0.0, Origin 10.255.14.174,
10.255.14.178
NH-interface t3-3/1/3.0
Area 0.0.0.0, Origin 10.255.14.178,
10.255.14.185;0.0.0.2
NH-interface t1-3/0/1.0
NH-interface so-1/2/2.0
Area 0.0.0.0, Origin 10.255.14.185
1000:1:1::1/128
NH-interface so-1/2/2.0
Area 0.0.0.0, Origin 10.255.14.174,
1001:2:1::/48
NH-interface so-1/2/2.0
Area 0.0.0.0, Origin 10.255.14.174,
1002:1:7::/48
NH-interface so-1/2/2.0
Area 0.0.0.0, Origin 10.255.14.174,
1002:3:4::/48
NH-interface so-1/2/2.0
Area 0.0.0.0, Origin 10.255.14.174,
abcd::10:255:14:172/128
NH-interface lo0.0
Area 0.0.0.0, Origin 10.255.14.172,

Path
type
Intra

NH
type
IP

Metric

Optional-capability 0x3
Intra Router

IP

200

Optional-capability 0x0
Intra Transit

IP

200

Network

IP

110

Priority low
Ext1
Network

IP

110

Fwd NZ, Priority medium

Ext2
Network

IP

Fwd NZ, Priority low

Ext2
Network

IP

Fwd NZ, Priority high

Intra Network

IP

Inter

Route
type
Area/AS BR

110

Priority low

show ospf route topology voice

user@host show ospf route topology voice

Copyright 2014, Juniper Networks, Inc.

1923

Interfaces Fundamentals for Routing Devices

Topology voice Route Table:

Prefix
Path
Route
Type
Type
10.255.8.2
Intra Router
10.255.8.3
Intra Router
10.255.8.1/32
Intra Network
10.255.8.2/32
Intra Network
10.255.8.3/32
Intra Network
192.168.8.0/29
Intra Network
192.168.8.44/30
Intra Network
192.168.8.46/32
Intra Network
192.168.8.48/30
Intra Network
192.168.8.52/30
Intra Network
192.168.9.44/30
Intra Network
192.168.9.45/32
Intra Network

1924

NH
Metric
Type
IP
1
IP
2
IP
0
IP
1
IP
2
IP
2
IP
2
IP
1
IP
1
IP
2
IP
1
IP
2

NextHop
Interface
so-0/2/0.0
so-0/2/0.0
lo0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/1.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0

Nexthop
addr/label

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

show (ospf | ospf3) statistics

List of Syntax

Syntax

Syntax (EX Series

Switch and QFX
Series)
Release Information

Description
Options

Syntax on page 1925

Syntax (EX Series Switch and QFX Series) on page 1925
show (ospf | ospf3) statistics
<instance instance-name>
<logical-system (all | logical-system-name)>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
show (ospf | ospf3) statistics
<instance instance-name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
realm option introduced in Junos OS Release 9.2.
Command introduced in Junos OS Release 11.3 for the QFX Series.
Display OSPF statistics.
noneDisplay OSPF statistics for all routing instances.
instance instance-name(Optional) Display all statistics for the specified routing instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) (OSPFv3 only) Display

all statistics for the specified OSPFv3 realm, or address family. Use the realm option
to specify an address family for OSPFv3 other than IPv6 unicast, which is the default.
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

clear (ospf | ospf3) statistics on page 1859

show ospf statistics on page 1927

show ospf statistics logical-system all on page 1927
show ospf3 statistics on page 1928
Table 188 on page 1925 lists the output fields for the show (ospf | ospf3) statistics command.
Output fields are listed in the approximate order in which they appear.

Table 188: show (ospf | ospf3) statistics Output Fields

Field Name

Field Description

Packet type

Type of OSPF packet.

Total Sent/Total Received

Total number of packets sent and received.

Copyright 2014, Juniper Networks, Inc.

1925

Interfaces Fundamentals for Routing Devices

Table 188: show (ospf | ospf3) statistics Output Fields (continued)

Field Name

Field Description

Last 5 seconds Sent/Last 5

seconds Received

Total number of packets sent and received in the last 5 seconds.

DBDs retransmitted

Total number of database description packets retransmitted, and

number retransmitted in the last 5 seconds.

LSAs flooded

Total number of link-state advertisements flooded, and number

flooded in the last 5 seconds.

LSAs flooded high-prio

Total number of high priority link-state advertisements flooded,

and number flooded in the last 5 seconds.
A link-state advertisement is deemed a high priority if it has changed
since it was last sent.

LSAs retransmitted

Total number of link-state advertisements retransmitted, and

number retransmitted in the last 5 seconds.

LSAs transmitted to nbr

Total number of link-state advertisements transmitted to a neighbor,

and number transmitted in the last 5 seconds.

LSAs requested

Total number of link-state advertisements requested by neighboring

devices, and number requested in the last 5 seconds.

LSAs acknowledged

Total number of link-state advertisements acknowledged, and

number acknowledged in the last 5 seconds.

Flood queue depth

Total number of entries in the extended queue.

Total rexmit entries

Total number of retransmission entries waiting to be sent from the

OSPF routing instance.

db summaries

Total number of database description summaries waiting to be sent

from the OSPF routing instance.

lsreq entries

Total number of link-state request entries waiting to be sent from

the OSPF routing instance.

Receive errors

Number and type of receive errors. Some sample receive errors

include:

mtu mismatches

no interface found

no virtual link found

nssa mismatches

stub area mismatches

subnet mismatches

If there are no receive errors, the output displays none.

1926

Copyright 2014, Juniper Networks, Inc.

Chapter 24: OSPF Operational Commands

Sample Output
show ospf statistics
user@host> show ospf statistics
Packet type
Total
Sent
Received
Hello
31
14
DbD
9
10
LSReq
2
2
LSUpdate
8
16
LSAck
9
9
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs

Last 5 seconds
Sent
Received
2
2
0
0
0
0
0
0
0
0

retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:

Flood queue depth

Total rexmit entries
db summaries
lsreq entries

3,
12,
0,
0,
3,
5,
19,

:
:
:
:

last
last
last
last
last
last
last

5
5
5
5
5
5
5

seconds
seconds
seconds
seconds
seconds
seconds
seconds

:
:
:
:
:
:
:

0
0
0
0
0
0
0

0
0
0
0

Receive errors:
862 no interface found
115923 no virtual link found

show ospf statistics logical-system all

user@host> show ospf statistics logical-system all
logical-system: C
OSPF instance is not running
----logical-system: B
Packet type
Hello
DbD
LSReq
LSUpdate
LSAck
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs

Total
Sent
313740
3
1
2752
1821

Last 5 seconds
Sent
Received
1
0
0
0
0
0
0
0
0
0

Received
313653
2
1
1825
2747

retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:

Flood queue depth

Total rexmit entries
db summaries
lsreq entries

:
:
:
:

0,
2741,
10,
0,
2,
1,
1831,

last
last
last
last
last
last
last

5
5
5
5
5
5
5

seconds
seconds
seconds
seconds
seconds
seconds
seconds

:
:
:
:
:
:
:

0
0
0
0
0
0
0

0
0
0
0

Receive errors:

Copyright 2014, Juniper Networks, Inc.

1927

Interfaces Fundamentals for Routing Devices

None
----logical-system: A
Packet type
Hello
DbD
LSReq
LSUpdate
LSAck
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs

Total
Sent
313698
2
1
1825
2747

Last 5 seconds
Sent
Received
0
0
0
0
0
0
0
0
0
0

Received
313695
3
1
2752
1821

retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:

Flood queue depth

Total rexmit entries
db summaries
lsreq entries

:
:
:
:

0,
1825,
10,
0,
1,
2,
2748,

last
last
last
last
last
last
last

5
5
5
5
5
5
5

seconds
seconds
seconds
seconds
seconds
seconds
seconds

:
:
:
:
:
:
:

0
0
0
0
0
0
0

0
0
0
0

Receive errors:
None
-----

show ospf3 statistics

user@host> show ospf3 statistics
Packet type
Total
Sent
Received
Hello
0
0
DbD
0
0
LSReq
0
0
LSUpdate
0
0
LSAck
0
0
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs

Last 5 seconds
Sent
Received
0
0
0
0
0
0
0
0
0
0

retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:

Flood queue depth

Total rexmit entries
db summaries
lsreq entries

:
:
:
:

0,
0,
0,
0,
0,
0,
0,

last
last
last
last
last
last
last

5
5
5
5
5
5
5

seconds
seconds
seconds
seconds
seconds
seconds
seconds

:
:
:
:
:
:
:

0
0
0
0
0
0
0

0
0
0
0

Receive errors:
None

1928

Copyright 2014, Juniper Networks, Inc.

CHAPTER 25

Protocol-Independent Routing
Operational Commands

show as-path

show as-path domain

show as-path summary

show route

show route active-path

show route advertising-protocol

show route all

show route aspath-regex

show route best

show route brief

show route ccc

show route community

show route community-name

show route damping

show route detail

show route exact

show route export

show route export vrf-target

show route extensive

show route flow validation

show route forwarding-table

show route forwarding-table interface-name

show route hidden

show route inactive-path

show route inactive-prefix

show route instance

Copyright 2014, Juniper Networks, Inc.

1929

Interfaces Fundamentals for Routing Devices

1930

show route label

show route label-switched-path

show route localization

show route martians

show route match-prefix

show route next-hop

show route no-community

show route output

show route protocol

show route range

show route receive-protocol

show route resolution

show route snooping

show route source-gateway

show route summary

show route table

show route terse

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show as-path
List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Syntax on page 1931

Syntax (EX Series Switches) on page 1931
show as-path
<brief | detail>
<logical-system (all | logical-system-name)>
show as-path
<brief | detail>

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.3 for the QFX Series.
Display the distribution of autonomous system (AS) paths that the local routing device
is using (usually through the routing table). Use this command to debug problems for
AS paths and to understand how AS paths have been manipulated through a policy
(through the as-path-prepend action) or through aggregation.
AS paths are stored in a hash table. A hash table is one method for fast lookup. Each
entry in the table is called a bucket. Junos OS computes a hash value that indicates in
which bucket the AS path is stored. The AS paths are dispersed among the hash buckets
so that a manageable number of AS paths is stored in each bucket. Only unique AS paths
are stored. Duplicate AS paths increase a reference count, but do not increase the number
of AS paths stored in the hash table.

Options

noneDisplay basic information about AS paths that the local routing device is using

(same as brief).
brief | detail(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

show as-path summary on page 1938

show as-path on page 1932

show as-path detail on page 1933
Table 189 on page 1932 lists the output fields for the show as-path command. Output fields
are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1931

Interfaces Fundamentals for Routing Devices

Table 189: show as-path Output Fields

Field Name

Field Description

Level of Output

Total AS paths

Total number of AS paths.

brief none

Bucket

Bucket number.

All levels

Count

Number of AS path entries in this bucket.

All levels

AS path

AS path through which the route was learned. The letters at the end of the AS
path indicate the path origin, providing an indication of the state of the route at
the point at which the AS path originated:

All levels

IIGP.

EEGP.

?Incomplete; typically, the AS path was aggregated.

AtomicRoute is an aggregate of several route prefixes.

AggregatorRouting device has summarized a range of prefixes.

domain

Number of independent AS domains. The AS paths of an independent AS

domain are not shared with the AS paths and AS path attributes of other
domains, including the master routing instance domain.

detail

neighbor as

AS peer address.

detail

length

Length of the AS path.

detail

segments

Length of the AS segment descriptor.

detail

references

Path reference count.

detail

Sample Output
show as-path
user@host> show as-path
Total AS paths: 30382
Bucket 0
Count: 36
I
14203 2914 174 31752 I
14203 2914 701 21512 I
14203 2914 1239 26632 I
14203 2914 1239 29704 I
14203 2914 4323 10248 I
14203 2914 4766 23560 I
14203 2914 6395 32776 I
14203 2914 7911 11272 I
14203 2914 12180 18440 I
14203 2914 17408 17416 I
14203 2914 701 702 24586 I
14203 2914 1239 4657 9226 I
14203 2914 1239 7132 16394 I
14203 2914 1299 8308 34826 I
14203 2914 3320 5603 28682 I

1932

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

14203 2914 3491 1680 33802 I

14203 2914 3549 7908 27658 I
14203 2914 3549 20804 30730 I
14203 2914 7018 2687 9226 I
14203 2914 174 9318 9318 23564 I
14203 2914 701 3786 3786 23564 I
14203 2914 701 4761 4795 9228 I
14203 2914 1239 7132 5673 18444 I
14203 2914 3491 20485 24588 24588 I
14203 2914 5511 2200 1945 2060 I
14203 2914 7911 14325 14325 14348 I
14203 2914 701 4637 9230 9230 9230 I
14203 2914 6395 14 14 14 14 I
14203 2914 9299 6163 6163 6163 6163 9232 I
14203 2914 3356 3356 3356 3356 3356 11955 21522 I
14203 2914 9837 9837 9219 I Aggregator: 9219 202.27.91.253
14203 2914 174 30209 30222 30222 30222 ?
14203 2914 1299 5377 I (Atomic) Aggregator: 5377 193.219.192.22
14203 2914 4323 36097 I (Atomic) Aggregator: 36097 216.69.252.254
14203 2914 209 2516 17676 23813 I (Atomic) Aggregator: 23813 219.127.233.66
Bucket 1
Count: 28
14203 2914 35847 I
14203 2914 174 19465 I
14203 2914 174 35849 I
14203 2914 2828 32777 I
14203 2914 4323 14345 I
14203 2914 4323 29705 I
14203 2914 6395 32777 I
...

show as-path detail

user@host> show as-path detail
Total AS paths: 30410
Bucket 0
Count: 36
AS path: I
domain 0, length 0, segments 0, references 54
AS path: 14203 2914 174 31752 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 701 21512 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 1239 26632 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 1239 29704 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 4323 10248 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 4766 23560 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 6395 32776 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 7911 11272 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 12180 18440 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 17408 17416 I
domain 1, neighbor as: 14203, length 4, segments
AS path: 14203 2914 701 702 24586 I
domain 1, neighbor as: 14203, length 5, segments
AS path: 14203 2914 1239 4657 9226 I

Copyright 2014, Juniper Networks, Inc.

1, references 2
1, references 2
1, references 2
1, references 2
1, references 2
1, references 2
1, references 3
1, references 2
1, references 3
1, references 3
1, references 3

1933

Interfaces Fundamentals for Routing Devices

domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain
AS path:
domain

1, neighbor as: 14203, length 5, segments

14203 2914 1239 7132 16394 I
1, neighbor as: 14203, length 5, segments
14203 2914 1299 8308 34826 I
1, neighbor as: 14203, length 5, segments
14203 2914 3320 5603 28682 I
1, neighbor as: 14203, length 5, segments
14203 2914 3491 1680 33802 I
1, neighbor as: 14203, length 5, segments
14203 2914 3549 7908 27658 I
1, neighbor as: 14203, length 5, segments
14203 2914 3549 20804 30730 I
1, neighbor as: 14203, length 5, segments
14203 2914 7018 2687 9226 I
1, neighbor as: 14203, length 5, segments
14203 2914 174 9318 9318 23564 I
1, neighbor as: 14203, length 6, segments
14203 2914 701 3786 3786 23564 I
1, neighbor as: 14203, length 6, segments
14203 2914 701 4761 4795 9228 I
1, neighbor as: 14203, length 6, segments
14203 2914 1239 7132 5673 18444 I
1, neighbor as: 14203, length 6, segments
14203 2914 3491 20485 24588 24588 I
1, neighbor as: 14203, length 6, segments
14203 2914 5511 2200 1945 2060 I
1, neighbor as: 14203, length 6, segments
14203 2914 7911 14325 14325 14348 I
1, neighbor as: 14203, length 6, segments
14203 2914 701 4637 9230 9230 9230 I
1, neighbor as: 14203, length 7, segments
14203 2914 6395 14 14 14 14 I
1, neighbor as: 14203, length 7, segments

1, references 7
1, references 2
1, references 2
1, references 2
1, references 2
1, references 2
1, references 2
1, references 3
1, references 2
1, references 2
1, references 14
1, references 2
1, references 4
1, references 2
1, references 2
1, references 3
1, references 10

...

1934

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show as-path domain

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description
Options

Syntax on page 1935

Syntax (EX Series Switches) on page 1935
show as-path domain
<logical-system (all | logical-system-name)>
show as-path domain

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display autonomous system (AS) path domain information.
none(Optional) Display AS path domain information for all routing instances.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show as-path domain on page 1937

Table 190 on page 1935 lists the output fields for the show as-path domain command.
Output fields are listed in the approximate order in which they appear

Table 190: show as-path domain Output Fields

Field Name

Field Description

Domain

Number of independent AS domains. The AS paths of an

independent AS domain are not shared with the AS paths and AS
path attributes of other domains, including the master routing
instance domain.

Primary

Primary AS number.

References

Path reference count.

Number Paths

Number of known AS paths.

Flags

Information about the AS path:

Local AS

Copyright 2014, Juniper Networks, Inc.

ASLoopPath contains an AS loop.

AtomicPath includes the ATOMIC_AGGREGATE path attribute.

LocalPath was created by local aggregation.

MasterPath was created by the master routing instance.

AS number of the local routing device.

1935

Interfaces Fundamentals for Routing Devices

Table 190: show as-path domain Output Fields (continued)

1936

Field Name

Field Description

Loops

How many times this AS number can appear in an AS path.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Sample Output
show as-path domain
user@host> show as-path domain
Domain: 1
Primary: 10458
References:
3 Paths:
Flags: Master
Local AS: 10458 Loops: 1

Copyright 2014, Juniper Networks, Inc.

30383

1937

Interfaces Fundamentals for Routing Devices

show as-path summary

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Syntax on page 1938

Syntax (EX Series Switches) on page 1938
show as-path summary
<logical-system (all | logical-system-name)>
show as-path summary

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display autonomous system (AS) path summary information.
AS paths are stored in a hash table. A hash table is one method for fast lookup. Each
entry in the table is called a bucket. Junos OS computes a hash value that indicates in
which bucket the AS path is stored. The AS paths are dispersed among the hash buckets
so that a manageable number of AS paths is stored in each bucket. Only unique AS paths
are stored. Duplicate AS paths increase a reference count, but do not increase the number
of AS paths stored in the hash table.

Options

none(Optional) Display AS path summary information for all routing instances.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

show as-path on page 1931

show as-path summary on page 1939

Table 191 on page 1938 lists the output fields for the show as-path summary command.
Output fields are listed in the approximate order in which they appear.

Table 191: show as-path summary Output Fields

1938

Field Name

Field Description

AS Paths

Number of AS paths.

Buckets

Number of hash buckets in use.

Max

Maximum number of AS path entries per bucket.

Min

Minimum number of AS path entries per bucket.

Avg

Average number of AS path entries per bucket.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 191: show as-path summary Output Fields (continued)

Field Name

Field Description

Std deviation

Standard deviation of AS path entries per bucket.

Sample Output
show as-path summary
user@host> show as-path summary
AS Paths Buckets
Max
Min
30425
1024
95
12

Copyright 2014, Juniper Networks, Inc.

Avg
29

Std deviation
6.481419

1939

Interfaces Fundamentals for Routing Devices

show route
List of Syntax

Syntax

Syntax (EX Series

Switches)

Release Information

Description
Options

Syntax on page 1940

Syntax (EX Series Switches) on page 1940
show route
<all>
<destination-prefix>
<logical-system (all | logical-system-name)>
<private>
show route
<all>
<destination-prefix>
<private>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Option private introduced in Junos OS Release 9.5.
Option private introduced in Junos OS Release 9.5 for EX Series switches.
Display the active entries in the routing tables.
noneDisplay brief information about all active entries in the routing tables.
all(Optional) Display information about all routing tables, including private, or internal,

routing tables.
destination-prefix(Optional) Display active entries for the specified address or range

of addresses.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

private(Optional) Display information only about all private, or internal, routing tables.

Required Privilege
Level
Related
Documentation

List of Sample Output

1940

view

Example: Configuring RIP

Example: Configuring RIPng

Example: Configuring IS-IS

Examples: Configuring Internal BGP Peering

Examples: Configuring External BGP Peering

Examples: Configuring OSPF Routing Policy

show route on page 1943

show route on page 1944

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route destination-prefix on page 1944

show route extensive on page 1944
Output Fields

Table 192 on page 1941 describes the output fields for the show route command. Output
fields are listed in the approximate order in which they appear.

Table 192: show route Output Fields

Field Name

Field Description

routing-table-name

Name of the routing table (for example, inet.0).

number destinations

Number of destinations for which there are routes in the routing table.

number routes

Number of routes in the routing table and total number of routes in the following states:

active (routes that are active).

holddown (routes that are in the pending state before being declared inactive). A holddown route

was once the active route and is no longer the active route. The route is in the holddown state
because a protocol still has interest in the route, meaning that the interest bit is set. A protocol
might have its interest bit set on the previously active route because the protocol is still advertising
the route. The route will be deleted after all protocols withdraw their advertisement of the route
and remove their interest bit. A persistent holddown state often means that the interested protocol
is not releasing its interest bit properly.
However, if you have configured advertisement of multiple routes (with the add-path or
advertise-inactive statement), the holddown bit is most likely set because BGP is advertising the
route as an active route. In this case, you can ignore the holddown state because nothing is wrong.

destination-prefix

hidden (routes that are not used because of a routing policy).

Route destination (for example:10.0.0.1/24). Sometimes the route information is presented in another
format, such as:

MPLS-label (for example, 80001).

interface-name (for example, ge-1/0/2).

neighbor-address:control-word-status:encapsulation type:vc-id :source (Layer 2 circuit only. For example,

10.1.1.195:NoCtrlWord:1:1:Local/96):

neighbor-addressAddress of the neighbor.

control-word-statusWhether the use of the control word has been negotiated for this virtual
circuit: NoCtrlWord or CtrlWord.

encapsulation typeType of encapsulation, represented by a number: (1) Frame Relay DLCI, (2)

ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet,
(6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport.

vc-idVirtual circuit identifier.

sourceSource of the advertisement: Local or Remote.

Copyright 2014, Juniper Networks, Inc.

1941

Interfaces Fundamentals for Routing Devices

Table 192: show route Output Fields (continued)

Field Name

Field Description

[ protocol, preference ]

Protocol from which the route was learned and the preference value for the route.

+A plus sign indicates the active route, which is the route installed from the routing table into the

forwarding table.

- A hyphen indicates the last active route.

*An asterisk indicates that the route is both the active and the last active route. An asterisk before
a to line indicates the best subpath to the route.

In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to
use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the
Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101.
If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it
has a higher LocalPref value and a lower Preference2 value.
weeks:days
hours:minutes:seconds

How long the route been known (for example, 2w4d 13:11:14, or 2 weeks, 4 days, 13 hours, 11 minutes,
and 14 seconds).

metric

Cost value of the indicated route. For routes within an AS, the cost is determined by the IGP and the
individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined
by a preference value.

localpref

Local preference value included in the route.

from

Interface from which the route was received.

AS path

AS path through which the route was learned. The letters at the end of the AS path indicate the path
origin, providing an indication of the state of the route at the point at which the AS path originated:

IIGP.

EEGP.

?Incomplete; typically, the AS path was aggregated.

When AS path numbers are included in the route, the format is as follows:

[ ]Brackets enclose the local AS number associated with the AS path if more than one AS number

is configured on the routing device, or if AS path prepending is configured.

{ }Braces enclose AS sets, which are groups of AS numbers in which the order does not matter.

A set commonly results from route aggregation. The numbers in each AS set are displayed in
ascending order.

( )Parentheses enclose a confederation.

( [ ] )Parentheses and brackets enclose a confederation set.

NOTE: In Junos OS Release 10.3 and later, the AS path field displays an unrecognized attribute and
associated hexadecimal value if BGP receives attribute 128 (attribute set) and you have not configured
an independent domain in any routing instance.

1942

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 192: show route Output Fields (continued)

Field Name

Field Description

validation-state

(BGP-learned routes) Validation status of the route:

InvalidIndicates that the prefix is found, but either the corresponding AS received from the EBGP

peer is not the AS that appears in the database, or the prefix length in the BGP update message is
longer than the maximum length permitted in the database.

UnknownIndicates that the prefix is not among the prefixes or prefix ranges in the database.

UnverifiedIndicates that the origin of the prefix is not verified against the database. This is because

the database got populated and the validation is not called for in the BGP import policy, although
origin validation is enabled, or the origin validation is not enabled for the BGP peers.

to

ValidIndicates that the prefix and autonomous system pair are found in the database.

Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.
If the destination is Discard, traffic is dropped.

via

Interface used to reach the next hop. If there is more than one interface available to the next hop, the
interface that is actually used is followed by the word Selected. This field can also contain the following
information:

WeightValue used to distinguish primary, secondary, and fast reroute backup routes. Weight

information is available when MPLS label-switched path (LSP) link protection, node-link protection,
or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight
value is preferred. Among routes with the same weight value, load balancing is possible.

BalanceBalance coefficient indicating how traffic of unequal cost is distributed among next hops

when a routing device is performing unequal-cost load balancing. This information is available
when you enable BGP multipath load balancing.

lsp-path-nameName of the LSP used to reach the next hop.

label-actionMPLS label and operation occurring at the next hop. The operation can be pop (where
a label is removed from the top of the stack), push (where another label is added to the label stack),
or swap (where a label is replaced by another label). For VPNs, expect to see multiple push

operations, corresponding to the inner and outer labels required for VPN routes (in the case of a
direct PE-to-PE connection, the VPN route would have the inner label push only).

Sample Output
show route
user@host> show route
inet.0: 11 destinations, 12 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:65500:1:10.0.0.20/240
*[MVPN/70] 19:53:41, metric2 1
Indirect
1:65500:1:10.0.0.40/240
*[BGP/170] 19:53:29, localpref 100, from 10.0.0.30
AS path: I
> to 10.0.24.4 via lt-0/3/0.24, label-switched-path toD
[BGP/170] 19:53:26, localpref 100, from 10.0.0.33
AS path: I
> to 10.0.24.4 via lt-0/3/0.24, label-switched-path toD
1:65500:1:10.0.0.60/240
*[BGP/170] 19:53:29, localpref 100, from 10.0.0.30

Copyright 2014, Juniper Networks, Inc.

1943

Interfaces Fundamentals for Routing Devices

AS path: I
> to 10.0.28.8 via lt-0/3/0.28, label-switched-path toF
[BGP/170] 19:53:25, localpref 100, from 10.0.0.33
AS path: I
> to 10.0.28.8 via lt-0/3/0.28, label-switched-path toF

show route
The following sample output shows a VPN route with composite next hops enabled. The
first Push operation corresponds to the outer label. The second Push operation
corresponds to the inner label.
user@host> show route 70.0.0.0
13979:665001.inet.0: 871 destinations, 3556 routes (871 active, 0 holddown, 0
hidden)
+ = Active Route, - = Last Active, * = Both
70.0.0.0/24

@[BGP/170] 00:28:32, localpref 100, from 10.9.9.160

AS path: 13980 ?, validation-state: unverified
> to 10.100.0.42 via ae2.0, Push 16, Push 300368(top)
[BGP/170] 00:28:28, localpref 100, from 10.9.9.169
AS path: 13980 ?, validation-state: unverified
> to 10.100.0.42 via ae2.0, Push 126016, Push 300368(top)
#[Multipath/255] 00:28:28, metric2 102
> to 10.100.0.42 via ae2.0, Push 16, Push 300368(top)
to 10.100.0.42 via ae2.0, Push 16, Push 300368(top)

show route destination-prefix

user@host> show route 172.16.0.0/12
inet.0: 10 destinations, 10 routes (9 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.0.0/12

*[Static/5] 2w4d 12:54:27

> to 192.168.167.254 via fxp0.0

show route extensive

user@host> show route extensive
v1.mvpn.0: 5 destinations, 8 routes (5 active, 1 holddown, 0 hidden)
1:65500:1:10.0.0.40/240 (1 entry, 1 announced)
*BGP
Preference: 170/-101
PMSI: Flags 0x0: Label[0:0:0]: PIM-SM: Sender 10.0.0.40 Group 225.1.1.1
Next hop type: Indirect
Address: 0x92455b8
Next-hop reference count: 2
Source: 10.0.0.30
Protocol next hop: 10.0.0.40
Indirect next hop: 2 no-forward
State: <Active Int Ext>
Local AS: 65500 Peer AS: 65500
Age: 3 Metric2: 1
Validation State: unverified
Task: BGP_65500.10.0.0.30+179
Announcement bits (2): 0-PIM.v1 1-mvpn global task
AS path: I (Originator) Cluster list: 10.0.0.30
AS path: Originator ID: 10.0.0.40
Communities: target:65520:100

1944

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Import Accepted
Localpref: 100
Router ID: 10.0.0.30
Primary Routing Table bgp.mvpn.0
Indirect next hops: 1
Protocol next hop: 10.0.0.40 Metric: 1
Indirect next hop: 2 no-forward
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.0.24.4 via lt-0/3/0.24 weight 0x1
10.0.0.40/32 Originating RIB: inet.3
Metric: 1
Node path count: 1
Forwarding nexthops: 1
Nexthop: 10.0.24.4 via lt-0/3/0.24

Copyright 2014, Juniper Networks, Inc.

1945

Interfaces Fundamentals for Routing Devices

show route active-path

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Options

Syntax on page 1946

Syntax (EX Series Switches) on page 1946
show route active-path
<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>
show route active-path
<brief | detail | extensive | terse>

Command introduced in Junos OS Release 8.0.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display all active routes for destinations. An active route is a route that is selected as the
best path. Inactive routes are not displayed.
noneDisplay all active routes.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route active-path on page 1946

show route active-path brief on page 1947
show route active-path detail on page 1947
show route active-path extensive on page 1948
show route active-path terse on page 1950
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route active-path
user@host> show route active-path
inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
10.255.70.19/32
10.255.71.50/32
100.1.2.0/24

1946

*[Direct/0] 21:33:52
> via lo0.0
*[IS-IS/15] 00:18:13, metric 10
> to 100.1.2.1 via so-2/1/3.0
*[Direct/0] 00:18:36
> via so-2/1/3.0

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

100.1.2.2/32
192.168.64.0/21

*[Local/0] 00:18:41
Local via so-2/1/3.0
*[Direct/0] 21:33:52
> via fxp0.0
*[Local/0] 21:33:52
Local via fxp0.0

192.168.70.19/32

show route active-path brief

The output for the show route active-path brief command is identical to that for the show
route active-path command. For sample output, see show route active-path on page 1946.
show route active-path detail
user@host> show route active-path detail
inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden)
10.255.70.19/32 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 3
Next hop: via lo0.0, selected
State: Active Int
Local AS:
200
Age: 21:37:10
Task: IF
Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3
AS path: I
10.255.71.50/32 (1 entry, 1 announced)
*IS-IS Preference: 15
Level: 1
Next hop type: Router, Next hop index: 397
Next-hop reference count: 4
Next hop: 100.1.2.1 via so-2/1/3.0, selected
State: Active Int
Local AS:
200
Age: 21:31
Metric: 10
Task: IS-IS
Announcement bits (4): 0-KRT 2-IS-IS 5-Resolve tree 2 6-Resolve
tree 3
AS path: I
100.1.2.0/24 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 3
Next hop: via so-2/1/3.0, selected
State: Active Int
Local AS:
200
Age: 21:54
Task: IF
Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3
AS path: I
100.1.2.2/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local

Copyright 2014, Juniper Networks, Inc.

1947

Interfaces Fundamentals for Routing Devices

Next-hop reference count: 11

Interface: so-2/1/3.0
State: Active NoReadvrt Int
Local AS:
200
Age: 21:59
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3
AS path: I
192.168.64.0/21 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 3
Next hop: via fxp0.0, selected
State: Active Int
Local AS:
200
Age: 21:37:10
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3
AS path: I
192.168.70.19/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local
Next-hop reference count: 11
Interface: fxp0.0
State: Active NoReadvrt Int
Local AS:
200
Age: 21:37:10
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3
AS path: I

show route active-path extensive

user@host> show route active-path extensive
inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden)
10.255.70.19/32 (1 entry, 1 announced)
TSI:
IS-IS level 1, LSP fragment 0
IS-IS level 2, LSP fragment 0
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 3
Next hop: via lo0.0, selected
State: Active Int
Local AS:
200
Age: 21:39:47
Task: IF
Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3
AS path: I
10.255.71.50/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.255.71.50/32 -> {100.1.2.1}
IS-IS level 2, LSP fragment 0
*IS-IS Preference: 15
Level: 1
Next hop type: Router, Next hop index: 397

1948

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Next-hop reference count: 4

Next hop: 100.1.2.1 via so-2/1/3.0, selected
State: Active Int
Local AS:
200
Age: 24:08
Metric: 10
Task: IS-IS
Announcement bits (4): 0-KRT 2-IS-IS 5-Resolve tree 2 6-Resolve
tree 3
AS path: I
100.1.2.0/24 (1 entry, 1 announced)
TSI:
IS-IS level 1, LSP fragment 0
IS-IS level 2, LSP fragment 0
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 3
Next hop: via so-2/1/3.0, selected
State: Active Int
Local AS:
200
Age: 24:31
Task: IF
Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3
AS path: I
100.1.2.2/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local
Next-hop reference count: 11
Interface: so-2/1/3.0
State: Active NoReadvrt Int
Local AS:
200
Age: 24:36
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3
AS path: I
192.168.64.0/21 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 3
Next hop: via fxp0.0, selected
State: Active Int
Local AS:
200
Age: 21:39:47
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3
AS path: I
192.168.70.19/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local
Next-hop reference count: 11
Interface: fxp0.0
State: Active NoReadvrt Int
Local AS:
200
Age: 21:39:47
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3

Copyright 2014, Juniper Networks, Inc.

1949

Interfaces Fundamentals for Routing Devices

AS path: I

show route active-path terse

user@host> show route active-path terse
inet.0: 7 destinations, 7 routes (6 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A
*
*
*
*
*
*

1950

Destination
10.255.70.19/32
10.255.71.50/32
100.1.2.0/24
100.1.2.2/32
192.168.64.0/21
192.168.70.19/32

P Prf
D
0
I 15
D
0
L
0
D
0
L
0

Metric 1
10

Metric 2

Next hop
>lo0.0
>100.1.2.1
>so-2/1/3.0
Local
>fxp0.0
Local

AS path

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route advertising-protocol

Syntax

Release Information
Description

Options

show route advertising-protocol protocol neighbor-address

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display the routing information as it has been prepared for advertisement to a particular
neighbor of a particular dynamic routing protocol.
brief | detail | extensive | terse(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor-addressAddress of the neighboring router to which the route entry is being

transmitted.
protocolProtocol transmitting the route:

Additional Information

Required Privilege
Level
Related
Documentation

bgpBorder Gateway Protocol

dvmrpDistance Vector Multicast Routing Protocol

msdpMulticast Source Discovery Protocol

pimProtocol Independent Multicast

ripRouting Information Protocol

ripngRouting Information Protocol next generation

Routes displayed are routes that the routing table has exported into the routing protocol
and that have been filtered by the associated protocol's export routing policy statements.
view

Example: Configuring the MED Attribute Directly

List of Sample Output

show route advertising-protocol bgp (Layer 3 VPN) on page 1953

show route advertising-protocol bgp detail on page 1954
show route advertising-protocol bgp detail (Layer 2 VPN) on page 1954
show route advertising-protocol bgp detail (Layer 3 VPN) on page 1954
show route advertising-protocol bgp extensive all (Next Hop Self with RIB-out IP
Address) on page 1954

Output Fields

Table 193 on page 1952 lists the output fields for the show route advertising-protocol
command. Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

1951

Interfaces Fundamentals for Routing Devices

Table 193: show route advertising-protocol Output Fields

Field Name

Field Description

Level of Output

routing-table-name

Name of the routing tablefor example, inet.0.

All levels

number
destinations

Number of destinations for which there are routes in the routing table.

All levels

number routes

Number of routes in the routing table and total number of routes in the following
states:

All levels

active (routes that are active)

holddown (routes that are in the pending state before being declared inactive)

hidden (routes that are not used because of a routing policy)

Prefix

Destination prefix.

brief none

destination-prefix
(entry , announced)

Destination prefix. The entry value is the number of routes for this destination,
and the announced value is the number of routes being announced for this
destination.

detail extensive

BGP group and type

BGP group name and type (Internal or External).

detail extensive

Route Distinguisher

Unique 64-bit prefix augmenting each IP subnet.

detail extensive

Advertised Label

Incoming label advertised by the LDP. When an IP packet enters a label-switched

path (LSP), the ingress router examines the packet and assigns it a label based
on its destination, placing the label in the packet's header. The label transforms
the packet from one that is forwarded based on its IP routing information to
one that is forwarded based on information associated with the label.

detail extensive

Label-Base, range

First label in a block of labels and label block size. A remote PE router uses this
first label when sending traffic toward the advertising PE router.

detail extensive

VPN Label

Virtual private network (VPN) label. Packets are sent between CE and PE routers
by advertising VPN labels. VPN labels transit over either an RSVP or an LDP
LSP tunnel.

detail extensive

Nexthop

Next hop to the destination. An angle bracket (>) indicates that the route is the
selected route.

All levels

If the next-hop advertisement to the peer is Self, and the RIB-out next hop is a
specific IP address, the RIB-out IP address is included in the extensive output.
See show route advertising-protocol bgp extensive all (Next Hop Self with RIB-out
IP Address) on page 1954.
MED

Multiple exit discriminator value included in the route.

brief

Lclpref or Localpref

Local preference value included in the route.

All levels

1952

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 193: show route advertising-protocol Output Fields (continued)

Field Name

Field Description

Level of Output

AS path

AS path through which the route was learned. The letters at the end of the AS
path indicate the path origin, providing an indication of the state of the route at
the point at which the AS path originated:

All levels

IIGP.

EEGP.

?Incomplete; typically, the AS path was aggregated.

When AS path numbers are included in the route, the format is as follows:

[ ]Brackets enclose the local AS number associated with the AS path if

configured on the router, or if AS path prepending is configured.

{ }Braces enclose AS sets, which are groups of AS numbers in which the

order does not matter. A set commonly results from route aggregation. The
numbers in each AS set are displayed in ascending order.

( )Parentheses enclose a confederation.

( [ ] )Parentheses and brackets enclose a confederation set.

NOTE: In Junos OS Release 10.3 and later, the AS path field displays an
unrecognized attribute and associated hexadecimal value if BGP receives
attribute 128 (attribute set) and you have not configured an independent domain
in any routing instance.
Communities

Community path attribute for the route. See the output field table for the show
route detail command for all possible values for this field.

detail extensive

AIGP

Accumulated interior gateway protocol (AIGP) BGP attribute.

detail extensive

Attrset AS

Number, local preference, and path of the autonomous system (AS) that
originated the route. These values are stored in the Attrset attribute at the
originating router.

detail extensive

Layer2-info: encaps

Layer 2 encapsulation (for example, VPLS).

detail extensive

control flags

Control flags: none or Site Down.

detail extensive

mtu

Maximum transmission unit (MTU) of the Layer 2 circuit.

detail extensive

Sample Output
show route advertising-protocol bgp (Layer 3 VPN)
user@host> show route advertising-protocol bgp 10.255.14.171
VPN-A.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.172/32
Self
1
100 I
VPN-B.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.181/32
Self
2
100 I

Copyright 2014, Juniper Networks, Inc.

1953

Interfaces Fundamentals for Routing Devices

show route advertising-protocol bgp detail

user@host> show route advertising-protocol bgp 111.222.1.3 detail
bgp20.inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
111.222.1.11/32 (1 entry, 1 announced)
BGP group pe-pe type Internal
Route Distinguisher: 111.255.14.11:69
Advertised Label: 100000
next hop: Self
Localpref: 100
AS path: 2 I
Communities: target:69:20
AIGP 210
111.8.0.0/16 (1 entry, 1 announced)
BGP group pe-pe type Internal
Route Distinguisher: 111.255.14.11:69
Advertised Label: 100000
Next hop: Self
Localpref: 100
AS path: 2 I
Communities: target:69:20
AIGP 210

show route advertising-protocol bgp detail (Layer 2 VPN)

user@host> show route advertising-protocol bgp 192.168.24.1 detail
vpn-a.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
192.168.16.1:1:1:1/96 (1 entry, 1 announced)
BGP group int type Internal
Route Distinguisher: 192.168.16.1:1
Label-base : 32768, range : 3
Nexthop: Self
Localpref: 100
AS path: I
Communities: target:65412:100
AIGP 210
Layer2-info: encaps:VLAN, control flags:, mtu:

show route advertising-protocol bgp detail (Layer 3 VPN)

user@host> show route advertising-protocol bgp 10.255.14.176 detail
vpna.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
* 10.49.0.0/30 (1 entry, 1 announced)
BGP group ibgp type Internal
Route Distinguisher: 10.255.14.174:2
VPN Label: 101264
Nexthop: Self
Localpref: 100
AS path: I
Communities: target:200:100
AIGP 210
AttrSet AS: 100
Localpref: 100
AS path: I
...

show route advertising-protocol bgp extensive all (Next Hop Self with RIB-out IP Address)
user@host> show route advertising-protocol bgp 200.0.0.2 170.0.1.0/24 extensive all
inet.0: 13 destinations, 19 routes (13 active, 0 holddown, 6 hidden)
170.0.1.0/24 (2 entries, 1 announced)

1954

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

BGP group eBGP-INTEROP type External

Nexthop: Self (rib-out 10.100.3.2)
AS path: [4713] 200 I
...

Copyright 2014, Juniper Networks, Inc.

1955

Interfaces Fundamentals for Routing Devices

show route all

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Options

Syntax on page 1956

Syntax (EX Series Switches) on page 1956
show route all
<logical-system (all | logical-system-name)>
show route all

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display information about all routes in all routing tables, including private, or internal,
tables.
noneDisplay information about all routes in all routing tables, including private, or

internal, tables.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show route all on page 1956

In Junos OS Release 9.5 and later, only the output fields for the show route all command
display all routing tables, including private, or hidden, routing tables. The output field
table of the show route command does not display entries for private, or hidden, routing
tables in Junos OS Release 9.5 and later.

Sample Output
show route all
The following example displays a snippet of output from the show route command and
then displays the same snippet of output from the show route all command:
user@host> show route
mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
0
*[MPLS/0] 2d 02:24:39, metric 1
Receive
1
*[MPLS/0] 2d 02:24:39, metric 1
Receive
2
*[MPLS/0] 2d 02:24:39, metric 1
Receive
800017
*[VPLS/7] 1d 14:00:16
> via vt-3/2/0.32769, Pop
800018
*[VPLS/7] 1d 14:00:26
> via vt-3/2/0.32772, Pop

1956

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

user@host> show route all

mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
0
*[MPLS/0] 2d 02:19:12, metric 1
Receive
1
*[MPLS/0] 2d 02:19:12, metric 1
Receive
2
*[MPLS/0] 2d 02:19:12, metric 1
Receive
800017
*[VPLS/7] 1d 13:54:49
> via vt-3/2/0.32769, Pop
800018
*[VPLS/7] 1d 13:54:59
> via vt-3/2/0.32772, Pop
vt-3/2/0.32769
[VPLS/7] 1d 13:54:49
Unusable
vt-3/2/0.32772
[VPLS/7] 1d 13:54:59
Unusable

Copyright 2014, Juniper Networks, Inc.

1957

Interfaces Fundamentals for Routing Devices

show route aspath-regex

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Options

Syntax on page 1958

Syntax (EX Series Switches) on page 1958
show route aspath-regex regular-expression
<logical-system (all | logical-system-name)>
show route aspath-regex regular-expression

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the entries in the routing table that match the specified autonomous system
(AS) path regular expression.
regular-expressionRegular expression that matches an entire AS path.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Additional Information

You can specify a regular expression as:

An individual AS number

A period wildcard used in place of an AS number

An AS path regular expression that is enclosed in parentheses

You also can include the operators described in the table of AS path regular expression
operators in the Junos Policy Framework Configuration Guide. The following list summarizes
these operators:

{m,n}At least m and at most n repetitions of the AS path term.

{m}Exactly m repetitions of the AS path term.

{m,}m or more repetitions of the AS path term.

*Zero or more repetitions of an AS path term.

+One or more repetitions of an AS path term.

?Zero or one repetition of an AS path term.

aspath_term | aspath_termMatch one of the two AS path terms.

When you specify more than one AS number or path term, or when you include an
operator in the regular expression, enclose the entire regular expression in quotation
marks. For example, to match any path that contains AS number 234, specify the
following command:
show route aspath-regex ".* 234 .*"

1958

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Example: Using AS Path Regular Expressions

show route aspath-regex (Matching a Specific AS Number) on page 1959

show route aspath-regex (Matching Any Path with Two AS Numbers) on page 1959
For information about output fields, see the output field table for the show route
command.

Sample Output
show route aspath-regex (Matching a Specific AS Number)
user@host> show route aspath-regex 65477
inet.0: 46411 destinations, 46411 routes (46409 active, 0 holddown, 2 hidden)
+ = Active Route, - = Last Active, * = Both
111.222.1.0/25

111.222.1.128/25

*[BGP/170] 00:08:48, localpref 100, from 111.222.2.24

AS Path: [65477] ({65488 65535}) IGP
to 111.222.18.225 via fpa0.0(111.222.18.233)
*[IS-IS/15] 09:15:37, metric 37, tag 1
to 111.222.18.225 via fpa0.0(111.222.18.233)
[BGP/170] 00:08:48, localpref 100, from 111.222.2.24
AS Path: [65477] ({65488 65535}) IGP
to 111.222.18.225 via fpa0.0(111.222.18.233)

...

show route aspath-regex (Matching Any Path with Two AS Numbers)

user@host> show route aspath-regex ?.* 234 3561 .*?
inet.0: 46351 destinations, 46351 routes (46349 active, 0 holddown, 2 hidden)
+ = Active Route, - = Last Active, * = Both
9.20.0.0/17

12.10.231.0/24

24.64.32.0/19

*[BGP/170] 01:35:00, localpref 100, from 131.103.20.49

AS Path: [666] 234 3561 2685 2686 Incomplete
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
*[BGP/170] 01:35:00, localpref 100, from 131.103.20.49
AS Path: [666] 234 3561 5696 7369 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
*[BGP/170] 01:34:59, localpref 100, from 131.103.20.49
AS Path: [666] 234 3561 6327 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)

...

Copyright 2014, Juniper Networks, Inc.

1959

Interfaces Fundamentals for Routing Devices

show route best

List of Syntax

Syntax on page 1960

Syntax (EX Series Switches) on page 1960

Syntax

show route best destination-prefix

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)
Release Information

Description

Options

show route best destination-prefix

<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the route in the routing table that is the best route to the specified address or
range of addresses. The best route is the longest matching route.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

destination-prefixAddress or range of addresses.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route best on page 1960

show route best detail on page 1961
show route best extensive on page 1962
show route best terse on page 1962
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route best
user@host> show route best 10.255.70.103
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.255.70.103/32
*[OSPF/10] 1d 13:19:20, metric 2
> to 10.31.1.6 via ge-3/1/0.0
via so-0/3/0.0
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.255.70.103/32
*[RSVP/7] 1d 13:20:13, metric 2

1960

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

> via so-0/3/0.0, label-switched-path green-r1-r3

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.0.0/8
*[Direct/0] 2d 01:43:34
> via fxp2.0
[Direct/0] 2d 01:43:34
> via fxp1.0

show route best detail

user@host> show route best 10.255.70.103 detail
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
10.255.70.103/32 (1 entry, 1 announced)
*OSPF
Preference: 10
Next-hop reference count: 9
Next hop: 10.31.1.6 via ge-3/1/0.0, selected
Next hop: via so-0/3/0.0
State: <Active Int>
Local AS:
69
Age: 1d 13:20:06
Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
10.255.70.103/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
Next-hop reference count: 5
Next hop: via so-0/3/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 100016
State: <Active Int>
Local AS:
69
Age: 1d 13:20:59
Metric: 2
Task: RSVP
Announcement bits (1): 1-Resolve tree 2
AS path: I
private1__inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
10.0.0.0/8 (2 entries, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via fxp2.0, selected
State: <Active Int>
Age: 2d 1:44:20
Task: IF
AS path: I
Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via fxp1.0, selected
State: <NotBest Int>
Inactive reason: No difference
Age: 2d 1:44:20

Copyright 2014, Juniper Networks, Inc.

1961

Interfaces Fundamentals for Routing Devices

Task: IF
AS path: I

show route best extensive

The output for the show route best extensive command is identical to that for the show
route best detail command. For sample output, see show route best detail on page 1961.
show route best terse
user@host> show route best 10.255.70.103 terse
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination
* 10.255.70.103/32

P Prf
O 10

Metric 1
2

Metric 2

Next hop
>10.31.1.6
so-0/3/0.0

AS path

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination
* 10.255.70.103/32

P Prf
R
7

Metric 1
2

Metric 2

Next hop
>so-0/3/0.0

AS path

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
A Destination
* 10.0.0.0/8

1962

P Prf
D
0
D
0

Metric 1

Metric 2

Next hop
>fxp2.0
>fxp1.0

AS path

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route brief

List of Syntax

Syntax

Syntax (EX Series

Switches)

Syntax on page 1963

Syntax (EX Series Switches) on page 1963
show route brief
<destination-prefix>
<logical-system (all | logical-system-name)>
show route brief
<destination-prefix>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description

Display brief information about the active entries in the routing tables.

Options

noneDisplay all active entries in the routing table.

destination-prefix(Optional) Display active entries for the specified address or range

of addresses.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show route brief on page 1963

For information about output fields, see the Output Field table of the show route
command.

Sample Output
show route brief
user@host> show route brief
inet.0: 10 destinations, 10 routes (9 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
0.0.0.0/0
10.255.245.51/32
172.16.0.0/12
192.168.0.0/18
192.168.40.0/22
192.168.64.0/18
192.168.164.0/22

Copyright 2014, Juniper Networks, Inc.

*[Static/5] 1w5d 20:30:29

Discard
*[Direct/0] 2w4d 13:11:14
> via lo0.0
*[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via
*[Static/5] 1w5d 20:30:29
> to 192.168.167.254 via
*[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via
*[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via
*[Direct/0] 2w4d 13:11:14
> via fxp0.0

fxp0.0
fxp0.0
fxp0.0
fxp0.0

1963

Interfaces Fundamentals for Routing Devices

192.168.164.51/32

*[Local/0] 2w4d 13:11:14

Local via fxp0.0
207.17.136.192/32 *[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via fxp0.0
green.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100.101.0.0/16
*[Direct/0] 1w5d 20:30:28
> via fe-0/0/3.0
100.101.2.3/32
*[Local/0] 1w5d 20:30:28
Local via fe-0/0/3.0
224.0.0.5/32
*[OSPF/10] 1w5d 20:30:29, metric 1
MultiRecv

1964

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route ccc

Syntax

Release Information
Description

Options

show route ccc ccc

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display circuit cross-connect (CCC) entries in the Multiprotocol Link Switching (MPLS)
routing table.
cccName of an entry with a circuit cross-connect interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

show connections

show route ccc extensive on page 1965

For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route ccc extensive
user@host> show route ccc fe-0/1/0.600 extensive
mpls.0: 19 destinations, 19 routes (19 active, 0 holddown, 0 hidden)
fe-0/1/2.600 (1 entry, 1 announced)
TSI:
KRT in-kernel fe-0/1/2.600.0
/16 -> {0.0.0.0}
*CCC
Preference: 7
Next-hop reference count: 2
Next hop: via so-0/0/3.0 weight 0x1, selected
Label operation: Push 101424
State: <Active Int>
Local AS:
100
Age: 28:13
Metric: 3
Task: MPLS
Announcement bits (1): 0-KRT
AS path: I

Copyright 2014, Juniper Networks, Inc.

1965

Interfaces Fundamentals for Routing Devices

show route community

List of Syntax

Syntax on page 1966

Syntax (EX Series Switches) on page 1966

Syntax

show route community as-number:community-value

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)

show route community as-number:community-value

<brief | detail | extensive | terse>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description

Display the route entries in each routing table that are members of a Border Gateway
Protocol (BGP) community.

Options

as-number:community-valueOne or more community identifiers. as-number is the AS

number, and community-value is the community identifier. When you specify more
than one community identifier, enclose the identifiers in double quotation marks.
Community identifiers can include wildcards.
brief | detail | extensive | terse(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Additional Information

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

Specifying the community option displays all routes matching the community found
within the routing table. The community option does not limit the output to only the
routes being advertised to the neighbor after any egress routing policy.
view

show route detail on page 1975

show route community on page 1966

For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route community
user@host> show route community 234:80
inet.0: 46511 destinations, 46511 routes (46509 active, 0 holddown, 2 hidden)
+ = Active Route, - = Last Active, * = Both

1966

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

4.0.0.0/8

6.0.0.0/8

9.2.0.0/16

Copyright 2014, Juniper Networks, Inc.

*[BGP/170] 03:33:07, localpref 100, from 131.103.20.49

AS Path: {666} 234 2548 1 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
*[BGP/170] 03:33:07, localpref 100, from 131.103.20.49
AS Path: {666} 234 2548 568 721 Incomplete
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
*[BGP/170] 03:33:06, localpref 100, from 131.103.20.49
AS Path: {666} 234 2548 1673 1675 1747 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)

1967

Interfaces Fundamentals for Routing Devices

show route community-name

List of Syntax

Syntax on page 1968

Syntax (EX Series Switches) on page 1968

Syntax

show route community-name community-name

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)

show route community-name community-name

<brief | detail | extensive | terse>

Release Information

Description

Options

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the route entries in each routing table that are members of a Border Gateway
Protocol (BGP) community, specified by a community name.
community-nameName of the community.
brief | detail | extensive | terse(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show route community-name on page 1968

For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route community-name
user@host> show route community-name red-com
inet.0: 17 destinations, 17 routes (16 active, 0 holddown, 1 hidden)
inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
instance1.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
red.inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.255.245.212/32

20.20.20.20/32

100.1.4.0/24

1968

*[BGP/170] 00:04:40, localpref 100, from 10.255.245.204

AS path: 300 I
> to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix
*[BGP/170] 00:04:40, localpref 100, from 10.255.245.204
AS path: I
> to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix
*[BGP/170] 00:04:40, localpref 100, from 10.255.245.204

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

AS path: I
> to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.255.245.204:10:10.255.245.212/32
*[BGP/170] 00:06:40, localpref 100, from 10.255.245.204
AS path: 300 I
> to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix
10.255.245.204:10:20.20.20.20/32
*[BGP/170] 00:36:02, localpref 100, from 10.255.245.204
AS path: I
> to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix
10.255.245.204:10:100.1.4.0/24
*[BGP/170] 00:36:02, localpref 100, from 10.255.245.204
AS path: I
> to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
instance1.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Copyright 2014, Juniper Networks, Inc.

1969

Interfaces Fundamentals for Routing Devices

show route damping

List of Syntax

Syntax on page 1970

Syntax (EX Series Switch and QFX Series) on page 1970

Syntax

show route damping (decayed | history | suppressed)

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switch and QFX
Series)

show route damping (decayed | history | suppressed)

<brief | detail | extensive | terse>

Release Information

Description

Options

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.3 for the QFX Series.
Display the BGP routes for which updates might have been reduced because of route
flap damping.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

decayedDisplay route damping entries that might no longer be valid, but are not

suppressed.
historyDisplay entries that have already been withdrawn, but have been logged.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

suppressedDisplay entries that have been suppressed and are no longer being installed

into the forwarding table or exported by routing protocols.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

1970

view

clear bgp damping on page 1462

show policy damping on page 1501

show route damping decayed detail on page 1973

show route damping history on page 1974
show route damping history detail on page 1974
Table 194 on page 1971 lists the output fields for the show route damping command. Output
fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 194: show route damping Output Fields

Field Name

Field Description

Level of Output

routing-table-name

Name of the routing tablefor example, inet.0.

All levels

destinations

Number of destinations for which there are routes in the routing table.

All levels

number routes

Number of routes in the routing table and total number of routes in the following
states:

All levels

active

holddown (routes that are in a pending state before being declared inactive)

hidden (the routes are not used because of a routing policy)

destination-prefix
(entry, announced)

Destination prefix. The entry value is the number of routes for this destination,
and the announced value is the number of routes being announced for this
destination.

detail extensive

[protocol,
preference]

Protocol from which the route was learned and the preference value for the
route.

All levels

+A plus sign indicates the active route, which is the route installed from the

routing table into the forwarding table.

- A hyphen indicates the last active route.

*An asterisk indicates that the route is both the active and the last active
route. An asterisk before a to line indicates the best subpath to the route.

In every routing metric except for the BGP LocalPref attribute, a lesser value is
preferred. In order to use common comparison routines, Junos OS stores the 1's
complement of the LocalPref value in the Preference2 field. For example, if the
LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref
value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred
because it has a higher LocalPref value and a lower Preference2 value.
Next-hop reference
count

Number of references made to the next hop.

detail extensive

Source

IP address of the route source.

detail extensive

Next hop

Network layer address of the directly reachable neighboring system.

detail extensive

via

Interface used to reach the next hop. If there is more than one interface available
to the next hop, the interface that is actually used is followed by the word
Selected.

detail extensive

Protocol next hop

Network layer address of the remote routing device that advertised the prefix.
This address is used to derive a forwarding next hop.

detail extensive

Indirect next hop

Index designation used to specify the mapping between protocol next hops,
tags, kernel export policy, and the forwarding next hops.

detail extensive

State

Flags for this route. For a description of possible values for this field, see the
output field table for the show route detail command.

detail extensive

Copyright 2014, Juniper Networks, Inc.

1971

Interfaces Fundamentals for Routing Devices

Table 194: show route damping Output Fields (continued)

Field Name

Field Description

Level of Output

Local AS

AS number of the local routing device.

detail extensive

Peer AS

AS number of the peer routing device.

detail extensive

Age

How long the route has been known.

detail extensive

Metric

Metric for the route.

detail extensive

Task

Name of the protocol that has added the route.

detail extensive

Announcement bits

List of protocols that announce this route. n-Resolve inet indicates that the route
is used for route resolution for next hops found in the routing table. n is an index
used by Juniper Networks customer support only.

detail extensive

AS path

AS path through which the route was learned. The letters at the end of the AS
path indicate the path origin, providing an indication of the state of the route at
the point at which the AS path originated:

All levels

IIGP.

EEGP.

?Incomplete; typically, the AS path was aggregated.

When AS path numbers are included in the route, the format is as follows:

[ ]Brackets enclose the local AS number associated with the AS path if

more than one AS number is configured on the routing device or if AS path

prepending is configured.

{ }Braces enclose AS sets, which are groups of AS numbers in which the

order does not matter. A set commonly results from route aggregation. The
numbers in each AS set are displayed in ascending order.

( )Parentheses enclose a confederation.

( [ ] )Parentheses and brackets enclose a confederation set.

NOTE: In Junos OS Release 10.3 and later, the AS path field displays an
unrecognized attribute and associated hexadecimal value if BGP receives
attribute 128 (attribute set) and you have not configured an independent domain
in any routing instance.
to

Next hop to the destination. An angle bracket (>) indicates that the route is the
selected route.

brief none

via

Interface used to reach the next hop. If there is more than one interface available
to the next hop, the interface that is actually used is followed by the word
Selected.

brief none

Communities

Community path attribute for the route. See the output field table for the show
route detail command.

detail extensive

Localpref

Local preference value included in the route.

All levels

Router ID

BGP router ID as advertised by the neighbor in the open message.

detail extensive

1972

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 194: show route damping Output Fields (continued)

Field Name

Field Description

Level of Output

Merit (last
update/now)

Last updated and current figure-of-merit value.

detail extensive

damping-parameters

Name that identifies the damping parameters used, which is defined in the
damping statement at the [edit policy-options] hierarchy level.

detail extensive

Last update

Time of most recent change in path attributes.

detail extensive

First update

Time of first change in path attributes, which started the route damping process.

detail extensive

Flaps

Number of times the route has gone up or down or its path attributes have
changed.

detail extensive

Suppressed

(suppressed keyword only) This route is currently suppressed. A suppressed

route does not appear in the forwarding table and routing protocols do not
export it.

All levels

Reusable in

(suppressed keyword only) Time when a suppressed route will again be available.

All levels

Preference will be

(suppressed keyword only) Preference value that will be applied to the route
when it is again active.

All levels

Sample Output
show route damping decayed detail
user@host> show route damping decayed detail
inet.0: 173319 destinations, 1533668 routes (172625 active, 4 holddown, 108083
hidden)
10.0.111.0/24 (7 entries, 1 announced)
*BGP
Preference: 170/-101
Next-hop reference count: 151973
Source: 172.23.2.129
Next hop: via so-1/2/0.0
Next hop: via so-5/1/0.0, selected
Next hop: via so-6/0/0.0
Protocol next hop: 172.23.2.129
Indirect next hop: 89a1a00 264185
State: <Active Ext>
Local AS: 65000 Peer AS:
65490
Age: 3:28
Metric2: 0
Task: BGP_65490.172.23.2.129+179
Announcement bits (6): 0-KRT 1-RT 4-KRT 5-BGP.0.0.0.0+179
6-Resolve tree 2 7-Resolve tree 3
AS path: 65490 65520 65525 65525 65525 65525 I ()
Communities: 65501:390 65501:2000 65501:3000 65504:701
Localpref: 100
Router ID: 172.23.2.129
Merit (last update/now): 1934/1790
damping-parameters: damping-high

Copyright 2014, Juniper Networks, Inc.

1973

Interfaces Fundamentals for Routing Devices

Last update:
Flaps: 2

00:03:28 First update:

00:06:40

show route damping history

user@host> show route damping history
inet.0: 173320 destinations, 1533529 routes (172624 active, 6 holddown, 108122
hidden)
+ = Active Route, - = Last Active, * = Both
10.108.0.0/15

[BGP ] 2d 22:47:58, localpref 100

AS path: 65220 65501 65502 I
> to 192.168.60.85 via so-3/1/0.0

show route damping history detail

user@host> show route damping history detail
inet.0: 173319 destinations, 1533435 routes (172627 active, 2 holddown, 108105
hidden)
10.108.0.0/15 (3 entries, 1 announced)
BGP
/-101
Next-hop reference count: 69058
Source: 192.168.60.85
Next hop: 192.168.60.85 via so-3/1/0.0, selected
State: <Hidden Ext>
Inactive reason: Unusable path
Local AS: 65000 Peer AS: 65220
Age: 2d 22:48:10
Task: BGP_65220.192.168.60.85+179
AS path: 65220 65501 65502 I ()
Communities: 65501:390 65501:2000 65501:3000 65504:3561
Localpref: 100
Router ID: 192.168.80.25
Merit (last update/now): 1000/932
damping-parameters: set-normal
Last update:
00:01:05 First update:
00:01:05
Flaps: 1

1974

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route detail

List of Syntax

Syntax on page 1975

Syntax (EX Series Switches) on page 1975

Syntax

show route detail

<destination-prefix>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)

show route detail

<destination-prefix>

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description

Display detailed information about the active entries in the routing tables.

Options

noneDisplay all active entries in the routing table on all systems.

destination-prefix(Optional) Display active entries for the specified address or range

of addresses.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level

view

List of Sample Output

show route detail on page 1984

show route detail (with BGP Multipath) on page 1990
show route label detail (Multipoint LDP Inband Signaling for Point-to-Multipoint
LSPs) on page 1990
show route label detail (Multipoint LDP with Multicast-Only Fast Reroute) on page 1991

Output Fields

Table 195 on page 1975 describes the output fields for the show route detail command.
Output fields are listed in the approximate order in which they appear.

Table 195: show route detail Output Fields

Field Name

Field Description

routing-table-name

Name of the routing table (for example, inet.0).

number destinations

Number of destinations for which there are routes in the routing table.

number routes

Number of routes in the routing table and total number of routes in the following states:

active (routes that are active)

holddown (routes that are in the pending state before being declared inactive)

hidden (routes that are not used because of a routing policy)

Copyright 2014, Juniper Networks, Inc.

1975

Interfaces Fundamentals for Routing Devices

Table 195: show route detail Output Fields (continued)

Field Name

Field Description

route-destination
(entry, announced)

Route destination (for example:10.0.0.1/24). The entry value is the number of routes for this destination,
and the announced value is the number of routes being announced for this destination. Sometimes
the route destination is presented in another format, such as:

MPLS-label (for example, 80001).

interface-name (for example, ge-1/0/2).

neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only; for example,

10.1.1.195:NoCtrlWord:1:1:Local/96).

neighbor-addressAddress of the neighbor.

control-word-statusWhether the use of the control word has been negotiated for this virtual
circuit: NoCtrlWord or CtrlWord.

encapsulation typeType of encapsulation, represented by a number: (1) Frame Relay DLCI, (2)

ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet,
(6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport.

label stacking

vc-idVirtual circuit identifier.

sourceSource of the advertisement: Local or Remote.

(Next-to-the-last-hop routing device for MPLS only) Depth of the MPLS label stack, where the

label-popping operation is needed to remove one or more labels from the top of the stack. A pair of
routes is displayed, because the pop operation is performed only when the stack depth is two or more
labels.

S=0 route indicates that a packet with an incoming label stack depth of 2 or more exits this routing

device with one fewer label (the label-popping operation is performed).

[protocol, preference]

If there is no S= information, the route is a normal MPLS route, which has a stack depth of 1 (the
label-popping operation is not performed).

Protocol from which the route was learned and the preference value for the route.

+A plus sign indicates the active route, which is the route installed from the routing table into the

forwarding table.

- A hyphen indicates the last active route.

*An asterisk indicates that the route is both the active and the last active route. An asterisk before
a to line indicates the best subpath to the route.

In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to
use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the
Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101.
If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it
has a higher LocalPref value and a lower Preference2 value.
Level

(IS-IS only). In IS-IS, a single AS can be divided into smaller groups called areas. Routing between
areas is organized hierarchically, allowing a domain to be administratively divided into smaller areas.
This organization is accomplished by configuring Level 1 and Level 2 intermediate systems. Level 1
systems route within an area. When the destination is outside an area, they route toward a Level 2
system. Level 2 intermediate systems route between areas and toward other ASs.

Route Distinguisher

IP subnet augmented with a 64-bit prefix.

PMSI

Provider multicast service interface (MVPN routing table).

Next-hop type

Type of next hop. For a description of possible values for this field, see Table 196 on page 1980.

1976

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 195: show route detail Output Fields (continued)

Field Name

Field Description

Next-hop reference
count

Number of references made to the next hop.

Flood nexthop branches

exceed maximum

Indicates that the number of flood next-hop branches exceeded the system limit of 32 branches, and
only a subset of the flood next-hop branches were installed in the kernel.

message
Source

IP address of the route source.

Next hop

Network layer address of the directly reachable neighboring system.

via

Interface used to reach the next hop. If there is more than one interface available to the next hop, the
name of the interface that is actually used is followed by the word Selected. This field can also contain
the following information:

WeightValue used to distinguish primary, secondary, and fast reroute backup routes. Weight
information is available when MPLS label-switched path (LSP) link protection, node-link protection,
or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight
value is preferred. Among routes with the same weight value, load balancing is possible.

BalanceBalance coefficient indicating how traffic of unequal cost is distributed among next hops
when a routing device is performing unequal-cost load balancing. This information is available
when you enable BGP multipath load balancing.

Label-switched-path
lsp-path-name

Name of the LSP used to reach the next hop.

Label operation

MPLS label and operation occurring at this routing device. The operation can be pop (where a label
is removed from the top of the stack), push (where another label is added to the label stack), or swap
(where a label is replaced by another label).

Interface

(Local only) Local interface name.

Protocol next hop

Network layer address of the remote routing device that advertised the prefix. This address is used
to derive a forwarding next hop.

Indirect next hop

Index designation used to specify the mapping between protocol next hops, tags, kernel export policy,
and the forwarding next hops.

State

State of the route (a route can be in more than one state). See Table 197 on page 1981.

Local AS

AS number of the local routing device.

Age

How long the route has been known.

AIGP

Accumulated interior gateway protocol (AIGP) BGP attribute.

Metricn

Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the
individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined
by a preference value.

Copyright 2014, Juniper Networks, Inc.

1977

Interfaces Fundamentals for Routing Devices

Table 195: show route detail Output Fields (continued)

Field Name

Field Description

MED-plus-IGP

Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added.

TTL-Action

For MPLS LSPs, state of the TTL propagation attribute. Can be enabled or disabled for all
RSVP-signaled and LDP-signaled LSPs or for specific VRF routing instances.
For sample output, see show route table.

Task

Name of the protocol that has added the route.

Announcement bits

List of protocols that announce this route. n-Resolve inet indicates that the route is used for route
resolution for next hops found in the routing table. n is an index used by Juniper Networks customer
support only.

AS path

AS path through which the route was learned. The letters at the end of the AS path indicate the path
origin, providing an indication of the state of the route at the point at which the AS path originated:

IIGP.

EEGP.

RecordedThe AS path is recorded by the sample process (sampled).

?Incomplete; typically, the AS path was aggregated.

When AS path numbers are included in the route, the format is as follows:

[ ]Brackets enclose the number that precedes the AS path. This number represents the number

of ASs present in the AS path, when calculated as defined in RFC 4271. This value is used in the
AS-path merge process, as defined in RFC 4893.

[ ]If more than one AS number is configured on the routing device, or if AS path prepending is

configured, brackets enclose the local AS number associated with the AS path.

{ }Braces enclose AS sets, which are groups of AS numbers in which the order does not matter.

A set commonly results from route aggregation. The numbers in each AS set are displayed in
ascending order.

( )Parentheses enclose a confederation.

( [ ] )Parentheses and brackets enclose a confederation set.

NOTE: In Junos OS Release 10.3 and later, the AS path field displays an unrecognized attribute and
associated hexadecimal value if BGP receives attribute 128 (attribute set) and you have not configured
an independent domain in any routing instance.
validation-state

(BGP-learned routes) Validation status of the route:

InvalidIndicates that the prefix is found, but either the corresponding AS received from the EBGP

peer is not the AS that appears in the database, or the prefix length in the BGP update message is
longer than the maximum length permitted in the database.

UnknownIndicates that the prefix is not among the prefixes or prefix ranges in the database.

UnverifiedIndicates that the origin of the prefix is not verified against the database. This is because

the database got populated and the validation is not called for in the BGP import policy, although
origin validation is enabled, or the origin validation is not enabled for the BGP peers.

FECs bound to route

1978

ValidIndicates that the prefix and autonomous system pair are found in the database.

Point-to-multipoint root address, multicast source address, and multicast group address when
multipoint LDP (M-LDP) inband signaling is configured.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 195: show route detail Output Fields (continued)

Field Name

Field Description

Primary Upstream

When multipoint LDP with multicast-only fast reroute (MoFRR) is configured, the primary upstream
path. MoFRR transmits a multicast join message from a receiver toward a source on a primary path,
while also transmitting a secondary multicast join message from the receiver toward the source on
a backup path.

RPF Nexthops

When multipoint LDP with MoFRR is configured, the reverse-path forwarding (RPF) next-hop
information. Data packets are received from both the primary path and the secondary paths. The
redundant packets are discarded at topology merge points due to the RPF checks.

Label

Multiple MPLS labels are used to control MoFRR stream selection. Each label represents a separate
route, but each references the same interface list check. Only the primary label is forwarded while all
others are dropped. Multiple interfaces can receive packets using the same label.

weight

Value used to distinguish MoFRR primary and backup routes. A lower weight value is preferred. Among
routes with the same weight value, load balancing is possible.

VC Label

MPLS label assigned to the Layer 2 circuit virtual connection.

MTU

Maximum transmission unit (MTU) of the Layer 2 circuit.

VLAN ID

VLAN identifier of the Layer 2 circuit.

Prefixes bound to route

Forwarding equivalent class (FEC) bound to this route. Applicable only to routes installed by LDP.

Communities

Community path attribute for the route. See Table 198 on page 1983 for all possible values for this field.

Layer2-info: encaps

Layer 2 encapsulation (for example, VPLS).

control flags

Control flags: none or Site Down.

mtu

Maximum transmission unit (MTU) information.

Label-Base, range

First label in a block of labels and label block size. A remote PE routing device uses this first label
when sending traffic toward the advertising PE routing device.

status vector

Layer 2 VPN and VPLS network layer reachability information (NLRI).

Accepted Multipath

Current active path when BGP multipath is configured.

Accepted
MultipathContrib

Path currently contributing to BGP multipath.

Localpref

Local preference value included in the route.

Router ID

BGP router ID as advertised by the neighbor in the open message.

Primary Routing Table

In a routing table group, the name of the primary routing table in which the route resides.

Secondary Tables

In a routing table group, the name of one or more secondary tables in which the route resides.

Copyright 2014, Juniper Networks, Inc.

1979

Interfaces Fundamentals for Routing Devices

Table 196 on page 1980 describes all possible values for the Next-hop Types output field.

Table 196: Next-hop Types Output Field Values

1980

Next-Hop Type

Description

Broadcast (bcast)

Broadcast next hop.

Deny

Deny next hop.

Discard

Discard next hop.

Flood

Flood next hop. Consists of components called branches,

up to a maximum of 32 branches. Each flood next-hop
branch sends a copy of the traffic to the forwarding
interface. Used by point-to-multipoint RSVP,
point-to-multipoint LDP, point-to-multipoint CCC, and
multicast.

Hold

Next hop is waiting to be resolved into a unicast or

multicast type.

Indexed (idxd)

Indexed next hop.

Indirect (indr)

Used with applications that have a protocol next hop

address that is remote. You are likely to see this next-hop
type for internal BGP (IBGP) routes when the BGP next
hop is a BGP neighbor that is not directly connected.

Interface

Used for a network address assigned to an interface. Unlike

the router next hop, the interface next hop does not
reference any specific node on the network.

Local (locl)

Local address on an interface. This next-hop type causes

packets with this destination address to be received locally.

Multicast (mcst)

Wire multicast next hop (limited to the LAN).

Multicast discard (mdsc)

Multicast discard.

Multicast group (mgrp)

Multicast group member.

Receive (recv)

Receive.

Reject (rjct)

Discard. An ICMP unreachable message was sent.

Resolve (rslv)

Resolving next hop.

Routed multicast (mcrt)

Regular multicast next hop.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 196: Next-hop Types Output Field Values (continued)

Next-Hop Type

Description

Router

A specific node or set of nodes to which the routing device

forwards packets that match the route prefix.
To qualify as next-hop type router, the route must meet
the following criteria:

Must not be a direct or local subnet for the routing

device.

Must have a next hop that is directly connected to the

routing device.

Table

Routing table next hop.

Unicast (ucst)

Unicast.

Unilist (ulst)

List of unicast next hops. A packet sent to this next hop

goes to any next hop in the list.

Table 197 on page 1981 describes all possible values for the State output field. A route can
be in more than one state (for example, <Active NoReadvrt Int Ext>).

Table 197: State Output Field Values

Value

Description

Accounting

Route needs accounting.

Active

Route is active.

Always Compare MED

Path with a lower multiple exit discriminator (MED) is

available.

AS path

Shorter AS path is available.

Cisco Non-deterministic MED

selection

Cisco nondeterministic MED is enabled, and a path with a

lower MED is available.

Clone

Route is a clone.

Cluster list length

Length of cluster list sent by the route reflector.

Delete

Route has been deleted.

Ex

Exterior route.

Ext

BGP route received from an external BGP neighbor.

Copyright 2014, Juniper Networks, Inc.

1981

Interfaces Fundamentals for Routing Devices

Table 197: State Output Field Values (continued)

1982

Value

Description

FlashAll

Forces all protocols to be notified of a change to any route,

active or inactive, for a prefix. When not set, protocols are
informed of a prefix only when the active route changes.

Hidden

Route not used because of routing policy.

IfCheck

Route needs forwarding RPF check.

IGP metric

Path through next hop with lower IGP metric is available.

Inactive reason

Flags for this route, which was not selected as best for a
particular destination.

Initial

Route being added.

Int

Interior route.

Int Ext

BGP route received from an internal BGP peer or a BGP

confederation peer.

Interior > Exterior > Exterior via

Interior

Direct, static, IGP, or EBGP path is available.

Local Preference

Path with a higher local preference value is available.

Martian

Route is a martian (ignored because it is obviously invalid).

MartianOK

Route exempt from martian filtering.

Next hop address

Path with lower metric next hop is available.

No difference

Path from neighbor with lower IP address is available.

NoReadvrt

Route not to be advertised.

NotBest

Route not chosen because it does not have the lowest MED.

Not Best in its group

Incoming BGP AS is not the best of a group (only one AS can

be the best).

NotInstall

Route not to be installed in the forwarding table.

Number of gateways

Path with a greater number of next hops is available.

Origin

Path with a lower origin code is available.

Pending

Route pending because of a hold-down configured on another

route.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 197: State Output Field Values (continued)

Value

Description

Release

Route scheduled for release.

RIB preference

Route from a higher-numbered routing table is available.

Route Distinguisher

64-bit prefix added to IP subnets to make them unique.

Route Metric or MED comparison

Route with a lower metric or MED is available.

Route Preference

Route with lower preference value is available

Router ID

Path through a neighbor with lower ID is available.

Secondary

Route not a primary route.

Unusable path

Path is not usable because of one of the following conditions:

Update source

The route is damped.

The route is rejected by an import policy.

The route is unresolved.

Last tiebreaker is the lowest IP address value.

Table 198 on page 1983 describes the possible values for the Communities output field.

Table 198: Communities Output Field Values

Value

Description

area-number

4 bytes, encoding a 32-bit area number. For AS-external routes, the value is 0. A nonzero value
identifies the route as internal to the OSPF domain, and as within the identified area. Area
numbers are relative to a particular OSPF domain.

bandwidth: local AS
number:link-bandwidth-number

Link-bandwidth community value used for unequal-cost load balancing. When BGP has
several candidate paths available for multipath purposes, it does not perform unequal-cost
load balancing according to the link-bandwidth community unless all candidate paths have
this attribute.

domain-id

Unique configurable number that identifies the OSPF domain.

domain-id-vendor

Unique configurable number that further identifies the OSPF domain.

link-bandwidth-number

Link-bandwidth number: from 0 through 4,294,967,295 (bytes per second).

local AS number

Local AS number: from 1 through 65,535.

options

1 byte. Currently this is only used if the route type is 5 or 7. Setting the least significant bit in
the field indicates that the route carries a type 2 metric.

Copyright 2014, Juniper Networks, Inc.

1983

Interfaces Fundamentals for Routing Devices

Table 198: Communities Output Field Values (continued)

Value

Description

origin

(Used with VPNs) Identifies where the route came from.

ospf-route-type

1 byte, encoded as 1 or 2 for intra-area routes (depending on whether the route came from a
type 1 or a type 2 LSA); 3 for summary routes; 5 for external routes (area number must be0);
7 for NSSA routes; or 129 for sham link endpoint addresses.

route-type-vendor

Displays the area number, OSPF route type, and option of the route. This is configured using
the BGP extended community attribute 0x8000. The format is
area-number:ospf-route-type:options.

rte-type

Displays the area number, OSPF route type, and option of the route. This is configured using
the BGP extended community attribute 0x0306. The format is
area-number:ospf-route-type:options.

target

Defines which VPN the route participates in; target has the format 32-bit IP address:16-bit
number. For example, 10.19.0.0:100.

unknown IANA

Incoming IANA codes with a value between 0x1 and 0x7fff. This code of the BGP extended
community attribute is accepted, but it is not recognized.

unknown OSPF vendor

community

Incoming IANA codes with a value above 0x8000. This code of the BGP extended community
attribute is accepted, but it is not recognized.

Sample Output
show route detail
user@host> show route detail
inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 29
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 1:31:43
Task: RT
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
10.31.1.0/30 (2 entries, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 2
Next hop: via so-0/3/0.0, selected
State: <Active Int>
Local AS:
69
Age: 1:30:17
Task: IF
Announcement bits (1): 3-Resolve tree 2
AS path: I
OSPF
Preference: 10

1984

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Next-hop reference count: 1

Next hop: via so-0/3/0.0, selected
State: <Int>
Inactive reason: Route Preference
Local AS:
69
Age: 1:30:17
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
10.31.1.1/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local
Next-hop reference count: 7
Interface: so-0/3/0.0
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:30:20
Task: IF
Announcement bits (1): 3-Resolve tree 2
AS path: I
...
10.31.2.0/30 (1 entry, 1 announced)
*OSPF
Preference: 10
Next-hop reference count: 9
Next hop: via so-0/3/0.0
Next hop: 10.31.1.6 via ge-3/1/0.0, selected
State: <Active Int>
Local AS:
69
Age: 1:29:56
Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
...
224.0.0.2/32 (1 entry, 1 announced)
*PIM
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:31:45
Task: PIM Recv
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
...
224.0.0.22/32 (1 entry, 1 announced)
*IGMP
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:31:43
Task: IGMP
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I

Copyright 2014, Juniper Networks, Inc.

1985

Interfaces Fundamentals for Routing Devices

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

10.255.70.103/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
Next-hop reference count: 6
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 100096
State: <Active Int>
Local AS:
69
Age: 1:25:49
Metric: 2
Task: RSVP
Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2
AS path: I
10.255.71.238/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
Next-hop reference count: 6
Next hop: via so-0/3/0.0 weight 0x1, selected
Label-switched-path green-r1-r2
State: <Active Int>
Local AS:
69
Age: 1:25:49
Metric: 1
Task: RSVP
Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2
AS path: I
private__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
47.0005.80ff.f800.0000.0108.0001.0102.5507.1052/152 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Local AS:
69
Age: 1:31:44
Task: IF
AS path: I
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
0
(1 entry, 1 announced)
*MPLS
Preference: 0
Next hop type: Receive
Next-hop reference count: 6
State: <Active Int>
Local AS:
69
Age: 1:31:45
Metric: 1
Task: MPLS
Announcement bits (1): 0-KRT
AS path: I
...
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
299840 (1 entry, 1 announced)

1986

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

TSI:
KRT in-kernel 299840 /52 -> {indirect(1048575)}
*RSVP
Preference: 7/2
Next hop type: Flood
Address: 0x9174a30
Next-hop reference count: 4
Next hop type: Router, Next hop index: 798
Address: 0x9174c28
Next-hop reference count: 2
Next hop: 8.0.0.2 via lt-1/2/0.9 weight 0x1
Label-switched-path R2-to-R4-2p2mp
Label operation: Pop
Next hop type: Router, Next hop index: 1048574
Address: 0x92544f0
Next-hop reference count: 2
Next hop: 7.0.0.2 via lt-1/2/0.7 weight 0x1
Label-switched-path R2-to-R200-p2mp
Label operation: Pop
Next hop: 6.0.0.2 via lt-1/2/0.5 weight 0x8001
Label operation: Pop
State: <Active Int>
Age: 1:29
Metric: 1
Task: RSVP
Announcement bits (1): 0-KRT
AS path: I...
800010 (1 entry, 1 announced)
*VPLS
Preference: 7
Next-hop reference count: 2
Next hop: via vt-3/2/0.32769, selected
Label operation: Pop
State: <Active Int>
Age: 1:29:30
Task: Common L2 VC
Announcement bits (1): 0-KRT
AS path: I
vt-3/2/0.32769 (1 entry, 1 announced)
*VPLS
Preference: 7
Next-hop reference count: 2
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 800012, Push 100096(top)
Protocol next hop: 10.255.70.103
Push 800012
Indirect next hop: 87272e4 1048574
State: <Active Int>
Age: 1:29:30
Metric2: 2
Task: Common L2 VC
Announcement bits (2): 0-KRT 1-Common L2 VC
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
abcd::10:255:71:52/128 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected

Copyright 2014, Juniper Networks, Inc.

1987

Interfaces Fundamentals for Routing Devices

State: <Active Int>

Local AS:
69
Age: 1:31:44
Task: IF
AS path: I
fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:31:44
Task: IF
AS path: I
ff02::2/128 (1 entry, 1 announced)
*PIM
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:31:45
Task: PIM Recv6
Announcement bits (1): 0-KRT
AS path: I
ff02::d/128 (1 entry, 1 announced)
*PIM
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:31:45
Task: PIM Recv6
Announcement bits (1): 0-KRT
AS path: I
ff02::16/128 (1 entry, 1 announced)
*MLD
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:31:43
Task: MLD
Announcement bits (1): 0-KRT
AS path: I
private.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.16385, selected
State: <Active NoReadvrt Int>
Age: 1:31:44
Task: IF
AS path: I
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

1988

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

10.255.70.103:1:3:1/96 (1 entry, 1 announced)

*BGP
Preference: 170/-101
Route Distinguisher: 10.255.70.103:1
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 1:25:49
Metric2: 1
AIGP 210
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-green-l2vpn
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
Label-base: 800008, range: 8
Localpref: 100
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
10.255.71.52:1:1:1/96 (1 entry, 1 announced)
*L2VPN Preference: 170/-1
Next-hop reference count: 5
Protocol next hop: 10.255.71.52
Indirect next hop: 0 State: <Active Int Ext>
Age: 1:31:40
Metric2: 1
Task: green-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down,
mtu: 0
Label-base: 800016, range: 8, status-vector: 0x9F
10.255.71.52:1:5:1/96 (1 entry, 1 announced)
*L2VPN Preference: 170/-101
Next-hop reference count: 5
Protocol next hop: 10.255.71.52
Indirect next hop: 0 State: <Active Int Ext>
Age: 1:31:40
Metric2: 1
Task: green-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:, mtu: 0
Label-base: 800008, range: 8, status-vector: 0x9F
...
l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced)
*L2CKT Preference: 7
Next hop: via so-1/1/2.0 weight 1, selected
Label-switched-path my-lsp
Label operation: Push 100000[0]
Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296
State: <Active Int>
Local AS:
99
Age: 10:21
Task: l2 circuit

Copyright 2014, Juniper Networks, Inc.

1989

Interfaces Fundamentals for Routing Devices

Announcement bits (1): 0-LDP

AS path: I
VC Label 100000, MTU 1500, VLAN ID 512

show route detail (with BGP Multipath)

user@host> show route detail
10.1.1.8/30 (2 entries, 1 announced)
*BGP
Preference: 170/-101
Next hop type: Router, Next hop index: 262142
Address: 0x901a010
Next-hop reference count: 2
Source: 10.1.1.2
Next hop: 10.1.1.2 via ge-0/3/0.1, selected
Next hop: 10.1.1.6 via ge-0/3/0.5
State: <Active Ext>
Local AS:
1 Peer AS:
2
Age: 5:04:43
Validation State: unverified
Task: BGP_2.10.1.1.2+59955
Announcement bits (1): 0-KRT
AS path: 2 I
Accepted Multipath
Localpref: 100
Router ID: 1.1.1.2
BGP
Preference: 170/-101
Next hop type: Router, Next hop index: 678
Address: 0x8f97520
Next-hop reference count: 9
Source: 10.1.1.6
Next hop: 10.1.1.6 via ge-0/3/0.5, selected
State: <NotBest Ext>
Inactive reason: Not Best in its group - Active preferred
Local AS:
1 Peer AS:
2
Age: 5:04:43
Validation State: unverified
Task: BGP_2.10.1.1.6+58198
AS path: 2 I
Accepted MultipathContrib
Localpref: 100
Router ID: 1.1.1.3

show route label detail (Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show route label 299872 detail
mpls.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
299872 (1 entry, 1 announced)
*LDP
Preference: 9
Next hop type: Flood
Next-hop reference count: 3
Address: 0x9097d90
Next hop: via vt-0/1/0.1
Next-hop index: 661
Label operation: Pop
Address: 0x9172130
Next hop: via so-0/0/3.0
Next-hop index: 654
Label operation: Swap 299872
State: **Active Int>
Local AS: 1001

1990

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Age: 8:20
Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
FECs bound to route: P2MP root-addr 10.255.72.166, grp 232.1.1.1,
src 192.168.142.2

show route label detail (Multipoint LDP with Multicast-Only Fast Reroute)
user@host> show route label 301568 detail
mpls.0: 18 destinations, 18 routes (18 active, 0 holddown, 0 hidden)
301568 (1 entry, 1 announced)
*LDP
Preference: 9
Next hop type: Flood
Address: 0x2735208
Next-hop reference count: 3
Next hop type: Router, Next hop index: 1397
Address: 0x2735d2c
Next-hop reference count: 3
Next hop: 1.3.8.2 via ge-1/2/22.0
Label operation: Pop
Load balance label: None;
Next hop type: Router, Next hop index: 1395
Address: 0x2736290
Next-hop reference count: 3
Next hop: 1.3.4.2 via ge-1/2/18.0
Label operation: Pop
Load balance label: None;
State: <Active Int AckRequest MulticastRPF>
Local AS:
10
Age: 54:05
Metric: 1
Validation State: unverified
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
FECs bound to route: P2MP root-addr 1.1.1.1, grp: 232.1.1.1, src:
192.168.219.11
Primary Upstream : 1.1.1.3:0--1.1.1.2:0
RPF Nexthops :
ge-1/2/15.0, 1.2.94.1, Label: 301568, weight: 0x1
ge-1/2/14.0, 1.2.3.1, Label: 301568, weight: 0x1
Backup Upstream : 1.1.1.3:0--1.1.1.6:0
RPF Nexthops :
ge-1/2/20.0, 1.2.96.1, Label: 301584, weight: 0xfffe
ge-1/2/19.0, 1.3.6.1, Label: 301584, weight: 0xfffe

Copyright 2014, Juniper Networks, Inc.

1991

Interfaces Fundamentals for Routing Devices

show route exact

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description
Options

Syntax on page 1992

Syntax (EX Series Switches) on page 1992
show route exact destination-prefix
<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>
show route exact destination-prefix
<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display only the routes that exactly match the specified address or range of addresses.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

destination-prefixAddress or range of addresses.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route exact on page 1992

show route exact detail on page 1992
show route exact extensive on page 1993
show route exact terse on page 1993
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route exact
user@host> show route exact 207.17.136.0/24
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
207.17.136.0/24
*[Static/5] 2d 03:30:22
> to 192.168.71.254 via fxp0.0

show route exact detail

user@host> show route exact 207.17.136.0/24 detail
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)

1992

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Restart Complete
207.17.136.0/24 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 29
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2d 3:30:26
Task: RT
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I

show route exact extensive

user@host> show route exact 207.17.136.0/24 extensive
inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden)
207.17.136.0/24 (1 entry, 1 announced)
TSI:
KRT in-kernel 207.17.136.0/24 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 29
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 1:25:18
Task: RT
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I

show route exact terse

user@host> show route exact 207.17.136.0/24 terse
inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A Destination
P Prf
Metric 1
Metric 2 Next hop
AS path
* 207.17.136.0/24
S
5
>192.168.71.254

Copyright 2014, Juniper Networks, Inc.

1993

Interfaces Fundamentals for Routing Devices

show route export

List of Syntax

Syntax on page 1994

Syntax (EX Series Switches) on page 1994

Syntax

show route export

<brief | detail>
<instance <instance-name> | routing-table-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)

show route export

<brief | detail>
<instance <instance-name> | routing-table-name>

Release Information

Description

Options

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display policy-based route export information. Policy-based export simplifies the process
of exchanging route information between routing instances.
none(Same as brief.) Display standard information about policy-based export for all

instances and routing tables on all systems.

brief | detail(Optional) Display the specified level of output.
instance <instance-name>(Optional) Display a particular routing instance for which

policy-based export is currently enabled.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

routing-table-name(Optional) Display information about policy-based export for all

routing tables whose name begins with this string (for example, inet.0 and inet6.0
are both displayed when you run the show route export inet command).
Required Privilege
Level
List of Sample Output

Output Fields

view

show route export on page 1995

show route export detail on page 1995
show route export instance detail on page 1995
Table 199 on page 1994 lists the output fields for the show route export command. Output
fields are listed in the approximate order in which they appear.

Table 199: show route export Output Fields

Field Name

Field Description

Level of Output

Table or table-name

Name of the routing tables that either import or export routes.

All levels

Routes

Number of routes exported from this table into other tables. If a particular route
is exported to different tables, the counter will only increment by one.

brief none

1994

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 199: show route export Output Fields (continued)

Field Name

Field Description

Level of Output

Export

Whether the table is currently exporting routes to other tables: Y or N (Yes or No).

brief none

Import

Tables currently importing routes from the originator table. (Not displayed for
tables that are not exporting any routes.)

detail

Flags

(instance keyword only) Flags for this feature on this instance:

detail

config auto-policyThe policy was deduced from the configured IGP export

policies.

Options

cleanupConfiguration information for this instance is no longer valid.

configThe instance was explicitly configured.

(instance keyword only) Configured option displays the type of routing tables the
feature handles:

unicastIndicates instance.inet.0.

multicastIndicates instance.inet.2.

unicast multicastIndicates instance.inet.0 and instance.inet.2.

detail

Import policy

(instance keyword only) Policy that route export uses to construct the import-export
matrix. Not displayed if the instance type is vrf.

detail

Instance

(instance keyword only) Name of the routing instance.

detail

Type

(instance keyword only) Type of routing instance: forwarding, non-forwarding, or

vrf.

detail

Sample Output
show route export
user@host> show route export
Table
inet.0
black.inet.0
red.inet.0

Export
N
Y
Y

Routes
0
3
4

show route export detail

user@host> show route export detail
inet.0
black.inet.0
Import: [ inet.0 ]
red.inet.0
Import: [ inet.0 ]

Routes:
Routes:

0
3

Routes:

show route export instance detail

user@host> show route export instance detail
Instance: master
Type: forwarding
Flags: <config auto-policy> Options: <unicast multicast>
Import policy: [ (ospf-master-from-red || isis-master-from-black) ]

Copyright 2014, Juniper Networks, Inc.

1995

Interfaces Fundamentals for Routing Devices

Instance: black
Instance: red

1996

Type: non-forwarding
Type: non-forwarding

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route export vrf-target

Syntax

Release Information
Description

Options

show route export vrf-target

<brief | detail>
<community community--regular-expression>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display the VPN routing and forwarding (VRF) target communities for which policy-based
route export is currently distributing routes. This command is relevant when there are
overlapping virtual private networks (VPNs).
noneDisplay standard information about all target communities.
brief | detail(Optional) Display the specified level of output. If you do not specify a level

of output, the system defaults to brief.

community community-regular-expression(Optional) Display information about the

specified community.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route export vrf-target on page 1998

show route export vrf-target community on page 1998
show route export vrf-target detail on page 1998
Table 200 on page 1997 lists the output fields for the show route export vrf-target command.
Output fields are listed in the approximate order in which they appear.

Table 200: show route export vrf-target Output Fields

Field Name

Field Description

Level of Output

Route target

Target communities for which auto-export is currently distributing routes.

brief none

Family

Routing table entries for the specified family.

brief none

type-of-routing-table(s)

Type of routing tables the feature handles:

brief none

Import

unicastIndicates instance.inet.0.

multicastIndicates instance.inet.2.

unicast multicastIndicates instance.inet.0 and instance.inet.2.

Number of routing tables that are currently importing routes with this target
community. Omitted for tables that are not importing routes.

Copyright 2014, Juniper Networks, Inc.

brief none

1997

Interfaces Fundamentals for Routing Devices

Table 200: show route export vrf-target Output Fields (continued)

Field Name

Field Description

Level of Output

Export

Number of routing tables that are currently exporting routes with this target
community. Omitted for tables that are not exporting routes.

brief none

Target

Target communities, family, and options for which auto-export is currently

distributing routes.

detail

Import table(s)

Name of the routing tables that are importing a particular route target.

detail

Export table(s)

Name of the routing tables that are exporting a particular route target.

detail

Sample Output
show route export vrf-target
user@host> show route export vrf-target
Route Target
Family
69:1
inet
unicast
69:2
inet
unicast

Import
2
2

Export
2
2

user@host> show route export vrf-target community target:69:1

Route Target
Family
Import
69:1
inet
unicast
2

Export
2

show route export vrf-target community

show route export vrf-target detail

user@host> show route export vrf-target detail
Target: 1:12
inet
Import table(s): vrf-11.inet.0 vrf-12.inet.0
Export table(s): vrf-12.inet.0
Target: 1:13
inet
Import table(s): vrf-12.inet.0 vrf-13.inet.0
Export table(s): vrf-13.inet.0

1998

unicast

unicast

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route extensive

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description
Options

Syntax on page 1999

Syntax (EX Series Switches) on page 1999
show route extensive
<destination-prefix>
<logical-system (all | logical-system-name)>
show route extensive
<destination-prefix>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display extensive information about the active entries in the routing tables.
noneDisplay all active entries in the routing table.
destination-prefix(Optional) Display active entries for the specified address or range

of addresses.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level

view

List of Sample Output

show route extensive on page 2006

show route extensive (Access Route) on page 2012
show route extensive (BGP PIC Edge) on page 2013
show route extensive (FRR and LFA) on page 2013
show route extensive (Route Reflector) on page 2014
show route label detail (Multipoint LDP Inband Signaling for Point-to-Multipoint
LSPs) on page 2014
show route label detail (Multipoint LDP with Multicast-Only Fast Reroute) on page 2015

Output Fields

Table 201 on page 1999 describes the output fields for the show route extensive command.
Output fields are listed in the approximate order in which they appear.

Table 201: show route extensive Output Fields

Field Name

Field Description

routing-table-name

Name of the routing table (for example, inet.0).

number destinations

Number of destinations for which there are routes in the routing table.

Copyright 2014, Juniper Networks, Inc.

1999

Interfaces Fundamentals for Routing Devices

Table 201: show route extensive Output Fields (continued)

Field Name

Field Description

number routes

Number of routes in the routing table and total number of routes in the following states:

route-destination
(entry, announced)

active (routes that are active).

holddown (routes that are in the pending state before being declared inactive).

hidden (routes that are not used because of a routing policy).

Route destination (for example: 10.0.0.1/24). The entry value is the number of route for this destination,
and the announced value is the number of routes being announced for this destination. Sometimes
the route destination is presented in another format, such as:

MPLS-label (for example, 80001 ).

interface-name (for example, ge-1/0/2).

neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only; for example,

10.1.1.195:NoCtrlWord:1:1:Local/96).

neighbor-addressAddress of the neighbor.

control-word-statusWhether the use of the control word has been negotiated for this virtual
circuit: NoCtrlWord or CtrlWord.

encapsulation typeType of encapsulation, represented by a number: (1) Frame Relay DLCI, (2)

ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet,
(6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport.

vc-idVirtual circuit identifier.

sourceSource of the advertisement: Local or Remote.

TSI

Protocol header information.

label stacking

(Next-to-the-last-hop routing device for MPLS only) Depth of the MPLS label stack, where the
label-popping operation is needed to remove one or more labels from the top of the stack. A pair of
routes is displayed, because the pop operation is performed only when the stack depth is two or more
labels.

S=0 route indicates that a packet with an incoming label stack depth of two or more exits this router

with one fewer label (the label-popping operation is performed).

[protocol, preference]

If there is no S= information, the route is a normal MPLS route, which has a stack depth of 1 (the
label-popping operation is not performed).

Protocol from which the route was learned and the preference value for the route.

+A plus sign indicates the active route, which is the route installed from the routing table into the

forwarding table.

- A hyphen indicates the last active route.

*An asterisk indicates that the route is both the active and the last active route. An asterisk before
a to line indicates the best subpath to the route.

In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to
use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the
Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101.
If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it
has a higher LocalPref value and a lower Preference2 value.

2000

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 201: show route extensive Output Fields (continued)

Field Name

Field Description

Level

(IS-IS only). In IS-IS, a single autonomous system (AS) can be divided into smaller groups called
areas. Routing between areas is organized hierarchically, allowing a domain to be administratively
divided into smaller areas. This organization is accomplished by configuring Level 1 and Level 2
intermediate systems. Level 1 systems route within an area. When the destination is outside an area,
they route toward a Level 2 system. Level 2 intermediate systems route between areas and toward
other ASs.

Route Distinguisher

IP subnet augmented with a 64-bit prefix.

PMSI

Provider multicast service interface (MVPN routing table).

Next-hop type

Type of next hop. For a description of possible values for this field, see the Output Field table in the
show route detail command.

Next-hop reference
count

Number of references made to the next hop.

Flood nexthop branches

exceed maximum

Indicates that the number of flood next-hop branches exceeded the system limit of 32 branches, and
only a subset of the flood next-hop branches were installed in the kernel.

message
Source

IP address of the route source.

Next hop

Network layer address of the directly reachable neighboring system.

via

Interface used to reach the next hop. If there is more than one interface available to the next hop, the
name of the interface that is actually used is followed by the word Selected. This field can also contain
the following information:

WeightValue used to distinguish primary, secondary, and fast reroute backup routes. Weight
information is available when MPLS label-switched path (LSP) link protection, node-link protection,
or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight
value is preferred. Among routes with the same weight value, load balancing is possible.

BalanceBalance coefficient indicating how traffic of unequal cost is distributed among next hops
when a routing device is performing unequal-cost load balancing. This information is available
when you enable BGP multipath load balancing.

Label-switched-path
lsp-path-name

Name of the LSP used to reach the next hop.

Label operation

MPLS label and operation occurring at this routing device. The operation can be pop (where a label
is removed from the top of the stack), push (where another label is added to the label stack), or swap
(where a label is replaced by another label).

Offset

Whether the metric has been increased or decreased by an offset value.

Interface

(Local only) Local interface name.

Protocol next hop

Network layer address of the remote routing device that advertised the prefix. This address is used
to recursively derive a forwarding next hop.

Copyright 2014, Juniper Networks, Inc.

2001

Interfaces Fundamentals for Routing Devices

Table 201: show route extensive Output Fields (continued)

Field Name

Field Description

label-operation

MPLS label and operation occurring at this routing device. The operation can be pop (where a label
is removed from the top of the stack), push (where another label is added to the label stack), or swap
(where a label is replaced by another label).

Indirect next hops

When present, a list of nodes that are used to resolve the path to the next-hop destination, in the
order that they are resolved.
When BGP PIC Edge is enabled, the output lines that contain Indirect next hop: weight follow next
hops that the software can use to repair paths where a link failure occurs. The next-hop weight has
one of the following values:

0x1 indicates active next hops.

0x4000 indicates passive next hops.

State

State of the route (a route can be in more than one state). See the Output Field table in the show
route detail command.

Session ID

The BFD session ID number that represents the protection using MPLS fast reroute (FRR) and loop-free
alternate (LFA).

Weight

Weight for the backup path. If the weight of an indirect next hop is larger than zero, the weight value
is shown.
For sample output, see show route table.

2002

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 201: show route extensive Output Fields (continued)

Field Name

Field Description

Inactive reason

If the route is inactive, the reason for its current state is indicated. Typical reasons include:

Active preferredCurrently active route was selected over this route.

Always compare MEDPath with a lower multiple exit discriminator (MED) is available.

AS pathShorter AS path is available.

Cisco Non-deterministic MED selectionCisco nondeterministic MED is enabled and a path with a

lower MED is available.

Cluster list lengthPath with a shorter cluster list length is available.

Forwarding use onlyPath is only available for forwarding purposes.

IGP metricPath through the next hop with a lower IGP metric is available.

IGP metric typePath with a lower OSPF link-state advertisement type is available.

Interior > Exterior > Exterior via InteriorDirect, static, IGP, or EBGP path is available.

Local preferencePath with a higher local preference value is available.

Next hop addressPath with a lower metric next hop is available.

No differencePath from a neighbor with a lower IP address is available.

Not Best in its groupOccurs when multiple peers of the same external AS advertise the same

prefix and are grouped together in the selection process. When this reason is displayed, an additional
reason is provided (typically one of the other reasons listed).

Number of gatewaysPath with a higher number of next hops is available.

OriginPath with a lower origin code is available.

OSPF versionPath does not support the indicated OSPF version.

RIB preferenceRoute from a higher-numbered routing table is available.

Route destinguisher64-bit prefix added to IP subnets to make them unique.

Route metric or MED comparisonRoute with a lower metric or MED is available.

Route preferenceRoute with a lower preference value is available.

Router IDPath through a neighbor with a lower ID is available.

Unusable pathPath is not usable because of one of the following conditions: the route is damped,

the route is rejected by an import policy, or the route is unresolved.

Update sourceLast tiebreaker is the lowest IP address value.

Local AS

Autonomous system (AS) number of the local routing device.

Age

How long the route has been known.

AIGP

Accumulated interior gateway protocol (AIGP) BGP attribute.

Metric

Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the
individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined
by a preference value.

MED-plus-IGP

Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added.

TTL-Action

For MPLS LSPs, state of the TTL propagation attribute. Can be enabled or disabled for all
RSVP-signaled and LDP-signaled LSPs or for specific VRF routing instances.
For sample output, see show route table.

Copyright 2014, Juniper Networks, Inc.

2003

Interfaces Fundamentals for Routing Devices

Table 201: show route extensive Output Fields (continued)

Field Name

Field Description

Task

Name of the protocol that has added the route.

Announcement bits

List of protocols that announce this route. n-Resolve inet indicates that the route is used for route
resolution for next hops found in the routing table. n is an index used by Juniper Networks customer
support only.

AS path

AS path through which the route was learned. The letters at the end of the AS path indicate the path
origin, providing an indication of the state of the route at the point at which the AS path originated:

IIGP.

EEGP.

RecordedThe AS path is recorded by the sample process (sampled).

?Incomplete; typically, the AS path was aggregated.

When AS path numbers are included in the route, the format is as follows:

[ ]Brackets enclose the local AS number associated with the AS path if more than one AS number

is configured on the routing device, or if AS path prepending is configured.

{ }Braces enclose AS sets, which are groups of AS numbers in which the order does not matter.

A set commonly results from route aggregation. The numbers in each AS set are displayed in
ascending order.

( )Parentheses enclose a confederation.

( [ ] )Parentheses and brackets enclose a confederation set.

NOTE: In Junos OS Release 10.3 and later, the AS path field displays an unrecognized attribute and
associated hexadecimal value if BGP receives attribute 128 (attribute set) and you have not configured
an independent domain in any routing instance.
validation-state

(BGP-learned routes) Validation status of the route:

InvalidIndicates that the prefix is found, but either the corresponding AS received from the EBGP

peer is not the AS that appears in the database, or the prefix length in the BGP update message is
longer than the maximum length permitted in the database.

UnknownIndicates that the prefix is not among the prefixes or prefix ranges in the database.

UnverifiedIndicates that origin validation is not enabled for the BGP peers.

ValidIndicates that the prefix and autonomous system pair are found in the database.

FECs bound to route

Point-to-multipoint root address, multicast source address, and multicast group address when
multipoint LDP (M-LDP) inband signaling is configured.

AS path: I <Originator>

(For route reflected output only) Originator ID attribute set by the route reflector.

Primary Upstream

When multipoint LDP with multicast-only fast reroute (MoFRR) is configured, the primary upstream
path. MoFRR transmits a multicast join message from a receiver toward a source on a primary path,
while also transmitting a secondary multicast join message from the receiver toward the source on
a backup path.

RPF Nexthops

When multipoint LDP with MoFRR is configured, the reverse-path forwarding (RPF) next-hop
information. Data packets are received from both the primary path and the secondary paths. The
redundant packets are discarded at topology merge points due to the RPF checks.

2004

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 201: show route extensive Output Fields (continued)

Field Name

Field Description

Label

Multiple MPLS labels are used to control MoFRR stream selection. Each label represents a separate
route, but each references the same interface list check. Only the primary label is forwarded while all
others are dropped. Multiple interfaces can receive packets using the same label.

weight

Value used to distinguish MoFRR primary and backup routes. A lower weight value is preferred. Among
routes with the same weight value, load balancing is possible.

VC Label

MPLS label assigned to the Layer 2 circuit virtual connection.

MTU

Maximum transmission unit (MTU) of the Layer 2 circuit.

VLAN ID

VLAN identifier of the Layer 2 circuit.

Cluster list

(For route reflected output only) Cluster ID sent by the route reflector.

Originator ID

(For route reflected output only) Address of router that originally sent the route to the route reflector.

Prefixes bound to route

Forwarding equivalent class (FEC) bound to this route. Applicable only to routes installed by LDP.

Communities

Community path attribute for the route. See the Output Field table in the show route detail command
for all possible values for this field.

Layer2-info: encaps

Layer 2 encapsulation (for example, VPLS).

control flags

Control flags: none or Site Down.

mtu

Maximum transmission unit (MTU) information.

Label-Base, range

First label in a block of labels and label block size. A remote PE routing device uses this first label
when sending traffic toward the advertising PE routing device.

status vector

Layer 2 VPN and VPLS network layer reachability information (NLRI).

Localpref

Local preference value included in the route.

Router ID

BGP router ID as advertised by the neighbor in the open message.

Primary Routing Table

In a routing table group, the name of the primary routing table in which the route resides.

Secondary Tables

In a routing table group, the name of one or more secondary tables in which the route resides.

Originating RIB

Name of the routing table whose active route was used to determine the forwarding next-hop entry
in the resolution database. For example, in the case of inet.0 resolving through inet.0 and inet.3, this
field indicates which routing table, inet.0 or inet.3, provided the best path for a particular prefix.

Node path count

Number of nodes in the path.

Copyright 2014, Juniper Networks, Inc.

2005

Interfaces Fundamentals for Routing Devices

Table 201: show route extensive Output Fields (continued)

Field Name

Field Description

Forwarding nexthops

Number of forwarding next hops. The forwarding next hop is the network layer address of the directly
reachable neighboring system (if applicable) and the interface used to reach it.

Sample Output
show route extensive
user@host> show route extensive
inet.0: 22 destinations, 23 routes (21 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.10.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 29
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 1:34:06
Task: RT
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
10.31.1.0/30 (2 entries, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 2
Next hop: via so-0/3/0.0, selected
State: <Active Int>
Local AS:
69
Age: 1:32:40
Task: IF
Announcement bits (1): 3-Resolve tree 2
AS path: I
OSPF
Preference: 10
Next-hop reference count: 1
Next hop: via so-0/3/0.0, selected
State: <Int>
Inactive reason: Route Preference
Local AS:
69
Age: 1:32:40
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
10.31.1.1/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local
Next-hop reference count: 7
Interface: so-0/3/0.0
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:32:43
Task: IF
Announcement bits (1): 3-Resolve tree 2
AS path: I

2006

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

...
10.31.2.0/30 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.31.2.0/30 -> {10.31.1.6}
*OSPF
Preference: 10
Next-hop reference count: 9
Next hop: via so-0/3/0.0
Next hop: 10.31.1.6 via ge-3/1/0.0, selected
State: <Active Int>
Local AS:
69
Age: 1:32:19
Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
...
224.0.0.2/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 224.0.0.2/32 -> {}
*PIM
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:34:08
Task: PIM Recv
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
...
224.0.0.22/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 224.0.0.22/32 -> {}
*IGMP
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:34:06
Task: IGMP
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.255.70.103/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
Next-hop reference count: 6
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 100096
State: <Active Int>
Local AS:
69
Age: 1:28:12
Metric: 2
Task: RSVP
Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2
AS path: I

Copyright 2014, Juniper Networks, Inc.

2007

Interfaces Fundamentals for Routing Devices

10.255.71.238/32 (1 entry, 1 announced)

State: <FlashAll>
*RSVP
Preference: 7
Next-hop reference count: 6
Next hop: via so-0/3/0.0 weight 0x1, selected
Label-switched-path green-r1-r2
State: <Active Int>
Local AS:
69
Age: 1:28:12
Metric: 1
Task: RSVP
Announcement bits (2): 1-Resolve tree 1 2-Resolve tree 2
AS path: I
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
...
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
47.0005.80ff.f800.0000.0108.0001.0102.5507.1052/152 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Local AS:
69
Age: 1:34:07
Task: IF
AS path: I
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
0
(1 entry, 1 announced)
TSI:
KRT in-kernel 0
/36 -> {}
*MPLS
Preference: 0
Next hop type: Receive
Next-hop reference count: 6
State: <Active Int>
Local AS:
69
Age: 1:34:08
Metric: 1
Task: MPLS
Announcement bits (1): 0-KRT
AS path: I
...
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
299840 (1 entry, 1 announced)
TSI:
KRT in-kernel 299840 /52 -> {indirect(1048575)}
*RSVP
Preference: 7/2
Next hop type: Flood
Address: 0x9174a30
Next-hop reference count: 4
Next hop type: Router, Next hop index: 798
Address: 0x9174c28
Next-hop reference count: 2
Next hop: 8.0.0.2 via lt-1/2/0.9 weight 0x1
Label-switched-path R2-to-R4-2p2mp

2008

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Label operation: Pop

Next hop type: Router, Next hop index: 1048574
Address: 0x92544f0
Next-hop reference count: 2
Next hop: 7.0.0.2 via lt-1/2/0.7 weight 0x1
Label-switched-path R2-to-R200-p2mp
Label operation: Pop
Next hop: 6.0.0.2 via lt-1/2/0.5 weight 0x8001
Label operation: Pop
State: <Active Int>
Age: 1:29
Metric: 1
Task: RSVP
Announcement bits (1): 0-KRT
AS path: I...
800010 (1 entry, 1 announced)
TSI:
KRT in-kernel 800010 /36 -> {vt-3/2/0.32769}
*VPLS
Preference: 7
Next-hop reference count: 2
Next hop: via vt-3/2/0.32769, selected
Label operation: Pop
State: <Active Int>
Age: 1:31:53
Task: Common L2 VC
Announcement bits (1): 0-KRT
AS path: I
vt-3/2/0.32769 (1 entry, 1 announced)
TSI:
KRT in-kernel vt-3/2/0.32769.0
/16 -> {indirect(1048574)}
*VPLS
Preference: 7
Next-hop reference count: 2
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 800012, Push 100096(top)
Protocol next hop: 10.255.70.103
Push 800012
Indirect next hop: 87272e4 1048574
State: <Active Int>
Age: 1:31:53
Metric2: 2
Task: Common L2 VC
Announcement bits (2): 0-KRT 1-Common L2 VC
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
Indirect next hops: 1
Protocol next hop: 10.255.70.103 Metric: 2
Push 800012
Indirect next hop: 87272e4 1048574
Indirect path forwarding next hops: 1
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1
10.255.70.103/32 Originating RIB: inet.3
Metric: 2
Node path count: 1
Forwarding nexthops: 1
Nexthop: 10.31.1.6 via ge-3/1/0.0
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
abcd::10:255:71:52/128 (1 entry, 0 announced)

Copyright 2014, Juniper Networks, Inc.

2009

Interfaces Fundamentals for Routing Devices

*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Local AS:
69
Age: 1:34:07
Task: IF
AS path: I
fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:34:07
Task: IF
AS path: I
ff02::2/128 (1 entry, 1 announced)
TSI:
KRT in-kernel ff02::2/128 -> {}
*PIM
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:34:08
Task: PIM Recv6
Announcement bits (1): 0-KRT
AS path: I
ff02::d/128 (1 entry, 1 announced)
TSI:
KRT in-kernel ff02::d/128 -> {}
*PIM
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:34:08
Task: PIM Recv6
Announcement bits (1): 0-KRT
AS path: I
ff02::16/128 (1 entry, 1 announced)
TSI:
KRT in-kernel ff02::16/128 -> {}
*MLD
Preference: 0
Next-hop reference count: 18
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:34:06
Task: MLD
Announcement bits (1): 0-KRT
AS path: I
private.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced)
*Direct Preference: 0

2010

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Next hop type: Interface

Next-hop reference count: 1
Next hop: via lo0.16385, selected
State: <Active NoReadvrt Int>
Age: 1:34:07
Task: IF
AS path: I
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
10.255.70.103:1:3:1/96 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.70.103:1
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 1:28:12
Metric2: 1
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-green-l2vpn
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
Label-base: 800008, range: 8
Localpref: 100
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
10.255.71.52:1:1:1/96 (1 entry, 1 announced)
TSI:
Page 0 idx 0 Type 1 val 8699540
*L2VPN Preference: 170/-1
Next-hop reference count: 5
Protocol next hop: 10.255.71.52
Indirect next hop: 0 State: <Active Int Ext>
Age: 1:34:03
Metric2: 1
Task: green-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down,
mtu: 0
Label-base: 800016, range: 8, status-vector: 0x9F
10.255.71.52:1:5:1/96 (1 entry, 1 announced)
TSI:
Page 0 idx 0 Type 1 val 8699528
*L2VPN Preference: 170/-101
Next-hop reference count: 5
Protocol next hop: 10.255.71.52
Indirect next hop: 0 State: <Active Int Ext>
Age: 1:34:03
Metric2: 1
Task: green-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:, mtu: 0
Label-base: 800008, range: 8, status-vector: 0x9F

Copyright 2014, Juniper Networks, Inc.

2011

Interfaces Fundamentals for Routing Devices

...
l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
TSI:
10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced)
*L2CKT Preference: 7
Next hop: via so-1/1/2.0 weight 1, selected
Label-switched-path my-lsp
Label operation: Push 100000[0]
Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296
State: <Active Int>
Local AS:
99
Age: 10:21
Task: l2 circuit
Announcement bits (1): 0-LDP
AS path: I
VC Label 100000, MTU 1500, VLAN ID 512

55.0.0.0/24 (1 entry, 1 announced)

TSI:
KRT queued (pending) add
55.0.0.0/24 -> {Push 300112}
*BGP
Preference: 170/-101
Next hop type: Router
Address: 0x925c208
Next-hop reference count: 2
Source: 10.0.0.9
Next hop: 10.0.0.9 via ge-1/2/0.15, selected
Label operation: Push 300112
Label TTL action: prop-ttl
State: <Active Ext>
Local AS: 7019 Peer AS: 13979
Age: 1w0d 23:06:56
AIGP: 25
Task: BGP_13979.10.0.0.9+56732
Announcement bits (1): 0-KRT
AS path: 13979 7018 I
Accepted
Route Label: 300112
Localpref: 100
Router ID: 10.9.9.1

show route extensive (Access Route)

user@host> show route 13.160.0.102 extensive
inet.0: 39256 destinations, 39258 routes (39255 active, 0 holddown, 1 hidden)
13.160.0.102/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 13.160.0.102/32 -> {13.160.0.2}
OSPF area : 0.0.0.0, LSA ID : 13.160.0.102, LSA type : Extern
*Access Preference: 13
Next-hop reference count: 78472
Next hop: 13.160.0.2 via fe-0/0/0.0, selected
State: <Active Int>
Age: 12
Task: RPD Unix Domain Server./var/run/rpd_serv.local
Announcement bits (2): 0-KRT 1-OSPFv2
AS path: I

2012

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route extensive (BGP PIC Edge)

user@host> show route 1.1.1.6 extensive
ed.inet.0: 6 destinations, 9 routes (6 active, 0 holddown, 0 hidden)
1.1.1.6/32 (3 entries, 2 announced)
State: <CalcForwarding>
TSI:
KRT in-kernel 1.1.1.6/32 -> {indirect(1048574), indirect(1048577)}
Page 0 idx 0 Type 1 val 9219e30
Nexthop: Self
AS path: [2] 3 I
Communities: target:2:1
Path 1.1.1.6 from 1.1.1.4 Vector len 4. Val: 0
..
#Multipath Preference: 255
Next hop type: Indirect
Address: 0x93f4010
Next-hop reference count: 2
..
Protocol next hop: 1.1.1.4
Push 299824
Indirect next hop: 944c000 1048574 INH Session ID: 0x3
Indirect next hop: weight 0x1
Protocol next hop: 1.1.1.5
Push 299824
Indirect next hop: 944c1d8 1048577 INH Session ID: 0x4
Indirect next hop: weight 0x4000
State: <ForwardingOnly Int Ext)>
Inactive reason: Forwarding use only
Age: 25
Metric2: 15
Validation State: unverified
Task: RT
Announcement bits (1): 0-KRT
AS path: 3 I
Communities: target:2:1

show route extensive (FRR and LFA)

user@host> show route 20:31:2:0 extensive
inet.0: 46 destinations, 49 routes (45 active, 0 holddown, 1 hidden)
20.31.2.0/24 (2 entries, 1 announced)
State: FlashAll
TSI:
KRT in-kernel 20.31.2.0/24 -> {Push 299776, Push 299792}
*RSVP
Preference: 7/1
Next hop type: Router, Next hop index: 1048574
Address: 0xbbbc010
Next-hop reference count: 5
Next hop: 10.31.1.2 via ge-2/1/8.0 weight 0x1, selected
Label-switched-path europa-d-to-europa-e
Label operation: Push 299776
Label TTL action: prop-ttl
Session Id: 0x201
Next hop: 10.31.2.2 via ge-2/1/4.0 weight 0x4001
Label-switched-path europa-d-to-europa-e
Label operation: Push 299792
Label TTL action: prop-ttl
Session Id: 0x202
State: Active Int
Local AS:
100
Age: 5:31 Metric: 2

Copyright 2014, Juniper Networks, Inc.

2013

Interfaces Fundamentals for Routing Devices

OSPF

Task: RSVP
Announcement bits (1): 0-KRT
AS path: I
Preference: 10
Next hop type: Router, Next hop index: 615
Address: 0xb9d78c4
Next-hop reference count: 7
Next hop: 10.31.1.2 via ge-2/1/8.0, selected
Session Id: 0x201
State: Int
Inactive reason: Route Preference
Local AS:
100
Age: 5:35 Metric: 3
Area: 0.0.0.0
Task: OSPF
AS path: I

show route extensive (Route Reflector)

user@host> show route extensive
1.0.0.0/8 (1 entry, 1 announced)
TSI:
KRT in-kernel 1.0.0.0/8 -> {indirect(40)}
*BGP
Preference: 170/-101
Source: 192.168.4.214
Protocol next hop: 207.17.136.192 Indirect next hop: 84ac908 40
State: <Active Int Ext>
Local AS: 10458 Peer AS: 10458
Age: 3:09
Metric: 0
Metric2: 0
Task: BGP_10458.192.168.4.214+1033
Announcement bits (2): 0-KRT 4-Resolve inet.0
AS path: 3944 7777 I <Originator>
Cluster list: 1.1.1.1
Originator ID: 10.255.245.88
Communities: 7777:7777
Localpref: 100
Router ID: 4.4.4.4
Indirect next hops: 1
Protocol next hop: 207.17.136.192 Metric: 0
Indirect next hop: 84ac908 40
Indirect path forwarding next hops: 0
Next hop type: Discard

show route label detail (Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show route label 299872 detail
mpls.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
299872 (1 entry, 1 announced)
*LDP
Preference: 9
Next hop type: Flood
Next-hop reference count: 3
Address: 0x9097d90
Next hop: via vt-0/1/0.1
Next-hop index: 661
Label operation: Pop
Address: 0x9172130
Next hop: via so-0/0/3.0
Next-hop index: 654
Label operation: Swap 299872
State: **Active Int>

2014

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Local AS: 1001

Age: 8:20
Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
FECs bound to route: P2MP root-addr 10.255.72.166, grp 232.1.1.1,
src 192.168.142.2

show route label detail (Multipoint LDP with Multicast-Only Fast Reroute)
user@host> show route label 301568 detail
mpls.0: 18 destinations, 18 routes (18 active, 0 holddown, 0 hidden)
301568 (1 entry, 1 announced)
*LDP
Preference: 9
Next hop type: Flood
Address: 0x2735208
Next-hop reference count: 3
Next hop type: Router, Next hop index: 1397
Address: 0x2735d2c
Next-hop reference count: 3
Next hop: 1.3.8.2 via ge-1/2/22.0
Label operation: Pop
Load balance label: None;
Next hop type: Router, Next hop index: 1395
Address: 0x2736290
Next-hop reference count: 3
Next hop: 1.3.4.2 via ge-1/2/18.0
Label operation: Pop
Load balance label: None;
State: <Active Int AckRequest MulticastRPF>
Local AS:
10
Age: 54:05
Metric: 1
Validation State: unverified
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
FECs bound to route: P2MP root-addr 1.1.1.1, grp: 232.1.1.1, src:
192.168.219.11
Primary Upstream : 1.1.1.3:0--1.1.1.2:0
RPF Nexthops :
ge-1/2/15.0, 1.2.94.1, Label: 301568, weight: 0x1
ge-1/2/14.0, 1.2.3.1, Label: 301568, weight: 0x1
Backup Upstream : 1.1.1.3:0--1.1.1.6:0
RPF Nexthops :
ge-1/2/20.0, 1.2.96.1, Label: 301584, weight: 0xfffe
ge-1/2/19.0, 1.3.6.1, Label: 301584, weight: 0xfffe

Copyright 2014, Juniper Networks, Inc.

2015

Interfaces Fundamentals for Routing Devices

show route flow validation

List of Syntax

Syntax

Syntax (EX Series

Switches)

Release Information

Description
Options

Syntax on page 2016

Syntax (EX Series Switches) on page 2016
show route flow validation
<brief | detail>
<ip-prefix>
<table table-name>
<logical-system (all | logical-system-name)>
show route flow validation
<brief | detail>
<ip-prefix>
<table table-name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display flow route information.
noneDisplay flow route information.
brief | detail(Optional) Display the specified level of output. If you do not specify a level

of output, the system defaults to brief.

ip-prefix(Optional) IP address for the flow route.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

table table-name(Optional) Display flow route information for all routing tables whose

name begins with this string (for example, inet.0 and inet6.0 are both displayed
when you run the show route flow validation inet command).
Required Privilege
Level
List of Sample Output
Output Fields

view

show route flow validation on page 2017

Table 202 on page 2016 lists the output fields for the show route flow validation command.
Output fields are listed in the approximate order in which they appear.

Table 202: show route flow validation Output Fields

Field Name

Field Description

Level of Output

routing-table-name

Name of the routing table (for example, inet.0).

All levels

prefix

Route address.

All levels

Active unicast
route

Active route in the routing table.

All levels

2016

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 202: show route flow validation Output Fields (continued)

Field Name

Field Description

Level of Output

Dependent flow
destinations

Number of flows for which there are routes in the routing table.

All levels

Origin

Source of the route flow.

All levels

Neighbor AS

Autonomous system identifier of the neighbor.

All levels

Flow destination

Number of entries and number of destinations that match the route flow.

All levels

Unicast best
match

Destination that is the best match for the route flow.

All levels

Flags

Information about the route flow.

All levels

Sample Output
show route flow validation
user@host> show route flow validation
inet.0:
10.0.5.0/24Active unicast route
Dependent flow destinations: 1
Origin: 192.168.224.218, Neighbor AS: 65001
Flow destination (3 entries, 1 match origin)
Unicast best match: 10.0.5.0/24
Flags: SubtreeApex Consistent

Copyright 2014, Juniper Networks, Inc.

2017

Interfaces Fundamentals for Routing Devices

show route forwarding-table

List of Syntax

Syntax

show route forwarding-table

<detail | extensive | summary>
<all>
<ccc interface-name>
<destination destination-prefix>
<family family | matching matching>
<interface-name interface-name>
<label name>
<matching matching>
<multicast>
<table (default | logical-system-name/routing-instance-name | routing-instance-name)>
<vlan (all | vlan-name)>
<vpn vpn>

Syntax (MX Series

Routers)

show route forwarding-table

<detail | extensive | summary>
<all>
<bridge-domain (all | domain-name)>
<ccc interface-name>
<destination destination-prefix>
<family family | matching matching>
<interface-name interface-name>
<label name>
<learning-vlan-id learning-vlan-id>
<matching matching>
<multicast>
<table (default | logical-system-name/routing-instance-name | routing-instance-name)>
<vlan (all | vlan-name)>
<vpn vpn>

Syntax (TX Matrix and

TX Matrix Plus
Routers)

Release Information

2018

Syntax on page 2018

Syntax (MX Series Routers) on page 2018
Syntax (TX Matrix and TX Matrix Plus Routers) on page 2018

show route forwarding-table

<detail | extensive | summary>
<all>
<ccc interface-name>
<destination destination-prefix>
<family family | matching matching>
<interface-name interface-name>
<matching matching>
<label name>
<lcc number>
<multicast>
<table routing-instance-name>
<vpn vpn>

Command introduced before Junos OS Release 7.4.

Option bridge-domain introduced in Junos OS Release 7.5
Option learning-vlan-id introduced in Junos OS Release 8.4

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Options all and vlan introduced in Junos OS Release 9.6.

Command introduced in Junos OS Release 11.3 for the QFX Series.
Description

Display the Routing Engine's forwarding table, including the network-layer prefixes and
their next hops. This command is used to help verify that the routing protocol process
has relayed the correction information to the forwarding table. The Routing Engine
constructs and maintains one or more routing tables. From the routing tables, the Routing
Engine derives a table of active routes, called the forwarding table.

NOTE: The Routing Engine copies the forwarding table to the Packet
Forwarding Engine, the part of the router that is responsible for forwarding
packets. To display the entries in the Packet Forwarding Engine's forwarding
table, use the show pfe route command.

Options

noneDisplay the routes in the forwarding tables. By default, the show route
forwarding-table command does not display information about private, or internal,

forwarding tables.
detail | extensive | summary(Optional) Display the specified level of output.
all(Optional) Display routing table entries for all forwarding tables, including private,

or internal, tables.
bridge-domain (all | bridge-domain-name)(MX Series routers only) (Optional) Display

route entries for all bridge domains or the specified bridge domain.
ccc interface-name(Optional) Display route entries for the specified circuit cross-connect

interface.
destination destination-prefix(Optional) Destination prefix.
family family(Optional) Display routing table entries for the specified family:
fibre-channel, fmembers, inet, inet6, iso, mpls, tnp, unix, vpls, or vlan-classification.
interface-name interface-name(Optional) Display routing table entries for the specified

interface.
label name(Optional) Display route entries for the specified label.
lcc number(TX Matrix and TX matrix Plus routers only) (Optional) On a routing matrix

composed of a TX Matrix router and T640 routers, display information for the
specified T640 router (or line-card chassis) connected to the TX Matrix router. On
a routing matrix composed of the TX Matrix Plus router and T1600 or T4000 routers,
display information for the specified router (line-card chassis) connected to the TX
Matrix Plus router.

Copyright 2014, Juniper Networks, Inc.

2019

Interfaces Fundamentals for Routing Devices

Replace number with the following values depending on the LCC configuration:

0 through 3, when T640 routers are connected to a TX Matrix router in a routing

matrix.

0 through 3, when T1600 routers are connected to a TX Matrix Plus router in a

routing matrix.

0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.

0, 2, 4, or 6, when T4000 routers are connected to a TX Matrix Plus router with

3D SIBs in a routing matrix.

learning-vlan-id learning-vlan-id(MX Series routers only) (Optional) Display learned

information for all VLANs or for the specified VLAN.

matching matching(Optional) Display routing table entries matching the specified prefix

or prefix length.
multicast(Optional) Display routing table entries for multicast routes.
table (default | logical-system-name/routing-instance-name |
routing-instance-name)(Optional) Display route entries for all the routing tables in

the main routing instance or for the specified routing instance. If your device supports
logical systems, you can also display route entries for the specified logical system
and routing instance. To view the routing instances on your device, use the show
route instance command.
vlan (all | vlan-name)(Optional) Display information for all VLANs or for the specified

VLAN.
vpn vpn(Optional) Display routing table entries for a specified VPN.

Required Privilege
Level
List of Sample Output

2020

view

show route forwarding-table on page 2023

show route forwarding-table detail on page 2024
show route forwarding-table destination extensive (Weights and Balances) on page 2024
show route forwarding-table extensive on page 2025
show route forwarding-table extensive (RPF) on page 2026
show route forwarding-table family mpls on page 2027
show route forwarding-table family vpls on page 2027
show route forwarding-table vpls (Broadcast, unknown unicast, and multicast (BUM)
hashing is enabled) on page 2027
show route forwarding-table vpls (Broadcast, unknown unicast, and multicast (BUM)
hashing is enabled with MAC Statistics) on page 2028
show route forwarding-table family vpls extensive on page 2028
show route forwarding-table table default on page 2029
show route forwarding-table table
logical-system-name/routing-instance-name on page 2030

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route forwarding-table vpn on page 2031

Output Fields

Table 203 on page 2021 lists the output fields for the show route forwarding-table command.
Output fields are listed in the approximate order in which they appear. Field names might
be abbreviated (as shown in parentheses) when no level of output is specified, or when
the detail keyword is used instead of the extensive keyword.

Table 203: show route forwarding-table Output Fields

Field Name

Field Description

Level of Output

Logical system

Name of the logical system. This field is displayed if you specify the table
logical-system-name/routing-instance-name option on a device that is configured
for and supports logical systems.

All levels

Routing table

Name of the routing table (for example, inet, inet6, mpls).

All levels

Address family

Address family (for example, IP, IPv6, ISO, MPLS, and VPLS).

All levels

Destination

Destination of the route.

detail extensive

Route Type (Type)

How the route was placed into the forwarding table. When the detail keyword
is used, the route type might be abbreviated (as shown in parentheses):

All levels

cloned (clon)(TCP or multicast only) Cloned route.

destination (dest)Remote addresses directly reachable through an interface.

destination down (iddn)Destination route for which the interface is

unreachable.

interface cloned (ifcl)Cloned route for which the interface is unreachable.

route down (ifdn)Interface route for which the interface is unreachable.

ignore (ignr)Ignore this route.

interface (intf)Installed as a result of configuring an interface.

permanent (perm)Routes installed by the kernel when the routing table is

initialized.

userRoutes installed by the routing protocol process or as a result of the

configuration.
Route Reference
(RtRef)

Number of routes to reference.

detail extensive

Flags

Route type flags:

extensive

noneNo flags are enabled.

accountingRoute has accounting enabled.

cachedCache route.

incoming-iface interface-numberCheck against incoming interface.

prefix load balanceLoad balancing is enabled for this prefix.

rt nh decoupledRoute has been decoupled from the next hop to the

destination.

Next hop

sent to PFERoute has been sent to the Packet Forwarding Engine.

staticStatic route.

IP address of the next hop to the destination.

Copyright 2014, Juniper Networks, Inc.

detail extensive

2021

Interfaces Fundamentals for Routing Devices

Table 203: show route forwarding-table Output Fields (continued)

Field Name

Field Description

Level of Output

Next hop Type

(Type)

Next-hop type. When the detail keyword is used, the next-hop type might be
abbreviated (as indicated in parentheses):

detail extensive

broadcast (bcst)Broadcast.

denyDeny.

discard (dscd) Discard.

holdNext hop is waiting to be resolved into a unicast or multicast type.

indexed (idxd)Indexed next hop.

indirect (indr)Indirect next hop.

local (locl)Local address on an interface.

routed multicast (mcrt)Regular multicast next hop.

multicast (mcst)Wire multicast next hop (limited to the LAN).

multicast discard (mdsc)Multicast discard.

multicast group (mgrp)Multicast group member.

receive (recv)Receive.

reject (rjct)Discard. An ICMP unreachable message was sent.

resolve (rslv)Resolving the next hop.

unicast (ucst)Unicast.

unilist (ulst)List of unicast next hops. A packet sent to this next hop goes

to any next hop in the list.

Index

Software index of the next hop that is used to route the traffic for a given prefix.

detail extensive none

Route
interface-index

Logical interface index from which the route is learned. For example, for interface
routes, this is the logical interface index of the route itself. For static routes, this
field is zero. For routes learned through routing protocols, this is the logical
interface index from which the route is learned.

extensive

Reference (NhRef)

Number of routes that refer to this next hop.

detail extensive none

Next-hop interface
(Netif)

Interface used to reach the next hop.

detail extensive none

Weight

Value used to distinguish primary, secondary, and fast reroute backup routes.
Weight information is available when MPLS label-switched path (LSP) link
protection, node-link protection, or fast reroute is enabled, or when the standby
state is enabled for secondary paths. A lower weight value is preferred. Among
routes with the same weight value, load balancing is possible (see the Balance
field description).

extensive

Balance

Balance coefficient indicating how traffic of unequal cost is distributed among

next hops when a router is performing unequal-cost load balancing. This
information is available when you enable BGP multipath load balancing.

extensive

RPF interface

List of interfaces from which the prefix can be accepted. Reverse path forwarding
(RPF) information is displayed only when rpf-check is configured on the interface.

extensive

2022

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Sample Output
show route forwarding-table
user@host> show route forwarding-table
Routing table: default.inet
Internet:
Destination
Type RtRef Next hop
default
perm
0
0.0.0.0/32
perm
0
1.1.1.0/24
ifdn
0
1.1.1.0/32
iddn
0 1.1.1.0
1.1.1.1/32
user
0
1.1.1.1/32
intf
0 1.1.1.1
1.1.1.1/32
iddn
0 1.1.1.1
1.1.1.255/32
iddn
0 ff:ff:ff:ff:ff:ff
10.0.0.0/24
intf
0
10.0.0.0/32
dest
0 10.0.0.0
10.0.0.1/32
intf
0 10.0.0.1
10.0.0.1/32
dest
0 10.0.0.1
10.0.0.255/32
dest
0 10.0.0.255
10.1.1.0/24
ifdn
0
10.1.1.0/32
iddn
0 10.1.1.0
10.1.1.1/32
user
0
10.1.1.1/32
intf
0 10.1.1.1
10.1.1.1/32
iddn
0 10.1.1.1
10.1.1.255/32
iddn
0 ff:ff:ff:ff:ff:ff
10.206.0.0/16
user
0 10.209.63.254
10.209.0.0/16
user
1 0:12:1e:ca:98:0
10.209.0.0/18
intf
0
10.209.0.0/32
dest
0 10.209.0.0
10.209.2.131/32
intf
0 10.209.2.131
10.209.2.131/32
dest
0 10.209.2.131
10.209.17.55/32
dest
0 0:30:48:5b:78:d2
10.209.63.42/32
dest
0 0:23:7d:58:92:ca
10.209.63.254/32
dest
0 0:12:1e:ca:98:0
10.209.63.255/32
dest
0 10.209.63.255
10.227.0.0/16
user
0 10.209.63.254

Type Index NhRef Netif

rjct
46
4
dscd
44
1
rslv
608
1 ge-2/0/1.0
recv
606
1 ge-2/0/1.0
rjct
46
4
locl
607
2
locl
607
2
bcst
605
1 ge-2/0/1.0
rslv
616
1 ge-2/0/0.0
recv
614
1 ge-2/0/0.0
locl
615
2
locl
615
2
bcst
613
1 ge-2/0/0.0
rslv
612
1 ge-2/0/1.0
recv
610
1 ge-2/0/1.0
rjct
46
4
locl
611
2
locl
611
2
bcst
609
1 ge-2/0/1.0
ucst
419
20 fxp0.0
ucst
419
20 fxp0.0
rslv
418
1 fxp0.0
recv
416
1 fxp0.0
locl
417
2
locl
417
2
ucst
435
1 fxp0.0
ucst
434
1 fxp0.0
ucst
419
20 fxp0.0
bcst
415
1 fxp0.0
ucst
419
20 fxp0.0

...
Routing table: iso
ISO:
Destination
Type RtRef Next hop
Type Index NhRef Netif
default
perm
0
rjct
27
1
47.0005.80ff.f800.0000.0108.0003.0102.5524.5220.00
intf
0
locl
28
1
Routing table: inet6
Internet6:
Destination
Type RtRef Next hop
default
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1
Routing table: ccc
MPLS:
Interface.Label
Type RtRef Next hop
default
perm
0
100004(top)fe-0/0/1.0

Copyright 2014, Juniper Networks, Inc.

Type Index NhRef Netif

rjct
6
1
mdsc
4
1
mcst
3
1

Type Index NhRef Netif

rjct 16
1

2023

Interfaces Fundamentals for Routing Devices

show route forwarding-table detail

user@host> show route forwarding-table detail
Routing table: inet
Internet:
Destination
Type RtRef Next hop
default
user
2 0:90:69:8e:b1:1b
default
perm
0
10.1.1.0/24
intf
0 ff.3.0.21
10.1.1.0/32
dest
0 10.1.1.0
10.1.1.1/32
intf
0 10.1.1.1
10.1.1.255/32
dest
0 10.1.1.255
10.21.21.0/24
intf
0 ff.3.0.21
10.21.21.0/32
dest
0 10.21.21.0
10.21.21.1/32
intf
0 10.21.21.1
10.21.21.255/32
dest
0 10.21.21.255
127.0.0.1/32
intf
0 127.0.0.1
172.17.28.19/32
clon
1 192.168.4.254
172.17.28.44/32
clon
1 192.168.4.254

Type Index NhRef Netif

ucst
132
4 fxp0.0
rjct
14
1
ucst
322
1 so-5/3/0.0
recv
324
1 so-5/3/0.0
locl
321
1
bcst
323
1 so-5/3/0.0
ucst
326
1 so-5/3/0.0
recv
328
1 so-5/3/0.0
locl
325
1
bcst
327
1 so-5/3/0.0
locl
320
1
ucst
132
4 fxp0.0
ucst
132
4 fxp0.0

...
Routing table: private1__.inet
Internet:
Destination
Type RtRef Next hop
default
perm
0
10.0.0.0/8
intf
0
10.0.0.0/32
dest
0 10.0.0.0
10.0.0.4/32
intf
0 10.0.0.4
10.0.0.4/32
dest
0 10.0.0.4

Type Index NhRef Netif

rjct
46
1
rslv
136
1 fxp1.0
recv
134
1 fxp1.0
locl
135
2
locl
135
2

...
Routing table: iso
ISO:
Destination
Type RtRef Next hop
default
perm
0

Type Index NhRef Netif

rjct
38
1

Routing table: inet6

Internet6:
Destination
Type RtRef Next hop
default
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1

Type Index NhRef Netif

rjct
22
1
mdsc
21
1
mcst
17
1

...
Routing table: mpls
MPLS:
Destination
Type RtRef Next hop
default
perm
0

Type Index NhRef Netif

rjct 28
1

show route forwarding-table destination extensive (Weights and Balances)

user@host> show route forwarding-table destination 3.4.2.1 extensive
Routing table: inet [Index 0]
Internet:
Destination: 3.4.2.1/32
Route type: user
Route reference: 0

2024

Route interface-index: 0

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Flags: sent to PFE

Next-hop type: unilist
Nexthop: 4.4.4.4
Next-hop type: unicast
Next-hop interface: so-1/1/0.0
Nexthop: 145.12.1.2
Next-hop type: unicast
Next-hop interface: so-0/1/2.0

Index: 262143

Reference: 1

Index: 335
Weight: 22

Reference: 2
Balance: 3

Index: 337
Weight: 33

Reference: 2
Balance: 33

show route forwarding-table extensive

user@host> show route forwarding-table extensive
Routing table: inet [Index 0]
Internet:
Destination: default
Route type: user
Route reference: 2
Flags: sent to PFE
Nexthop: 0:90:69:8e:b1:1b
Next-hop type: unicast
Next-hop interface: fxp0.0
Destination: default
Route type: permanent
Route reference: 0
Flags: none
Next-hop type: reject
Destination: 127.0.0.1/32
Route type: interface
Route reference: 0
Flags: sent to PFE
Nexthop: 127.0.0.1
Next-hop type: local

Route interface-index: 0

Index: 132

Reference: 4

Route interface-index: 0
Index: 14

Reference: 1

Route interface-index: 0

Index: 320

Reference: 1

...
Routing table: private1__.inet [Index 1]
Internet:
Destination: default
Route type: permanent
Route reference: 0
Flags: sent to PFE
Next-hop type: reject
Destination: 10.0.0.0/8
Route type: interface
Route reference: 0
Flags: sent to PFE
Next-hop type: resolve
Next-hop interface: fxp1.0

Route interface-index: 0
Index: 46

Reference: 1

Route interface-index: 3
Index: 136

Reference: 1

...
Routing table: iso [Index 0]
ISO:
Destination: default
Route type: permanent

Copyright 2014, Juniper Networks, Inc.

2025

Interfaces Fundamentals for Routing Devices

Route reference: 0
Flags: sent to PFE
Next-hop type: reject

Route interface-index: 0
Index: 38

Reference: 1

Routing table: inet6 [Index 0]

Internet6:
Destination: default
Route type: permanent
Route reference: 0
Flags: sent to PFE
Next-hop type: reject

Route interface-index: 0

Destination: ff00::/8
Route type: permanent
Route reference: 0
Flags: sent to PFE
Next-hop type: multicast discard

Route interface-index: 0

Index: 22

Index: 21

Reference: 1

Reference: 1

...
Routing table: private1__.inet6 [Index 1]
Internet6:
Destination: default
Route type: permanent
Route reference: 0
Flags: sent to PFE
Next-hop type: reject

Route interface-index: 0
Index: 54

Reference: 1

Destination: fe80::2a0:a5ff:fe3d:375/128
Route type: interface
Route reference: 0
Route interface-index: 0
Flags: sent to PFE
Nexthop: fe80::2a0:a5ff:fe3d:375
Next-hop type: local
Index: 75
Reference: 1
...

show route forwarding-table extensive (RPF)

The next example is based on the following configuration, which enables an RPF check
on all routes that are learned from this interface, including the interface route:
so-1/1/0 {
unit 0 {
family inet {
rpf-check;
address 15.95.1.2/30;
}
}
}
user@host> show route forwarding-table extensive
Routing table: inet [Index 0]
Internet:
...
...
Destination: 15.95.1.3/32
Route type: destination
Route reference: 0
Route interface-index: 67

2026

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Flags: sent to PFE

Nexthop: 15.95.1.3
Next-hop type: broadcast
Next-hop interface: so-1/1/0.0
RPF interface: so-1/1/0.0

Index: 328

Reference: 1

show route forwarding-table family mpls

user@host> show route forwarding-table family mpls
Routing table: mpls
MPLS:
Destination
Type RtRef Next hop
default
perm
0
0
user
0
1
user
0
2
user
0
100000
user
0 10.31.1.6
800002
user
0
vt-0/3/0.32770 (VPLS)
user

Type Index NhRef Netif

rjct
19
1
recv
18
3
recv
18
3
recv
18
3
swap 100001
fe-1/1/0.0
Pop
vt-0/3/0.32770

indr
351
4
Push 800000, Push 100002(top)

so-0/0/0.0

show route forwarding-table family vpls

user@host> show route forwarding-table family vpls
Routing table: green.vpls
VPLS:
Destination
Type RtRef Next hop
Type Index NhRef Netif
default
dynm
0
flood
353
1
default
perm
0
rjct
298
1
fe-0/1/0.0
dynm
0
flood
355
1
00:90:69:0c:20:1f/48
<<<<<Remote CE
dynm

so-0/0/0.0
00:90:69:85:b0:1f/48
dynm

indr
351
4
Push 800000, Push 100002(top)
<<<<<<Local CE

ucst

354

2 fe-0/1/0.0

show route forwarding-table vpls (Broadcast, unknown unicast, and multicast (BUM) hashing is enabled)
user@host> show route forwarding-table vpls
Routing table: green.vpls
VPLS:
Enabled protocols: BUM hashing
Destination
Type RtRef Next hop
default
perm
0
lsi.1048832
intf
0
4.4.3.2
ge-3/0/0.0
00:19:e2:25:d0:01/48 user
0
0x30003/51
user
0
ge-2/3/9.0
intf
0
ge-3/1/3.0
intf
0
0x30002/51
user
0
0x30001/51
user
0

Copyright 2014, Juniper Networks, Inc.

Type Index
NhRef Netif
dscd
519
1
indr 1048574
4
Push 262145
621
2
ucst
comp
ucst
ucst
comp
comp

590
627
590
619
600
597

5 ge-2/3/9.0
2
5 ge-2/3/9.0
4 ge-3/1/3.0
2
2

2027

Interfaces Fundamentals for Routing Devices

show route forwarding-table vpls (Broadcast, unknown unicast, and multicast (BUM) hashing is enabled with
MAC Statistics)
user@host> show route forwarding-table vpls
Routing table: green.vpls
VPLS:
Enabled protocols: BUM hashing, MAC Stats
Destination
Type RtRef Next hop
default
perm
0
lsi.1048834
intf
0
4.4.3.2
ge-3/0/0.0
00:19:e2:25:d0:01/48 user
0
0x30003/51
user
0
ge-2/3/9.0
intf
0
ge-3/1/3.0
intf
0
0x30002/51
user
0
0x30001/51
user
0

Type Index
NhRef Netif
dscd
519
1
indr 1048574
4
Push 262145
592
2
ucst
comp
ucst
ucst
comp
comp

590
630
590
591
627
624

5 ge-2/3/9.0
2
5 ge-2/3/9.0
4 ge-3/1/3.0
2
2

show route forwarding-table family vpls extensive

user@host> show route forwarding-table family vpls extensive
Routing table: green.vpls [Index 2]
VPLS:
Destination: default
Route type: dynamic
Route reference: 0
Flags: sent to PFE
Next-hop type: flood
Next-hop type: unicast
Next-hop interface: fe-0/1/3.0
Next-hop type: unicast
Next-hop interface: fe-0/1/2.0
Destination: default
Route type: permanent
Route reference: 0
Flags: none
Next-hop type: discard
Destination: fe-0/1/2.0
Route type: dynamic
Route reference: 0
Flags: sent to PFE
Next-hop type: flood
Next-hop type: indirect
Next-hop type: Push 800016
Next-hop interface: at-1/0/1.0
Next-hop type: indirect
Next hop: 10.31.3.2
Next-hop type: Push 800000
Next-hop interface: fe-0/1/1.0
Next-hop type: unicast
Next-hop interface: fe-0/1/3.0
Destination: fe-0/1/3.0
Route type: dynamic
Route reference: 0
Flags: sent to PFE
Next-hop type: flood

2028

Route interface-index: 72
Index: 289
Index: 291

Reference: 1
Reference: 3

Index: 290

Reference: 3

Route interface-index: 0
Index: 341

Reference: 1

Route interface-index: 69
Index: 293
Index: 363

Reference: 1
Reference: 4

Index: 301

Reference: 5

Index: 291

Reference: 3

Route interface-index: 70
Index: 292

Reference: 1

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Next-hop type: indirect

Next-hop type: Push 800016
Next-hop interface: at-1/0/1.0
Next-hop type: indirect
Next hop: 10.31.3.2
Next-hop type: Push 800000
Next-hop interface: fe-0/1/1.0
Next-hop type: unicast
Next-hop interface: fe-0/1/2.0

Index: 363

Reference: 4

Index: 301

Reference: 5

Index: 290

Reference: 3

Destination: 10:00:00:01:01:01/48
Route type: dynamic
Route reference: 0
Route interface-index: 70
Flags: sent to PFE, prefix load balance
Next-hop type: unicast
Index: 291
Reference: 3
Next-hop interface: fe-0/1/3.0
Route used as destination:
Packet count:
6640
Byte count:
675786
Route used as source
Packet count:
6894
Byte count:
696424
Destination: 10:00:00:01:01:04/48
Route type: dynamic
Route reference: 0
Route interface-index: 69
Flags: sent to PFE, prefix load balance
Next-hop type: unicast
Index: 290
Reference: 3
Next-hop interface: fe-0/1/2.0
Route used as destination:
Packet count:
96
Byte count:
8079
Route used as source:
Packet count:
296
Byte count:
24955
Destination: 10:00:00:01:03:05/48
Route type: dynamic
Route reference: 0
Route interface-index: 74
Flags: sent to PFE, prefix load balance
Next-hop type: indirect
Index: 301
Reference: 5
Next hop: 10.31.3.2
Next-hop type: Push 800000
Next-hop interface: fe-0/1/1.0

show route forwarding-table table default

user@host> show route forwarding-table table default
Routing table: default.inet
Internet:
Destination
Type RtRef Next hop
default
perm
0
0.0.0.0/32
perm
0
10.0.60.0/30
user
0 10.0.60.13
10.0.60.12/30
intf
0
10.0.60.12/32
dest
0 10.0.60.12
10.0.60.13/32
dest
0 0:5:85:8b:bc:22
10.0.60.14/32
intf
0 10.0.60.14
10.0.60.14/32
dest
0 10.0.60.14
10.0.60.15/32
dest
0 10.0.60.15
10.0.67.12/30
user
0 10.0.60.13
10.0.80.0/30
ifdn
0 ff.3.0.21
10.0.80.0/32
dest
0 10.0.80.0
10.0.80.2/32
user
0
10.0.80.2/32
intf
0 10.0.80.2

Copyright 2014, Juniper Networks, Inc.

Type Index NhRef Netif

rjct
36
2
dscd
34
1
ucst
713
5 fe-0/1/3.0
rslv
688
1 fe-0/1/3.0
recv
686
1 fe-0/1/3.0
ucst
713
5 fe-0/1/3.0
locl
687
2
locl
687
2
bcst
685
1 fe-0/1/3.0
ucst
713
5 fe-0/1/3.0
ucst
676
1 so-0/0/1.0
recv
678
1 so-0/0/1.0
rjct
36
2
locl
675
1

2029

Interfaces Fundamentals for Routing Devices

10.0.80.3/32
10.0.90.12/30
10.0.90.12/32
10.0.90.14/32
10.0.90.14/32
10.0.90.15/32
10.5.0.0/16
10.10.0.0/16
10.13.10.0/23
10.84.0.0/16
10.150.0.0/16
10.157.64.0/19
10.209.0.0/16

dest
intf
dest
intf
dest
dest
user
user
user
user
user
user
user

0
0
0
0
0
0
0
0
0
0
0
0
0

10.0.80.3
10.0.90.12
10.0.90.14
10.0.90.14
10.0.90.15
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126

bcst
rslv
recv
locl
locl
bcst
ucst
ucst
ucst
ucst
ucst
ucst
ucst

677
684
682
683
683
681
324
324
324
324
324
324
324

1
1
1
2
2
1
15
15
15
15
15
15
15

so-0/0/1.0
fe-0/1/0.0
fe-0/1/0.0

fe-0/1/0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0

...
Routing table: default.iso
ISO:
Destination
Type RtRef Next hop
default
perm
0

Type Index NhRef Netif

rjct
60
1

Routing table: default.inet6

Internet6:
Destination
Type RtRef Next hop
default
perm
0
::/128
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1

Type Index NhRef Netif

rjct
44
1
dscd
42
1
mdsc
43
1
mcst
39
1

Routing table: default.mpls

MPLS:
Destination
Type RtRef Next hop
default
perm
0

Type Index NhRef Netif

dscd
50
1

show route forwarding-table table logical-system-name/routing-instance-name

user@host> show route forwarding-table table R4/vpn-red
Logical system: R4
Routing table: vpn-red.inet
Internet:
Destination
Type RtRef Next hop
Type Index NhRef Netif
default
perm
0
rjct
563
1
0.0.0.0/32
perm
0
dscd
561
2
1.0.0.1/32
user
0
dscd
561
2
2.0.2.0/24
intf
0
rslv
771
1 ge-1/2/0.3
2.0.2.0/32
dest
0 2.0.2.0
recv
769
1 ge-1/2/0.3
2.0.2.1/32
intf
0 2.0.2.1
locl
770
2
2.0.2.1/32
dest
0 2.0.2.1
locl
770
2
2.0.2.2/32
dest
0 0.4.80.3.0.1b.c0.d5.e4.bd.0.1b.c0.d5.e4.bc.8.0
ucst
789
1 ge-1/2/0.3
2.0.2.255/32
dest
0 2.0.2.255
bcst
768
1 ge-1/2/0.3
224.0.0.0/4
perm
1
mdsc
562
1
224.0.0.1/32
perm
0 224.0.0.1
mcst
558
1
255.255.255.255/32 perm
0
bcst
559
1
Logical system: R4
Routing table: vpn-red.iso
ISO:
Destination
Type RtRef Next hop
default
perm
0

2030

Type Index NhRef Netif

rjct
608
1

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Logical system: R4
Routing table: vpn-red.inet6
Internet6:
Destination
Type RtRef Next hop
default
perm
0
::/128
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1

Type Index NhRef Netif

rjct
708
1
dscd
706
1
mdsc
707
1
mcst
704
1

Logical system: R4
Routing table: vpn-red.mpls
MPLS:
Destination
Type RtRef Next hop
default
perm
0

Type Index NhRef Netif

dscd
638

show route forwarding-table vpn

user@host> show route forwarding-table vpn VPN-A
Routing table:: VPN-A.inet
Internet:
Destination
Type RtRef Nexthop
default
perm
0
10.39.10.20/30
intf
0 ff.3.0.21
so-0/0/0.0
10.39.10.21/32
intf
0 10.39.10.21
10.255.14.172/32
user
0
so-0/0/0.0
10.255.14.175/32
user
0
100004(top) so-1/0/0.0
224.0.0.0/4
perm
224.0.0.1/32
perm
224.0.0.5/32
user
255.255.255.255/32 perm

Copyright 2014, Juniper Networks, Inc.

2
0 224.0.0.1
1 224.0.0.5
0

Type Index NhRef Netif

rjct
4
4
ucst
40
1
locl
ucst

36
69

1
2

indr
81
3
Push 100004, Push
mdsc
mcst
mcst
bcst

5
1
1
2

3
8
8
3

2031

Interfaces Fundamentals for Routing Devices

show route forwarding-table interface-name

Syntax

Release Information
Description
Options

show route forwarding-table interface-name interface-name

<detail | extensive>
<all>

Command introduced in Junos OS Release 9.6.

Display the interfaces in the Routing Engine's forwarding table.
noneDisplay information for the specified interface.
detail | extensive(Optional) Display the specified level of output.
all(Optional) Display all interfaces in the routing table.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route forwarding-table interface-name fe-0/1/1 on page 2033

show route forwarding-table interface-name all on page 2033
show route forwarding-table interface-name all detail on page 2034
Table 204 on page 2032 lists the output fields for the show route forwarding-table
interface-name command. Output fields are listed in the approximate order in which they
appear.

Table 204: show route forwarding-table interface-name Output Fields

Field Name

Field Description

Level of Output

Name

Name of the interface (for example fe-0/1/1, lo0, ae0, and so on).

All levels

MTU

Interfaces maximum transmission unit (MTU).

All levels

Afam

Configured address family (for example inet, tnp, inet6, and so on).

detail extensive

Network

Network information:

All levels

<Link>Physical interface, not a logical interface.

<PtoP>Point-to-point network.

ipaddressNetwork address.

Address

Address of the interface. The address can be a MAC address, IPv4 address, IPv6
address, and so on.

All levels

IPkts

Number of packets received on the interface.

All levels

Ierr

Number of packets received on the interface with errors.

All levels

Opkts

Number of packets transmitted or sent from the interface.

All levels

2032

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 204: show route forwarding-table interface-name Output Fields (continued)

Field Name

Field Description

Level of Output

Oerr

Number of packets transmitted or sent from the interface with errors.

All levels

Coll

Number of packets that experienced collisions on the interface.

All levels

Sample Output
show route forwarding-table interface-name fe-0/1/1
user@host> show route forwarding-table interface-name fe-0/1/1
Name
Mtu Network
Address
Ipkts Ierr
fe-0/1/1
1514 <Link>
00.05.85.88.cc.20
0
0

Opkts Oerr
0
0

Coll
0

Opkts Oerr
39907
0

Coll
0

show route forwarding-table interface-name all

user@host> show route forwarding-table interface-name all
Name
Mtu Network
Address
Ipkts Ierr
fxp0
1514 <Link>
00.a0.a5.56.03.83
180965
0
unit 0
fxp1
unit 0

lsi
dsc
lo0

1500 192.168.187.0/ 192.168.187.10

1514 <Link>
02.00.00.00.00.04 33010497

0 30110800

1500 10.0.0.0/8
10.0.0.0/8
128.0.0.0/2
128.0.0.0/2
1500 fe80::/64
fec0::/64
1500
1496 <Link>
max <Link>
max <Link>

0
8980

0
0

0
8980

0
0

0
0

1679900

1068611

10.0.0.1
10.0.0.4
128.0.0.1
128.0.0.4
fe80::200:ff:fe0
fec0::a:0:0:4
4

unit 0

max 127.0.0.1/8
127.0.0.1
192.168.0.1/8 192.168.0.1
unit 16384 max 127.0.0.1/8
127.0.0.1
unit 16385 max
gre
max <Link>
ipip
max <Link>
tap
max <Link>
pime
max <Link>
pimd
max <Link>
mtun
max <Link>
so-0/0/0
4474 <Link>
unit 0
0
so-0/0/1

4470 <PtoP>

unit 0
0
so-0/0/2
so-0/0/3
fe-0/1/0

4470 <PtoP>

unit 0

Copyright 2014, Juniper Networks, Inc.

10.0.60.2

4474 <Link>

4474 <Link>
4474 <Link>
1514 <Link>

0
0

10.0.80.2

00.05.85.88.cc.1f

1500 10.0.90.12/30

10.0.90.14

0
0

0
0
0
523120

0
0

0
0
0
0

0
0
0
0
0
623044

0
0
0
0
0
0

0
0
0
0

2033

Interfaces Fundamentals for Routing Devices

0
fe-0/1/1
fe-0/1/2

1514 <Link>
1514 <Link>

00.05.85.88.cc.20
00.05.85.88.cc.21

0
0

0
0

0
0

0
0

0
0

...

show route forwarding-table interface-name all detail

user@host> show route forwarding-table interface-name all detail
Name
Mtu AFam
Network
Address
Ipkts Ierr
Opkts
Oerr Coll
fxp0
1514
<Link>
00.a0.a5.56.03.83
181005
0
39948
0
0
unit 0
1500 inet
192.168.187.0/ 192.168.187.10
fxp1
1514
<Link>
02.00.00.00.00.04 33012676
0 30112468
0
0
unit 0
1500 inet
10.0.0.0/8
10.0.0.1
10.0.0.0/8
10.0.0.4
128.0.0.0/2
128.0.0.1
128.0.0.0/2
128.0.0.4
1500 inet6
fe80::/64
fe80::200:ff:fe0
fec0::/64
fec0::a:0:0:4
1500 tnp
4
lsi
1496
<Link>
dsc
max
<Link>
0
0
0
0
0
lo0
max
<Link>
8980
0
8980
0
0
unit 0
max inet
127.0.0.1/8
127.0.0.1
192.168.0.1/8 192.168.0.1
unit 16384 max inet
127.0.0.1/8
127.0.0.1
unit 16385 max inet
gre
max
<Link>
ipip
max
<Link>
tap
max
<Link>
pime
max
<Link>
pimd
max
<Link>
mtun
max
<Link>
so-0/0/0
4474
<Link>
1679980
0 1068661
0
0
unit 0
4470 inet
<PtoP>
10.0.60.2
0
0
0
0
0
...

2034

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route hidden

Syntax

Release Information
Description

Options

show route hidden

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

Display only hidden route information. A hidden route is unusable, even if it is the best
path.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Understanding Hidden Routes

show route hidden on page 2035

show route hidden detail on page 2036
show route hidden extensive on page 2036
show route hidden terse on page 2036
For information about output fields, see the output field table for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route hidden
user@host> show route hidden
inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
127.0.0.1/32
[Direct/0] 04:26:38
> via lo0.0
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.5.5.5/32
[BGP/170] 03:44:10, localpref 100, from 10.4.4.4
AS path: 100 I
Unusable
10.12.1.0/24
[BGP/170] 03:44:10, localpref 100, from 10.4.4.4
AS path: 100 I
Unusable

Copyright 2014, Juniper Networks, Inc.

2035

Interfaces Fundamentals for Routing Devices

10.12.80.4/30

[BGP/170] 03:44:10, localpref 100, from 10.4.4.4

AS path: I
Unusable

...

show route hidden detail

user@host> show route hidden detail
inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)
Restart Complete
127.0.0.1/32 (1 entry, 0 announced)
Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Hidden Martian Int>
Local AS:
1
Age: 4:27:37
Task: IF
AS path: I
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden)
Restart Complete
10.5.5.5/32 (1 entry, 0 announced)
BGP
Preference: 170/-101
Route Distinguisher: 10.4.4.4:4
Next hop type: Unusable
Next-hop reference count: 6
State: <Secondary Hidden Int Ext>
Local AS:
1 Peer AS:
1
Age: 3:45:09
Task: BGP_1.10.4.4.4+2493
AS path: 100 I
Communities: target:1:999
VPN Label: 100064
Localpref: 100
Router ID: 10.4.4.4
Primary Routing Table bgp.l3vpn.0
...

show route hidden extensive

The output for the show route hidden extensive command is identical to that of the show
route hidden detail command. For sample output, see show route hidden detail on
page 2036.
show route hidden terse
user@host> show route hidden terse
inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination
127.0.0.1/32

2036

P Prf
D
0

Metric 1

Metric 2

Next hop
>lo0.0

AS path

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination
10.5.5.5/32
10.12.1.0/24
10.12.80.4/30

P
B
B
B

Prf
170
170
170

Metric 1
100
100
100

Metric 2

Next hop
Unusable
Unusable
Unusable

AS path
100 I
100 I
I

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Restart Complete
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
bgp.l3vpn.0: 3 destinations, 3 routes (0 active, 0 holddown, 3 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination
P Prf
10.4.4.4:4:10.5.5.5/32
B 170
10.4.4.4:4:10.12.1.0/24
B 170
10.4.4.4:4:10.12.80.4/30
B 170

Metric 1

Metric 2

Next hop

AS path

100

Unusable

100 I

100

Unusable

100 I

100

Unusable

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Copyright 2014, Juniper Networks, Inc.

2037

Interfaces Fundamentals for Routing Devices

show route inactive-path

List of Syntax

Syntax on page 2038

Syntax (EX Series Switches) on page 2038

Syntax

show route inactive-path

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)
Release Information

Description

Options

show route inactive-path

<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display routes for destinations that have no active route. An inactive route is a route that
was not selected as the best path.
noneDisplay all inactive routes.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route inactive-path on page 2038

show route inactive-path detail on page 2039
show route inactive-path extensive on page 2040
show route inactive-path terse on page 2040
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route inactive-path
user@host> show route inactive-path
inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.12.100.12/30

[OSPF/10] 03:57:28, metric 1

> via so-0/3/0.0

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

2038

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

10.0.0.0/8

[Direct/0] 04:39:56
> via fxp1.0

red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden)

Restart Complete
+ = Active Route, - = Last Active, * = Both
10.12.80.0/30

[BGP/170] 04:38:17, localpref 100

AS path: 100 I
> to 10.12.80.1 via ge-6/3/2.0

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Restart Complete
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
bgp.l3vpn.0: 3 destinations, 3 routes (0 active, 0 holddown, 3 hidden)
Restart Complete
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

show route inactive-path detail

user@host> show route inactive-path detail
inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)
Restart Complete
10.12.100.12/30 (2 entries, 1 announced)
OSPF
Preference: 10
Next-hop reference count: 1
Next hop: via so-0/3/0.0, selected
State: <Int>
Inactive reason: Route Preference
Local AS:
1
Age: 3:58:24
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
10.0.0.0/8 (2 entries, 0 announced)
Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via fxp1.0, selected
State: <NotBest Int>
Inactive reason: No difference
Age: 4:40:52
Task: IF
AS path: I
red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden)
Restart Complete
10.12.80.0/30 (2 entries, 1 announced)

Copyright 2014, Juniper Networks, Inc.

2039

Interfaces Fundamentals for Routing Devices

BGP

Preference: 170/-101
Next-hop reference count: 6
Source: 10.12.80.1
Next hop: 10.12.80.1 via ge-6/3/2.0, selected
State: <Ext>
Inactive reason: Route Preference
Peer AS:
100
Age: 4:39:13
Task: BGP_100.10.12.80.1+179
AS path: 100 I
Localpref: 100
Router ID: 10.0.0.0

show route inactive-path extensive

The output for the show route inactive-path extensive command is identical to that of
the show route inactive-path detail command. For sample output, see show route
inactive-path detail on page 2039.
show route inactive-path terse
user@host> show route inactive-path terse
inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination
10.12.100.12/30

P Prf
O 10

Metric 1
1

Metric 2

Next hop
>so-0/3/0.0

AS path

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
A Destination
10.0.0.0/8

P Prf
D
0

Metric 1

Metric 2

Next hop
>fxp1.0

AS path

red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden)

Restart Complete
+ = Active Route, - = Last Active, * = Both
A Destination
10.12.80.0/30

P Prf
B 170

Metric 1
100

Metric 2

Next hop
>10.12.80.1

AS path
100 I

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Restart Complete
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
bgp.l3vpn.0: 3 destinations, 3 routes (0 active, 0 holddown, 3 hidden)
Restart Complete
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

2040

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route inactive-prefix

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description
Options

Syntax on page 2041

Syntax (EX Series Switches) on page 2041
show route inactive-prefix
<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>
show route inactive-prefix
<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display inactive route destinations in each routing table.
noneDisplay all inactive route destination.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route inactive-prefix on page 2041

show route inactive-prefix detail on page 2041
show route inactive-prefix extensive on page 2042
show route inactive-prefix terse on page 2042
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route inactive-prefix
user@host> show route inactive-prefix
inet.0: 14 destinations, 14 routes (13 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
127.0.0.1/32

[Direct/0] 00:04:54
> via lo0.0

show route inactive-prefix detail

user@host> show route inactive-prefix detail
inet.0: 14 destinations, 14 routes (13 active, 0 holddown, 1 hidden)

Copyright 2014, Juniper Networks, Inc.

2041

Interfaces Fundamentals for Routing Devices

127.0.0.1/32 (1 entry, 0 announced)

Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Hidden Martian Int>
Age: 4:51
Task: IF
AS path: I00:04:54
> via lo0.0

show route inactive-prefix extensive

The output for the show route inactive-prefix extensive command is identical to that of
the show route inactive-path detail command. For sample output, see show route
inactive-prefix detail on page 2041.
show route inactive-prefix terse
user@host> show route inactive-prefix terse
inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A Destination
127.0.0.1/32

2042

P Prf
D
0

Metric 1

Metric 2

Next hop
>lo0.0

AS path

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route instance

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)

Release Information

Description
Options

Syntax on page 2043

Syntax (EX Series Switches and QFX Series) on page 2043
show route instance
<brief | detail | summary>
<instance-name>
<logical-system (all | logical-system-name)>
<operational>
show route instance
<brief | detail | summary>
<instance-name>
<operational>

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.3 for the QFX Series.
Display routing instance information.
none(Same as brief) Display standard information about all routing instances.
brief | detail | summary(Optional) Display the specified level of output. If you do not

specify a level of output, the system defaults to brief. (These options are not available
with the operational keyword.)
instance-name(Optional) Display information for all routing instances whose name

begins with this string (for example, cust1, cust11, and cust111 are all displayed when
you run the show route instance cust1 command).
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

operational(Optional) Display operational routing instances.

Required Privilege
Level
Related
Documentation

List of Sample Output

view

Example: Transporting IPv6 Traffic Across IPv4 Using Filter-Based Tunneling

Example: Configuring the Helper Capability Mode for OSPFv3 Graceful Restart

show route instance on page 2045

show route instance detail (Graceful Restart Complete) on page 2045
show route instance detail (Graceful Restart Incomplete) on page 2047
show route instance detail (VPLS Routing Instance) on page 2048
show route instance operational on page 2049
show route instance summary on page 2049

Copyright 2014, Juniper Networks, Inc.

2043

Interfaces Fundamentals for Routing Devices

Output Fields

Table 205 on page 2044 lists the output fields for the show route instance command. Output
fields are listed in the approximate order in which they appear.

Table 205: show route instance Output Fields

Field Name

Field Description

Level of Output

Instance or instance-name

Name of the routing instance.

All levels

Operational Routing Instances

(operational keyword only) Names of all operational routing

instances.

Type

Type of routing instance: forwarding, l2vpn, no-forwarding, vpls,

virtual-router, or vrf.

All levels

State

State of the routing instance: active or inactive.

brief detail none

Interfaces

Name of interfaces belonging to this routing instance.

brief detail none

Restart State

Status of graceful restart for this instance: Pending or Complete.

detail

Path selection timeout

Maximum amount of time, in seconds, remaining until graceful

restart is declared complete. The default is 300.

detail

Tables

Tables (and number of routes) associated with this routing instance.

brief detail none

Route-distinguisher

Unique route distinguisher associated with this routing instance.

detail

Vrf-import

VPN routing and forwarding instance import policy name.

detail

Vrf-export

VPN routing and forwarding instance export policy name.

detail

Vrf-import-target

VPN routing and forwarding instance import target community

name.

detail

Vrf-export-target

VPN routing and forwarding instance export target community name.

detail

Vrf-edge-protection-id

Context identifier configured for edge-protection.

detail

Fast-reroute-priority

Fast reroute priority setting for a VPLS routing instance: high, medium,
or low. The default is low.

detail

Restart State

Restart state:

detail

Pending:protocol-nameList of protocols that have not yet

completed graceful restart for this routing table.

CompleteAll protocols have restarted for this routing table.

Primary rib

Primary table for this routing instance.

brief none summary

Active/holddown/hidden

Number of active, hold-down, and hidden routes.

All levels

2044

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Sample Output
show route instance
user@host> show route instance
Instance
Type
Primary RIB
master
forwarding
inet.0
iso.0
mpls.0
inet6.0
l2circuit.0
__juniper_private1__ forwarding
__juniper_private1__.inet.0
__juniper_private1__.inet6.0

Active/holddown/hidden
16/0/1
1/0/0
0/0/0
2/0/0
0/0/0
12/0/0
1/0/0

show route instance detail (Graceful Restart Complete)

user@host> show route instance detail
master:
Router ID: 10.255.14.176
Type: forwarding
State: Active
Restart State: Complete Path selection timeout: 300
Tables:
inet.0
: 17 routes (15 active, 0 holddown,
Restart Complete
inet.3
: 2 routes (2 active, 0 holddown, 0
Restart Complete
iso.0
: 1 routes (1 active, 0 holddown, 0
Restart Complete
mpls.0
: 19 routes (19 active, 0 holddown,
Restart Complete
bgp.l3vpn.0
: 10 routes (10 active, 0 holddown,
Restart Complete
inet6.0
: 2 routes (2 active, 0 holddown, 0
Restart Complete
bgp.l2vpn.0
: 1 routes (1 active, 0 holddown, 0
Restart Complete
BGP-INET:
Router ID: 10.69.103.1
Type: vrf
State: Active
Restart State: Complete Path selection timeout: 300
Interfaces:
t3-0/0/0.103
Route-distinguisher: 10.255.14.176:103
Vrf-import: [ BGP-INET-import ]
Vrf-export: [ BGP-INET-export ]
Tables:
BGP-INET.inet.0
: 4 routes (4 active, 0 holddown, 0
Restart Complete
BGP-L:
Router ID: 10.69.104.1
Type: vrf
State: Active
Restart State: Complete Path selection timeout: 300
Interfaces:
t3-0/0/0.104
Route-distinguisher: 10.255.14.176:104
Vrf-import: [ BGP-L-import ]
Vrf-export: [ BGP-L-export ]
Tables:

Copyright 2014, Juniper Networks, Inc.

1 hidden)
hidden)
hidden)
0 hidden)
0 hidden)
hidden)
hidden)

hidden)

2045

Interfaces Fundamentals for Routing Devices

BGP-L.inet.0
: 4 routes (4
Restart Complete
BGP-L.mpls.0
: 3 routes (3
Restart Complete
L2VPN:
Router ID: 0.0.0.0
Type: l2vpn
State: Active
Restart State: Complete Path selection
Interfaces:
t3-0/0/0.512
Route-distinguisher: 10.255.14.176:512
Vrf-import: [ L2VPN-import ]
Vrf-export: [ L2VPN-export ]
Tables:
L2VPN.l2vpn.0
: 2 routes (2
Restart Complete
LDP:
Router ID: 10.69.105.1
Type: vrf
State: Active
Restart State: Complete Path selection
Interfaces:
t3-0/0/0.105
Route-distinguisher: 10.255.14.176:105
Vrf-import: [ LDP-import ]
Vrf-export: [ LDP-export ]
Tables:
LDP.inet.0
: 5 routes (4
Restart Complete
OSPF:
Router ID: 10.69.101.1
Type: vrf
State: Active
Restart State: Complete Path selection
Interfaces:
t3-0/0/0.101
Route-distinguisher: 10.255.14.176:101
Vrf-import: [ OSPF-import ]
Vrf-export: [ OSPF-export ]
Vrf-import-target: [ target:11111
Tables:
OSPF.inet.0
: 8 routes (7
Restart Complete
RIP:
Router ID: 10.69.102.1
Type: vrf
State: Active
Restart State: Complete Path selection
Interfaces:
t3-0/0/0.102
Route-distinguisher: 10.255.14.176:102
Vrf-import: [ RIP-import ]
Vrf-export: [ RIP-export ]
Tables:
RIP.inet.0
: 6 routes (6
Restart Complete
STATIC:
Router ID: 10.69.100.1
Type: vrf
State: Active
Restart State: Complete Path selection
Interfaces:
t3-0/0/0.100
Route-distinguisher: 10.255.14.176:100
Vrf-import: [ STATIC-import ]

2046

active, 0 holddown, 0 hidden)

active, 0 holddown, 0 hidden)

timeout: 300

active, 0 holddown, 0 hidden)

timeout: 300

active, 0 holddown, 0 hidden)

timeout: 300

active, 0 holddown, 0 hidden)

timeout: 300

active, 0 holddown, 0 hidden)

timeout: 300

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Vrf-export: [ STATIC-export ]
Tables:
STATIC.inet.0
: 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete

show route instance detail (Graceful Restart Incomplete)

user@host> show route instance detail
master:
Router ID: 10.255.14.176
Type: forwarding
State: Active
Restart State: Pending Path selection timeout: 300
Tables:
inet.0
: 17 routes (15 active, 1 holddown,
Restart Pending: OSPF LDP
inet.3
: 2 routes (2 active, 0 holddown, 0
Restart Pending: OSPF LDP
iso.0
: 1 routes (1 active, 0 holddown, 0
Restart Complete
mpls.0
: 23 routes (23 active, 0 holddown,
Restart Pending: LDP VPN
bgp.l3vpn.0
: 10 routes (10 active, 0 holddown,
Restart Pending: BGP VPN
inet6.0
: 2 routes (2 active, 0 holddown, 0
Restart Complete
bgp.l2vpn.0
: 1 routes (1 active, 0 holddown, 0
Restart Pending: BGP VPN
BGP-INET:
Router ID: 10.69.103.1
Type: vrf
State: Active
Restart State: Pending Path selection timeout: 300
Interfaces:
t3-0/0/0.103
Route-distinguisher: 10.255.14.176:103
Vrf-import: [ BGP-INET-import ]
Vrf-export: [ BGP-INET-export ]
Tables:
BGP-INET.inet.0
: 6 routes (5 active, 0 holddown, 0
Restart Pending: VPN
BGP-L:
Router ID: 10.69.104.1
Type: vrf
State: Active
Restart State: Pending Path selection timeout: 300
Interfaces:
t3-0/0/0.104
Route-distinguisher: 10.255.14.176:104
Vrf-import: [ BGP-L-import ]
Vrf-export: [ BGP-L-export ]
Tables:
BGP-L.inet.0
: 6 routes (5 active, 0 holddown, 0
Restart Pending: VPN
BGP-L.mpls.0
: 2 routes (2 active, 0 holddown, 0
Restart Pending: VPN
L2VPN:
Router ID: 0.0.0.0
Type: l2vpn
State: Active
Restart State: Pending Path selection timeout: 300
Interfaces:
t3-0/0/0.512
Route-distinguisher: 10.255.14.176:512
Vrf-import: [ L2VPN-import ]

Copyright 2014, Juniper Networks, Inc.

1 hidden)
hidden)
hidden)
0 hidden)
0 hidden)
hidden)
hidden)

hidden)

hidden)
hidden)

2047

Interfaces Fundamentals for Routing Devices

Vrf-export: [ L2VPN-export ]
Tables:
L2VPN.l2vpn.0
: 2 routes (2
Restart Pending: VPN L2VPN
LDP:
Router ID: 10.69.105.1
Type: vrf
State: Active
Restart State: Pending Path selection
Interfaces:
t3-0/0/0.105
Route-distinguisher: 10.255.14.176:105
Vrf-import: [ LDP-import ]
Vrf-export: [ LDP-export ]
Tables:
LDP.inet.0
: 5 routes (4
Restart Pending: OSPF LDP VPN
OSPF:
Router ID: 10.69.101.1
Type: vrf
State: Active
Restart State: Pending Path selection
Interfaces:
t3-0/0/0.101
Route-distinguisher: 10.255.14.176:101
Vrf-import: [ OSPF-import ]
Vrf-export: [ OSPF-export ]
Tables:
OSPF.inet.0
: 8 routes (7
Restart Pending: OSPF VPN
RIP:
Router ID: 10.69.102.1
Type: vrf
State: Active
Restart State: Pending Path selection
Interfaces:
t3-0/0/0.102
Route-distinguisher: 10.255.14.176:102
Vrf-import: [ RIP-import ]
Vrf-export: [ RIP-export ]
Tables:
RIP.inet.0
: 8 routes (6
Restart Pending: RIP VPN
STATIC:
Router ID: 10.69.100.1
Type: vrf
State: Active
Restart State: Pending Path selection
Interfaces:
t3-0/0/0.100
Route-distinguisher: 10.255.14.176:100
Vrf-import: [ STATIC-import ]
Vrf-export: [ STATIC-export ]
Tables:
STATIC.inet.0
: 4 routes (4
Restart Pending: VPN

active, 0 holddown, 0 hidden)

timeout: 300

active, 1 holddown, 0 hidden)

timeout: 300

active, 1 holddown, 0 hidden)

timeout: 300

active, 2 holddown, 0 hidden)

timeout: 300

active, 0 holddown, 0 hidden)

show route instance detail (VPLS Routing Instance)

user@host> show route instance detail test-vpls
test-vpls:
Router ID: 0.0.0.0
Type: vpls
State: Active
Interfaces:
lsi.1048833

2048

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

lsi.1048832
fe-0/1/0.513
Route-distinguisher: 10.255.37.65:1
Vrf-import: [ __vrf-import-test-vpls-internal__ ]
Vrf-export: [ __vrf-export-test-vpls-internal__ ]
Vrf-import-target: [ target:300:1 ]
Vrf-export-target: [ target:300:1 ]
Vrf-edge-protection-id: 166.1.3.1 Fast-reroute-priority: high
Tables:
test-vpls.l2vpn.0
: 3 routes (3 active, 0 holddown, 0 hidden)

show route instance operational

user@host> show route instance operational
Operational Routing Instances:
master
default

show route instance summary

user@host> show route instance summary
Instance
Type
Primary rib
master
forwarding
inet.0
iso.0
mpls.0
l3vpn.0
inet6.0
l2vpn.0
l2circuit.0
BGP-INET
vrf
BGP-INET.inet.0
BGP-INET.iso.0
BGP-INET.inet6.0
BGP-L
vrf
BGP-L.inet.0
BGP-L.iso.0
BGP-L.mpls.0
BGP-L.inet6.0
L2VPN
l2vpn
L2VPN.inet.0
L2VPN.iso.0
L2VPN.inet6.0
L2VPN.l2vpn.0
LDP
vrf
LDP.inet.0
LDP.iso.0
LDP.mpls.0
LDP.inet6.0
LDP.l2circuit.0
OSPF
vrf
OSPF.inet.0
OSPF.iso.0
OSPF.inet6.0
RIP
vrf
RIP.inet.0
RIP.iso.0
RIP.inet6.0
STATIC
vrf
STATIC.inet.0

Copyright 2014, Juniper Networks, Inc.

Active/holddown/hidden
15/0/1
1/0/0
35/0/0
0/0/0
2/0/0
0/0/0
0/0/0
5/0/0
0/0/0
0/0/0
5/0/0
0/0/0
4/0/0
0/0/0
0/0/0
0/0/0
0/0/0
2/0/0
4/0/0
0/0/0
0/0/0
0/0/0
0/0/0
7/0/0
0/0/0
0/0/0
6/0/0
0/0/0
0/0/0
4/0/0

2049

Interfaces Fundamentals for Routing Devices

STATIC.iso.0
STATIC.inet6.0

2050

0/0/0
0/0/0

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route label

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Options

Syntax on page 2051

Syntax (EX Series Switches) on page 2051
show route label label
<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>
show route label label
<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.5 for EX Series switches.
Display the routes based on a specified Multiprotocol Label Switching (MPLS) label
value.
labelValue of the MPLS label.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Example: Configuring Multipoint LDP In-Band Signaling for Point-to-Multipoint LSPs

show route label terse on page 2051

show route label on page 2052
show route label detail on page 2052
show route label detail (Multipoint LDP Inband Signaling for Point-to-Multipoint
LSPs) on page 2052
show route label detail (Multipoint LDP with Multicast-Only Fast Reroute) on page 2053
show route label extensive on page 2053
For information about output fields, see the output field table for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route label terse
user@host> show route label 100016 terse
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both

Copyright 2014, Juniper Networks, Inc.

2051

Interfaces Fundamentals for Routing Devices

A Destination
* 100016

P Prf
V 170

Metric 1

Metric 2

Next hop
>10.12.80.1

AS path

show route label

user@host> show route label 100016
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
100016
*[VPN/170] 03:25:41
> to 10.12.80.1 via ge-6/3/2.0, Pop

show route label detail

user@host> show route label 100016 detail
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
100016 (1 entry, 1 announced)
*VPN
Preference: 170
Next-hop reference count: 2
Source: 10.12.80.1
Next hop: 10.12.80.1 via ge-6/3/2.0, selected
Label operation: Pop
State: <Active Int Ext>
Local AS:
1
Age: 3:23:31
Task: BGP.0.0.0.0+179
Announcement bits (1): 0-KRT
AS path: 100 I
Ref Cnt: 2

show route label detail (Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show route label 299872 detail
mpls.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
299872 (1 entry, 1 announced)
*LDP
Preference: 9
Next hop type: Flood
Next-hop reference count: 3
Address: 0x9097d90
Next hop: via vt-0/1/0.1
Next-hop index: 661
Label operation: Pop
Address: 0x9172130
Next hop: via so-0/0/3.0
Next-hop index: 654
Label operation: Swap 299872
State: **Active Int>
Local AS: 1001
Age: 8:20
Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
FECs bound to route: P2MP root-addr 10.255.72.166, grp 232.1.1.1,
src 192.168.142.2

2052

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route label detail (Multipoint LDP with Multicast-Only Fast Reroute)
user@host> show route label 301568 detail
mpls.0: 18 destinations, 18 routes (18 active, 0 holddown, 0 hidden)
301568 (1 entry, 1 announced)
*LDP
Preference: 9
Next hop type: Flood
Address: 0x2735208
Next-hop reference count: 3
Next hop type: Router, Next hop index: 1397
Address: 0x2735d2c
Next-hop reference count: 3
Next hop: 1.3.8.2 via ge-1/2/22.0
Label operation: Pop
Load balance label: None;
Next hop type: Router, Next hop index: 1395
Address: 0x2736290
Next-hop reference count: 3
Next hop: 1.3.4.2 via ge-1/2/18.0
Label operation: Pop
Load balance label: None;
State: <Active Int AckRequest MulticastRPF>
Local AS:
10
Age: 54:05
Metric: 1
Validation State: unverified
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
FECs bound to route: P2MP root-addr 1.1.1.1, grp: 232.1.1.1, src:
192.168.219.11
Primary Upstream : 1.1.1.3:0--1.1.1.2:0
RPF Nexthops :
ge-1/2/15.0, 1.2.94.1, Label: 301568, weight: 0x1
ge-1/2/14.0, 1.2.3.1, Label: 301568, weight: 0x1
Backup Upstream : 1.1.1.3:0--1.1.1.6:0
RPF Nexthops :
ge-1/2/20.0, 1.2.96.1, Label: 301584, weight: 0xfffe
ge-1/2/19.0, 1.3.6.1, Label: 301584, weight: 0xfffe

show route label extensive

The output for the show route label extensive command is identical to that of the show
route label detail command. For sample output, see show route label detail on page 2052.

Copyright 2014, Juniper Networks, Inc.

2053

Interfaces Fundamentals for Routing Devices

show route label-switched-path

List of Syntax

Syntax on page 2054

Syntax (EX Series Switches) on page 2054

Syntax

show route label-switched-path path-name

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)
Release Information

Description
Options

show route label-switched-path path-name

<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.5 for EX Series switches.
Display the routes used in an MPLS label-switched path (LSP).
brief | detail | extensive | terse(Optional) Display the specified level of output.
path-nameLSP tunnel name.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output
Output Fields

view

show route label-switched-path on page 2054

For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route label-switched-path
user@host> show route label-switched-path sf-to-ny
inet.0: 29 destinations, 29 routes (29 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.1/32
3.3.3.3/32

[MPLS/7] 00:00:06, metric 0

> to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny
*[MPLS/7] 00:00:06, metric 0
> to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny

inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
2.2.2.2/32
4.4.4.4/32

2054

*[MPLS/7] 00:00:06, metric 0

> to 111.222.1.9 via s0-0/0/0,
*[MPLS/7] 00:00:06, metric 0
to 111.222.1.9 via s0-0/0/0,
> to 111.222.1.9 via s0-0/0/0,
to 111.222.1.9 via s0-0/0/0,

label-switched-path sf-to-ny
label-switched-path abc
label-switched-path xyz
label-switched-path sf-to-ny

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

111.222.1.9/32

[MPLS/7] 00:00:06, metric 0

> to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
mpls.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

Copyright 2014, Juniper Networks, Inc.

2055

Interfaces Fundamentals for Routing Devices

show route localization

Syntax
Release Information

Description
Options
Required Privilege
Level
Related
Documentation
Output Fields

show route localization

Command introduced in Junos OS Release 11.4 for T-Series routers.

Command introduced in Junos OS Release 12.3 for MX Series routers.
(T320, T640, and T1600 routers only) Display route localization details.
detailDisplay detailed output.

view

Example: Configuring Packet Forwarding Engine FIB Localization

Table 206 on page 2056 lists the output fields for the show route localization command.
Output fields are listed in the approximate order in which they appear.

Table 206: show route localization Output Fields

Field Name

Field Description

FIB-local

FPCs configured as FIB-local.

FIB-remote

FPCs configured as FIB-remote.

Normal

FPCs neither configured as FIB-local or FIB-remote.

Protocols

IPv4 (inet) or IPv6 (inet6) traffic configured for route localization.

Sample Output
user@R0> show route localization
FIB localization ready FPCs (and FIB-local Forwarding Engine addresses)
FIB-local: FPC2(4,5)
FIB-remote: FPC0, FPC1
Normal:
FPC3, FPC4, FPC5, FPC6, FPC7
user@R0> show route localization detail
FIB localization ready FPCs (and FIB-local Forwarding Engine addresses)
FIB-local: FPC2(4,5)
FIB-remote: FPC0, FPC1
Normal:
FPC3, FPC4, FPC5, FPC6, FPC7
FIB localization configuration
Protocols: inet, inet6
FIB-local: FPC2
FIB-remote: FPC0, FPC1
Forwarding Engine addresses
FPC0: 1
FPC1: 2
FPC2: 4, 5

2056

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

FPC3:
FPC4:
FPC5:
FPC6:
FPC7:

Copyright 2014, Juniper Networks, Inc.

6
8
11
13
15

2057

Interfaces Fundamentals for Routing Devices

show route martians

List of Syntax

Syntax on page 2058

Syntax (EX Series Switches) on page 2058

Syntax

show route martians

<logical-system (all | logical-system-name)>
<table routing-table-name>

Syntax (EX Series

Switches)
Release Information

Description
Options

show route martians

<table routing-table-name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the martian (invalid and ignored) entries associated with each routing table.
noneDisplay standard information about route martians for all routing tables.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

table routing-table-name(Optional) Display information about route martians for all

routing tables whose name begins with this string (for example, inet.0 and inet6.0
are both displayed when you run the show route martians table inet command).
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

Example: Configuring Martian Addresses

show route martians on page 2059

Table 207 on page 2058 lists the output fields for the show route martians command. Output
fields are listed in the approximate order in which they appear

Table 207: show route martians Output Fields

2058

Field Name

Field Description

table-name

Name of the route table in which the route martians reside.

destination-prefix

Route destination.

match value

Route match parameter.

status

Status of the route: allowed or disallowed.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Sample Output
show route martians
user@host> show route martians
inet.0:
0.0.0.0/0 exact -- allowed
0.0.0.0/8 orlonger -- disallowed
127.0.0.0/8 orlonger -- disallowed
192.0.0.0/24 orlonger -- disallowed
240.0.0.0/4 orlonger -- disallowed
224.0.0.0/4 exact -- disallowed
224.0.0.0/24 exact -- disallowed
inet.1:
0.0.0.0/0 exact -- allowed
0.0.0.0/8 orlonger -- disallowed
127.0.0.0/8 orlonger -- disallowed
192.0.0.0/24 orlonger -- disallowed
240.0.0.0/4 orlonger -- disallowed
inet.2:
0.0.0.0/0 exact -- allowed
0.0.0.0/8 orlonger -- disallowed
127.0.0.0/8 orlonger -- disallowed
192.0.0.0/24 orlonger -- disallowed
240.0.0.0/4 orlonger -- disallowed
224.0.0.0/4 exact -- disallowed
224.0.0.0/24 exact -- disallowed
inet.3:
0.0.0.0/0 exact -- allowed
0.0.0.0/8 orlonger -- disallowed
127.0.0.0/8 orlonger -- disallowed
192.0.0.0/24 orlonger -- disallowed
240.0.0.0/4 orlonger -- disallowed
224.0.0.0/4 exact -- disallowed
224.0.0.0/24 exact -- disallowed
...
inet6.0:
::1/128 exact -- disallowed
ff00::/8 exact -- disallowed
ff02::/16 exact -- disallowed
inet6.1:
::1/128 exact -- disallowed
inet6.2:
::1/128 exact -- disallowed
ff00::/8 exact -- disallowed
ff02::/16 exact -- disallowed
inet6.3:
::1/128 exact -- disallowed
ff00::/8 exact -- disallowed
ff02::/16 exact -- disallowed
...

Copyright 2014, Juniper Networks, Inc.

2059

Interfaces Fundamentals for Routing Devices

show route match-prefix

Syntax
Release Information
Description

Options

show route match-prefix match-prefix;

Command introduced in Junos OS Release 11.4.

Allows you to search for routes using regular expressions based on the extended (modern)
regular expressions as defined in POSIX 1003.2.
match-prefixRegular expression to match formatted prefix.

Additional Information
Required Privilege
Level
Related
Documentation
List of Sample Output

Output Fields

view

Regular Expressions for Allowing and Denying Junos OS Operational Mode Commands

show route match-prefix *:10.255.2.200:6:* (Show all routes matching route distributor
10.255.2.200:6) on page 2060
show route match-prefix 7* (Show all mvpn type-7 routes) on page 2060
show route match-prefix *:224.* (Show all routes matching group 224/4) on page 2060
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route match-prefix *:10.255.2.200:6:* (Show all routes matching route distributor 10.255.2.200:6)
user@host> show route match-prefix *:10.255.2.200:6:*

show route match-prefix 7* (Show all mvpn type-7 routes)

user@host> show route table blue.mvpn.0 match-prefix 7*
Paste
router command output here

show route match-prefix *:224.* (Show all routes matching group 224/4)
user@host> show route match-prefix *:224.*

2060

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route next-hop

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Options

Syntax on page 2061

Syntax (EX Series Switches) on page 2061
show route next-hop next-hop
<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>
show route next-hop next-hop
<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the entries in the routing table that are being sent to the specified next-hop
address.
brief | detail | extensive | terse(Optional) Display the specified level of ouput.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

next-hopNext-hop address.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route next-hop on page 2061

show route next-hop detail on page 2062
show route next-hop extensive on page 2064
show route next-hop terse on page 2065
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route next-hop
user@host> show route next-hop 192.168.71.254
inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.10.0.0/16
10.209.0.0/16
172.16.0.0/12
192.168.0.0/16

Copyright 2014, Juniper Networks, Inc.

*[Static/5] 06:26:25
> to 192.168.71.254 via fxp0.0
*[Static/5] 06:26:25
> to 192.168.71.254 via fxp0.0
*[Static/5] 06:26:25
> to 192.168.71.254 via fxp0.0
*[Static/5] 06:26:25

2061

Interfaces Fundamentals for Routing Devices

192.168.102.0/23
207.17.136.0/24
207.17.136.192/32

> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254

via fxp0.0
via fxp0.0
via fxp0.0
via fxp0.0

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

red.inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

show route next-hop detail

user@host> show route next-hop 192.168.71.254 detail
inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden)
Restart Complete
10.10.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 36
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 36
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2
AS path: I
172.16.0.0/12 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 36
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2

2062

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

AS path: I
192.168.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 36
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2
AS path: I
192.168.102.0/23 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 36
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2
AS path: I
207.17.136.0/24 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 36
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2
AS path: I
207.17.136.192/32 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 36
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2
AS path: I
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
red.inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Copyright 2014, Juniper Networks, Inc.

2063

Interfaces Fundamentals for Routing Devices

show route next-hop extensive

user@host> show route next-hop 192.168.71.254 extensive
inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.10.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:02:28
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.209.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:02:28
Task: RT
Announcement bits (1): 0-KRT
AS path: I
172.16.0.0/12 (1 entry, 1 announced)
TSI:
KRT in-kernel 172.16.0.0/12 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:02:28
Task: RT
Announcement bits (1): 0-KRT
AS path: I
192.168.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 192.168.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:02:28
Task: RT
Announcement bits (1): 0-KRT
AS path: I
192.168.102.0/23 (1 entry, 1 announced)
TSI:
KRT in-kernel 192.168.102.0/23 -> {192.168.71.254}
*Static Preference: 5

2064

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Next-hop reference count: 22

Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:02:28
Task: RT
Announcement bits (1): 0-KRT
AS path: I
207.17.136.0/24 (1 entry, 1 announced)
TSI:
KRT in-kernel 207.17.136.0/24 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:02:28
Task: RT
Announcement bits (1): 0-KRT
AS path: I
207.17.136.192/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 207.17.136.192/32 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:02:28
Task: RT
Announcement bits (1): 0-KRT
AS path: I
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
green.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
red.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

show route next-hop terse

user@host> show route next-hop 192.168.71.254 terse
inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
A
*
*
*

Destination
10.10.0.0/16
10.209.0.0/16
172.16.0.0/12

Copyright 2014, Juniper Networks, Inc.

P Prf
S
5
S
5
S
5

Metric 1

Metric 2

Next hop
>192.168.71.254
>192.168.71.254
>192.168.71.254

AS path

2065

Interfaces Fundamentals for Routing Devices

*
*
*
*

192.168.0.0/16
192.168.102.0/23
207.17.136.0/24
207.17.136.192/32

S
S
S
S

5
5
5
5

>192.168.71.254
>192.168.71.254
>192.168.71.254
>192.168.71.254

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

red.inet.0: 4 destinations, 5 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

2066

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route no-community

List of Syntax

Syntax on page 2067

Syntax (EX Series Switches) on page 2067

Syntax

show route no-community

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)
Release Information

Description
Options

show route no-community

<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the route entries in each routing table that are not associated with any community.
none(Same as brief) Display the route entries in each routing table that are not

associated with any community.

brief | detail | extensive | terse(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route no-community on page 2067

show route no-community detail on page 2068
show route no-community extensive on page 2068
show route no-community terse on page 2069
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route no-community
user@host> show route no-community
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
10.10.0.0/16
10.209.0.0/16
10.255.71.52/32
10.255.71.63/32
10.255.71.64/32

Copyright 2014, Juniper Networks, Inc.

*[Static/5] 00:36:27
> to 192.168.71.254 via fxp0.0
*[Static/5] 00:36:27
> to 192.168.71.254 via fxp0.0
*[Direct/0] 00:36:27
> via lo0.0
*[OSPF/10] 00:04:39, metric 1
> to 35.1.1.2 via ge-3/1/0.0
*[OSPF/10] 00:00:08, metric 2

2067

Interfaces Fundamentals for Routing Devices

10.255.71.240/32

10.255.71.241/32
10.255.71.242/32
12.1.1.0/24
14.1.1.0/24

16.1.1.0/24

> to 35.1.1.2 via ge-3/1/0.0

*[OSPF/10] 00:05:04, metric 2
via so-0/1/2.0
> via so-0/3/2.0
*[OSPF/10] 00:05:14, metric 1
> via so-0/1/2.0
*[OSPF/10] 00:05:19, metric 1
> via so-0/3/2.0
*[OSPF/10] 00:05:14, metric 2
> via so-0/3/2.0
*[OSPF/10] 00:00:08, metric 3
> to 35.1.1.2 via ge-3/1/0.0
via so-0/1/2.0
via so-0/3/2.0
*[OSPF/10] 00:05:14, metric 2
> via so-0/1/2.0

.....

show route no-community detail

user@host> show route no-community detail
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Age: 38:08
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Age: 38:08
Task: RT
Announcement bits (1): 0-KRT
AS path: I
....

show route no-community extensive

user@host> show route no-community extensive
inet.0: 18 destinations, 18 routes (17 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.10.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:03:33
Task: RT
Announcement bits (1): 0-KRT
AS path: I

2068

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

10.209.0.0/16 (1 entry, 1 announced)

TSI:
KRT in-kernel 10.209.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 2:03:33
Task: RT
Announcement bits (1): 0-KRT
AS path: I

show route no-community terse

user@host> show route no-community terse
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A
*
*
*
*
*
*

Destination
10.10.0.0/16
10.209.0.0/16
10.255.71.52/32
10.255.71.63/32
10.255.71.64/32
10.255.71.240/32

P Prf
S
5
S
5
D
0
O 10
O 10
O 10

*
*
*
*

10.255.71.241/32
10.255.71.242/32
12.1.1.0/24
14.1.1.0/24

O
O
O
O

10
10
10
10

1
1
2
3

10

* 16.1.1.0/24
...

Copyright 2014, Juniper Networks, Inc.

Metric 1

1
2
2

Metric 2

Next hop
>192.168.71.254
>192.168.71.254
>lo0.0
>35.1.1.2
>35.1.1.2
so-0/1/2.0
>so-0/3/2.0
>so-0/1/2.0
>so-0/3/2.0
>so-0/3/2.0
>35.1.1.2
so-0/1/2.0
so-0/3/2.0
>so-0/1/2.0

AS path

2069

Interfaces Fundamentals for Routing Devices

show route output

List of Syntax

Syntax on page 2070

Syntax (EX Series Switches) on page 2070

Syntax

show route output (address ip-address | interface interface-name)

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)

show route output (address ip-address | interface interface-name)

<brief | detail | extensive | terse>

Release Information

Description

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the entries in the routing table learned through static routes and interior gateway
protocols that are to be sent out the interface with either the specified IP address or
specified name.
To view routes advertised to a neighbor or received from a neighbor for the BGP protocol,
use the show route advertising-protocol bgp and show route receive-protocol bgp
commands instead.

Options

address ip-addressDisplay entries in the routing table that are to be sent out the interface

with the specified IP address.

brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

interface interface-nameDisplay entries in the routing table that are to be sent out the

interface with the specified name.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

2070

view

show route output address on page 2071

show route output address detail on page 2071
show route output address extensive on page 2072
show route output address terse on page 2072
show route output interface on page 2072
show route output interface detail on page 2073
show route output interface extensive on page 2073
show route output interface terse on page 2073
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Sample Output
show route output address
user@host> show route output address 36.1.1.1/24
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
36.1.1.0/24

*[Direct/0] 00:19:56
> via so-0/1/2.0
[OSPF/10] 00:19:55, metric 1
> via so-0/1/2.0

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

show route output address detail

user@host> show route output address 36.1.1.1 detail
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
36.1.1.0/24 (2 entries, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via so-0/1/2.0, selected
State: <Active Int>
Age: 23:00
Task: IF
AS path: I
OSPF
Preference: 10
Next-hop reference count: 1
Next hop: via so-0/1/2.0, selected
State: <Int>
Inactive reason: Route Preference
Age: 22:59
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

Copyright 2014, Juniper Networks, Inc.

2071

Interfaces Fundamentals for Routing Devices

show route output address extensive

The output for the show route output address extensive command is identical to that of
the show route output address detail command. For sample output, see show route
output address detail on page 2071.
show route output address terse
user@host> show route output address 36.1.1.1 terse
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A Destination
* 36.1.1.0/24

P Prf
D
0
O 10

Metric 1

Metric 2

Next hop
>so-0/1/2.0
>so-0/1/2.0

AS path

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

show route output interface

user@host> show route output interface so-0/1/2.0
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
10.255.71.240/32

10.255.71.241/32
14.1.1.0/24

16.1.1.0/24
36.1.1.0/24

*[OSPF/10] 00:13:00, metric 2

via so-0/1/2.0
> via so-0/3/2.0
*[OSPF/10] 00:13:10, metric 1
> via so-0/1/2.0
*[OSPF/10] 00:05:11, metric 3
to 35.1.1.2 via ge-3/1/0.0
> via so-0/1/2.0
via so-0/3/2.0
*[OSPF/10] 00:13:10, metric 2
> via so-0/1/2.0
*[Direct/0] 00:13:21
> via so-0/1/2.0
[OSPF/10] 00:13:20, metric 1
> via so-0/1/2.0

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

2072

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route output interface detail

user@host> show route output interface so-0/1/2.0 detail
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
10.255.71.240/32 (1 entry, 1 announced)
*OSPF
Preference: 10
Next-hop reference count: 2
Next hop: via so-0/1/2.0
Next hop: via so-0/3/2.0, selected
State: <Active Int>
Age: 14:52
Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcement bits (1): 0-KRT
AS path: I
10.255.71.241/32 (1 entry, 1 announced)
*OSPF
Preference: 10
Next-hop reference count: 4
Next hop: via so-0/1/2.0, selected
State: <Active Int>
Age: 15:02
Metric: 1
Area: 0.0.0.0
Task: OSPF
Announcement bits (1): 0-KRT
AS path: I
...

show route output interface extensive

The output for the show route output interface extensive command is identical to that of
the show route output interface detail command. For sample output, see show route
output interface detail on page 2073.
show route output interface terse
user@host> show route output interface so-0/1/2.0 terse
inet.0: 28 destinations, 30 routes (27 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A Destination
* 10.255.71.240/32

P Prf
O 10

Metric 1
2

* 10.255.71.241/32
* 14.1.1.0/24

O
O

10
10

1
3

* 16.1.1.0/24
* 36.1.1.0/24

O
D
O

10
0
10

2
1

Metric 2

Next hop
so-0/1/2.0
>so-0/3/2.0
>so-0/1/2.0
35.1.1.2
>so-0/1/2.0
so-0/3/2.0
>so-0/1/2.0
>so-0/1/2.0
>so-0/1/2.0

AS path

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

Copyright 2014, Juniper Networks, Inc.

2073

Interfaces Fundamentals for Routing Devices

private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

2074

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route protocol

List of Syntax

Syntax on page 2075

Syntax (EX Series Switches) on page 2075

Syntax

show route protocol protocol

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)
Release Information

show route protocol protocol

<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
opsf2 and ospf3 options introduced in Junos OS Release 9.2.
opsf2 and ospf3 options introduced in Junos OS Release 9.2 for EX Series switches.
flow option introduced in Junos OS Release 10.0.
flow option introduced in Junos OS Release 10.0 for EX Series switches.

Description

Display the route entries in the routing table that were learned from a particular protocol.

Options

brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

protocolProtocol from which the route was learned:

accessAccess route for use by DHCP application

access-internalAccess-internal route for use by DHCP application

aggregateLocally generated aggregate route

arpRoute learned through the Address Resolution Protocol

atmvpnAsynchronous Transfer Mode virtual private network

bgpBorder Gateway Protocol

cccCircuit cross-connect

directDirectly connected route

dvmrpDistance Vector Multicast Routing Protocol

esisEnd System-to-Intermediate System

flowLocally defined flow-specification route

frrPrecomputed protection route or backup route used when a link goes down

isisIntermediate System-to-Intermediate System

ldpLabel Distribution Protocol

l2circuitLayer 2 circuit

Copyright 2014, Juniper Networks, Inc.

2075

Interfaces Fundamentals for Routing Devices

l2vpnLayer 2 virtual private network

localLocal address

mplsMultiprotocol Label Switching

msdpMulticast Source Discovery Protocol

ospfOpen Shortest Path First versions 2 and 3

ospf2Open Shortest Path First versions 2 only

ospf3Open Shortest Path First version 3 only

pimProtocol Independent Multicast

ripRouting Information Protocol

ripngRouting Information Protocol next generation

rsvpResource Reservation Protocol

rtargetLocal route target virtual private network

staticStatically defined route

tunnelDynamic tunnel

vpnVirtual private network

NOTE: EX Series switches run a subset of these protocols. See the switch
CLI for details.

Required Privilege
Level
List of Sample Output

2076

view

show route protocol access on page 2077

show route protocol access-internal extensive on page 2077
show route protocol arp on page 2077
show route protocol bgp on page 2078
show route protocol bgp detail on page 2078
show route protocol bgp extensive on page 2078
show route protocol bgp terse on page 2079
show route protocol direct on page 2079
show route protocol frr on page 2080
show route protocol l2circuit detail on page 2080
show route protocol l2vpn extensive on page 2081
show route protocol ldp on page 2082
show route protocol ldp extensive on page 2082
show route protocol ospf (Layer 3 VPN) on page 2083
show route protocol ospf detail on page 2084
show route protocol rip on page 2084
show route protocol rip detail on page 2084

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route protocol ripng table inet6 on page 2085

show route protocol static detail on page 2085
Output Fields

For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route protocol access
user@host> show route protocol access
inet.0: 30380 destinations, 30382 routes (30379 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
13.160.0.3/32
13.160.0.4/32
13.160.0.5/32

*[Access/13] 00:00:09
> to 13.160.0.2 via fe-0/0/0.0
*[Access/13] 00:00:09
> to 13.160.0.2 via fe-0/0/0.0
*[Access/13] 00:00:09
> to 13.160.0.2 via fe-0/0/0.0

show route protocol access-internal extensive

user@host> show route protocol access-internal 13.160.0.19 extensive
inet.0: 100020 destinations, 100022 routes (100019 active, 0 holddown, 1 hidden)
13.160.0.19/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 13.160.0.19/32 -> {13.160.0.2}
*Access-internal Preference: 12
Next-hop reference count: 200000
Next hop: 13.160.0.2 via fe-0/0/0.0, selected
State: <Active Int>
Age: 36
Task: RPD Unix Domain Server./var/run/rpd_serv.local
Announcement bits (1): 0-KRT
AS path: I

show route protocol arp

user@host> show route protocol arp
inet.0: 43 destinations, 43 routes (42 active, 0 holddown, 1 hidden)
inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
cust1.inet.0: 1033 destinations, 2043 routes (1033 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
20.20.1.3/32
20.20.1.4/32
20.20.1.5/32
20.20.1.6/32
20.20.1.7/32
20.20.1.8/32

Copyright 2014, Juniper Networks, Inc.

[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable

00:04:35, from 20.20.1.1

00:04:35, from 20.20.1.1
00:04:32, from 20.20.1.1
00:04:34, from 20.20.1.1
00:04:35, from 20.20.1.1
00:04:35, from 20.20.1.1

2077

Interfaces Fundamentals for Routing Devices

20.20.1.9/32
20.20.1.10/32
20.20.1.11/32
20.20.1.12/32
20.20.1.13/32

[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable

00:04:35, from 20.20.1.1

00:04:35, from 20.20.1.1
00:04:33, from 20.20.1.1
00:04:33, from 20.20.1.1
00:04:33, from 20.20.1.1

...

show route protocol bgp

user@host> show route protocol bgp 192.168.64.0/21
inet.0: 335832 destinations, 335833 routes (335383 active, 0 holddown, 450 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.64.0/21

*[BGP/170] 6d 10:41:16, localpref 100, from 192.168.69.71

AS path: 10458 14203 2914 4788 4788 I
> to 192.168.167.254 via fxp0.0

show route protocol bgp detail

user@host> show route protocol bgp 66.117.63.0/24 detail
inet.0: 335805 destinations, 335806 routes (335356 active, 0 holddown, 450 hidden)
66.117.63.0/24 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Next hop type: Indirect
Next-hop reference count: 1006436
Source: 192.168.69.71
Next hop type: Router, Next hop index: 324
Next hop: 192.168.167.254 via fxp0.0, selected
Protocol next hop: 192.168.69.71
Indirect next hop: 8e166c0 342
State: <Active Ext>
Local AS:
69 Peer AS: 10458
Age: 6d 10:42:42
Metric2: 0
Task: BGP_10458.192.168.69.71+179
Announcement bits (3): 0-KRT 2-BGP RT Background 3-Resolve tree
1
AS path: 10458 14203 2914 4788 4788 I
Communities: 2914:410 2914:2403 2914:3400
Accepted
Localpref: 100
Router ID: 207.17.136.192

show route protocol bgp extensive

user@host> show route protocol bgp 192.168.64.0/21 extensive
inet.0: 335827 destinations, 335828 routes (335378 active, 0 holddown, 450 hidden)
192.168.64.0/21 (1 entry, 1 announced)
TSI:
KRT in-kernel 1.9.0.0/16 -> {indirect(342)}
Page 0 idx 1 Type 1 val db31a80
Nexthop: Self
AS path: [69] 10458 14203 2914 4788 4788 I
Communities: 2914:410 2914:2403 2914:3400
Path 1.9.0.0 from 192.168.69.71 Vector len 4. Val: 1
*BGP
Preference: 170/-101
Next hop type: Indirect

2078

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Next-hop reference count: 1006502

Source: 192.168.69.71
Next hop type: Router, Next hop index: 324
Next hop: 192.168.167.254 via fxp0.0, selected
Protocol next hop: 192.168.69.71
Indirect next hop: 8e166c0 342
State: <Active Ext>
Local AS:
69 Peer AS: 10458
Age: 6d 10:44:45
Metric2: 0
Task: BGP_10458.192.168.69.71+179
Announcement bits (3): 0-KRT 2-BGP RT Background 3-Resolve tree
1
AS path: 10458 14203 2914 4788 4788 I
Communities: 2914:410 2914:2403 2914:3400
Accepted
Localpref: 100
Router ID: 207.17.136.192
Indirect next hops: 1
Protocol next hop: 192.168.69.71
Indirect next hop: 8e166c0 342
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 192.168.167.254 via fxp0.0
192.168.0.0/16 Originating RIB: inet.0
Node path count: 1
Forwarding nexthops: 1
Nexthop: 192.168.167.254 via fxp0.0

show route protocol bgp terse

user@host> show route protocol bgp 192.168.64.0/21 terse
inet.0: 24 destinations, 32 routes (23 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A Destination
192.168.64.0/21

P Prf
B 170

Metric 1
100

Metric 2

Next hop
>100.1.3.2

AS path
10023 21 I

show route protocol direct

user@host> show route protocol direct
inet.0: 335843 destinations, 335844 routes (335394 active, 0 holddown, 450 hidden)
+ = Active Route, - = Last Active, * = Both
8.8.8.0/24
10.255.165.1/32
30.30.30.0/24
192.168.164.0/22

*[Direct/0] 17w0d
> via fe-1/3/1.0
*[Direct/0] 25w4d
> via lo0.0
*[Direct/0] 17w0d
> via fe-1/3/2.0
*[Direct/0] 25w4d
> via fxp0.0

10:31:49
04:13:18
23:06:26
04:13:20

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
47.0005.80ff.f800.0000.0108.0001.0102.5516.5001/152
*[Direct/0] 25w4d 04:13:21
> via lo0.0

Copyright 2014, Juniper Networks, Inc.

2079

Interfaces Fundamentals for Routing Devices

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
abcd::10:255:165:1/128
*[Direct/0] 25w4d 04:13:21
> via lo0.0
fe80::2a0:a5ff:fe12:ad7/128
*[Direct/0] 25w4d 04:13:21
> via lo0.0

show route protocol frr

user@host> show route protocol frr
inet.0: 43 destinations, 43 routes (42 active, 0 holddown, 1 hidden)
inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
cust1.inet.0: 1033 destinations, 2043 routes (1033 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
20.20.1.3/32

20.20.1.4/32

20.20.1.5/32

20.20.1.6/32

20.20.1.7/32

20.20.1.8/32

20.20.1.9/32

20.20.1.10/32
...

*[FRR/200] 00:05:38, from 20.20.1.1

> to 20.20.1.3 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.4 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:35, from 20.20.1.1
> to 20.20.1.5 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:37, from 20.20.1.1
> to 20.20.1.6 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.7 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.8 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.9 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1

16, Push 299792(top)

16, Push 299792(top)

16, Push 299792(top)

16, Push 299792(top)

16, Push 299792(top)

16, Push 299792(top)

16, Push 299792(top)

show route protocol l2circuit detail

user@host> show route protocol l2circuit detail
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
100000 (1 entry, 1 announced)
*L2CKT Preference: 7
Next hop: via ge-2/0/0.0, selected
Label operation: Pop
Offset: 4
State: <Active Int>
Local AS:
99
Age: 9:52
Task: Common L2 VC
Announcement bits (1): 0-KRT
AS path: I
ge-2/0/0.0 (1 entry, 1 announced)

2080

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

*L2CKT

Preference: 7
Next hop: via so-1/1/2.0 weight 1, selected
Label-switched-path my-lsp
Label operation: Push 100000, Push 100000(top)[0] Offset: -4
Protocol next hop: 10.245.255.63
Push 100000 Offset: -4
Indirect next hop: 86af0c0 298
State: <Active Int>
Local AS:
99
Age: 9:52
Task: Common L2 VC
Announcement bits (2): 0-KRT 1-Common L2 VC
AS path: I

l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced)
*L2CKT Preference: 7
Next hop: via so-1/1/2.0 weight 1, selected
Label-switched-path my-lsp
Label operation: Push 100000[0]
Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296
State: <Active Int>
Local AS:
99
Age: 10:21
Task: l2 circuit
Announcement bits (1): 0-LDP
AS path: I
VC Label 100000, MTU 1500, VLAN ID 512

show route protocol l2vpn extensive

user@host> show route protocol l2vpn extensive
inet.0: 14 destinations, 15 routes (13 active, 0 holddown, 1 hidden)
inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
800001 (1 entry, 1 announced)
TSI:
KRT in-kernel 800001 /36 -> {so-0/0/0.0}
*L2VPN Preference: 7
Next hop: via so-0/0/0.0 weight 49087 balance 97%, selected
Label operation: Pop
Offset: 4
State: <Active Int>
Local AS:
69
Age: 7:48
Task: Common L2 VC
Announcement bits (1): 0-KRT
AS path: I
so-0/0/0.0 (1 entry, 1 announced)
TSI:
KRT in-kernel so-0/0/0.0.0
/16 -> {indirect(288)}
*L2VPN Preference: 7
Next hop: via so-0/0/1.0, selected
Label operation: Push 800000 Offset: -4
Protocol next hop: 10.255.14.220

Copyright 2014, Juniper Networks, Inc.

2081

Interfaces Fundamentals for Routing Devices

Push 800000 Offset: -4

Indirect next hop: 85142a0 288
State: <Active Int>
Local AS:
69
Age: 7:48
Task: Common L2 VC
Announcement bits (2): 0-KRT 1-Common L2 VC
AS path: I
Communities: target:69:1 Layer2-info: encaps:PPP,
control flags:2, mtu: 0

show route protocol ldp

user@host> show route protocol ldp
inet.0: 12 destinations, 13 routes (12 active, 0 holddown, 0 hidden)
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.16.1/32
192.168.17.1/32

*[LDP/9] 1d 23:03:35, metric 1

> via t1-4/0/0.0, Push 100000
*[LDP/9] 1d 23:03:35, metric 1
> via t1-4/0/0.0

private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100064
100064(S=0)
100080

*[LDP/9] 1d 23:03:35, metric 1

> via t1-4/0/0.0, Pop
*[LDP/9] 1d 23:03:35, metric 1
> via t1-4/0/0.0, Pop
*[LDP/9] 1d 23:03:35, metric 1
> via t1-4/0/0.0, Swap 100000

show route protocol ldp extensive

user@host> show route protocol ldp extensive
192.168.16.1/32 (1 entry, 1 announced)
State: <FlashAll>
*LDP
Preference: 9
Next-hop reference count: 3
Next hop: via t1-4/0/0.0, selected
Label operation: Push 100000
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
Announcement bits (2): 0-Resolve tree 1 2-Resolve tree 2
AS path: I
192.168.17.1/32 (1 entry, 1 announced)
State: <FlashAll>
*LDP
Preference: 9
Next-hop reference count: 3
Next hop: via t1-4/0/0.0, selected
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP

2082

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Announcement bits (2): 0-Resolve tree 1 2-Resolve tree 2

AS path: I
private1__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
100064 (1 entry, 1 announced)
TSI:
KRT in-kernel 100064 /36 -> {t1-4/0/0.0}
*LDP
Preference: 9
Next-hop reference count: 2
Next hop: via t1-4/0/0.0, selected
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
Prefixes bound to route: 192.168.17.1/32
100064(S=0) (1 entry, 1 announced)
TSI:
KRT in-kernel 100064 /40 -> {t1-4/0/0.0}
*LDP
Preference: 9
Next-hop reference count: 2
Next hop: via t1-4/0/0.0, selected
Label operation: Pop
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
100080 (1 entry, 1 announced)
TSI:
KRT in-kernel 100080 /36 -> {t1-4/0/0.0}
*LDP
Preference: 9
Next-hop reference count: 2
Next hop: via t1-4/0/0.0, selected
Label operation: Swap 100000
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
Prefixes bound to route: 192.168.16.1/32

show route protocol ospf (Layer 3 VPN)

user@host> show route protocol ospf
inet.0: 40 destinations, 40 routes (39 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
10.39.1.4/30
10.39.1.8/30
10.255.14.171/32

Copyright 2014, Juniper Networks, Inc.

*[OSPF/10] 00:05:18, metric 4

> via t3-3/2/0.0
[OSPF/10] 00:05:18, metric 2
> via t3-3/2/0.0
*[OSPF/10] 00:05:18, metric 4

2083

Interfaces Fundamentals for Routing Devices

10.255.14.179/32
224.0.0.5/32

> via t3-3/2/0.0

*[OSPF/10] 00:05:18, metric 2
> via t3-3/2/0.0
*[OSPF/10] 20:25:55, metric 1

VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
10.39.1.16/30
10.255.14.173/32
224.0.0.5/32

[OSPF/10] 00:05:43, metric 1

> via so-0/2/2.0
*[OSPF/10] 00:05:43, metric 1
> via so-0/2/2.0
*[OSPF/10] 20:26:20, metric 1

show route protocol ospf detail

user@host> show route protocol ospf detail
VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.39.1.16/30 (2 entries, 0 announced)
OSPF
Preference: 10
Nexthop: via so-0/2/2.0, selected
State: <Int>
Inactive reason: Route Preference
Age: 6:25
Metric: 1
Area: 0.0.0.0
Task: VPN-AB-OSPF
AS path: I
Communities: Route-Type:0.0.0.0:1:0
...

show route protocol rip

user@host> show route protocol rip
inet.0: 26 destinations, 27 routes (25 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.255.14.177/32
*[RIP/100] 20:24:34, metric 2
> to 10.39.1.22 via t3-0/2/2.0
224.0.0.9/32
*[RIP/100] 00:03:59, metric 1

show route protocol rip detail

user@host> show route protocol rip detail
inet.0: 26 destinations, 27 routes (25 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.255.14.177/32 (1 entry, 1 announced)
*RIP
Preference: 100
Nexthop: 10.39.1.22 via t3-0/2/2.0, selected
State: <Active Int>
Age: 20:25:02
Metric: 2
Task: VPN-AB-RIPv2
Announcement bits (2): 0-KRT 2-BGP.0.0.0.0+179
AS path: I
Route learned from 10.39.1.22 expires in 96 seconds

2084

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route protocol ripng table inet6

user@host> show route protocol ripng table inet6
inet6.0: 4215 destinations, 4215 routes (4214 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
1111::1/128
1111::2/128
1111::3/128
1111::4/128
1111::5/128
1111::6/128

*[RIPng/100] 02:13:33, metric 2

> to fe80::2a0:a5ff:fe3d:56 via
*[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via
*[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via
*[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via
*[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via
*[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via

t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0

show route protocol static detail

user@host> show route protocol static detail
inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
10.5.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next hop type: Router, Next hop index: 324
Address: 0x9274010
Next-hop reference count: 27
Next hop: 192.168.187.126 via fxp0.0, selected
Session Id: 0x0
State: <Active NoReadvrt Int Ext>
Age: 7w3d 21:24:25
Validation State: unverified
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.10.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next hop type: Router, Next hop index: 324
Address: 0x9274010
Next-hop reference count: 27
Next hop: 192.168.187.126 via fxp0.0, selected
Session Id: 0x0
State: <Active NoReadvrt Int Ext>
Age: 7w3d 21:24:25
Validation State: unverified
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.13.10.0/23 (1 entry, 1 announced)
*Static Preference: 5
Next hop type: Router, Next hop index: 324
Address: 0x9274010
Next-hop reference count: 27
Next hop: 192.168.187.126 via fxp0.0, selected
Session Id: 0x0
State: <Active NoReadvrt Int Ext>
Age: 7w3d 21:24:25
Validation State: unverified

Copyright 2014, Juniper Networks, Inc.

2085

Interfaces Fundamentals for Routing Devices

Task: RT
Announcement bits (1): 0-KRT
AS path: I

2086

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route range

List of Syntax

Syntax on page 2087

Syntax (EX Series Switches) on page 2087

Syntax

show route range

<brief | detail | extensive | terse>
<destination-prefix>
<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)

Release Information

Description
Options

show route range

<brief | detail | extensive | terse>
<destination-prefix>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display routing table entries using a prefix range.
noneDisplay standard information about all routing table entries using a prefix range.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

destination-prefixDestination and prefix mask for the range.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route range on page 2087

show route range destination-prefix on page 2088
show route range detail on page 2088
show route range extensive on page 2089
show route range terse on page 2090
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route range
user@host> show route range
inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
10.10.0.0/16
10.209.0.0/16

Copyright 2014, Juniper Networks, Inc.

*[Static/5] 00:30:01
> to 192.168.71.254 via fxp0.0
*[Static/5] 00:30:01

2087

Interfaces Fundamentals for Routing Devices

10.255.71.14/32
172.16.0.0/12
192.168.0.0/16
192.168.64.0/21
192.168.71.14/32
192.168.102.0/23

> to 192.168.71.254
*[Direct/0] 00:30:01
> via lo0.0
*[Static/5] 00:30:01
> to 192.168.71.254
*[Static/5] 00:30:01
> to 192.168.71.254
*[Direct/0] 00:30:01
> via fxp0.0
*[Local/0] 00:30:01
Local via fxp0.0
*[Static/5] 00:30:01
> to 192.168.71.254

via fxp0.0

via fxp0.0
via fxp0.0

via fxp0.0

...

show route range destination-prefix

user@host> show route range 192.168.0.0/16
inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.0.0/16
192.168.64.0/21
192.168.71.14/32
192.168.102.0/23

*[Static/5] 00:31:14
> to 192.168.71.254 via fxp0.0
*[Direct/0] 00:31:14
> via fxp0.0
*[Local/0] 00:31:14
Local via fxp0.0
*[Static/5] 00:31:14
> to 192.168.71.254 via fxp0.0

show route range detail

user@host> show route range detail
inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Age: 30:05
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Age: 30:05
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.255.71.14/32 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected

2088

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

State: <Active Int>

Age: 30:05
Task: IF
AS path: I
172.16.0.0/12 (1 entry, 1 announced)
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Age: 30:05
Task: RT
Announcement bits (1): 0-KRT
AS path: I
...

show route range extensive

user@host> show route range extensive
inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden)
10.10.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.10.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Age: 30:17
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.209.0.0/16 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Age: 30:17
Task: RT
Announcement bits (1): 0-KRT
AS path: I
10.255.71.14/32 (1 entry, 0 announced)
*Direct Preference: 0
Next hop type: Interface
Next-hop reference count: 1
Next hop: via lo0.0, selected
State: <Active Int>
Age: 30:17
Task: IF
AS path: I
172.16.0.0/12 (1 entry, 1 announced)
TSI:
KRT in-kernel 172.16.0.0/12 -> {192.168.71.254}
*Static Preference: 5
Next-hop reference count: 22

Copyright 2014, Juniper Networks, Inc.

2089

Interfaces Fundamentals for Routing Devices

Next hop: 192.168.71.254 via fxp0.0, selected

State: <Active NoReadvrt Int Ext>
Age: 30:17
Task: RT
Announcement bits (1): 0-KRT
AS path: I
...

show route range terse

user@host> show route range terse
inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
A
*
*
*
*
*
*
*
*
*
*

Destination
10.10.0.0/16
10.209.0.0/16
10.255.71.14/32
172.16.0.0/12
192.168.0.0/16
192.168.64.0/21
192.168.71.14/32
192.168.102.0/23
207.17.136.0/24
207.17.136.192/32

P Prf
S
5
S
5
D
0
S
5
S
5
D
0
L
0
S
5
S
5
S
5

Metric 1

Metric 2

Next hop
>192.168.71.254
>192.168.71.254
>lo0.0
>192.168.71.254
>192.168.71.254
>fxp0.0
Local
>192.168.71.254
>192.168.71.254
>192.168.71.254

AS path

__juniper_private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0

hidden)
+ = Active Route, - = Last Active, * = Both
A Destination
* 10.0.0.0/8
* 10.0.0.4/32

P Prf
D
0
D
0
L
0

Metric 1

Metric 2

Next hop
>fxp2.0
>fxp1.0
Local

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
A Destination
P Prf
Metric 1
Metric 2 Next hop
47.0005.80ff.f800.0000.0108.0001.0102.5507.1014/152
*
D
0
>lo0.0

AS path

AS path

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
A Destination
P Prf
Metric 1
abcd::10:255:71:14/128
*
D
0
fe80::280:42ff:fe11:226f/128
*
D
0

Metric 2

Next hop

AS path

>lo0.0
>lo0.0

__juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0

hidden)
+ = Active Route, - = Last Active, * = Both
A Destination
P Prf
Metric 1
fe80::280:42ff:fe11:226f/128
*
D
0

2090

Metric 2

Next hop

AS path

>lo0.16385

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route receive-protocol

List of Syntax

Syntax on page 2091

Syntax (EX Series Switches) on page 2091

Syntax

show route receive-protocol protocol neighbor-address

<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)

Syntax (EX Series

Switches)

show route receive-protocol protocol neighbor-address

<brief | detail | extensive | terse>

Release Information

Description

Options

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the routing information as it was received through a particular neighbor using a
particular dynamic routing protocol.
brief | detail | extensive | terse(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

protocol neighbor-addressProtocol transmitting the route (bgp, dvmrp, msdp, pim, rip,

or ripng) and address of the neighboring router from which the route entry was
received.
Additional Information

Required Privilege
Level
List of Sample Output

Output Fields

The output displays the selected routes and the attributes with which they were received,
but does not show the effects of import policy on the routing attributes.
view

show route receive-protocol bgp on page 2094

show route receive-protocol bgp extensive on page 2094
show route receive-protocol bgp table extensive on page 2094
show route receive-protocol bgp logical-system extensive on page 2095
show route receive-protocol bgp detail (Layer 2 VPN) on page 2096
show route receive-protocol bgp extensive (Layer 2 VPN) on page 2096
show route receive-protocol bgp (Layer 3 VPN) on page 2097
show route receive-protocol bgp detail (Layer 3 VPN) on page 2097
show route receive-protocol bgp extensive (Layer 3 VPN) on page 2098
Table 208 on page 2091 describes the output fields for the show route receive-protocol
command. Output fields are listed in the approximate order in which they appear.

Table 208: show route receive-protocol Output Fields

Field Name

Field Description

Level of Output

routing-table-name

Name of the routing tablefor example, inet.0.

All levels

Copyright 2014, Juniper Networks, Inc.

2091

Interfaces Fundamentals for Routing Devices

Table 208: show route receive-protocol Output Fields (continued)

Field Name

Field Description

Level of Output

number
destinations

Number of destinations for which there are routes in the routing table.

All levels

number routes

Number of routes in the routing table and total number of routes in the following
states:

All levels

active

holddown (routes that are in pending state before being declared inactive)

hidden (routes that are not used because of a routing policy)

Prefix

Destination prefix.

none brief

MED

Multiple exit discriminator value included in the route.

none brief

destination-prefix
(entry, announced)

Destination prefix. The entry value is the number of routes for this destination,
and the announced value is the number of routes being announced for this
destination.

detail extensive

Route Distinguisher

64-bit prefix added to IP subnets to make them unique.

detail extensive

Label-Base, range

First label in a block of labels and label block size. A remote PE routing device
uses this first label when sending traffic toward the advertising PE routing device.

detail extensive

VPN Label

Virtual private network (VPN) label. Packets are sent between CE and PE routing
devices by advertising VPN labels. VPN labels transit over either an RSVP or an
LDP label-switched path (LSP) tunnel.

detail extensive

Next hop

Next hop to the destination. An angle bracket (>) indicates that the route is the
selected route.

All levels

Localpref or
Lclpref

Local preference value included in the route.

All levels

2092

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 208: show route receive-protocol Output Fields (continued)

Field Name

Field Description

Level of Output

AS path

Autonomous system (AS) path through which the route was learned. The letters
at the end of the AS path indicate the path origin, providing an indication of the
state of the route at the point at which the AS path originated:

All levels

IIGP.

EEGP.

?Incomplete; typically, the AS path was aggregated.

When AS path numbers are included in the route, the format is as follows:

[ ]Brackets enclose the number that precedes the AS path. This number

represents the number of ASs present in the AS path, when calculated as

defined in RFC 4271. This value is used the AS-path merge process, as defined
in RFC 4893.

[ ]If more than one AS number is configured on the router, or if AS path

prepending is configured, brackets enclose the local AS number associated

with the AS path.

{ }Braces enclose AS sets, which are groups of AS numbers in which the

order does not matter. A set commonly results from route aggregation. The
numbers in each AS set are displayed in ascending order.

( )Parentheses enclose a confederation.

( [ ] )Parentheses and brackets enclose a confederation set.

NOTE: In Junos OS Release 10.3 and later, the AS path field displays an
unrecognized attribute and associated hexadecimal value if BGP receives
attribute 128 (attribute set) and you have not configured an independent domain
in any routing instance.
Cluster list

(For route reflected output only) Cluster ID sent by the route reflector.

detail extensive

Originator ID

(For route reflected output only) Address of routing device that originally sent
the route to the route reflector.

detail extensive

Communities

Community path attribute for the route. See the Output Field table in the show
route detail command for all possible values for this field.

detail extensive

AIGP

Accumulated interior gateway protocol (AIGP) BGP attribute.

detail extensive

Attrset AS

Number, local preference, and path of the AS that originated the route. These
values are stored in the Attrset attribute at the originating routing device.

detail extensive

Layer2-info:
encaps

Layer 2 encapsulation (for example, VPLS).

detail extensive

control flags

Control flags: none or Site Down.

detail extensive

mtu

Maximum transmission unit (MTU) of the Layer 2 circuit.

detail extensive

Copyright 2014, Juniper Networks, Inc.

2093

Interfaces Fundamentals for Routing Devices

Sample Output
show route receive-protocol bgp
user@host> show route receive-protocol bgp 10.255.245.215
inet.0: 28 destinations,
Prefix
10.22.1.0/24
10.22.2.0/24

33 routes (27 active, 0 holddown, 1 hidden)

Next hop
MED
Lclpref
AS path
10.255.245.215
0
100
I
10.255.245.215
0
100
I

show route receive-protocol bgp extensive

user@host> show route receive-protocol bgp 10.255.245.63 extensive
inet.0: 244 destinations, 244 routes (243 active, 0 holddown, 1 hidden)
Prefix
Next hop
MED
Lclpref AS path
1.1.1.0/24 (1 entry, 1 announced)
Next hop: 10.0.50.3
Localpref: 100
AS path: I <Orginator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.45
165.3.0.0/16 (1 entry, 1 announced)
Next hop: 111.222.5.254
Localpref: 100
AS path: I <Originator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.68
165.4.0.0/16 (1 entry, 1 announced)
Next hop: 111.222.5.254
Localpref: 100
AS path: I <Originator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.45
195.1.2.0/24 (1 entry, 1 announced)
Next hop: 111.222.5.254
Localpref: 100
AS path: I <Originator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.68
inet.2: 63 destinations, 63 routes (63 active, 0 holddown, 0 hidden)
Prefix
Next hop
MED
Lclpref AS path
inet.3: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
Prefix
Next hop
MED
Lclpref AS path
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Prefix
Next hop
MED
Lclpref AS path
mpls.0: 48 destinations, 48 routes (48 active, 0 holddown, 0 hidden)

show route receive-protocol bgp table extensive

user@host> show route receive-protocol bgp 207.17.136.192 table inet.0 66.117.68.0/24 extensive
inet.0: 227315 destinations, 227316 routes (227302 active, 0 holddown, 13 hidden)
* 66.117.63.0/24 (1 entry, 1 announced)
Nexthop: 207.17.136.29
Localpref: 100
AS path: AS2 PA[6]: 14203 2914 3356 29748 33437 AS_TRANS
AS path: AS4 PA[2]: 33437 393219
AS path: Merged[6]: 14203 2914 3356 29748 33437 393219 I
Communities: 2914:420

2094

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route receive-protocol bgp logical-system extensive

user@host> show route receive-protocol bgp 10.0.0.9 logical-system PE4 extensive
inet.0: 12 destinations, 13 routes (12 active, 0 holddown, 0 hidden)
* 10.0.0.0/30 (1 entry, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 10.0.0.4/30 (1 entry, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
10.0.0.8/30 (2 entries, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 10.9.9.1/32 (1 entry, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 10.100.1.1/32 (1 entry, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 44.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300096
Nexthop: 10.0.0.9
AS path: 13979 I
AIGP: 203
* 55.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300112
Nexthop: 10.0.0.9
AS path: 13979 7018 I
AIGP: 25
* 66.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300144
Nexthop: 10.0.0.9
AS path: 13979 7018 I
* 99.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300160
Nexthop: 10.0.0.9
AS path: 13979 7018 I

Copyright 2014, Juniper Networks, Inc.

2095

Interfaces Fundamentals for Routing Devices

show route receive-protocol bgp detail (Layer 2 VPN)

user@host> show route receive-protocol bgp 10.255.14.171 detail
inet.0: 68 destinations, 68 routes (67 active, 0 holddown, 1 hidden)
Prefix
Nexthop
MED
Lclpref AS path
inet.3: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
mpls.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
frame-vpn.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0
hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 1 announced)
Route Distinguisher: 10.255.245.35:1
Label-base : 800000, range : 4, status-vector : 0x0
Nexthop: 10.255.245.35
Localpref: 100
AS path: I
Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY,
control flags: 0, mtu: 0
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 0 announced)
Route Distinguisher: 10.255.245.35:1
Label-base : 800000, range : 4, status-vector : 0x0
Nexthop: 10.255.245.35
Localpref: 100
AS path: I
Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY,
control flags:0, mtu: 0

show route receive-protocol bgp extensive (Layer 2 VPN)

user@host> show route receive-protocol bgp 10.255.14.171 extensive
inet.0: 68 destinations, 68 routes (67 active, 0 holddown, 1 hidden)
Prefix
Nexthop
MED
Lclpref AS path
inet.3: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
mpls.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
frame-vpn.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 1 announced)
Route Distinguisher: 10.255.245.35:1
Label-base : 800000, range : 4, status-vector : 0x0
Nexthop: 10.255.245.35
Localpref: 100
AS path: I
Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY,
control flags:0, mtu: 0
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 0 announced)
Route Distinguisher: 10.255.245.35:1
Label-base : 800000, range : 4, status-vector : 0x0
Nexthop: 10.255.245.35
Localpref: 100

2096

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

AS path: I
Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY,
control flags:0, mtu: 0

show route receive-protocol bgp (Layer 3 VPN)

user@host> show route receive-protocol bgp 10.255.14.171
inet.0: 33 destinations, 33 routes (32 active, 0 holddown, 1 hidden)
Prefix
Nexthop
MED
Lclpref AS path
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
VPN-A.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.175/32
10.255.14.171
100 2 I
10.255.14.179/32
10.255.14.171
2
100 I
VPN-B.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.175/32
10.255.14.171
100 2 I
10.255.14.177/32
10.255.14.171
100 I
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
mpls.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.171:300:10.255.14.177/32
10.255.14.171
100 I
10.255.14.171:100:10.255.14.179/32
10.255.14.171
2
100 I
10.255.14.171:200:10.255.14.175/32
10.255.14.171
100 2 I

show route receive-protocol bgp detail (Layer 3 VPN)

user@host> show route receive-protocol bgp 10.255.14.174 detail
inet.0: 16 destinations, 17 routes (15 active, 0 holddown, 1 hidden)
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
vpna.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
* 10.49.0.0/30 (1 entry, 1 announced)
Route Distinguisher: 10.255.14.176:2
VPN Label: 101264
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
Communities: target:200:100
AttrSet AS: 100
Localpref: 100
AS path: I
* 10.255.14.172/32 (1 entry, 1 announced)
Route Distinguisher: 10.255.14.176:2
VPN Label: 101280
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
Communities: target:200:100
AttrSet AS: 100
Localpref: 100
AS path: I
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
mpls.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

Copyright 2014, Juniper Networks, Inc.

2097

Interfaces Fundamentals for Routing Devices

* 10.255.14.174:2:10.49.0.0/30 (1 entry, 0 announced)

Route Distinguisher: 10.255.14.174:2
VPN Label: 101264
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
Communities: target:200:100
AttrSet AS: 100
Localpref: 100
AS path: I
* 10.255.14.174:2:10.255.14.172/32 (1 entry, 0 announced)
Route Distinguisher: 10.255.14.174:2
VPN Label: 101280
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
Communities: target:200:100
AttrSet AS: 100
Localpref: 100
AS path: I
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

show route receive-protocol bgp extensive (Layer 3 VPN)

user@host> show route receive-protocol bgp 10.255.245.63 extensive
inet.0: 244 destinations, 244 routes (243 active, 0 holddown, 1 hidden)
Prefix
Nexthop
MED
Lclpref AS path
1.1.1.0/24 (1 entry, 1 announced)
Nexthop: 10.0.50.3
Localpref: 100
AS path: I <Originator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.45
165.3.0.0/16 (1 entry, 1 announced)
Nexthop: 111.222.5.254
Localpref: 100
AS path: I <Originator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.68
165.4.0.0/16 (1 entry, 1 announced)
Nexthop: 111.222.5.254
Localpref: 100
AS path: I <Originator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.45
195.1.2.0/24 (1 entry, 1 announced)
Nexthop: 111.222.5.254
Localpref: 100
AS path: I <Originator>
Cluster list: 10.2.3.1
Originator ID: 10.255.245.68
inet.2: 63 destinations, 63 routes (63 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
inet.3: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
mpls.0: 48 destinations, 48 routes (48 active, 0 holddown, 0 hidden)

2098

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route resolution

List of Syntax

Syntax on page 2099

Syntax (EX Series Switches) on page 2099

Syntax

show route resolution

<brief | detail | extensive | summary>
<index index>
<logical-system (all | logical-system-name)>
<prefix>
<table routing-table-name>
<unresolved>

Syntax (EX Series

Switches)

Release Information

Description

Options

show route resolution

<brief | detail | extensive | summary>
<index index>
<prefix>
<table routing-table-name>
<unresolved>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the entries in the next-hop resolution database. This database provides for
recursive resolution of next hops through other prefixes in the routing table.
noneDisplay standard information about all entries in the next-hop resolution database.
brief | detail | extensive | summary(Optional) Display the specified level of output.
index index(Optional) Show the index of the resolution tree.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

prefix network/destination-prefix(Optional) Display database entries for the specified

address.
table routing-table-name(Optional) Display information about a particular routing table

(for example, inet.0) where policy-based export is currently enabled.

unresolved(Optional) Display routes that could not be resolved.

Required Privilege
Level
Related
Documentation
List of Sample Output

view

Example: Configuring Route Resolution on PE Routers

show route resolution detail on page 2100

show route resolution summary on page 2101
show route resolution unresolved on page 2101

Copyright 2014, Juniper Networks, Inc.

2099

Interfaces Fundamentals for Routing Devices

Output Fields

Table 209 on page 2100 describes the output fields for the show route resolution command.
Output fields are listed in the approximate order in which they appear.

Table 209: show route resolution Output Fields

Field Name

Field Description

routing-table-name

Name of the routing table whose prefixes are resolved using the entries in the
route resolution database. For routing table groups, this is the name of the
primary routing table whose prefixes are resolved using the entries in the route
resolution database.

Tree index

Tree index identifier.

Nodes

Number of nodes in the tree.

Reference count

Number of references made to the next hop.

Contributing routing
tables

Routing tables used for next-hop resolution.

Originating RIB

Name of the routing table whose active route was used to determine the
forwarding next-hop entry in the resolution database. For example, in the case
of inet.0 resolving through inet.0 and inet.3, this field indicates which routing
table, inet.0 or inet.3, provided the best path for a particular prefix.

Metric

Metric associated with the forwarding next hop.

Node path count

Number of nodes in the path.

Forwarding next
hops

Number of forwarding next hops. The forwarding next hop is the network layer
address of the directly reachable neighboring system (if applicable) and the
interface used to reach it.

Sample Output
show route resolution detail
user@host> show route resolution detail
Tree Index: 1, Nodes 0, Reference Count 1
Contributing routing tables: inet.3
Tree Index: 2, Nodes 23, Reference Count 1
Contributing routing tables: inet.0 inet.3
10.10.0.0/16 Originating RIB: inet.0
Node path count: 1
Forwarding nexthops: 1
10.31.1.0/30 Originating RIB: inet.0
Node path count: 1
Forwarding nexthops: 1
10.31.1.1/32 Originating RIB: inet.0
Node path count: 1
Forwarding nexthops: 0
10.31.1.4/30 Originating RIB: inet.0
Node path count: 1
Forwarding nexthops: 1
10.31.1.5/32 Originating RIB: inet.0

2100

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Node path count: 1

Forwarding nexthops: 0
10.31.2.0/30 Originating RIB: inet.0
Metric: 2 Node path count: 1
Forwarding nexthops: 2
10.31.11.0/24 Originating RIB: inet.0
Node path count: 1
Forwarding nexthops: 1

show route resolution summary

user@host> show route resolution summary
Tree Index: 1, Nodes 24, Reference Count 1
Contributing routing tables: :voice.inet.0 :voice.inet.3
Tree Index: 2, Nodes 2, Reference Count 1
Contributing routing tables: inet.3
Tree Index: 3, Nodes 43, Reference Count 1
Contributing routing tables: inet.0 inet.3

show route resolution unresolved

user@host> show route resolution unresolved
Tree Index 1
vt-3/2/0.32769.0
/16
Protocol Nexthop: 10.255.71.238 Push 800000
Indirect nexthop: 0 vt-3/2/0.32772.0
/16
Protocol Nexthop: 10.255.70.103 Push 800008
Indirect nexthop: 0 Tree Index 2

Copyright 2014, Juniper Networks, Inc.

2101

Interfaces Fundamentals for Routing Devices

show route snooping

Syntax

Release Information

Description
Options

show route snooping

<brief | detail | extensive | terse>
<all>
<best address/prefix>
<exact address>
<logical-system logical-system-name>
<range prefix-range>
<summary>
<table table-name>

Command introduced in Junos OS Release 8.5.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the entries in the routing table that were learned from snooping.
noneDisplay the entries in the routing table that were learned from snooping.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

all(Optional) Display all entries, including hidden entries.
best address/prefix(Optional) Display the longest match for the provided address and

optional prefix.
exact address/prefix(Optional) Display exact matches for the provided address and

optional prefix.
logical-system logical-system-name(Optional) Display information about a particular

logical system, or type all.

range prefix-range(Optional) Display information for the provided address range.
summary(Optional) Display route snooping summary statisitics.
table table-name(Optional) Display information for the named table.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route snooping detail on page 2102

show route snooping logical-system all on page 2103
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route snooping detail
user@host> show route snooping detail

2102

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

__+domainAll__.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

224.0.0.2/32 (1 entry, 1 announced)
*IGMP
Preference: 0
Next hop type: MultiRecv
Next-hop reference count: 4
State: <Active NoReadvrt Int>
Age: 2:24
Task: IGMP
Announcement bits (1): 0-KRT
AS path: I
224.0.0.22/32 (1 entry, 1 announced)
*IGMP
Preference: 0
Next hop type: MultiRecv
Next-hop reference count: 4
State: <Active NoReadvrt Int>
Age: 2:24
Task: IGMP
Announcement bits (1): 0-KRT
AS path: I
__+domainAll__.inet.1: 36 destinations, 36 routes (36 active, 0 holddown, 0 hidden)
224.0.0.0.0.0.0.0/24 (1 entry, 1 announced)
*Multicast Preference: 180
Next hop type: Multicast (IPv4), Next hop index: 1048584
Next-hop reference count: 4
State: <Active Int>
Age: 2:24
Task: MC
Announcement bits (1): 0-KRT
AS path: I
<snip>

show route snooping logical-system all

user@host> show route snooping logical-system all
logical-system: default
inet.1: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
Restart Unsupported
+ = Active Route, - = Last Active, * = Both
0.0,0.1,0.0,232.1.1.65,100.1.1.2/112*[Multicast/180] 00:07:36
Multicast (IPv4) Composite
0.0,0.1,0.0,232.1.1.66,100.1.1.2/112*[Multicast/180] 00:07:36
Multicast (IPv4) Composite
0.0,0.1,0.0,232.1.1.67,100.1.1.2/112*[Multicast/180] 00:07:36
<snip>
default-switch.inet.1: 237 dest, 237 rts (237 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
0.15,0.1,0.0,0.0.0.0,0.0.0.0,2/120*[Multicast/180] 00:08:21
Multicast (IPv4) Composite
0.15,0.1,0.0,0.0.0.0,0.0.0.0,2,17/128*[Multicast/180] 00:08:21

Copyright 2014, Juniper Networks, Inc.

2103

Interfaces Fundamentals for Routing Devices

Multicast (IPv4) Composite

<snip>

2104

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route source-gateway

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Options

Syntax on page 2105

Syntax (EX Series Switches) on page 2105
show route source-gateway address
<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>
show route source-gateway address
<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the entries in the routing table that were learned from a particular address. The
Source field in the show route detail command output lists the source for each route, if
known.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do

not specify a level of output, the system defaults to brief.

addressIP address of the system.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show route source-gateway on page 2105

show route source-gateway detail on page 2106
show route source-gateway extensive on page 2108
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or
the show route terse command.

Sample Output
show route source-gateway
user@host> show route source-gateway 10.255.70.103
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete

Copyright 2014, Juniper Networks, Inc.

2105

Interfaces Fundamentals for Routing Devices

mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)

Restart Complete
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.255.70.103:1:3:1/96
*[BGP/170] 12:12:24, localpref 100, from 10.255.70.103
AS path: I
> via so-0/3/0.0, label-switched-path green-r1-r3
red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.255.70.103:2:3:1/96
*[BGP/170] 12:12:24, localpref 0, from 10.255.70.103
AS path: I
> via so-0/3/0.0, label-switched-path green-r1-r3
bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both
10.255.70.103:1:3:1/96
*[BGP/170] 12:12:24, localpref 100, from 10.255.70.103
AS path: I
> via so-0/3/0.0, label-switched-path green-r1-r3
10.255.70.103:2:3:1/96
*[BGP/170] 12:12:24, localpref 0, from 10.255.70.103
AS path: I
> via so-0/3/0.0, label-switched-path green-r1-r3

show route source-gateway detail

user@host> show route source-gateway 10.255.70.103 detail
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)
Restart Complete
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
Restart Complete
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

2106

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Restart Complete
10.255.70.103:1:3:1/96 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.70.103:1
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:14:00
Metric2: 1
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-green-l2vpn
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
Label-base: 800008, range: 8
Localpref: 100
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
Restart Complete
10.255.70.103:2:3:1/96 (1 entry, 1 announced)
*BGP
Preference: 170/-1
Route Distinguisher: 10.255.70.103:2
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:14:00
Metric2: 1
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-red-l2vpn
AS path: I
Communities: target:11111:2 Layer2-info: encaps:VPLS,
control flags:Site-Down, mtu: 0
Label-base: 800016, range: 8
Localpref: 0
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
10.255.70.103:1:3:1/96 (1 entry, 0 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.70.103:1
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:14:00
Metric2: 1
Task: BGP_69.10.255.70.103+179
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS, control
flags:, mtu: 0

Copyright 2014, Juniper Networks, Inc.

2107

Interfaces Fundamentals for Routing Devices

Label-base: 800008, range: 8

Localpref: 100
Router ID: 10.255.70.103
Secondary Tables: green.l2vpn.0
10.255.70.103:2:3:1/96 (1 entry, 0 announced)
*BGP
Preference: 170/-1
Route Distinguisher: 10.255.70.103:2
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:14:00
Metric2: 1
Task: BGP_69.10.255.70.103+179
AS path: I
Communities: target:11111:2 Layer2-info: encaps:VPLS,
control flags:Site-Down,
mtu: 0
Label-base: 800016, range: 8
Localpref: 0
Router ID: 10.255.70.103
Secondary Tables: red.l2vpn.0

show route source-gateway extensive

user@host> show route source-gateway 10.255.70.103 extensive
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)
Restart Complete
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
Restart Complete
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
10.255.70.103:1:3:1/96 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.70.103:1
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:15:24
Metric2: 1
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-green-l2vpn
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0

2108

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Label-base: 800008, range: 8

Localpref: 100
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
Restart Complete
10.255.70.103:2:3:1/96 (1 entry, 1 announced)
*BGP
Preference: 170/-1
Route Distinguisher: 10.255.70.103:2
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:15:24
Metric2: 1
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-red-l2vpn
AS path: I
Communities: target:11111:2 Layer2-info: encaps:VPLS,
control flags:Site-Down, mtu: 0
Label-base: 800016, range: 8
Localpref: 0
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
10.255.70.103:1:3:1/96 (1 entry, 0 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.70.103:1
Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:15:24
Metric2: 1
Task: BGP_69.10.255.70.103+179
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
Label-base: 800008, range: 8
Localpref: 100
Router ID: 10.255.70.103
Secondary Tables: green.l2vpn.0
Indirect next hops: 1
Protocol next hop: 10.255.70.103 Metric: 2
Indirect next hop: 2 no-forward
Indirect path forwarding next hops: 1
Next hop:
via so-0/3/0.0 weight 0x1
10.255.70.103/32 Originating RIB: inet.3
Metric: 2
Node path count: 1
Forwarding nexthops: 1
Nexthop: via so-0/3/0.0
10.255.70.103:2:3:1/96 (1 entry, 0 announced)
*BGP
Preference: 170/-1

Copyright 2014, Juniper Networks, Inc.

2109

Interfaces Fundamentals for Routing Devices

Route Distinguisher: 10.255.70.103:2

Next-hop reference count: 7
Source: 10.255.70.103
Protocol next hop: 10.255.70.103
Indirect next hop: 2 no-forward
State: <Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 12:15:24
Metric2: 1
Task: BGP_69.10.255.70.103+179
AS path: I
Communities: target:11111:2 Layer2-info: encaps:VPLS,
control flags:Site-Down,
mtu: 0
Label-base: 800016, range: 8
Localpref: 0
Router ID: 10.255.70.103
Secondary Tables: red.l2vpn.0
Indirect next hops: 1
Protocol next hop: 10.255.70.103 Metric: 2
Indirect next hop: 2 no-forward
Indirect path forwarding next hops: 1
Next hop:
via so-0/3/0.0 weight 0x1
10.255.70.103/32 Originating RIB: inet.3
Metric: 2
Node path count: 1
Forwarding nexthops: 1
Nexthop: via so-0/3/0.0

2110

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route summary

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Syntax on page 2111

Syntax (EX Series Switches) on page 2111
show route summary
<logical-system (all | logical-system-name)>
<table routing-table-name>
show route summary

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display summary statistics about the entries in the routing table.
CPU utilization might increase while the device learns routes. We recommend that you
use the show route summary command after the device learns and enters the routes into
the routing table. Depending on the size of your network, this might take several minutes.
If you receive a timeout communicating with routing daemon error when using the show
route summary command, wait several minutes before attempting to use the command
again. This is not a critical system error, but you might experience a delay in using the
command-line interface (CLI).

Options

noneDisplay summary statistics about the entries in the routing table.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

table routing-table-name(Optional) Display summary statistics for all routing tables

whose name begins with this string (for example, inet.0 and inet6.0 are both displayed
when you run the show route summary table inet command). If you only want to
display statistics for a specific routing table, make sure to enter the exact name of
that routing table.
Required Privilege
Level
List of Sample Output

Output Fields

view

show route summary on page 2112

show route summary table on page 2113
show route summary table (with Route Limits Configured for the Routing
Table) on page 2113
Table 210 on page 2111 lists the output fields for the show route summary command. Output
fields are listed in the approximate order in which they appear.

Table 210: show route summary Output Fields

Field Name

Field Description

Router ID

Address of the local routing device.

Copyright 2014, Juniper Networks, Inc.

2111

Interfaces Fundamentals for Routing Devices

Table 210: show route summary Output Fields (continued)

Field Name

Field Description

routing-table-name

Name of the routing table (for example, inet.0).

destinations

Number of destinations for which there are routes in the routing table.

routes

Number of routes in the routing table:

activeNumber of routes that are active.

holddownNumber of routes that are in the hold-down state before

being declared inactive.

Limit/Threshold

hiddenNumber of routes that are not used because of routing policy.

Displays the configured route limits for the routing table set with the
maximum-prefixes and the maximum-paths statements. If you do not
configure route limits for the routing table, the show output does not
display this information.

destinationsThe first number represents the maximum number of

route prefixes installed in the routing table. The second number

represents the number of route prefixes that trigger a warning message.

routesThe first number represents the maximum number of routes.

The second number represents the number of routes that trigger a

warning message.
Direct

Routes on the directly connected network.

Local

Local routes.

protocol-name

Name of the protocol from which the route was learned. For example,
OSPF, RSVP, and Static.

Sample Output
show route summary
user@host> show route summary
Autonomous system number: 69
Router ID: 10.255.71.52
Maximum-ECMP: 32
inet.0: 24 destinations, 25 routes (23 active, 0 holddown, 1 hidden)
Restart Complete
Direct:
6 routes,
5 active
Local:
4 routes,
4 active
OSPF:
5 routes,
4 active
Static:
7 routes,
7 active
IGMP:
1 routes,
1 active
PIM:
2 routes,
2 active
inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
RSVP:
2 routes,
2 active
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

2112

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Restart Complete
Direct:

1 routes,

1 active

mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)

Restart Complete
MPLS:
3 routes,
3 active
VPLS:
4 routes,
2 active
inet6.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
Restart Complete
Direct:
2 routes,
2 active
PIM:
2 routes,
2 active
MLD:
1 routes,
1 active
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
BGP:
2 routes,
2 active
L2VPN:
2 routes,
2 active
red.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
Restart Complete
BGP:
2 routes,
2 active
L2VPN:
1 routes,
1 active
bgp.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
BGP:
4 routes,
4 active

show route summary table

user@host> show route summary table inet
Router ID: 192.168.0.1
inet.0: 32 destinations, 34 routes (31 active, 0 holddown, 1 hidden)
Direct:
6 routes,
5 active
Local:
9 routes,
9 active
OSPF:
3 routes,
1 active
Static:
13 routes,
13 active
IGMP:
1 routes,
1 active
PIM:
2 routes,
2 active
inet.1: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Multicast:
1 routes,
1 active
inet6.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
Local:
1 routes,
1 active
PIM:
2 routes,
2 active
inet6.1: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Multicast:
1 routes,
1 active

show route summary table (with Route Limits Configured for the Routing Table)
user@host> show route summary table VPN-A.inet.0
Autonomous system number: 100
Router ID: 10.255.182.142
VPN-A.inet.0: 13 destinations, 14 routes (13 active, 0 holddown, 0 hidden)
Limit/Threshold: 2000/200 destinations 20/12 routes
Direct:
2 routes,
2 active
Local:
1 routes,
1 active

Copyright 2014, Juniper Networks, Inc.

2113

Interfaces Fundamentals for Routing Devices

OSPF:
BGP:
IGMP:
PIM:

2114

4
4
1
2

routes,
routes,
routes,
routes,

3
4
1
2

active
active
active
active

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route table

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description
Options

Syntax on page 2115

Syntax (EX Series Switches) on page 2115
show route table routing-table-name
<brief | detail | extensive | terse>
<logical-system (all | logical-system-name)>
show route table routing-table-name
<brief | detail | extensive | terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display the route entries in a particular routing table.
brief | detail | extensive | terse(Optional) Display the specified level of output.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

routing-table-nameDisplay route entries for all routing tables whose name begins with

this string (for example, inet.0 and inet6.0 are both displayed when you run the show
route table inet command).
Required Privilege
Level
Related
Documentation
List of Sample Output

view

show route summary on page 2111

show route table bgp.l2.vpn on page 2116

show route table bgp.l3vpn.0 on page 2116
show route table bgp.l3vpn.0 detail on page 2116
show route table bgp.rtarget.0 (When Proxy BGP Route Target Filtering Is
Configured) on page 2118
show route table inet.0 on page 2118
show route table inet.3 on page 2118
show route table inet6.0 on page 2119
show route table inet6.3 on page 2119
show route table inetflow detail on page 2119
show route table l2circuit.0 on page 2119
show route table mpls on page 2120
show route table mpls extensive on page 2120
show route table mpls.0 on page 2120
show route table mpls.0 detail (PTX Series) on page 2121
show route table mpls.0 extensive (PTX Series) on page 2121
show route table mpls.0 (RSVP RouteTransit LSP) on page 2122
show route table vpls_1 detail on page 2122

Copyright 2014, Juniper Networks, Inc.

2115

Interfaces Fundamentals for Routing Devices

show route table vpn-a on page 2123

show route table vpn-a.mdt.0 on page 2123
show route table VPN-A detail on page 2123
show route table VPN-AB.inet.0 on page 2124
show route table VPN_blue.mvpn-inet6.0 on page 2124
show route table vrf1.mvpn.0 extensive on page 2125
show route table inetflow detail on page 2125
Output Fields

For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.

Sample Output
show route table bgp.l2.vpn
user@host> show route table bgp.l2.vpn
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.24.1:1:4:1/96
*[BGP/170] 01:08:58, localpref 100, from 192.168.24.1
AS path: I
> to 10.0.16.2 via fe-0/0/1.0, label-switched-path am

show route table bgp.l3vpn.0

user@host> show route table bgp.l3vpn.0
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.255.71.15:100:10.255.71.17/32
*[BGP/170] 00:03:59, MED 1, localpref 100, from
10.255.71.15
AS path: I
> via so-2/1/0.0, Push 100020, Push 100011(top)
10.255.71.15:200:10.255.71.18/32
*[BGP/170] 00:03:59, MED 1, localpref 100, from
10.255.71.15
AS path: I
> via so-2/1/0.0, Push 100021, Push 100011(top)

show route table bgp.l3vpn.0 detail

user@host> show route table bgp.l3vpn.0 detail
bgp.l3vpn.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
10.255.245.12:1:4.0.0.0/8 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.245.12:1
Source: 10.255.245.12
Next hop: 192.168.208.66 via fe-0/0/0.0, selected
Label operation: Push 182449
Protocol next hop: 10.255.245.12
Push 182449
Indirect next hop: 863a630 297
State: <Active Int Ext>
Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1

2116

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Task: BGP_35.10.255.245.12+179
Announcement bits (1): 0-BGP.0.0.0.0+179
AS path: 30 10458 14203 2914 3356 I (Atomic) Aggregator: 3356 4.68.0.11
Communities: 2914:420 target:11111:1 origin:56:78
VPN Label: 182449
Localpref: 100
Router ID: 10.255.245.12
10.255.245.12:1:4.17.225.0/24 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.245.12:1
Source: 10.255.245.12
Next hop: 192.168.208.66 via fe-0/0/0.0, selected
Label operation: Push 182465
Protocol next hop: 10.255.245.12
Push 182465
Indirect next hop: 863a8f0 305
State: <Active Int Ext>
Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1
Task: BGP_35.10.255.245.12+179
Announcement bits (1): 0-BGP.0.0.0.0+179
AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 6496 I
Communities: 2914:410 target:12:34 target:11111:1 origin:12:34
VPN Label: 182465
Localpref: 100
Router ID: 10.255.245.12
10.255.245.12:1:4.17.226.0/23 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.245.12:1
Source: 10.255.245.12
Next hop: 192.168.208.66 via fe-0/0/0.0, selected
Label operation: Push 182465
Protocol next hop: 10.255.245.12
Push 182465
Indirect next hop: 86bd210 330
State: <Active Int Ext>
Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1
Task: BGP_35.10.255.245.12+179
Announcement bits (1): 0-BGP.0.0.0.0+179
AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496
6496 I
Communities: 2914:410 target:12:34 target:11111:1 origin:12:34
VPN Label: 182465
Localpref: 100
Router ID: 10.255.245.12
10.255.245.12:1:4.17.251.0/24 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.245.12:1
Source: 10.255.245.12
Next hop: 192.168.208.66 via fe-0/0/0.0, selected
Label operation: Push 182465
Protocol next hop: 10.255.245.12
Push 182465
Indirect next hop: 86bd210 330
State: <Active Int Ext>

Copyright 2014, Juniper Networks, Inc.

2117

Interfaces Fundamentals for Routing Devices

Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1
Task: BGP_35.10.255.245.12+179
Announcement bits (1): 0-BGP.0.0.0.0+179
AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496
6496 I
Communities: 2914:410 target:12:34 target:11111:1 origin:12:34
VPN Label: 182465
Localpref: 100

show route table bgp.rtarget.0 (When Proxy BGP Route Target Filtering Is Configured)
user@host> show route table bgp.rtarget.o
bgp.rtarget.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100:100:100/96
*[RTarget/5] 00:03:14
Type Proxy
for 10.255.165.103
for 10.255.166.124
Local

show route table inet.0

user@host> show route table inet.0
inet.0: 12 destinations, 12 routes (11 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
0.0.0.0/0
1.0.0.1/32
1.0.0.2/32
12.12.12.21/32
13.13.13.13/32
13.13.13.14/32
13.13.13.21/32
13.13.13.22/32
127.0.0.1/32
111.222.5.0/24
111.222.5.81/32

*[Static/5] 00:51:57
> to 111.222.5.254 via fxp0.0
*[Direct/0] 00:51:58
> via at-5/3/0.0
*[Local/0] 00:51:58
Local
*[Local/0] 00:51:57
Reject
*[Direct/0] 00:51:58
> via t3-5/2/1.0
*[Local/0] 00:51:58
Local
*[Local/0] 00:51:58
Local
*[Direct/0] 00:33:59
> via t3-5/2/0.0
[Direct/0] 00:51:58
> via lo0.0
*[Direct/0] 00:51:58
> via fxp0.0
*[Local/0] 00:51:58
Local

show route table inet.3

user@host> show route table inet.3
inet.3: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
22.0.0.5/32

2118

*[LDP/9] 00:25:43, metric 10, tag 200

to 1.2.94.2 via lt-1/2/0.49
> to 1.2.3.2 via lt-1/2/0.23

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route table inet6.0

user@host> show route table inet6.0
inet6.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Route, * = Both
fec0:0:0:3::/64 *[Direct/0] 00:01:34
>via fe-0/1/0.0
fec0:0:0:3::/128 *[Local/0] 00:01:34
>Local
fec0:0:0:4::/64 *[Static/5] 00:01:34
>to fec0:0:0:3::ffff via fe-0/1/0.0

show route table inet6.3

user@router> show route table inet6.3
inet6.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
::10.255.245.195/128
*[LDP/9] 00:00:22, metric 1
> via so-1/0/0.0
::10.255.245.196/128
*[LDP/9] 00:00:08, metric 1
> via so-1/0/0.0, Push 100008

show route table inetflow detail

user@host> show route table inetflow detail
inetflow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.12.44.1,*/48 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Next-hop reference count: 2
State: <Active Ext>
Local AS: 65002 Peer AS: 65000
Age: 4
Task: BGP_65000.10.12.99.5+3792
Announcement bits (1): 0-Flow
AS path: 65000 I
Communities: traffic-rate:0:0
Validation state: Accept, Originator: 10.12.99.5
Via: 10.12.44.0/24, Active
Localpref: 100
Router ID: 10.255.71.161
10.12.56.1,*/48 (1 entry, 1 announced)
*Flow
Preference: 5
Next-hop reference count: 2
State: <Active>
Local AS: 65002
Age: 6:30
Task: RT Flow
Announcement bits (2): 0-Flow 1-BGP.0.0.0.0+179
AS path: I
Communities: 1:1

show route table l2circuit.0

user@host> show route table l2circuit.0

Copyright 2014, Juniper Networks, Inc.

2119

Interfaces Fundamentals for Routing Devices

l2circuit.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both
10.1.1.195:NoCtrlWord:1:1:Local/96
*[L2CKT/7] 00:50:47
> via so-0/1/2.0, Push
via so-0/1/3.0, Push
10.1.1.195:NoCtrlWord:1:1:Remote/96
*[LDP/9] 00:50:14
Discard
10.1.1.195:CtrlWord:1:2:Local/96
*[L2CKT/7] 00:50:47
> via so-0/1/2.0, Push
via so-0/1/3.0, Push
10.1.1.195:CtrlWord:1:2:Remote/96
*[LDP/9] 00:50:14
Discard

100049
100049

100049
100049

show route table mpls

user@host> show route table mpls
mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0
1
2
1024

*[MPLS/0] 00:13:55, metric 1

Receive
*[MPLS/0] 00:13:55, metric 1
Receive
*[MPLS/0] 00:13:55, metric 1
Receive
*[VPN/0] 00:04:18
to table red.inet.0, Pop

show route table mpls extensive

user@host> show route table mpls extensive
100000 (1 entry, 1 announced)
TSI:
KRT in-kernel 100000 /36 -> {so-1/0/0.0}
*LDP
Preference:
9
Next hop: via so-1/0/0.0, selected
Pop
State: <Active Int>
Age: 29:50
Metric: 1
Task: LDP
Announcement bits (1): 0-KRT
AS path: I
Prefixes bound to route: 10.0.0.194/32

show route table mpls.0

user@host> show route table mpls.0
mpls.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0
1
2
100000

2120

*[MPLS/0] 00:45:09, metric 1

Receive
*[MPLS/0] 00:45:09, metric 1
Receive
*[MPLS/0] 00:45:09, metric 1
Receive
*[L2VPN/7] 00:43:04

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

100001
100002

100002(S=0)

100003

100004

so-0/1/0.1

so-0/1/0.2

> via so-0/1/0.1, Pop

*[L2VPN/7] 00:43:03
> via so-0/1/0.2, Pop
Offset:
*[LDP/9] 00:43:22, metric 1
via so-0/1/2.0, Pop
> via so-0/1/3.0, Pop
*[LDP/9] 00:43:22, metric 1
via so-0/1/2.0, Pop
> via so-0/1/3.0, Pop
*[LDP/9] 00:43:22, metric 1
> via so-0/1/2.0, Swap 100002
via so-0/1/3.0, Swap 100002
*[LDP/9] 00:43:16, metric 1
via so-0/1/2.0, Swap 100049
> via so-0/1/3.0, Swap 100049
*[L2VPN/7] 00:43:04
> via so-0/1/2.0, Push 100001, Push
via so-0/1/3.0, Push 100001, Push
*[L2VPN/7] 00:43:03
via so-0/1/2.0, Push 100000, Push
> via so-0/1/3.0, Push 100000, Push

100049(top)
100049(top)
100049(top) Offset: -4
100049(top) Offset: -4

show route table mpls.0 detail (PTX Series)

user@host> show route table mpls.0 detail
ge-0/0/2.600 (1 entry, 1 announced)
*L2VPN Preference: 7
Next hop type: Indirect
Address: 0x9438f34
Next-hop reference count: 2
Next hop type: Router, Next hop index: 567
Next hop: 3.0.0.1 via ge-0/0/1.0, selected
Label operation: Push 299808
Label TTL action: prop-ttl
Load balance label: Label 299808:None;
Session Id: 0x1
Protocol next hop: 10.255.255.1
Label operation: Push 299872 Offset: 252
Label TTL action: no-prop-ttl
Load balance label: Label 299872:Flow label PUSH;
Composite next hop: 0x9438ed8 570 INH Session ID: 0x2
Indirect next hop: 0x9448208 262142 INH Session ID: 0x2
State: <Active Int>
Age: 21
Metric2: 1
Validation State: unverified
Task: Common L2 VC
Announcement bits (2): 0-KRT 2-Common L2 VC
AS path: I

show route table mpls.0 extensive (PTX Series)

user@host> show route table mpls.0 extensive
ge-0/0/2.600 (1 entry, 1 announced)
TSI:
KRT in-kernel ge-0/0/2.600.0
/32 -> {composite(570)}
*L2VPN Preference: 7
Next hop type: Indirect
Address: 0x9438f34
Next-hop reference count: 2
Next hop type: Router, Next hop index: 567
Next hop: 3.0.0.1 via ge-0/0/1.0, selected

Copyright 2014, Juniper Networks, Inc.

2121

Interfaces Fundamentals for Routing Devices

Label operation: Push 299808

Label TTL action: prop-ttl
Load balance label: Label 299808:None;
Session Id: 0x1
Protocol next hop: 10.255.255.1
Label operation: Push 299872 Offset: 252
Label TTL action: no-prop-ttl
Load balance label: Label 299872:Flow label PUSH;
Composite next hop: 0x9438ed8 570 INH Session ID: 0x2
Indirect next hop: 0x9448208 262142 INH Session ID: 0x2
State: <Active Int>
Age: 47
Metric2: 1
Validation State: unverified
Task: Common L2 VC
Announcement bits (2): 0-KRT 2-Common L2 VC
AS path: I
Composite next hops: 1
Protocol next hop: 10.255.255.1 Metric: 1
Label operation: Push 299872 Offset: 252
Label TTL action: no-prop-ttl
Load balance label: Label 299872:Flow label PUSH;
Composite next hop: 0x9438ed8 570 INH Session ID: 0x2
Indirect next hop: 0x9448208 262142 INH Session ID: 0x2
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 3.0.0.1 via ge-0/0/1.0
Session Id: 0x1
10.255.255.1/32 Originating RIB: inet.3
Metric: 1
Node path count: 1
Forwarding nexthops: 1
Nexthop: 3.0.0.1 via ge-0/0/1.0

show route table mpls.0 (RSVP RouteTransit LSP)

user@host> show route table mpls.0
mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0
1
2
13
300352
300352(S=0)
300384
300384(S=0)

*[MPLS/0] 00:37:31, metric 1

Receive
*[MPLS/0] 00:37:31, metric 1
Receive
*[MPLS/0] 00:37:31, metric 1
Receive
*[MPLS/0] 00:37:31, metric 1
Receive
*[RSVP/7/1] 00:08:00, metric 1
> to 8.64.0.106 via ge-1/0/1.0,
*[RSVP/7/1] 00:08:00, metric 1
> to 8.64.0.106 via ge-1/0/1.0,
*[RSVP/7/2] 00:05:20, metric 1
> to 8.64.1.106 via ge-1/0/0.0,
*[RSVP/7/2] 00:05:20, metric 1
> to 8.64.1.106 via ge-1/0/0.0,

label-switched-path lsp1_p2p
label-switched-path lsp1_p2p
Pop
Pop

show route table vpls_1 detail

user@host> show route table vpls_1 detail
vpls_1.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete

2122

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

1.1.1.11:1000:1:1/96 (1 entry, 1 announced)

*L2VPN Preference: 170/-1
Receive table: vpls_1.l2vpn.0
Next-hop reference count: 2
State: <Active Int Ext>
Age: 4:29:47 Metric2: 1
Task: vpls_1-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down
Label-base: 800000, range: 8, status-vector: 0xFF

show route table vpn-a

user@host> show route table vpn-a
vpn-a.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.16.1:1:1:1/96
*[VPN/7] 05:48:27
Discard
192.168.24.1:1:2:1/96
*[BGP/170] 00:02:53, localpref 100, from 192.168.24.1
AS path: I
> to 10.0.16.2 via fe-0/0/1.0, label-switched-path am
192.168.24.1:1:3:1/96
*[BGP/170] 00:02:53, localpref 100, from 192.168.24.1
AS path: I
> to 10.0.16.2 via fe-0/0/1.0, label-switched-path am

show route table vpn-a.mdt.0

user@host> show route table vpn-a.mdt.0
vpn-a.mdt.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:1:0:10.255.14.216:232.1.1.1/144
*[MVPN/70] 01:23:05, metric2 1
Indirect
1:1:1:10.255.14.218:232.1.1.1/144
*[BGP/170] 00:57:49, localpref 100, from 10.255.14.218
AS path: I
> via so-0/0/0.0, label-switched-path r0e-to-r1
1:1:2:10.255.14.217:232.1.1.1/144
*[BGP/170] 00:57:49, localpref 100, from 10.255.14.217
AS path: I
> via so-0/0/1.0, label-switched-path r0-to-r2

show route table VPN-A detail

user@host> show route table VPN-A detail
VPN-AB.inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
10.255.179.9/32 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Route Distinguisher: 10.255.179.13:200
Next hop type: Indirect
Next-hop reference count: 5
Source: 10.255.179.13
Next hop type: Router, Next hop index: 732
Next hop: 10.39.1.14 via fe-0/3/0.0, selected
Label operation: Push 299824, Push 299824(top)

Copyright 2014, Juniper Networks, Inc.

2123

Interfaces Fundamentals for Routing Devices

Protocol next hop: 10.255.179.13

Push 299824
Indirect next hop: 8f275a0 1048574
State: (Secondary Active Int Ext)
Local AS: 1 Peer AS: 1
Age: 3:41:06 Metric: 1 Metric2: 1
Task: BGP_1.10.255.179.13+64309
Announcement bits (2): 0-KRT 1-BGP RT Background
AS path: I
Communities: target:1:200 rte-type:0.0.0.0:1:0
Import Accepted
VPN Label: 299824 TTL Action: vrf-ttl-propagate
Localpref: 100
Router ID: 10.255.179.13
Primary Routing Table bgp.l3vpn.0

show route table VPN-AB.inet.0

user@host> show route table VPN-AB.inet.0
VPN-AB.inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.39.1.0/30
10.39.1.4/30
10.39.1.6/32
10.255.71.16/32
10.255.71.17/32
10.255.71.15

10.255.71.18/32
10.255.71.15

10.255.245.245/32

10.255.245.246/32

*[OSPF/10] 00:07:24, metric 1

> via so-7/3/1.0
*[Direct/0] 00:08:42
> via so-5/1/0.0
*[Local/0] 00:08:46
Local
*[Static/5] 00:07:24
> via so-2/0/0.0
*[BGP/170] 00:07:24, MED 1, localpref 100, from
AS path: I
> via so-2/1/0.0, Push 100020, Push 100011(top)
*[BGP/170] 00:07:24, MED 1, localpref 100, from
AS path: I
> via so-2/1/0.0, Push 100021, Push 100011(top)
*[BGP/170] 00:08:35, localpref 100
AS path: 2 I
> to 10.39.1.5 via so-5/1/0.0
*[OSPF/10] 00:07:24, metric 1
> via so-7/3/1.0

show route table VPN_blue.mvpn-inet6.0

user@host> show route table VPN_blue.mvpn-inet6.0
vpn_blue.mvpn-inet6.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:10.255.2.202:65535:10.255.2.202/432
*[BGP/170] 00:02:37, localpref 100, from 10.255.2.202
AS path: I
> via so-0/1/3.0
1:10.255.2.203:65535:10.255.2.203/432
*[BGP/170] 00:02:37, localpref 100, from 10.255.2.203
AS path: I
> via so-0/1/0.0
1:10.255.2.204:65535:10.255.2.204/432
*[MVPN/70] 00:57:23, metric2 1
Indirect

2124

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

5:10.255.2.202:65535:128:::192.168.90.2:128:ffff::1/432
*[BGP/170] 00:02:37, localpref 100, from 10.255.2.202
AS path: I
> via so-0/1/3.0
6:10.255.2.203:65535:65000:128:::10.12.53.12:128:ffff::1/432
*[PIM/105] 00:02:37
Multicast (IPv6)
7:10.255.2.202:65535:65000:128:::192.168.90.2:128:ffff::1/432
*[MVPN/70] 00:02:37, metric2 1
Indirect

show route table vrf1.mvpn.0 extensive

user@host> show route table vrf1.mvpn.0 extensive
1:10.255.50.77:1:10.255.50.77/240 (1 entry, 1 announced)
*MVPN
Preference: 70
PMSI: Flags 0x0: Label 0: RSVP-TE:
Session_13[10.255.50.77:0:25624:10.255.50.77]
Next hop type: Indirect
Address: 0xbb2c944
Next-hop reference count: 360
Protocol next hop: 10.255.50.77
Indirect next hop: 0x0 - INH Session ID: 0x0
State: <Active Int Ext>
Age: 53:03
Metric2: 1
Validation State: unverified
Task: mvpn global task
Announcement bits (3): 0-PIM.vrf1 1-mvpn global task 2-rt-export
AS path: I

show route table inetflow detail

user@host> show route table inetflow detail
inetflow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.12.44.1,*/48 (1 entry, 1 announced)
*BGP
Preference: 170/-101
Next-hop reference count: 2
State: <Active Ext>
Local AS: 65002 Peer AS: 65000
Age: 4
Task: BGP_65000.10.12.99.5+3792
Announcement bits (1): 0-Flow
AS path: 65000 I
Communities: traffic-rate:0:0
Validation state: Accept, Originator: 10.12.99.5
Via: 10.12.44.0/24, Active
Localpref: 100
Router ID: 10.255.71.161
10.12.56.1,*/48 (1 entry, 1 announced)
*Flow
Preference: 5
Next-hop reference count: 2
State: <Active>
Local AS: 65002
Age: 6:30
Task: RT Flow
Announcement bits (2): 0-Flow 1-BGP.0.0.0.0+179
AS path: I
Communities: 1:1

Copyright 2014, Juniper Networks, Inc.

2125

Interfaces Fundamentals for Routing Devices

user@PE1> show route table green.l2vpn.0 (VPLS Multihoming with FEC 129)
green.l2vpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.2:100:1.1.1.2/96 AD
*[VPLS/170] 1d 03:11:03, metric2 1
Indirect
1.1.1.4:100:1.1.1.4/96 AD
*[BGP/170] 1d 03:11:02, localpref 100, from 1.1.1.4
AS path: I, validation-state: unverified
>
via ge-1/2/1.5
1.1.1.2:100:1:0/96 MH
*[VPLS/170] 1d 03:11:03, metric2 1
Indirect
1.1.1.4:100:1:0/96 MH
*[BGP/170] 1d 03:11:02, localpref 100, from 1.1.1.4
AS path: I, validation-state: unverified
>
via ge-1/2/1.5
1.1.1.4:NoCtrlWord:5:100:100:1.1.1.2:1.1.1.4/176
*[VPLS/7] 1d 03:11:02, metric2 1
>
via ge-1/2/1.5
1.1.1.4:NoCtrlWord:5:100:100:1.1.1.4:1.1.1.2/176
*[LDP/9] 1d 03:11:02
Discard
user@host> show route table red extensive
red.inet.0: 364481 destinations, 714087 routes (364480 active, 48448 holddown, 1
hidden)
22.0.0.0/32 (3 entries, 1 announced)
State: <OnList CalcForwarding>
TSI:
KRT in-kernel 22.0.0.0/32 -> {composite(1048575)} Page 0 idx 1 Type 1 val 0x934342c
Nexthop: Self
AS path: [2] I
Communities: target:2:1
Path 22.0.0.0 from 2.3.0.0 Vector len 4. Val: 1
@BGP
Preference: 170/-1
Route Distinguisher: 2:1
Next hop type: Indirect
Address: 0x258059e4
Next-hop reference count: 2
Source: 2.2.0.0
Next hop type: Router
Next hop: 10.1.1.1 via ge-1/1/9.0, selected
Label operation: Push 707633
Label TTL action: prop-ttl
Session Id: 0x17d8
Protocol next hop: 2.2.0.0
Push 16
Composite next hop: 0x25805988 - INH Session ID: 0x193c
Indirect next hop: 0x23eea900 - INH Session ID: 0x193c
State: <Secondary Active Int Ext ProtectionPath ProtectionCand>
Local AS:
2 Peer AS:
2
Age: 23
Metric2: 35
Validation State: unverified
Task: BGP_2.2.2.0.0+34549
AS path: I
Communities: target:2:1
Import Accepted

2126

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

BGP

VPN Label: 16
Localpref: 0
Router ID: 2.2.0.0
Primary Routing Table bgp.l3vpn.0
Composite next hops: 1
Protocol next hop: 2.2.0.0 Metric: 35
Push 16
Composite next hop: 0x25805988 - INH Session ID: 0x193c
Indirect next hop: 0x23eea900 - INH Session ID: 0x193c
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.1.1.1 via ge-1/1/9.0
Session Id: 0x17d8
2.2.0.0/32 Originating RIB: inet.3
Metric: 35
Node path count: 1
Forwarding nexthops: 1
Nexthop: 10.1.1.1 via ge-1/1/9.0
Preference: 170/-1
Route Distinguisher: 2:1
Next hop type: Indirect
Address: 0x9347028
Next-hop reference count: 3
Source: 2.3.0.0
Next hop type: Router, Next hop index: 702
Next hop: 10.1.4.2 via ge-1/0/0.0, selected
Label operation: Push 634278
Label TTL action: prop-ttl
Session Id: 0x17d9
Protocol next hop: 2.3.0.0
Push 16
Composite next hop: 0x93463a0 1048575 INH Session ID: 0x17da
Indirect next hop: 0x91e8800 1048574 INH Session ID: 0x17da
State: <Secondary NotBest Int Ext ProtectionPath ProtectionCand>
Inactive reason: Not Best in its group - IGP metric
Local AS:
2 Peer AS:
2
Age: 3:34
Metric2: 70
Validation State: unverified
Task: BGP_2.2.3.0.0+32805
Announcement bits (2): 0-KRT 1-BGP_RT_Background
AS path: I
Communities: target:2:1
Import Accepted
VPN Label: 16
Localpref: 0
Router ID: 2.3.0.0
Primary Routing Table bgp.l3vpn.0
Composite next hops: 1
Protocol next hop: 2.3.0.0 Metric: 70
Push 16
Composite next hop: 0x93463a0 1048575 INH Session ID:

0x17da
Indirect next hop: 0x91e8800 1048574 INH Session ID:
0x17da
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.1.4.2 via ge-1/0/0.0
Session Id: 0x17d9
2.3.0.0/32 Originating RIB: inet.3
Metric: 70
Node path count: 1
Forwarding nexthops: 1

Copyright 2014, Juniper Networks, Inc.

2127

Interfaces Fundamentals for Routing Devices

Nexthop: 10.1.4.2 via ge-1/0/0.0

#Multipath Preference: 255
Next hop type: Indirect
Address: 0x24afca30
Next-hop reference count: 1
Next hop type: Router
Next hop: 10.1.1.1 via ge-1/1/9.0, selected
Label operation: Push 707633
Label TTL action: prop-ttl
Session Id: 0x17d8
Next hop type: Router, Next hop index: 702
Next hop: 10.1.4.2 via ge-1/0/0.0
Label operation: Push 634278
Label TTL action: prop-ttl
Session Id: 0x17d9
Protocol next hop: 2.2.0.0
Push 16
Composite next hop: 0x25805988 - INH Session ID: 0x193c
Indirect next hop: 0x23eea900 - INH Session ID: 0x193c Weight 0x1
Protocol next hop: 2.3.0.0
Push 16
Composite next hop: 0x93463a0 1048575 INH Session ID: 0x17da
Indirect next hop: 0x91e8800 1048574 INH Session ID: 0x17da Weight
0x4000
State: <ForwardingOnly Int Ext>
Inactive reason: Forwarding use only
Age: 23
Metric2: 35
Validation State: unverified
Task: RT
AS path: I
Communities: target:2:1

2128

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

show route terse

List of Syntax

Syntax on page 2129

Syntax (EX Series Switches) on page 2129

Syntax

show route terse

<logical-system (all | logical-system-name)>

Syntax (EX Series

Switches)

show route terse

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description

Display a high-level summary of the routes in the routing table.

NOTE: For BGP routes, the show route terse command displays the local
preference attribute and MED instead of the metric1 and metric2 values. This
is mostly due to historical reasons.
To display the metric1 and metric2 value of a BGP route, use the show route
extensive command.

Options

noneDisplay a high-level summary of the routes in the routing table.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level

view

List of Sample Output

show route terse on page 2131

Output Fields

Table 211 on page 2129 describes the output fields for the show route terse command.
Output fields are listed in the approximate order in which they appear.

Table 211: show route terse Output Fields

Field Name

Field Description

routing-table-name

Name of the routing table (for example, inet.0).

number destinations

Number of destinations for which there are routes in the routing table.

number routes

Number of routes in the routing table and total number of routes in the following states:

active (routes that are active)

holddown (routes that are in the pending state before being declared inactive)

hidden (routes that are not used because of a routing policy)

Copyright 2014, Juniper Networks, Inc.

2129

Interfaces Fundamentals for Routing Devices

Table 211: show route terse Output Fields (continued)

Field Name

Field Description

route key

Key for the state of the route:

+A plus sign indicates the active route, which is the route installed from the routing table into the

forwarding table.

- A hyphen indicates the last active route.

*An asterisk indicates that the route is both the active and the last active route. An asterisk before
a to line indicates the best subpath to the route.

Active route. An asterisk (*) indicates this is the active route.

Validation status of the route:

?Not evaluated. Indicates that the route was not learned through BGP.

IInvalid. Indicates that the prefix is found, but either the corresponding AS received from the EBGP

peer is not the AS that appears in the database, or the prefix length in the BGP update message is
longer than the maximum length permitted in the database.

NUnknown. Indicates that the prefix is not among the prefixes or prefix ranges in the database.

VValid. Indicates that the prefix and autonomous system pair are found in the database.

Destination

Destination of the route.

Protocol through which the route was learned:

AAggregate

BBGP

CCCC

DDirect

GGMPLS

IIS-IS

LL2CKT, L2VPN, LDP, Local

KKernel

MMPLS, MSDP

OOSPF

PPIM

RRIP, RIPng

SStatic

TTunnel

Prf

Preference value of the route. In every routing metric except for the BGP LocalPref attribute, a lesser
value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement
of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100,
the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156.
Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value.

Metric 1

First metric value in the route. For routes learned from BGP, this is the MED metric.

Metric 2

Second metric value in the route. For routes learned from BGP, this is the IGP metric.

2130

Copyright 2014, Juniper Networks, Inc.

Chapter 25: Protocol-Independent Routing Operational Commands

Table 211: show route terse Output Fields (continued)

Field Name

Field Description

Next hop

Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.

AS path

AS path through which the route was learned. The letters at the end of the AS path indicate the path
origin, providing an indication of the state of the route at the point at which the AS path originated:

IIGP.

EEGP.

?Incomplete; typically, the AS path was aggregated.

Sample Output
show route terse
user@host> show route terse
inet.0: 10 destinations, 12 routes (10 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
A V Destination
* ? 1.0.1.1/32
?
unverified
* ? 1.1.1.1/32
* V 2.2.0.2/32
valid
* ? 10.0.0.0/30
?
unverified
* ? 10.0.0.1/32
* ? 10.0.0.4/30
unverified
* ? 10.0.0.8/30
unverified
* I 172.16.1.1/32
invalid
* N 192.168.2.3/32
unknown
* ? 224.0.0.5/32

Copyright 2014, Juniper Networks, Inc.

P Prf
O 10
B 170
D
0
B 170
D
0
B 170
L
0
B 170

Metric 1
1
100

Metric 2

Next hop
>10.0.0.2

AS path
I

>10.0.0.2
>lo0.2
110

200 I
>10.0.0.2
>lt-1/2/0.1

100

I
>10.0.0.2
Local

100

I
>10.0.0.2

B 170

100

I
>10.0.0.2

B 170

90

200 I
>10.0.0.2

B 170
O

10

100
1

200 I
>10.0.0.2
MultiRecv

2131

Interfaces Fundamentals for Routing Devices

2132

Copyright 2014, Juniper Networks, Inc.

CHAPTER 26

RIP Operational Commands

clear rip general-statistics

clear rip statistics

show rip general-statistics

show rip neighbor

show rip statistics

Copyright 2014, Juniper Networks, Inc.

2133

Interfaces Fundamentals for Routing Devices

clear rip general-statistics

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

Syntax on page 2134

Syntax (EX Series Switches and QFX Series) on page 2134
clear rip general-statistics
<logical-system (all | logical-system-name)>
clear rip general-statistics

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 12.1 for the QFX Series.
Clear RIP general statistics.
noneClear RIP general statistics.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show rip general-statistics on page 2136

clear rip general-statistics on page 2134

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear rip general-statistics
user@host> clear rip general-statistics

2134

Copyright 2014, Juniper Networks, Inc.

Chapter 26: RIP Operational Commands

clear rip statistics

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

Syntax on page 2135

Syntax (EX Series Switches and QFX Series) on page 2135
clear rip statistics
<instance (all | instance-name)>
<logical-system (all | logical-system-name)>
<neighbor>
<peer (all | address)>
clear rip statistics
<instance (all | instance-name)>
<neighbor>

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 12.1 for the QFX Series.
Clear RIP statistics.
noneReset RIP counters for all neighbors for all routing instances.
instance (all | instance-name)(Optional) Clear RIP statistics for all instances or for the

specified routing instance only.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor(Optional) Clear RIP statistics for the specified neighbor only.
peer (all | address)(Optional) Clear RIP statistics for a single peer or all peers.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show rip statistics on page 2140

clear rip statistics on page 2135

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear rip statistics
user@host> clear rip statistics

Copyright 2014, Juniper Networks, Inc.

2135

Interfaces Fundamentals for Routing Devices

show rip general-statistics

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

Syntax on page 2136

Syntax (EX Series Switches and QFX Series) on page 2136
show rip general-statistics
<logical-system (all | logical-system-name)>
show rip general-statistics

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 12.1 for the QFX Series.
Display brief RIP statistics.
noneDisplay brief RIP statistics.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

clear rip general-statistics on page 2134

show rip general-statistics on page 2136

Table 212 on page 2136 lists the output fields for the show rip general-statistics command.
Output fields are listed in the approximate order in which they appear.

Table 212: show rip general-statistics Output Fields

Field Name

Field Description

bad msgs

Number of invalid messages received.

no recv intf

Number of packets received with no matching interface.

curr memory

Amount of memory currently used by RIP.

max memory

Most memory used by RIP.

Sample Output
show rip general-statistics
user@host> show rip general-statistics

2136

Copyright 2014, Juniper Networks, Inc.

Chapter 26: RIP Operational Commands

RIPv2 I/O info:

bad msgs
no recv intf
curr memory
max memory

Copyright 2014, Juniper Networks, Inc.

:
:
:
:

0
0
0
0

2137

Interfaces Fundamentals for Routing Devices

show rip neighbor

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description
Options

Syntax on page 2138

Syntax (EX Series Switches and QFX Series) on page 2138
show rip neighbor
<instance (all | instance-name)>
<logical-system (all | logical-system-name)>
<name>
show rip neighbor
<instance (all | instance-name)>
<name>

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 12.1 for the QFX Series.
Display information about RIP neighbors.
noneDisplay information about all RIP neighbors for all instances.
instance (all | instance-name)(Optional) Display RIP neighbor information for all

instances or for only the specified routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

name(Optional) Display detailed information about only the specified RIP neighbor.

Required Privilege
Level
List of Sample Output

Output Fields

2138

view

show rip neighbor on page 2139

show rip neighbor (With Demand Circuits Configured) on page 2139
Table 213 on page 2139 lists the output fields for the show rip neighbor command. Output
fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 26: RIP Operational Commands

Table 213: show rip neighbor Output Fields

Field Name

Field Description

Neighbor

Name of the RIP neighbor.

NOTE: Beginning with Junos OS Release 11.1, when you configure
demand circuits, the output displays a demand circuit (DC) flag
next to neighbor interfaces configured for demand circuits.
If you configure demand circuits at the [edit protocols rip group
group-name neighbor neighbor-name] hierarchy level, the output
shows only the neighboring interface that you specifically configured
as a demand circuit. If you configure demand circuits at the [edit
protocols rip group group-name] hierarchy level, all of the interfaces
in the group are configured as demand circuits. Therefore, the output
shows all of the interfaces in that group as demand circuits.

State

State of the connection: Up or Dn (Down).

Source Address

Address of the port on the local router.

Destination Address

Address of the port on the remote router.

Send Mode

Send options: broadcast, multicast, none, or version 1.

Receive Mode

Type of packets to accept: both, none, version 1, or version 2.

In Met

Metric added to incoming routes when advertising into RIP routes

that were learned from other protocols.

Sample Output
show rip neighbor
user@host> show rip neighbor
Local Source
Neighbor
State Address
------------ ------ge-2/3/0.0
Up 192.168.9.105
at-5/1/1.42
Dn (null)
at-5/1/0.42
Dn (null)
at-5/1/0.0
Up 20.0.0.1
so-0/0/0.0
Up 192.168.9.97

Destination
Address
----------192.168.9.107
(null)
(null)
224.0.0.9
224.0.0.9

Send
Mode
---bcast
mcast
mcast
mcast
mcast

Destination
Address
----------224.0.0.9
224.0.0.9

Send
Mode
---mcast
mcast

Receive
Mode
------both
v2 only
both
both
both

In
Met
--1
3
3
3
3

show rip neighbor (With Demand Circuits Configured)

user@host> show rip neighbor
Local Source
Neighbor
State Address
------------ ------so-0/1/0.0(DC)
Up 10.10.10.2
so-0/2/0.0(DC)
Up 13.13.13.2

Copyright 2014, Juniper Networks, Inc.

Receive
Mode
------both
both

In
Met
--1
1

2139

Interfaces Fundamentals for Routing Devices

show rip statistics

List of Syntax

Syntax

Syntax (EX Series

Switches and QFX
Series)
Release Information

Description

Options

Syntax on page 2140

Syntax (EX Series Switches and QFX Series) on page 2140
show rip statistics
<instance (all | instance-name)>
<logical-system (all | logical-system-name)>
<name>
<peer (all | address)>
show rip statistics
<instance (all | instance-name)>
<name>

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 12.1 for the QFX Series.
Display RIP statistics about messages sent and received on an interface, as well as
information received from advertisements from other routing devices.
noneDisplay RIP statistics for all routing instances.
instance (all | instance-name)(Optional) Display RIP statistics for all instances or for

only the specified routing instance.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

name(Optional) Display detailed information about only the specified RIP neighbor.
peer (all | address)(Optional) Display RIP statistics for a single peer or all peers.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

2140

view

clear rip statistics on page 2135

show rip statistics on page 2141

Table 214 on page 2141 lists the output fields for the show rip statistics command. Output
fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 26: RIP Operational Commands

Table 214: show rip statistics Output Fields

Field Name

Field Description

RIP info

Information about RIP on the specified interface:

portUDP port number used for RIP.

update intervalInterval between routing table updates, in seconds.

holddownHold-down interval, in seconds.

timeoutTimeout interval, in seconds.

restart in progressGraceful restart status. Displayed when RIP is or has been in the process of

graceful restart.

logical-interface

Counter

restart timeEstimated time for the graceful restart to finish, in seconds.

restart will complete inRemaining time for the graceful restart to finish, in seconds.

rts learnedNumber of routes learned through RIP.

rts held downNumber of routes held down by RIP.

rqsts droppedNumber of received request packets that were dropped.

resps droppedNumber of received response packets that were dropped.

Name of the logical interface and its statistics:

routes learnedNumber of routes learned on the logical interface.

routes advertisedNumber of routes advertised by the logical interface.

List of counter types:

Updates SentNumber of update messages sent.

Triggered Updates SentNumber of triggered update messages sent.

Responses SentNumber of response messages sent.

Bad MessagesNumber of invalid messages received.

RIPv1 Updates ReceivedNumber of RIPv1 update messages received.

RIPv1 Bad Route EntriesNumber of RIPv1 invalid route entry messages received.

RIPv1 Updates IgnoredNumber of RIPv1 update messages ignored.

RIPv2 Updates ReceivedNumber of RIPv2 update messages received.

RIPv2 Bad Route EntriesNumber of RIPv2 invalid route entry messages received.

RIPv2 Updates IgnoredNumber of RIPv2 update messages ignored.

Authentication FailuresNumber of received update messages that failed authentication.

RIP Requests ReceivedNumber of RIP request messages received.

RIP Requests IgnoredNumber of RIP request messages ignored.

Total

Total number of packets for the selected counter.

Last 5 min

Number of packets for the selected counter in the most recent 5-minute period.

Last minute

Number of packets for the selected counter in the most recent 1-minute period.

Sample Output
show rip statistics
user@host> show rip statistics so-0/0/0.0

Copyright 2014, Juniper Networks, Inc.

2141

Interfaces Fundamentals for Routing Devices

RIP info: port 520; update interval: 30s; holddown 180s; timeout 120s
restart in progress: restart time 60s; restart will complete in 55s
rts learned rts held down rqsts dropped resps dropped
0
0
0
0
so-0/0/0.0: 0 routes learned; 501 routes advertised
Counter
Total
Last 5 min Last minute
----------------- ----------- ----------Updates Sent
0
0
0
Triggered Updates Sent
0
0
0
Responses Sent
0
0
0
Bad Messages
0
0
0
RIPv1 Updates Received
0
0
0
RIPv1 Bad Route Entries
0
0
0
RIPv1 Updates Ignored
0
0
0
RIPv2 Updates Received
0
0
0
RIPv2 Bad Route Entries
0
0
0
RIPv2 Updates Ignored
0
0
0
Authentication Failures
0
0
0
RIP Requests Received
0
0
0
RIP Requests Ignored
0
0
0

2142

Copyright 2014, Juniper Networks, Inc.

CHAPTER 27

RIPng Operational Commands

clear ripng general-statistics

clear ripng statistics

show ripng general-statistics

show ripng neighbor

show ripng statistics

Copyright 2014, Juniper Networks, Inc.

2143

Interfaces Fundamentals for Routing Devices

clear ripng general-statistics

List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description
Options

Syntax on page 2144

Syntax (EX Series Switches) on page 2144
clear ripng general-statistics
<logical-system (all | logical-system-name)>
clear ripng general-statistics

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Clear RIP next generation (RIPng) general statistics.
noneClear RIPng general statistics.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show ripng general-statistics on page 2146

clear ripng general-statistics on page 2144

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ripng general-statistics
user@host> clear ripng general-statistics

2144

Copyright 2014, Juniper Networks, Inc.

Chapter 27: RIPng Operational Commands

clear ripng statistics

List of Syntax

Syntax

Syntax (EX Series

Switch)
Release Information

Description
Options

Syntax on page 2145

Syntax (EX Series Switch) on page 2145
clear ripng statistics
<instance | name>
<logical-system (all | logical-system-name)>
clear ripng statistics
<instance | name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Clear RIP next-generation (RIPng) statistics.
noneReset RIPng counters for all neighbors for all routing instances.
instance(Optional) Reset RIPng counters for the specified instance.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

name(Optional) Reset RIPng counters for the specified neighbor.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

clear

show ripng statistics on page 2150

clear ripng statistics on page 2145

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear ripng statistics
user@host> clear ripng statistics

Copyright 2014, Juniper Networks, Inc.

2145

Interfaces Fundamentals for Routing Devices

show ripng general-statistics

List of Syntax

Syntax

Syntax (EX Series

Switch)
Release Information

Description
Options

Syntax on page 2146

Syntax (EX Series Switch) on page 2146
show ripng general-statistics
<logical-system (all | logical-system-name)>
show ripng general-statistics

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display general RIP next-generation (RIPng) statistics.
noneDisplay general RIPng statistics.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

clear ripng general-statistics on page 2144

show ripng general-statistics on page 2146

Table 215 on page 2146 lists the output fields for the show ripng general-statistics command.
Output fields are listed in the approximate order in which they appear.

Table 215: show ripng general-statistics Output Fields

Field Name

Field Description

bad msgs

Number of invalid messages received.

no recv intf

Number of packets received with no matching interface.

curr memory

Amount of memory currently used by RIPng.

max memory

Most memory used by RIPng.

Sample Output
show ripng general-statistics
user@host> show ripng general-statistics
RIPng I/O info:
bad msgs
:
0
no recv intf
:
0

2146

Copyright 2014, Juniper Networks, Inc.

Chapter 27: RIPng Operational Commands

curr memory
max memory

Copyright 2014, Juniper Networks, Inc.

:
:

0
0

2147

Interfaces Fundamentals for Routing Devices

show ripng neighbor

List of Syntax

Syntax

Syntax (EX Series

Switch)
Release Information

Description
Options

Syntax on page 2148

Syntax (EX Series Switch) on page 2148
show ripng neighbor
<logical-system (all | logical-system-name)>
<name>
show ripng neighbor
<name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display information about RIP next-generation (RIPng) neighbors.
noneDisplay information about all RIPng neighbors.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

name(Optional) Display detailed information about a specific RIPng neighbor.

Required Privilege
Level
List of Sample Output
Output Fields

view

show ripng neighbor on page 2149

Table 216 on page 2148 lists the output fields for the show ripng neighbor command. Output
fields are listed in the approximate order in which they appear.

Table 216: show ripng neighbor Output Fields

2148

Field Name

Field Description

Neighbor

Name of RIPng neighbor.

State

State of the connection: Up or Dn (Down).

Source Address

Source address.

Destination Address

Destination address.

Send

Send options: broadcast, multicast, none, version 1, or yes.

Recv

Type of packets to accept: both, none, version 1, or yes.

In Met

Metric added to incoming routes when advertising into RIPng routes

that were learned from other protocols.

Copyright 2014, Juniper Networks, Inc.

Chapter 27: RIPng Operational Commands

Sample Output
show ripng neighbor
user@host> show ripng neighbor
Source
Neighbor
State Address
------------ ------fe-0/0/2.0
Up fe80::290:69ff:fe68:b002

Copyright 2014, Juniper Networks, Inc.

Dest
Address
------ff02::9

In
Send Recv Met
---- ---- --yes yes
1

2149

Interfaces Fundamentals for Routing Devices

show ripng statistics

List of Syntax

Syntax

Syntax (EX Series

Switch)
Release Information

Description

Options

Syntax on page 2150

Syntax (EX Series Switch) on page 2150
show ripng statistics
<logical-system (all | logical-system-name)>
<name>
show ripng statistics
<name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Display RIP next generation (RIPng) statistics about messages sent and received on an
interface, as well as information received from advertisements from other routing devices.
noneDisplay RIPng statistics for all neighbors.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

name(Optional) Display detailed information about a specific RIPng neighbor.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

clear ripng statistics on page 2145

show ripng statistics on page 2151

Table 217 on page 2150 lists the output fields for the show ripng statistics command. Output
fields are listed in the approximate order in which they appear.

Table 217: show ripng statistics Output Fields

Field Name

Field Description

RIPng info

Information about RIPng on the specified interface:

2150

portUDP port number used for RIPng.

holddownHold-down interval, in seconds.

rts learnedNumber of routes learned through RIPng.

rts held downNumber of routes held down by RIPng.

rqsts droppedNumber of received request packets that were dropped.

resps droppedNumber of received response packets that were dropped.

restartGraceful restart status. Displayed when RIPng is or has been in the process of graceful restart.

Copyright 2014, Juniper Networks, Inc.

Chapter 27: RIPng Operational Commands

Table 217: show ripng statistics Output Fields (continued)

Field Name

Field Description

logical-interface

Name of the logical interface and its statistics:

Counter

routes learnedNumber of routes learned on the logical interface.

routes advertisedNumber of routes advertised by the logical interface.

timeoutTimeout interval, in seconds.

update intervalInterval between routing table updates, in seconds.

List of counter types:

Updates SentNumber of update messages sent.

Triggered Updates SentNumber of triggered update messages sent.

Responses SentNumber of response messages sent.

Bad MessagesNumber of invalid messages received.

Updates ReceivedNumber of RIPng update messages received.

Bad Route EntriesNumber of RIPng invalid route entry messages received.

Updates IgnoredNumber of RIPng update messages ignored.

RIPng Requests ReceivedNumber of RIPng request messages received.

RIPng Requests IgnoredNumber of RIPng request messages ignored.

Total

Total number of packets for the selected counter.

Last 5 min

Number of packets for the selected counter in the most recent 5-minute period.

Last minute

Number of packets for the selected counter in the most recent 1-minute period.

Sample Output
show ripng statistics
user@host> show ripng statistics
RIPng info: port 521; holddown 120s;
rts learned rts held down rqsts dropped
0
0
0

resps dropped
0

so-0/1/3.0: 0 routes learned; 1 routes advertised; timeout 180s; update interval

20s
Counter
Total
Last 5 min Last minute
----------------- ----------- ----------Updates Sent
934
16
4
Triggered Updates Sent
1
0
0
Responses Sent
0
0
0
Bad Messages
0
0
0
Updates Received
0
0
0
Bad Route Entries
0
0
0
Updates Ignored
0
0
0
RIPng Requests Received
0
0
0
RIPng Requests Ignored
0
0
0

Copyright 2014, Juniper Networks, Inc.

2151

Interfaces Fundamentals for Routing Devices

2152

Copyright 2014, Juniper Networks, Inc.

CHAPTER 28

Firewall Filter Operational Commands

clear firewall

show firewall

show firewall filter version

show firewall log

show firewall prefix-action-stats

show firewall templates-in-use

show policer

Copyright 2014, Juniper Networks, Inc.

2153

Interfaces Fundamentals for Routing Devices

clear firewall
List of Syntax

Syntax

Syntax (EX Series

Switches)
Release Information

Description

Syntax on page 2154

Syntax (EX Series Switches) on page 2154
clear firewall (all | counter counter-name | filter filter-name | log (all | logical-system-name
) | logical-system logical-system-name)
clear firewall (all | counter counter-name | filter filter-name | log (all | logical-system-name)
| policer counter (all | counter-id counter-index))

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
logical-system option introduced in Junos OS Release 9.3.
log option introduced before Junos OS Release 11.4.
Clear statistics about configured firewall filters.
When you clear the counters of a filter, this impacts not only the counters shown by the
CLI, but also the ones tracked by SNMP2.
Subscriber management uses firewall filters to capture and report the volume-based
service accounting counters that are used for subscriber billing. The clear firewall
command also clears the service accounting counters that are reported to the RADIUS
accounting server. For this reason, you must be cautious in specifying which firewall
statistics you want to clear.

NOTE: The clear firewall command cannot be used to clear the Routing Engine
filter counters on a backup Routing Engine that is enabled for graceful Routing
Engine switchover (GRES).

If you clear statistics for firewall filters that are applied to Trio-based DPCs and that also
use the prefix-action action on matched packets, wait at least 5 seconds before you enter
the show firewall prefix-action-stats command. A 5-second pause between issuing the
clear firewall and show firewall prefix-action-stats commands avoids a possible timeout
of the show firewall prefix-action-stats command.
Options

allClear the packet and byte counts for all filters. On EX Series switches, this option

also clears the packet counts for all policer counters.

counter counter-nameClear the packet and byte counts for a filter counter that has been

configured with the counter firewall filter action.

filter filter-nameClear the packet and byte counts for the specified firewall filter.
log (all | logical-system-name)Clear log entries for IPv4 firewall filters that have then
log as an action. Use log all to clear all log entries or log logical-system-name to clear

log entries for the specified logical system.

2154

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

logical-system logical-system-nameClear the packet and byte counts for the specified

logical system.
policer counter (all | counter-id counter-index)(EX8200 switches only) Clear all policer

counters using the policer counter all command, or clear a specific policer counter
using the policer counter counter-id counter-index command. The value of
counter-index can be 0, 1, or 2.
Required Privilege
Level
Related
Documentation
List of Sample Output

clear

show firewall on page 2156

clear firewall all on page 2155

clear firewall (counter counter-name) on page 2155
clear firewall (filter filter-name) on page 2155
clear firewall (policer counter all) (EX8200 Switch) on page 2155
clear firewall (policer counter counter-id counter-index) (EX8200 Switch) on page 2155

Sample Output
clear firewall all
user@host> clear firewall all

clear firewall (counter counter-name)

user@host> clear firewall counter port-filter-counter

clear firewall (filter filter-name)

user@host> clear firewall filter ingress-port-filter

clear firewall (policer counter all) (EX8200 Switch)

user@switch> clear firewall policer counter all

clear firewall (policer counter counter-id counter-index) (EX8200 Switch)

user@switch> clear firewall policer counter counter-id 0

Copyright 2014, Juniper Networks, Inc.

2155

Interfaces Fundamentals for Routing Devices

show firewall
List of Syntax

Syntax

Syntax (EX Series

Switches)

Release Information

Description
Options

Syntax on page 2156

Syntax (EX Series Switches) on page 2156
show firewall
<counter counter-name>
<detail>
<filter (filter-name | regex regular-expression)>
<log>
<logical-system (all | logical-system-name)>
<terse>
show firewall
<counter counter-name>
<detail>
<filter filter-name>
<log <(detail | interface interface-name)>>
<policer counters <(detail | counter-id counter-index <detail>)>>
<terse>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Option logical-system introduced in Junos OS Release 9.3.
Option terse introduced in Junos OS Release 9.4.
Option policer counters introduced in Junos OS Release 12.2 for EX Series switches.
Option detail introduced in Junos OS Release 12.3 for EX Series switches.
Option detail introduced in Junos OS Release 14.1 for MX Series routers.
Option regex regular-expression introduced in Junos OS Release 14.2.
Display enhanced statistics and counters for all configured firewall filters.
none(Optional) Display statistics and counters for all configured firewall filters and

counters. For EX Series switches, this command also displays statistics about all
configured policers.
counter counter-name(Optional) Name of a filter counter.
detail(EX Series switches and MX Series routers only) (Optional) Display firewall filter

statistics and enhanced policer statistics and counters.

filter filter-name(Optional) Name of a configured filter.
filter regex regular-expression(Optional) Regular expression that matches the names

of a subset of filters.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

log(Optional) Display log entries for firewall filters.

2156

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

log <(detail | interface interface-name)>(EX Series switches only) (Optional) Display

detailed log entries of firewall activity or log information about a specific interface.
policer counters <(detail | counter-id counter-index <detail>)>(EX8200 switches only)

(Optional) Display policer counter statistics in brief or in detail.

terse(Optional) Display firewall filter names only.

Required Privilege
Level
Related
Documentation

view

clear firewall on page 2154

show firewall log on page 2164

show policer on page 2171

Enhanced Policer Statistics Overview

enhanced-policer

List of Sample Output

show firewall filter (MX Series Router and EX Series Switch) on page 2160
show firewall filter (non MX Series Router and EX Series Switch) on page 2160
show firewall filter (Dynamic Input Filter) on page 2160
show firewall (Logical Systems) on page 2160
show firewall (counter counter-name) on page 2161
show firewall log on page 2161
show firewall policer counters (EX8200 Switch) on page 2161
show firewall policer counters (detail) (EX8200 Switch) on page 2161
show firewall policer counters (counter-id counter-index) (EX8200 Switch) on page 2162
show firewall policer counters (counter-id counter-index detail) (EX8200
Switch) on page 2162
show firewall detail on page 2162

Output Fields

Table 218 on page 2158 lists the output fields for the show firewall command. Output fields
are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

2157

Interfaces Fundamentals for Routing Devices

Table 218: show firewall Output Fields

Field Name

Field Description

Filter

Name of a filter that has been configured with the filter statement at the [edit firewall] hierarchy
level.
Except on EX Series switches:

When an interface-specific filter is displayed, the name of the filter is followed by the full
interface name and by either -i for an input filter or -o for an output filter.

When dynamic filters are displayed, the name of the filter is followed by the full interface name
and by either -in for an input filter or -out for an output filter. When a logical systemspecific
filter is displayed, the name of the filter is prefixed with two underscore (__) characters and the
name of the logical system (for example, __ls1/filter1).

When a service filter is displayed that uses a service set, the separator between the service-set
name and the service-filter name is a semicolon (:).
NOTE: For bridge family filter, the ip-protocol match criteria is supported only for IPv4 and not
for IPv6. This is applicable for line cards that support the Junos Trio chipset, such as the MX 3D
MPC line cards.

Counters

Display filter counter information:

NameName of a filter counter that has been configured with the counter firewall filter action.

BytesNumber of bytes that match the filter term under which the counter action is specified.

PacketsNumber of packets that matched the filter term under which the counter action is

specified.
NOTE: On M and T series routers, firewall filters cannot count ip-options packets on a per option
type and per interface basis. A limited work around is to use the show pfe statistics ip options
command to see ip-options statistics on a per Packet Forwarding Engine (PFE) basis. See show
pfe statistics ip for sample output.
Policers

Display policer information:

NameName of policer.

Bytes(For two-color policers on MX Series routers and EX Series switches, and for hierarchical

policers on MS-DPC, MIC, and MPC interfaces on MX Series routers) Number of bytes that
match the filter term under which the policer action is specified. This is only the number
out-of-specification (out-of-spec) byte counts, not all the bytes in all packets policed by the
policer.
For other combinations of policer type, device, and line card type, this field is blank.

PacketsNumber of packets that matched the filter term under which the policer action is

specified. This is only the number of out-of-specification (out-of-spec) packet counts, not all
packets policed by the policer.
Policer Counter Index

(EX8200 switch only) Global management counter ID. The counter ID value (counter-index) can
be 0, 1, or 2.

Green

(EX8200 switch only) Number of packets within the limits. The number of packets is smaller than
the committed information rate (CIR).

Yellow

(EX8200 switch only) Number of packets partially within the limits. The number of packets is
greater than the CIR, but the burst size is within the excess burst size (EBS) limit.

2158

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

Table 218: show firewall Output Fields (continued)

Field Name

Field Description

Discard

(EX8200 switch only) Number of discarded packets.

Bytes

(EX8200 switch only) Number of green, yellow, red, or discarded packets in bytes.

Packets

(EX8200 switch only) Number of green, yellow, red, or discarded packets.

Filter name

(EX8200 switch only) Name of the filter with a term associated to a policer.

Term name

(EX8200 switch only) Name of the term associated with a policer.

Policer name

(EX8200 switch only) Name of the policer that is associated with a global management counter.

P1-t1

OOS packet statistics for packets that are marked out-of-specification (out-of-spec) by the
policer. Changes to all packets that have out-of-spec actions, such as discard, color marking,
or forwarding-class, are included in this counter.

Offered packet statistics for traffic subjected to policing.

Transmitted packet statistics for traffic that is not discarded by the policer. When the policer
action is discard, the statistics are the same as the in-spec statistics; when the policer action
is non-discard (loss-priority or forwarding-class), the statistics are included in this counter.

Copyright 2014, Juniper Networks, Inc.

2159

Interfaces Fundamentals for Routing Devices

Sample Output
show firewall filter (MX Series Router and EX Series Switch)
user@host> show firewall filter test
Filter: test
Counters:
Name
Counter-1
Counter-2
Policers:
Name
Policer-1

Bytes
0
0

Packets
0
0

Bytes
2770

Packets
70

show firewall filter (non MX Series Router and EX Series Switch)

user@host> show firewall filter test
Filter: test
Counters:
Name
Counter-1
Counter-2
Policers:
Name
Policer-1

Bytes
0
0

Packets
0
0

Bytes

Packets
70

show firewall filter (Dynamic Input Filter)

user@host> show firewall filter dfwd-ge-5/0/0.1-in
Filter: dfwd-ge-5/0/0.1-in
Counters:
Name
c1-ge-5/0/0.1-in

Bytes
0

Packets
0

Bytes
420

Packets
5

Bytes
0
0

Packets
0
0

Bytes
0
0

Packets
0
0

Bytes
0
0

Packets
0
0

show firewall (Logical Systems)

user@host> show firewall
Filter: __lr1/test
Counters:
Name
icmp
Filter: __default_bpdu_filter__
Filter: __lr1/inet_filter1
Counters:
Name
inet_tcp_count
inet_udp_count
Filter: __lr1/inet_filter2
Counters:
Name
inet_icmp_count
inet_pim_count
Filter: __lr2/inet_filter1
Counters:
Name
inet_tcp_count
inet_udp_count

2160

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

show firewall (counter counter-name)

user@host> show firewall counter icmp-counter
Filter: ingress-port-voip-class-filter
Counters:
Name
icmp-counter

Bytes
0

Packets
0

show firewall log

user@host> show firewall log
Log :
Time

Filter
Action
Dest Addr
08:00:53 pfe
R
192.168.3.4
08:00:52 pfe
R
192.168.3.4
08:00:51 pfe
R
192.168.3.4
08:00:50 pfe
R
192.168.3.4
08:00:49 pfe
R
192.168.3.4
08:00:48 pfe
R
192.168.3.4
08:00:47 pfe
R
192.168.3.4

Interface

Protocol

Src Addr

ge-1/0/1.0

ICMP

192.168.3.5

ge-1/0/1.0

ICMP

192.168.3.5

ge-1/0/1.0

ICMP

192.168.3.5

ge-1/0/1.0

ICMP

192.168.3.5

ge-1/0/1.0

ICMP

192.168.3.5

ge-1/0/1.0

ICMP

192.168.3.5

ge-1/0/1.0

ICMP

192.168.3.5

show firewall policer counters (EX8200 Switch)

user@switch> show firewall policer counters
Policer Counter Index 0:
Bytes
Green:
73
Yellow:
9
Discard:
119

Packets
15914
1962
25942

Policer Counter Index 1:

Green:
Yellow:
Discard:

Bytes
0
0
0

Packets
0
0
0

Bytes
0
0
0

Packets
0
0
0

Policer Counter Index 2:

Green:
Yellow:
Discard:

show firewall policer counters (detail) (EX8200 Switch)

user@switch> show firewall policer counters detail
Policer Counter Index 0:
Bytes
Packets
Green:
73
15914
Yellow:
9
1962
Discard:
119
25942

Copyright 2014, Juniper Networks, Inc.

2161

Interfaces Fundamentals for Routing Devices

Filter name
myfilter
inet-filter-ae
inet-filter-ae

Term name
polcr-term-1
ae-snmp
ae-ssh

Policer name
myfilter-polcr-1
policer-1
policer-2

Policer Counter Index 1:

Green:
Yellow:
Discard:
Filter name

Bytes
0
0
0
Term name

Packets
0
0
0
Policer name

Policer Counter Index 2:

Green:
Yellow:
Discard:
Filter name

Bytes
0
0
0
Term name

Packets
0
0
0
Policer name

show firewall policer counters (counter-id counter-index) (EX8200 Switch)

user@switch> show firewall policer counters counter-id 0
Policer Counter Index 0:
Bytes
Packets
Green:
73
15914
Yellow:
9
1962
Discard:
119
25942

show firewall policer counters (counter-id counter-index detail) (EX8200 Switch)

user@switch> show firewall policer counters counter-id 0 detail
Policer Counter Index 0:
Bytes
Packets
Green:
73
15914
Yellow:
9
1962
Discard:
119
25942
Filter name
myfilter
inet-filter-ae
inet-filter-ae

Term name
polcr-term-1
ae-snmp
ae-ssh

Policer name
myfilter-polcr-1
policer-1
policer-2

show firewall detail

user@host> show firewall detail
Filter: __default_bpdu_filter__
Filter: foo
Counters:
Name
c1
Policers:
Name
P1-t1
OOS
Offered
Transmitted

2162

Bytes
17652140

Packets
160474

Bytes

Packets

0
18286
0 18446744073709376546
0 18446744073709358260

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

show firewall filter version

Syntax
Release Information
Description
Options

show firewall filter version <filter-name>

Command introduced in Junos OS Release 10.2R2.

Display the version number of the installed firewall filter in the Routing Engine.
none(Optional) Display the version number of all installed firewall filters.
filter-name(Optional) Name of a configured filter. If you specify the name of a filter,
only the version number of that filter is displayed.

Additional Information

Required Privilege
Level
List of Sample Output
Output Fields

The initial version number is 1. This number increments by one when you modify the
firewall filter settings or an associated prefix action. The maximum version number is
4,294,967,295. When the version number reaches 4,294,967,295, this number is reset
to 1.
view

show firewall filter version on page 2163

Table 219 on page 2163 lists the output fields for the show firewall filter version command.
Output fields are listed in the approximate order in which they appear.

Table 219: show firewall filter version Output Fields

Field Name

Field Description

Filter

Name of a filter that has been configured with the filter statement at the [edit firewall] hierarchy level.

Version

Display the version number of the firewall filter.

Sample Output
show firewall filter version
user@host> show firewall filter version
Filter version information :
Filter
test

Copyright 2014, Juniper Networks, Inc.

Version
10

2163

Interfaces Fundamentals for Routing Devices

show firewall log

List of Syntax

Syntax

Syntax (EX Series

Switches)

Release Information

Description
Options

Syntax on page 2164

Syntax (EX Series Switches) on page 2164
show firewall log
<detail>
<interface interface-name>
<logical-system (logical-system-name | all)>
show firewall log
<detail>
<interface interface-name>

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
logical-system option introduced in Junos OS Release 9.3.
Display log information about firewall filters.
noneDisplay log information about firewall filters.
detail(Optional) Display detailed information.
interface interface-name(Optional) Display log information about a specific interface.
logical-system (logical-system-name | all)(Optional) Perform this operation on all logical

systems or on a particular system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show firewall log on page 2165

show firewall log detail on page 2165
Table 220 on page 2164 lists the output fields for the show firewall log command. Output
fields are listed in the approximate order in which they appear.

Table 220: show firewall log Output Fields

2164

Field Name

Field Description

Time of Log

Time that the event occurred.

Filter

Displays the name of a configured firewall filter or service filter

only if the packet hit the filters log action in a kernel filter (in the
control plane). For any traffic that reaches the Routing Engine,
the packets hit the log action in the kernel.

For all other logged packets (packet hit the filters log action in
the Packet Forwarding Engine), this field displays pfe instead of
a configured filter name.

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

Table 220: show firewall log Output Fields (continued)

Field Name

Field Description

Filter Action

Filter action:

Name of Interface

AAccept

DDiscard

RReject

Displays a physical interface name if the packet arrived at a port

on a line card.

Displays local if the packet was generated by the device's internal

Ethernet interface, em1 or fxp1, which connects the Routing Engine
with the routers packet-forwarding components.

Name of protocol

Packets protocol name: egp, gre, icmp, ipip, ospf, pim, rsvp, tcp, or
udp.

Packet length

Length of the packet.

Source address

Packets source address.

Destination address

Packets destination address and port.

Sample Output
show firewall log
user@host>show firewall log
Time
Filter
Action Interface

Protocol

Src Addr

Dest Addr

13:10:12

pfe

rlsq0.902

ICMP

180.1.177.2

180.1.177.1

13:10:11

pfe

rlsq0.902

ICMP

180.1.177.2

180.1.177.1

show firewall log detail

user@host> show firewall log detail
Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of
interface: fxp0.0Name of protocol: TCP, Packet Length: 50824, Source address:
172.17.22.108:829,
Destination address: 192.168.70.66:513
Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of
interface: fxp0.0
Name of protocol: TCP, Packet Length: 1020, Source address: 172.17.22.108:829,
Destination address: 192.168.70.66:513
Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of
interface: fxp0.0
Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829,
Destination address: 192.168.70.66:513
Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of
interface: fxp0.0
Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829,
Destination address: 192.168.70.66:513
Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of
interface: fxp0.0

Copyright 2014, Juniper Networks, Inc.

2165

Interfaces Fundamentals for Routing Devices

Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829,

Destination address: 192.168.70.66:513
Time of Log: 2004-10-13 10:37:17 PDT, Filter: f, Filter action: accept, Name of
interface: fxp0.0
Name of protocol: TCP, Packet Length: 49245, Source address: 172.17.22.108:829,
Destination address: 192.168.70.66:513
....

2166

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

show firewall prefix-action-stats

List of Syntax

Syntax (filter-specific mode) on page 2167

Syntax (term-specific mode) on page 2167

Syntax (filter-specific
mode)

show firewall prefix-action-stats filter filter-name prefix-action prefix-action-name

<from number to number>
<logical-system (logical-system-name | all)>

Syntax (term-specific
mode)

show firewall prefix-action-stats filter filter-name prefix-action prefix-action-name-term-name

<from number to number>
<logical-system (logical-system-name | all)>

Release Information

Description

Command introduced before Junos OS Release 7.4.

logical-system option introduced in Junos OS Release 9.3.
Display prefix action statistics about configured firewall filters.
If you clear statistics for firewall filters that are applied to MPCs and that also use the
prefix-action action on matched packets, wait at least 5 seconds before you enter the
show firewall prefix-action-stats command. A 5-second pause between issuing the clear
firewall and show firewall prefix-action-stats commands avoids a possible timeout of
the show firewall prefix-action-stats command.
By default, policers operate in term-specific mode.
See Filter-Specific Policer Overview for information about how to configure policers in
filter-specific mode.

Options

filter filter-nameName of a filter.

prefix-action prefix-action-nameName of a prefix action.
from number to number(Optional) Starting and ending counter or policer.
logical-system (logical-system-name | all)(Optional) Perform this operation on all logical

systems or on a particular system.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

clear firewall on page 2154

show firewall prefix-action-stats on page 2168

Table 221 on page 2168 lists the output fields for the show firewall prefix-action-stats
command. Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

2167

Interfaces Fundamentals for Routing Devices

Table 221: show firewall prefix-action-stats Output Fields

Field Name

Field Description

Filter

Filter name.
Filters configured for logical systems include the name of the filter
prefixed with the two underscore characters (__) and the name of
the logical system (for example, __ls1/filter1).

Sample Output
The following sample output assumes that the policer act1 is in term mode and that there
is a term named term1 configured in the firewall filter test.
show firewall prefix-action-stats
user@host> show firewall prefix-action-stats filter test prefix-action act1-term1 from 0 to 9
Filter: test
Counters:
Name
Bytes
Packets
act1-0
0
0
act1-1
0
0
act1-2
0
0
act1-3
0
0
act1-4
0
0
act1-5
0
0
act1-6
0
0
act1-7
0
0
act1-8
0
0
act1-9
0
0
Policers:
Name
Bytes
Packets
act1-0
0
0
act1-1
0
0
act1-2
0
0
act1-3
0
0
act1-4
0
0
act1-5
0
0
act1-6
0
0
act1-7
0
0
act1-8
0
0
act1-9
0
0

2168

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

show firewall templates-in-use

Syntax
Release Information
Description

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

show firewall templates-in-use

Command introduced in Junos OS Release 12.3.

Display the names of configured filter templates that are currently in use by dynamic
subscribers and the number of times each template is referenced.
view

clear firewall on page 2154

show firewall log on page 2164

show firewall templates-in-use on page 2170

Table 222 on page 2169 lists the output fields for the show firewall templates-in-use
command. Output fields are listed in the approximate order in which they appear.

Table 222: show firewall templates-in-use Output Fields

Field Name

Field Description

Filter Template

Name of a filter that has been configured using the filter statement at either the [edit firewall] or [edit
dynamic-profiles profile-name firewall] hierarchy and is being used as a template for dynamic subscriber
filtering.

Reference Count

Number of times the filter has been referenced by subscribers accessing the network.

Copyright 2014, Juniper Networks, Inc.

2169

Interfaces Fundamentals for Routing Devices

Sample Output
show firewall templates-in-use
user@host> show firewall templates-in-use
Dynamic Subscribers Reference Counts
Filter Template
Reference Count
----------------------------egressFilter
10
ingressFilter
10
dfilter
5
dfilter-pol
5

2170

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

show policer
Syntax

Release Information

Description

Options

show policer
<detail>
<policer-name>

Command introduced before Junos OS Release 7.4.

Option detail introduced in Junos OS Release 12.3.
Display the number of policed packets for a given policer or an aggregate policer. An
aggregate policer is an aggregate of different policers on the same logical interface.
noneDisplay the number of policed packets for all configured policers.
detail(Optional) Display enhanced statistics and counters for policers.
policer-name(Optional) Display the number of policed packets for the specified policer.

Required Privilege
Level
List of Sample Output

Output Fields

view

show policer (MX Series) on page 2172

show policer (non MX Series Router) on page 2172
show policer (Aggregate Policer, non MX Series Router) on page 2172
show policer detail on page 2173
Table 223 on page 2171 lists the output fields for the show policer command. Output fields
are listed in the approximate order in which they appear.

Table 223: show policer Output Fields

Field Name

Field Description

Name

Name of the policer.

Bytes

(For two-color policers on MX Series routers, and for hierarchical

policers on MS-DPC, MIC, and MPC interfaces on MX Series
routers)Total number of bytes policed by the specified policer.
For other combinations of policer type, device, and line card type,
this field is blank.

Packets

Copyright 2014, Juniper Networks, Inc.

(T Series and M10i)Not applicable. The Bytes information is

not displayed.

Total number of packets policed by the specified policer.

2171

Interfaces Fundamentals for Routing Devices

Table 223: show policer Output Fields (continued)

Field Name

Field Description

Policer detail

OOS packet statistics for packets that are marked

out-of-specification by the policer. Changes to all packets that
have out-of-specification actions, such as discard, color marking,
or forwarding-class, are included in this counter.

Offered packet statistics for traffic subjected to policing.

Transmitted packet statistics for traffic that is not discarded by

the policer. When the policer action is discard, the statistics are
the same as the within-specification statistics; when the policer
action is non-discard (loss-priority or forwarding-class), the
statistics are included in this counter.

Sample Output
show policer (MX Series)
user@host> show policer
Policers:
Name
__default_arp_policer__
pol-2M-ge-1/2/0.1-inet-i
pol-2M-ge-1/2/0.1-inet6-i
pol-2M-ge-1/2/0.1-mpls-i
pol-2M-ge-1/2/0.1001-vpls-i
pol-2M-ge-1/2/0.2001-vpls-i
pol-2M-ge-1/2/0.3001-ccc-i

Bytes
314520
10372300
7727800
7070336
65153700
65180900
62202144

Packets
5242
103723
77278
67984
651537
651809
647939

Bytes
NA
NA
NA
NA
NA
NA
NA

Packets
5242
103723
77278
67984
651537
651809
647939

Bytes
NA
NA
NA
NA
NA
NA
NA
NA
NA
NA

Packets
0
0
0
0
0
0
0
0
0
0

show policer (non MX Series Router)

user@host> show policer
Policers:
Name
__default_arp_policer__
pol-2M-ge-1/2/0.1-inet-i
pol-2M-ge-1/2/0.1-inet6-i
pol-2M-ge-1/2/0.1-mpls-i
pol-2M-ge-1/2/0.1001-vpls-i
pol-2M-ge-1/2/0.2001-vpls-i
pol-2M-ge-1/2/0.3001-ccc-i

show policer (Aggregate Policer, non MX Series Router)

user@host> show policer
Policers:
Name
__default_arp_policer__
P1-ae0.0-log_int-o
P2-ge-7/0/2.0-inet-o
P2-ge-7/0/2.0-inet6-o
__policer_tmpl__-term
__policer_tmpl__-fc0
__policer_tmpl__-fc0
__policer_tmpl__-fc1
__policer_tmpl__-fc0
__policer_tmpl__-fc1

2172

Copyright 2014, Juniper Networks, Inc.

Chapter 28: Firewall Filter Operational Commands

__policer_tmpl__-fc2
__policer_tmpl__-fc0
__policer_tmpl__-fc1
__policer_tmpl__-fc2
__policer_tmpl__-fc3

NA
NA
NA
NA
NA

0
0
0
0
0

Bytes

Packets

0
0
0

0
496
496

0
0
0

11329
111188
99859

show policer detail

user@host> show policer detail
Policers:
Name
__default_arp_policer__
OOS
Offered
Transmitted
P1-xe-1/0/0.0-inet-i
OOS
Offered
Transmitted

Copyright 2014, Juniper Networks, Inc.

2173

Interfaces Fundamentals for Routing Devices

2174

Copyright 2014, Juniper Networks, Inc.

CHAPTER 29

Layer 2 Bridging and Switching

Operational Commands

clear bridge mac-table

clear error bpdu

clear error mac-rewrite

show bridge domain

show bridge flood

show bridge mac-table

show bridge statistics

show l2-learning global-information

show l2-learning global-mac-count

show l2-learning instance

show l2-learning interface

show mac-rewrite interface

Copyright 2014, Juniper Networks, Inc.

2175

Interfaces Fundamentals for Routing Devices

clear bridge mac-table

Syntax

Release Information
Description

Options

clear bridge mac-table

<bridge-domain (all | bridge-domain-name)>
<instance instance-name>
<interface interface-name>
<learning-vlan id (all-vlan | learning-vlan-id)>
<mac-address>

Command introduced in Junos OS Release 8.4.

(MX Series routers only) Clear learned Layer 2 address information from the media access
control (MAC) address table.
noneClear all learned Layer 2 address information from the MAC address table.
bridge-domain (all | bridge-domain-name)(Optional) Clear learned Layer 2 MAC

addresses for all bridging domains or for the specified bridging domain.
instance instance-name(Optional) Clear learned Layer 2 MAC addresses for the specified

routing instance.
interface interface-name(Optional) Clear learned Layer 2 MAC addresses for the specified

interface.
learning-vlan-id (all-vlan | learning-vlan-id)(Optional) Clears learned Layer 2 MAC

addresses for all VLANs or for the specified VLAN.

mac-address(Optional) Clear the specified learned Layer 2 address from the MAC

address table.
Required Privilege
Level
List of Sample Output
Output Fields

clear

clear bridge mac-table on page 2176

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear bridge mac-table
user@host> clear bridge mac-table

2176

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

clear error bpdu

Syntax

Release Information
Description

Options

clear error bpdu

<interface interface-name>

Command introduced in Junos OS Release 9.4.

(MX Series routers only) Clear a bridge protocol data unit (BPDU) error condition caused
by the detection of a possible bridging loop from Spanning Tree Protocol (STP) operation.
interface interface-name(Optional) Clear the BPDU error condition for the specified

interface.
Required Privilege
Level
List of Sample Output
Output Fields

clear

clear error bpdu interface on page 2177

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear error bpdu interface
user@host> clear error bpdu interface ge-1/1/1

Copyright 2014, Juniper Networks, Inc.

2177

Interfaces Fundamentals for Routing Devices

clear error mac-rewrite

Syntax

Release Information

clear error mac-rewrite

<interface interface-name>

Command introduced in Junos OS Release 9.1.

Description

(MX Series routers only) Clear a MAC rewrite error condition caused by the reception of
tunneled Cisco Discovery Protocol (CDP), Spanning Tree Protocol (STP), or VLAN Trunk
Protocol (VTP) packets on an interface with Layer 2 protocol tunneling enabled.

Options

interface interface-name(Optional) Clear the MAC rewrite error condition for the specified

interface.
Required Privilege
Level
List of Sample Output
Output Fields

clear

clear error mac-rewrite interface on page 2178

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear error mac-rewrite interface
user@host> clear error mac-rewrite interface ge-1/0/1

2178

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

show bridge domain

Syntax

Release Information
Description
Options

show bridge domain

<brief | detail | extensive>
<bridge-domain (all | domain-name)>
<instance instance-name>
<operational>

Command introduced in Junos OS Release 8.4.

(MX Series routers only) Display bridge domain information.
noneDisplay information for all bridge domains.
brief | detail | extensive(Optional) Display the specified level of output.
bridge-domain (all | domain-name) (Optional) Display information about all bridge

domains or the specified bridge domain.

instance instance-name(Optional) Display information for the specified routing instance.
operational(Optional) Display information for the operational routing instances.

Required Privilege
Level
List of Sample Output

view

show bridge domain on page 2179

show bridge domain brief on page 2179
show bridge domain detail on page 2179

Sample Output
show bridge domain
user@host> show bridge domain
Instance
Bridging Domain
Primary Table
vs1
vlan100
bridge.0
vs1
vlan200
bridge.0

Type
Active
bridge
2
bridge
0

show bridge domain brief

user@host> show bridge domain brief
Instance
Bridging Domain
Primary Table
vs1
vlan100
bridge.0
vs1
vlan200
bridge.0

Type
Active
bridge
2
bridge
0

show bridge domain detail

user@host> show bridge domain detail

Copyright 2014, Juniper Networks, Inc.

2179

Interfaces Fundamentals for Routing Devices

Routing Instance:vs1
Bridging Domain:vlan100
Router ID: 0.0.0.0
Type: bridge
Interfaces:
ge-11/0/3.0
ge-11/1/4.100
ge-11/1/1.100
ge-11/1/0.100
xe-10/2/0.100
xe-10/0/0.100
Tables:
bridge.0
Routing Instance:vs1
Bridging Domain:vlan200
Router ID: 0.0.0.0
Type: bridge
Interfaces:
ge-11/1/0.200
ge-11/1/1.200
ge-11/1/4.200
xe-10/0/0.200
xe-10/2/0.200
Tables:
bridge.0

2180

State: Active

: 2 macs (2 active)

State: Active

: 0 macs (0 active)

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

show bridge flood

Syntax

Release Information
Description
Options

show bridge flood

<brief | detail | extensive>
<bridge-domain domain-name>
<event-queue>
<instance instance-name>
<route (all-ce-flood | all ve-flood | alt-root-flood | bd-flood | mlp-flood | re-flood)>

Command introduced in Junos OS Release 8.4.

(MX Series routers only) Display bridging flooding information.
noneDisplay all bridging flooding information for all bridging domains.
brief | detail | extensive(Optional) Display the specified level of output.
bridge-domain domain-name(Optional) Display bridging flooding information for the

specified bridge domain.

event-queue(Optional) Display the queue of pending bridge flood events.
instance instance-name(Optional) Display bridging flooding information for the specified

routing instance.
route (all-ce-flood | all ve-flood | alt-root-flood | bd-flood | mlp-flood | re-flood)(Optional)

Display the following:

all-ce-floodDisplay the route for flooding traffic to all customer edge routers if
no-local-switching is enabled.

all-ve-floodDisplay the route for flooding traffic to all VPLS edge routers if
no-local-switching is enabled.

alt-root-floodDisplay the Spanning Tree Protocol (STP) alt-root flooding route

used for the interface.

bd-floodDisplay the route for flooding traffic of a bridge domain if

no-local-switching is not enabled.

Required Privilege
Level
List of Sample Output

Output Fields

mlp-floodDisplay the route for flooding traffic to MAC learning chips.

re-floodDisplay the route for Routing Engine flooding to all interfaces.

view

show bridge flood on page 2182

show bridge flood brief on page 2182
show bridge flood detail on page 2182
show bridge flood extensive on page 2183
to be provided

Copyright 2014, Juniper Networks, Inc.

2181

Interfaces Fundamentals for Routing Devices

Sample Output
show bridge flood
user@host> show bridge flood
Name: __juniper_private1__
CEs: 0
VEs: 0
Flood Routes:
Prefix
Type
Owner
0x36/16
MLP_FLOOD
__vs1+vlan100__
0x3a/16
MLP_FLOOD
__vs1+vlan200__
Name: vs1::vlan100
CEs: 6
VEs: 0
Flood Routes:
Prefix
Type
Owner
0x35/16
ALL_FLOOD
__vs1+vlan100__
0x35/16
RE_FLOOD
__vs1+vlan100__
0x3780/17 ALT_ROOT_RT
ge-11/0/3.0
0x3b80/17 ALT_ROOT_RT
ge-11/1/4.100
0x3c80/17 ALT_ROOT_RT
ge-11/1/1.100
0x3d80/17 ALT_ROOT_RT
ge-11/1/0.100
0x3e80/17 ALT_ROOT_RT
xe-10/2/0.100
0x3f80/17 ALT_ROOT_RT
xe-10/0/0.100
Name: vs1::vlan200
CEs: 5
VEs: 0
Flood Routes:
Prefix
Type
Owner
0x39/16
ALL_FLOOD
__vs1+vlan200__
0x39/16
RE_FLOOD
__vs1+vlan200__
0x4180/17 ALT_ROOT_RT
ge-11/1/0.200
0x4080/17 ALT_ROOT_RT
ge-11/1/1.200
0x4280/17 ALT_ROOT_RT
ge-11/1/4.200
0x4480/17 ALT_ROOT_RT
xe-10/0/0.200
0x4380/17 ALT_ROOT_RT
xe-10/2/0.200

NhType
flood
flood

NhIndex
426
428

NhType
flood
flood
flood
flood
flood
flood
flood
flood

NhIndex
425
425
425
425
425
425
425
425

NhType
flood
flood
flood
flood
flood
flood
flood

NhIndex
427
427
427
427
427
427
427

show bridge flood brief

user@host> show bridge flood brief
Name
Active CEs
__juniper_private1__ 0
vs1::vlan100
6
vs1::vlan200
5

Active VEs
0
0
0

show bridge flood detail

user@host> show bridge flood detail
Name: __juniper_private1__
CEs: 0
VEs: 0
Flood Routes:
Prefix
Type
Owner
0x36/16
MLP_FLOOD
__vs1+vlan100__
0x3a/16
MLP_FLOOD
__vs1+vlan200__
Name: vs1::vlan100
CEs: 6
VEs: 0
Flood Routes:
Prefix
Type
Owner

2182

NhType
flood
flood

NhIndex
426
428

NhType

NhIndex

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

0x35/16
ALL_FLOOD
0x35/16
RE_FLOOD
0x3780/17 ALT_ROOT_RT
0x3b80/17 ALT_ROOT_RT
0x3c80/17 ALT_ROOT_RT
0x3d80/17 ALT_ROOT_RT
0x3e80/17 ALT_ROOT_RT
0x3f80/17 ALT_ROOT_RT
Name: vs1::vlan200
CEs: 5
VEs: 0
Flood Routes:
Prefix
Type
0x39/16
ALL_FLOOD
0x39/16
RE_FLOOD
0x4180/17 ALT_ROOT_RT
0x4080/17 ALT_ROOT_RT
0x4280/17 ALT_ROOT_RT
0x4480/17 ALT_ROOT_RT
0x4380/17 ALT_ROOT_RT

__vs1+vlan100__
__vs1+vlan100__
ge-11/0/3.0
ge-11/1/4.100
ge-11/1/1.100
ge-11/1/0.100
xe-10/2/0.100
xe-10/0/0.100

flood
flood
flood
flood
flood
flood
flood
flood

425
425
425
425
425
425
425
425

Owner
__vs1+vlan200__
__vs1+vlan200__
ge-11/1/0.200
ge-11/1/1.200
ge-11/1/4.200
xe-10/0/0.200
xe-10/2/0.200

NhType
flood
flood
flood
flood
flood
flood
flood

NhIndex
427
427
427
427
427
427
427

show bridge flood extensive

user@host> show bridge flood extensive
Name: __juniper_private1__
CEs: 0
VEs: 0
Flood route prefix: 0x36/16
Flood route type: MLP_FLOOD
Flood route owner: __vs1+vlan100__
Nexthop type: flood
Nexthop index: 426
Interfaces Flooding to:
Name
Type
NhType
lc-11/0/0.32769 LC
lc-10/2/0.32769 LC
lc-10/0/0.32769 LC
lc-11/1/0.32769 LC
Flood route prefix: 0x3a/16
Flood route type: MLP_FLOOD
Flood route owner: __vs1+vlan200__
Nexthop type: flood
Nexthop index: 428
Interfaces Flooding to:
Name
Type
NhType
lc-10/0/0.32769 LC
lc-10/2/0.32769 LC
lc-11/1/0.32769 LC
Name: vs1::vlan100
CEs: 6
VEs: 0
Flood route prefix: 0x35/16
Flood route type: ALL_FLOOD
Flood route owner: __vs1+vlan100__
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
NhType
ge-11/0/3.0
CE

Copyright 2014, Juniper Networks, Inc.

Index

Index

Index

2183

Interfaces Fundamentals for Routing Devices

ge-11/1/4.100
ge-11/1/1.100
ge-11/1/0.100
xe-10/2/0.100
xe-10/0/0.100

2184

CE
CE
CE
CE
CE

Flood route prefix: 0x35/16

Flood route type: RE_FLOOD
Flood route owner: __vs1+vlan100__
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
NhType
ge-11/0/3.0
CE
ge-11/1/4.100
CE
ge-11/1/1.100
CE
ge-11/1/0.100
CE
xe-10/2/0.100
CE
xe-10/0/0.100
CE

Index

Flood route prefix: 0x3780/17

Flood route type: ALT_ROOT_RT
Flood route owner: ge-11/0/3.0
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
ge-11/0/3.0
CE
ge-11/1/4.100
CE
ge-11/1/1.100
CE
ge-11/1/0.100
CE
xe-10/2/0.100
CE
xe-10/0/0.100
CE

NhType

Index

Flood route prefix: 0x3b80/17

Flood route type: ALT_ROOT_RT
Flood route owner: ge-11/1/4.100
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
NhType
ge-11/0/3.0
CE
ge-11/1/4.100
CE
ge-11/1/1.100
CE
ge-11/1/0.100
CE
xe-10/2/0.100
CE
xe-10/0/0.100
CE

Index

Flood route prefix: 0x3c80/17

Flood route type: ALT_ROOT_RT
Flood route owner: ge-11/1/1.100
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
NhType
ge-11/0/3.0
CE
ge-11/1/4.100
CE
ge-11/1/1.100
CE
ge-11/1/0.100
CE
xe-10/2/0.100
CE
xe-10/0/0.100
CE

Index

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

Flood route prefix: 0x3d80/17

Flood route type: ALT_ROOT_RT
Flood route owner: ge-11/1/0.100
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
NhType
ge-11/0/3.0
CE
ge-11/1/4.100
CE
ge-11/1/1.100
CE
ge-11/1/0.100
CE
xe-10/2/0.100
CE
xe-10/0/0.100
CE

Index

Flood route prefix: 0x3e80/17

Flood route type: ALT_ROOT_RT
Flood route owner: xe-10/2/0.100
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
NhType
ge-11/0/3.0
CE
ge-11/1/4.100
CE
ge-11/1/1.100
CE
ge-11/1/0.100
CE
xe-10/2/0.100
CE
xe-10/0/0.100
CE

Index

Flood route prefix: 0x3f80/17

Flood route type: ALT_ROOT_RT
Flood route owner: xe-10/0/0.100
Nexthop type: flood
Nexthop index: 425
Interfaces Flooding to:
Name
Type
NhType
ge-11/0/3.0
CE
ge-11/1/4.100
CE
ge-11/1/1.100
CE
ge-11/1/0.100
CE
xe-10/2/0.100
CE
xe-10/0/0.100
CE
Name: vs1::vlan200
CEs: 5
VEs: 0
Flood route prefix: 0x39/16
Flood route type: ALL_FLOOD
Flood route owner: __vs1+vlan200__
Nexthop type: flood
Nexthop index: 427
Interfaces Flooding to:
Name
Type
NhType
ge-11/1/0.200
CE
ge-11/1/1.200
CE
ge-11/1/4.200
CE
xe-10/0/0.200
CE
xe-10/2/0.200
CE

Index

Index

Flood route prefix: 0x39/16

Flood route type: RE_FLOOD

Copyright 2014, Juniper Networks, Inc.

2185

Interfaces Fundamentals for Routing Devices

Flood route owner: __vs1+vlan200__

Nexthop type: flood
Nexthop index: 427
Interfaces Flooding to:
Name
Type
NhType
ge-11/1/0.200
CE
ge-11/1/1.200
CE
ge-11/1/4.200
CE
xe-10/0/0.200
CE
xe-10/2/0.200
CE
Flood route prefix: 0x4180/17
Flood route type: ALT_ROOT_RT
Flood route owner: ge-11/1/0.200
Nexthop type: flood
Nexthop index: 427
Interfaces Flooding to:
Name
Type
NhType
ge-11/1/0.200
CE
ge-11/1/1.200
CE
ge-11/1/4.200
CE
xe-10/0/0.200
CE
xe-10/2/0.200
CE
Flood route prefix: 0x4080/17
Flood route type: ALT_ROOT_RT
Flood route owner: ge-11/1/1.200
Nexthop type: flood
Nexthop index: 427
Interfaces Flooding to:
Name
Type
NhType
ge-11/1/0.200
CE
ge-11/1/1.200
CE
ge-11/1/4.200
CE
xe-10/0/0.200
CE
xe-10/2/0.200
CE
Flood route prefix: 0x4280/17
Flood route type: ALT_ROOT_RT
Flood route owner: ge-11/1/4.200
Nexthop type: flood
Nexthop index: 427
Interfaces Flooding to:
Name
Type
NhType
ge-11/1/0.200
CE
ge-11/1/1.200
CE
ge-11/1/4.200
CE
xe-10/0/0.200
CE
xe-10/2/0.200
CE
Flood route prefix: 0x4480/17
Flood route type: ALT_ROOT_RT
Flood route owner: xe-10/0/0.200
Nexthop type: flood
Nexthop index: 427
Interfaces Flooding to:
Name
Type
NhType
ge-11/1/0.200
CE
ge-11/1/1.200
CE
ge-11/1/4.200
CE
xe-10/0/0.200
CE

2186

Index

Index

Index

Index

Index

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

xe-10/2/0.200

CE

Flood route prefix: 0x4380/17

Flood route type: ALT_ROOT_RT
Flood route owner: xe-10/2/0.200
Nexthop type: flood
Nexthop index: 427
Interfaces Flooding to:
Name
Type
NhType
ge-11/1/0.200
CE
ge-11/1/1.200
CE
ge-11/1/4.200
CE
xe-10/0/0.200
CE
xe-10/2/0.200
CE

Copyright 2014, Juniper Networks, Inc.

Index

2187

Interfaces Fundamentals for Routing Devices

show bridge mac-table

Syntax

Release Information
Description
Options

show bridge mac-table

<brief | count | detail | extensive>
<bridge-domain (all | bridge-domain-name)>
<global-count>
<interface interface-name>
<mac-address>
<vlan-id (all-vlan | vlan-id)>

Command introduced in Junos OS Release 8.4.

(MX Series routers only) Display Layer 2 MAC address information.
noneDisplay all learned Layer 2 MAC address information.
brief | count | detail | extensive(Optional) Display the specified level of output.
bridge-domain (all | bridge-domain-name)(Optional) Display learned Layer 2 MAC

addresses for all bridging domains or for the specified bridging domain.
global-count(Optional) Display the total number of learned Layer 2 MAC addresses

on the system.
instance instance-name(Optional) Display learned Layer 2 MAC addresses for the

specified routing instance.

interface interface-name(Optional) Display learned Layer 2 MAC addresses for the

specified interface.
mac-address(Optional) Display the specified learned Layer 2 MAC address information.
vlan-id (all-vlan | vlan-id)(Optional) Display learned Layer 2 MAC addresses for all

VLANs or for the specified VLAN.

Additional Information

Required Privilege
Level
List of Sample Output

Output Fields

2188

When Layer 2 protocol tunneling is enabled, the tunneling MAC address 01:00:0c:cd:cd:d0
is installed in the MAC table. When the Cisco Discovery Protocol (CDP), Spanning Tree
Protocol (STP), or VLAN Trunk Protocol (VTP) is configured for Layer 2 protocol tunneling
on an interface, the corresponding protocol MAC address is installed in the MAC table.
view

show bridge mac-table on page 2189

show bridge mac-table (with VXLAN enabled) on page 2190
show bridge mac-table count on page 2190
show bridge mac-table detail on page 2191
Table 224 on page 2189 describes the output fields for the show bridge mac-table command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

Table 224: show bridge mac-table Output fields

Field Name

Field Description

Routing instance

Name of the routing instance.

Bridging domain

Name of the bridging domain.

MAC address

MAC address or addresses learned on a logical interface.

MAC flags

Status of MAC address learning properties for each interface:

SStatic MAC address is configured.

DDynamic MAC address is configured.

LLocally learned MAC address is configured.

CControl MAC address is configured.

SEMAC accounting is enabled.

NMNon-configured MAC.

RRemote PE MAC address is configured.

Logical interface

Name of the logical interface.

MAC count

Number of MAC addresses learned on the specific routing instance or

interface.

Learning interface

Name of the logical interface on which the MAC address was learned.

Learning VLAN

VLAN ID of the routing instance or bridge domain in which the MAC address
was learned.

VXLAN ID/VXLAN

VXLAN Network Identifier (VNI)

Layer 2 flags

Debugging flags signifying that the MAC address is present in various lists.

Epoch

Spanning Tree Protocol epoch number identifying when the MAC address
was learned. Used for debugging.

Sequence number

Sequence number assigned to this MAC address. Used for debugging.

Learning mask

Mask of the Packet Forwarding Engines where this MAC address was learned.
Used for debugging.

IPC generation

Creation time of the logical interface when this MAC address was learned.
Used for debugging.

Sample Output
show bridge mac-table
user@host> show bridge mac-table
MAC flags (S -static MAC, D -dynamic MAC, L -locally learned, C -Control MAC
SE -Statistics enabled, NM -Non configured MAC, R -Remote PE MAC)

Copyright 2014, Juniper Networks, Inc.

2189

Interfaces Fundamentals for Routing Devices

Routing instance : default-switch

Bridging domain : test1, VLAN : 1
MAC
MAC
Logical
address
flags
interface
01:00:0c:cc:cc:cc
S,NM
NULL
01:00:0c:cc:cc:cd
S,NM
NULL
01:00:0c:cd:cd:d0
S,NM
NULL
64:87:88:6a:17:d0
D
ae0.1
64:87:88:6a:17:f0
D
ae0.1

NH
Index

RTR
ID

show bridge mac-table (with VXLAN enabled)

user@host> show bridge mac-table
MAC flags (S -static MAC, D -dynamic MAC, L -locally learned
SE -Statistics enabled, NM -Non configured MAC, R -Remote PE MAC)
Routing instance : default-switch
Bridging domain : vlan-1, VLAN : 1
VXLAN: Id : 100, Multicast group: 226.1.1.1
MAC
MAC
Logical
address
flags
interface
00:01:01:00:01:f7
D,SE
vtep.1052010
00:03:00:32:01:f7
D,SE
vtep.1052011
00:00:21:11:11:10
DL
ge-1/0/0.0
00:00:21:11:11:11
DL
ge-1/1/0.0

Routing instance : default-switch

Bridging domain : vlan-2, VLAN : 2, VXLAN : 200
VXLAN: Id : 200, Multicast group: 226.1.1.2
MAC
MAC
Logical
address
flags
interface
00:02:01:33:01:f7
D,SE
vtep.1052010
00:04:00:14:01:f7
D,SE
vtep.1052011
00:00:21:11:21:10
DL
ge-1/0/0.1
00:00:21:11:21:11
DL
ge-1/1/0.1

show bridge mac-table count

user@host> show bridge mac-table count
2 MAC address learned in routing instance vs1 bridge domain vlan100
MAC address count per interface within routing instance:
Logical interface
MAC count
ge-11/0/3.0
1
ge-11/1/4.100
0
ge-11/1/1.100
0
ge-11/1/0.100
0
xe-10/2/0.100
1
xe-10/0/0.100
0
MAC address count per learn VLAN within routing instance:
Learn VLAN ID
MAC count
0
2
0 MAC address learned in routing instance vs1 bridge domain vlan200
MAC address count per interface within routing instance:
Logical interface
MAC count

2190

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

ge-11/1/0.200
ge-11/1/1.200
ge-11/1/4.200
xe-10/0/0.200
xe-10/2/0.200

0
0
0
0
0

MAC address count per learn VLAN within routing instance:

Learn VLAN ID
MAC count
0
0

show bridge mac-table detail

user@host> show bridge mac-table detail
MAC address: 00:00:00:19:1c:db
Routing instance: vs1
Bridging domain: vlan100
Learning interface: ge-11/0/3.0
Learning VLAN: 0
Layer 2 flags: in_ifd, in_ifl, in_vlan, kernel
Epoch: 4
Sequence number: 0
Learning mask: 0x800
IPC generation: 0
MAC address: 00:00:00:59:3a:2f
Routing instance: vs1
Bridging domain: vlan100
Learning interface: xe-10/2/0.100
Learning VLAN: 0
Layer 2 flags: in_ifd, in_ifl, in_vlan, kernel
Epoch: 7
Sequence number: 0
Learning mask: 0x400
IPC generation: 0

Copyright 2014, Juniper Networks, Inc.

2191

Interfaces Fundamentals for Routing Devices

show bridge statistics

Syntax

Release Information
Description
Options

show bridge statistics

<bridge-domain domain-name>
<instance instance-name>

Command introduced in Junos OS Release 8.4.

(MX Series routers only) Display bridge statistics.
noneDisplay bridge statistics for all bridge domains in all routing instances.
bridge-domain domain-name(Optional) Display statistics for the specified bridge domain.
instance instance-name(Optional) Display statistics for the specified routing instance.

Required Privilege
Level
List of Sample Output

view

show bridge statistics on page 2192

Sample Output
show bridge statistics
user@host> show bridge statistics
Information for routing instance:
Routing instance : __juniper_private1__
Index: 1
Sequence number: 0
MAC limit: 5000
MACs learned: 0
Static MACs learned: 0
Non config Static MACs learned: 0
Handle: 0x829e800
Information for routing instance:
Routing instance : vs1
Bridging domain : vlan100
Index: 3
Sequence number: 0
MAC limit: 5120
MACs learned: 2
Static MACs learned: 0
Non config Static MACs learned: 0
Handle: 0x829e400
Flags: Bridge instance, Config defined, VLAN : 100
Local interface: ge-11/0/3.0, Index: 79
Broadcast packets:
1
Broadcast bytes :
65
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0
Flooded bytes
:
0
Unicast packets :
358624489
Unicast bytes
:
23310592305
Current MAC count:
1 (Limit 1024)
Local interface: ge-11/1/4.100, Index: 84
Broadcast packets:
0
Broadcast bytes :
0
Multicast packets:
0
Multicast bytes :
0

2192

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

Flooded packets :
0
Flooded bytes
:
0
Unicast packets :
0
Unicast bytes
:
0
Current MAC count:
0
Local interface: ge-11/1/1.100, Index: 86
Broadcast packets:
0
Broadcast bytes :
0
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0
Flooded bytes
:
0
Unicast packets :
0
Unicast bytes
:
0
Current MAC count:
0
Local interface: ge-11/1/0.100, Index: 87
Broadcast packets:
0
Broadcast bytes :
0
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0
Flooded bytes
:
0
Unicast packets :
0
Unicast bytes
:
0
Current MAC count:
0
Local interface: xe-10/2/0.100, Index: 88
Broadcast packets:
0
Broadcast bytes :
0
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0
Flooded bytes
:
0
Unicast packets :
358627393
Unicast bytes
:
23310781065
Current MAC count:
1
Local interface: xe-10/0/0.100, Index: 89
Broadcast packets:
0
Broadcast bytes :
0
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0
Flooded bytes
:
0
Unicast packets :
0
Unicast bytes
:
0
Current MAC count:
0

(Limit 1024)

(Limit 1024)

(Limit 1024)

(Limit 1024)

(Limit 1024)

Information for routing instance:

Routing instance : vs1
Bridging domain : vlan200
Index: 4
Sequence number: 0
MAC limit: 5120
MACs learned: 0
Static MACs learned: 0
Non config Static MACs learned: 0
Handle: 0x829e600
Flags: Bridge instance, Config defined, VLAN : 200
Local interface: ge-11/1/0.200, Index: 90
Broadcast packets:
0
Broadcast bytes :
0
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0

Copyright 2014, Juniper Networks, Inc.

2193

Interfaces Fundamentals for Routing Devices

Flooded bytes
:
Unicast packets :
Unicast bytes
:
Current MAC count:
Local interface: ge-11/1/1.200,
Broadcast packets:
Broadcast bytes :
Multicast packets:
Multicast bytes :
Flooded packets :
Flooded bytes
:
Unicast packets :
Unicast bytes
:
Current MAC count:
Local interface: ge-11/1/4.200,
Broadcast packets:
Broadcast bytes :
Multicast packets:
Multicast bytes :
Flooded packets :
Flooded bytes
:
Unicast packets :
Unicast bytes
:
Current MAC count:
Local interface: xe-10/0/0.200,
Broadcast packets:
Broadcast bytes :
Multicast packets:
Multicast bytes :
Flooded packets :
Flooded bytes
:
Unicast packets :
Unicast bytes
:
Current MAC count:
Local interface: xe-10/2/0.200,
Broadcast packets:
Broadcast bytes :
Multicast packets:
Multicast bytes :
Flooded packets :
Flooded bytes
:
Unicast packets :
Unicast bytes
:
Current MAC count:

2194

0
0
0
0 (Limit 1024)
Index: 91
0
0
0
0
0
0
0
0
0 (Limit 1024)
Index: 92
0
0
0
0
0
0
0
0
0 (Limit 1024)
Index: 93
0
0
0
0
0
0
0
0
0 (Limit 1024)
Index: 94
4
260
0
0
0
0
0
0
0 (Limit 1024)

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

show l2-learning global-information

Syntax
Release Information
Description

Options
Required Privilege
Level
List of Sample Output
Output Fields

show l2-learning global-information

Command introduced in Junos OS Release 8.4.

(MX Series routers only) Display Layer 2 learning process-related information for the
entire router.
This command has no options.
view

show l2-learning global-information on page 2195

Table 225 on page 2195 describes the output fields for the show l2-learning
global-information command. Output fields are listed in the approximate order in which
they appear.

Table 225: show l2-learning global-information Output Fields

Field Name

Field Description

MAC aging
interval

Configured timeout interval, in seconds, for all MAC table entries.

MAC learning

Status of MAC learning: Enabled or Disabled.

MAC statistics

Status of MAC accounting: Enabled or Disabled.

MAC limit Count

Configured maximum limit on the number of MAC addresses that can be

learned.

MAC limit hit flag

Status of the learned MAC limit hit flag: Enabled (the learned MAC exceeds
the global MAC limit) or Disabled (the learned MAC does not exceed the
global MAC limit).

MAC packet
action drop

Status of action to drop packets after the configured MAC address limit is
reached: Enabled (packets are dropped) or Disabled (packets are forwarded).

Sample Output
show l2-learning global-information
user@host> show l2-learning global-information
Global Configuration:
MAC
MAC
MAC
MAC

aging interval
learning
statistics
limit Count

Copyright 2014, Juniper Networks, Inc.

:
:
:
:

300
Enabled
Disabled
393215

2195

Interfaces Fundamentals for Routing Devices

MAC limit hit flag

: Disabled
MAC packet action drop: Disabled

2196

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

show l2-learning global-mac-count

Syntax
Release Information
Description

Options
Required Privilege
Level
List of Sample Output
Output Fields

show l2-learning global-mac-count

Command introduced in Junos OS Release 9.3.

(MX Series routers only) Display the total number of dynamic and static MAC addresses
learned for the entire router.
This command has no options.
view

show l2-learning global-mac-count on page 2197

Displays the total number of dynamic and static MAC addresses learned for the entire
router.

Sample Output
show l2-learning global-mac-count
user@host> show l2-learning global-mac-count
100 dynamic and static MAC addresses learned globally

Copyright 2014, Juniper Networks, Inc.

2197

Interfaces Fundamentals for Routing Devices

show l2-learning instance

Syntax

show l2-learning instance

Release Information

(MX Series routers only) Command introduced in Junos OS Release 8.4.

Description

Display Layer 2 learning properties for all the configured routing instances.

Options

This command has no options.

Required Privilege
Level

view

List of Sample Output

show l2-learning instance on page 2198

Output Fields

Table 226 on page 2198 describes the output fields for the show l2-learning instance
command. Output fields are listed in the approximate order in which they appear.

Table 226: show l2-learning instance Output Fields

Field Name

Field Description

Routing Instance

Name of routing instance.

Bridging Domain

Name of bridging domain.

On MX Series routers you can use the show l2-learning instance <extensive> command option to
display the Bridge Service-id information which includes the Config Service ID and the Active Service
ID.

Index

Number associated with the routing instance or bridging domain.

Logical System

Name of logical system or Default if no logical system is configured.

Routing instance flags

Status of Layer 2 learning properties for each routing instance:

DLMAC learning is disabled.

SEMAC accounting is enabled.

ADPackets are dropped after MAC address limit is reached.

LHThe maximum number of MAC addresses has been learned on the routing instance. The routing

instance is not able to learn any additional MAC addresses.

MAC limit

Maximum number of MAC addresses that can be learned from each interface in the routing instance
or bridging domain.

Sample Output
show l2-learning instance
user@host> show l2-learning instance
Information for routing instance:
Routing Instance flags (DL -disable learning, SE -stats enabled,

2198

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

AD -packet action drop, LH -mac limit hit)

Routing
Instance
__juniper_private1__
vs1
vs1

Copyright 2014, Juniper Networks, Inc.

Bridging
Domain
vlan100
vlan200

Index
1
3
4

Logical
System
Default
Default
Default

Routing
flags

MAC
limit
5000
5120
5120

2199

Interfaces Fundamentals for Routing Devices

show l2-learning interface

Syntax
Release Information
Description
Options
Required Privilege
Level
List of Sample Output
Output Fields

show l2-learning interface

Command introduced in Junos OS Release 8.4.

(MX Series routers only) Display Layer 2 learning information for all the interfaces.
This command has no options.
view

show l2-learning interface on page 2200

Table 227 on page 2200 describes the output fields for the show l2-learning interface
command. Output fields are listed in the approximate order in which they appear.

Table 227: show l2-learning interfaceOutput Fields

Field Name

Field Description

Logical interface

Name of the logical interface.

Index

Index of the interface.

Routing Instance

Number of the routing instance to which the interface belongs.

Interface device

Value of the order in which the Junos OS finds and initializes the interface.

Logical interface flags

Status of Layer 2 learning properties for each interface:

DLMAC learning is disabled.

SEMAC accounting is enabled.

ADPackets are dropped after the MAC interface limit is reached.

MAC limitMaximum number of MAC addresses that can be learned

from the interface.

Sample Output
show l2-learning interface
user@host> showl2-learning interface
Information for interface family:
Logical Interface flags (DL -disable learning, SE -stats enabled,
AD -packet action drop, LH -mac limit hit)
Logical
interface
ge-11/0/3.0
ge-11/1/4.100
ge-11/1/1.100

2200

Index
79
84
86

Routing
instance
3
3
3

Interface
device
136
150
147

Logical
Interface flags

MAC
limit
1024
1024
1024

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

ge-11/1/0.100
xe-10/2/0.100
xe-10/0/0.100
ge-11/1/0.200
ge-11/1/1.200
ge-11/1/4.200
xe-10/0/0.200
xe-10/2/0.200

Copyright 2014, Juniper Networks, Inc.

87
88
89
90
91
92
93
94

3
3
3
4
4
4
4
4

146
144
129
146
147
150
129
144

1024
1024
1024
1024
1024
1024
1024
1024

2201

Interfaces Fundamentals for Routing Devices

show mac-rewrite interface

Syntax

Release Information

Description
Options

show mac-rewrite interface

<brief | detail>
<interface-name>

Command introduced in Junos OS Release 9.1.

Command introduced in Junos OS Release 14.1X53-D10 for EX Series switches.
Display Layer 2 protocol tunneling information.
brief | detail(Optional) Display the specified level of output.
interface interface-name(Optional) Display Layer 2 protocol tunneling information for

the specified interface.

Required Privilege
Level
Related
Documentation

List of Sample Output

Output Fields

view

layer2-control

mac-rewrite

show mac-rewrite interface on page 2202

show mac-rewrite interface (EX Series Switch) on page 2203
Table 228 on page 2202 lists the output fields for the show mac-rewrite interface command.
Output fields are listed in the approximate order in which they appear.

Table 228: show mac-rewrite interface Output Fields

Field Name

Field Description

Level of Output

Interface

Name of the interface that has Layer 2 protocol tunneling configured on it.

brief detail

Protocols

Layer 2 protocols being tunneled on this interface: Cisco Discovery Protocol

(CDP), Spanning Tree Protocol (STP), Per-VLAN Spanning Tree Plus (PVSTP+),
or VLAN Trunk Protocol (VTP)

brief detail

On EX Series switches, the following Layer 2 protocols are supported: 802.3A,

CDP, LACP, LLDP, MVRP, STP, VTP, GVRP,VSTP

Sample Output
show mac-rewrite interface
user@host> show mac-rewrite interface
Interface
Protocols
ge-1/0/5

2202

STP VTP CDP PVSTP+

Copyright 2014, Juniper Networks, Inc.

Chapter 29: Layer 2 Bridging and Switching Operational Commands

show mac-rewrite interface (EX Series Switch)

user@switch> show mac-rewrite interface
Interface
Protocols
ge-0/0/1

Copyright 2014, Juniper Networks, Inc.

STP

2203

Interfaces Fundamentals for Routing Devices

2204

Copyright 2014, Juniper Networks, Inc.

CHAPTER 30

VPN Operational Commands

clear vpls mac-address

clear vpls mac-table

request l2circuit-switchover

show dynamic-tunnels database

show hfrr profiles

show ingress-replication mvpn

show l2circuit connections

show l2vpn connections

show mvpn c-multicast

show mvpn instance

show mvpn neighbor

show vpls connections

show vpls flood event-queue

show vpls flood instance

show vpls flood route

show vpls mac-table

show vpls statistics

Copyright 2014, Juniper Networks, Inc.

2205

Interfaces Fundamentals for Routing Devices

clear vpls mac-address

Syntax

Release Information
Description

Options

clear vpls mac-address

<instance instance-name>
<logical-system (all | logical-system-name)>
<mac-address>

Command introduced before Junos OS Release 7.4.

(T Series and M Series routers, except for the M160 router) Clear media access control
(MAC) address entries from the virtual private LAN service (VPLS) table.
noneClear all MAC address entries from the VPLS table for all routing instances.
instance instance-name(Optional) Clear all MAC address entries for a VPLS instance

from the VPLS table.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

mac-address(Optional) Clear a specific MAC address in a VPLS instance from the

VPLS table.
Required Privilege
Level
List of Sample Output
Output Fields

maintenance

clear vpls mac-address on page 2206

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear vpls mac-address
user@host> clear vpls mac-address

2206

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

clear vpls mac-table

Syntax

Release Information
Description

Options

clear vpls mac-table

<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
<mac-address>
<vlan-id>

Command introduced before Junos OS Release 9.5.

(MX Series routers) Clear media access control (MAC) addresses from the virtual private
LAN service (VPLS) MAC table.
noneClear all MAC addresses from the VPLS table for all routing instances.
instance instance-name(Optional) Clear all MAC addresses for a VPLS instance from

the VPLS table.

interface interface-name(Optional) Clear all MAC addresses for a VPLS interface from

the VPLS table.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

mac-address(Optional) Clear a specific MAC address in a VPLS instance from the

VPLS table.
vlan-id(Optional) Clear MAC addresses on a specified VLAN (0 through 4095).

Required Privilege
Level
List of Sample Output
Output Fields

maintenance

clear vpls mac-table on page 2207

When you enter this command, you are provided feedback on the status of your request.

Sample Output
clear vpls mac-table
user@host> clear vpls mac-table

Copyright 2014, Juniper Networks, Inc.

2207

Interfaces Fundamentals for Routing Devices

request l2circuit-switchover
Syntax

request l2circuit-switchover
<logical-system (all | logical-system-name)>
<neighbor address>
<virtual-circuit-id identifier>

Release Information

Command introduced in Junos OS Release 9.2.

Statement introduced in Junos OS Release 14.1X53-D10 for the QFX Series and for EX4600
switches.

Description

Manually trigger a switch from the active pseudowire to the redundant pseudowire. This
command can be useful when performing network maintenance.

Options

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor address(Optional) Trigger a switch of all of the active pseudowire connections

with the specified neighbor to their respective redundant pseudowires.

virtual-circuit-id identifier(Optional) Trigger a switch from the active pseudowire

connection of the specified Layer 2 circuit to its redundant pseudowire.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

maintenance

MPLS Feature Support on the QFX Series and EX4600 Switch Overview

request l2circuit-switchover virtual-circuit-id on page 2208

When you enter this command, you are provided feedback on the status of your request.

Sample Output
request l2circuit-switchover virtual-circuit-id
user@host>request l2circuit-switchover virtual-circuit-id 12

2208

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show dynamic-tunnels database

Syntax

Release Information
Description
Options

show dynamic-tunnels database

<destination>
<logical-system (all | logical-system-name) >
<table routing-table-name>

Command introduced before Junos OS Release 7.4.

Display dynamic tunnel database information.
noneDisplay dynamic tunnel database information for all destinations and routing

tables.
destination(Optional) Display database entries for the specified IP address (with

optional destination prefix length) only.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

table routing-table-name(Optional) Display database entries for the specified table

only.
Required Privilege
Level
List of Sample Output

Output Fields

view

show dynamic-tunnels database (Tunnel Is Up) on page 2210

show dynamic-tunnels database (No Tunnel PIC) on page 2210
show dynamic-tunnels database (Tunnel Is Expiring) on page 2210
show dynamic-tunnels database (Destination Specified) on page 2210
Table 229 on page 2209 lists the output fields for the show dynamic-tunnels database
command. Output fields are listed in the approximate order in which they appear.

Table 229: show dynamic-tunnels database Output Fields

Field Name

Field Description

Table

Name of the routing table (for example, inet.0).

Destination-network

Destination IP address and subnet.

Tunnel to

Destination IP address and prefix of the tunnel.

State

State of the tunnel: Up, Up (expires in nn:nn:nnseconds), or Dn (down).

Reference count

Number of routes across the dynamic tunnel that are currently being
resolved.

Next-hop type

Type of tunnel: GRE.

Source address

Source IP address of the tunnel.

Copyright 2014, Juniper Networks, Inc.

2209

Interfaces Fundamentals for Routing Devices

Table 229: show dynamic-tunnels database Output Fields (continued)

Field Name

Field Description

Next-hop

IP address of the destination interface.

State

State of the destination interface: Up, Dn, or Dn (no tunnel pic).

Sample Output
show dynamic-tunnels database (Tunnel Is Up)
user@host> show dynamic-tunnels database
Table: inet.3
Destination-network: 10.255.120.94/32
Tunnel to: 10.255.120.94/32 State: Up
Reference count: 2
Next-hop type: gre
Source address: 10.255.120.92
Next hop: gr-4/3/0.32769
State: Up

show dynamic-tunnels database (No Tunnel PIC)

user@host> show dynamic-tunnels database
Table: inet.3
Destination-network: 10.255.120.94/32
Tunnel to: 10.255.120.94/32 State: Dn
Reference count: 2
Next-hop type: gre
Source address: 10.255.120.92
State: Dn (no tunnel pic)

show dynamic-tunnels database (Tunnel Is Expiring)

user@host> show dynamic-tunnels database
Table: inet.3
Destination-network: 10.255.120.94/32
Tunnel to: 10.255.120.94/32 State: Up (expires in 00:14:56 seconds)
Reference count: 0
Next-hop type: gre
Source address: 10.255.120.92
Next hop: gr-4/3/0.32769
State: Up

show dynamic-tunnels database (Destination Specified)

user@host> show dynamic-tunnels database 10.255.120.94
Table: inet.3
Destination-network: 10.255.120.94/32
Tunnel to: 10.255.120.94/32 State: Up
Reference count: 2
Next-hop type: gre
Source address: 10.255.120.92

2210

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Next hop: gr-4/3/0.32769

State: Up

Copyright 2014, Juniper Networks, Inc.

2211

Interfaces Fundamentals for Routing Devices

show hfrr profiles

Syntax

Release Information
Description

show hfrr profiles

<brief |extensive>

Command introduced in Junos OS Release 12.2.

Display host fast reroute (HFRR) profile information.
HFRR adds a precomputed protection path into the Packet Forwarding Engine, such that
if a link between a provider edge device and a server farm becomes unusable for
forwarding, the Packet Forwarding Engine can use another path without having to wait
for the router or the protocols to provide updated forwarding information.

Options

noneDisplay information about HRFF profiles.

brief | extensive(Optional) Display the specified level of output.

Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields

view

Example: Configuring Host Fast Reroute

show hfrr profiles on page 2213

Table 230 on page 2212 describes the output fields for the show hfrr profiles command.
Output fields are listed in the approximate order in which they appear.

Table 230: show hfrr profiles Output Fields

Field Name

Field Description

HFRR pointer
HFRR current state

Status of the HFRR profile: HFRR_ACTIVE , HFRR_INACTIVE ,

HFRR_IFLH-NOT-CONF, and so on.

HFRR Prefix limit blackout timer expiry (in secs)

Time interval between an HFRR profile becoming inactive on exceeding

the ARP prefix limit, and the profile starting the SYNC process.

HFRR prefix limit hit count

Number of times that an HFRR profile becomes inactive on exceeding

the ARP prefix limit.

HFRR protected IFL name

Interface configured for the HFRR feature.

HFRR protected IFL handle

HFRR routing instance name

The routing instance in which the HFRR interface is configured.

HFRR routing instance handle

2212

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 230: show hfrr profiles Output Fields (continued)

Field Name

Field Description

HFRR sync BG scheduled

HFRR RTS filter on
HFRR delete BG scheduled
HFRR ARP prefix limit

Configured ARP prefix limit.

HFRR ARP supplementary blackout timeout (in mins)

Supplementary time-out value configured for profile to be inactive

when it hits ARP prefix limit.

HFRR number of ARP routes learned

Number of ARP routes learned on the configured interface.

HFRR number of FRR routes created

Number of ARP routes created on the configured interface.

Sample Output
show hfrr profiles
user@host> show hfrr profiles
HFRR pointer: 0x9254000
HFRR current state: HFRR_ACTIVE
HFRR Prefix limit blackout timer expiry (in secs): 0
HFRR prefix limit hit count: 0
HFRR protected IFL name: ge-4/1/0.0
HFRR protected IFL handle: 0x9248738
HFRR routing instance name: test
HFRR routing instance handle: 0x9145740
HFRR sync BG scheduled: NO
HFRR RTS filter on: YES
HFRR delete BG scheduled: NO
HFRR ARP prefix limit: 0
HFRR ARP supplementary blackout timeout (in mins): 1
HFRR number of ARP routes learned: 4
HFRR number of FRR routes created: 2

Copyright 2014, Juniper Networks, Inc.

2213

Interfaces Fundamentals for Routing Devices

show ingress-replication mvpn

Syntax
Release Information
Description

Required Privilege
Level
List of Sample Output
Output Fields

show ingress-replication mvpn

Command introduced in Junos OS Release 10.4.
Display the state and configuration of the ingress replication tunnels created for the
MVPN application when using the mpls-internet-multicast routing instance type.
View

show ingress-replication mvpn on page 2214

Table 231 on page 2214 lists the output fields for the show ingress-replication mvpn
command. Output fields are listed in the approximate order in which they appear.

Table 231: show ingress-replication mvpn Output Fields

Field Name

Field Description

Ingress tunnel

Identifies the MVPN ingress replication tunnel.

Application

Identifies the application (MVPN).

Unicast tunnels

List of unicast tunnels in use.

Leaf address

Address of the tunnel.

Tunnel type

Identifies the unicast tunnel type.

Mode

Indicates whether the tunnel was created as a new tunnel for the ingress
replication, or if an existing tunnel was used.

State

Indicates whether the tunnel is Up or Down.

Sample Output
show ingress-replication mvpn
user@host> show ingress-replication mvpn
Ingress Tunnel: mvpn:1
Application: MVPN
Unicast tunnels
Leaf Address
Tunnel-type
10.255.245.2
P2P LSP
10.255.245.4
P2P LSP
Ingress Tunnel: mvpn:2
Application: MVPN
Unicast tunnels
Leaf Address
Tunnel-type
10.255.245.2
P2P LSP

2214

Mode
New
New

State
Up
Up

Mode
Existing

State
Up

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Copyright 2014, Juniper Networks, Inc.

2215

Interfaces Fundamentals for Routing Devices

show l2circuit connections

Syntax

Release Information

show l2circuit connections

<brief | extensive | summary>
<down | up | up-down>
<history>
<interface interface-name>
<logical-system (all | logical-system-name)>
<neighbor neighbor>
<status>

Command introduced before Junos OS Release 7.4.

Display enhancements in Junos OS Release 9.6.
Display enhancements in Junos OS Release 10.2.
Display enhancements in Junos OS Release 12.1.
Display enhancements in Junos OS Release 13.2.

Description

Display status information about Layer 2 virtual circuits from the local provider edge (PE)
router to its neighbors.

Options

noneDisplay standard information about Layer 2 virtual circuits on all interfaces for all

neighbors.
brief | extensive | summary(Optional) Display the specified level of output. Use history

to display information about connection history. Use status to display information

about the connection and interface status.
down | up | up-down(Optional) Display nonoperational, operational, or both kinds of

connections.
history(Optional) Display information about connection history.
interface interface-name(Optional) Show all Layer 2 virtual circuits on an interface.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

neighbor neighbor(Optional) IP address of a specific neighbor.
status(Optional) Display information about the connection and interface status.

Required Privilege
Level
List of Sample Output

Output Fields

2216

view

show l2circuit connections on page 2219

show l2circuit connections interface on page 2220
show l2circuit connections extensive on page 2220
show l2circuit connections extensive (Pseudowire Redundancy with Hot
Standby) on page 2221
Table 232 on page 2217 lists the output fields for the show l2circuit connections command.
Output fields are listed in the approximate order in which they appear.

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 232: show l2circuit connections Output Fields

Field Name

Field Description

Layer-2 Circuit
Connections

Displays the legends for connection and interface status.

Neighbor

Remote PE neighbor.

Interface

Logical PE-to-CE interface on which the virtual circuit is configured.

Type

VC type: rmt (remote) or loc (local).

Legend for
connection status
(St)

Status of the virtual circuit connection:

EIThe local virtual circuit interface is configured with an encapsulation that

is not supported.

MMThe two routers do not agree on an MTU value, which causes an MTU

mismatch.

EMThe encapsulation type received on this virtual circuit from the neighbor

does not match the local virtual circuit interface encapsulation type.

CMThe two routers do not agree on a control word, which causes a control

word mismatch.

VMThe remote and local VLAN IDs do not match across the Layer 2 circuit.

OLNo advertisement has been received for this virtual circuit from the

neighbor. There is no outgoing label available for use by this virtual circuit.

NCThe interface is not configured as a CCC or TCC interface.

BKThe virtual circuit has switched to a backup connection.

CBThe remote PE router is advertising a different cell bundle from that

configured on the local PE router.

LDThe connection to the local site is signaled down, because the CE-facing

interface to the local site is down.

RDThe remote neighbor is down. It has signaled a problem using the

pseudowire status code.

NPThe router detects that interface hardware is not present. The hardware

may be offline, a PIC may not be of the desired type, or the interface may be
configured in a different routing instance.

DnThe virtual circuit is down.

VC-DnThe virtual circuit is down because there is no tunnel LSP from the

local PE router to the neighbor.

UPThe virtual circuit is operational.

CFThe router cannot find enough bandwidth to the remote router to satisfy

the Layer 2 circuit bandwidth requirement.

IBThe bit rate is incompatible for Time Division Multiplexing (TDM).

TDMTDM is not configured correctly.

STThe virtual circuit has been switched to a standby connection.

SPThe virtual circuit connection is using a static pseudowire.

RSThe remote site is in a standby state.

XXThe virtual circuit is down for an unknown reason. This is a programming

error.
Time last up

Copyright 2014, Juniper Networks, Inc.

Date and time the virtual circuit was last operational.

2217

Interfaces Fundamentals for Routing Devices

Table 232: show l2circuit connections Output Fields (continued)

2218

Field Name

Field Description

# Up trans

Number of times the virtual circuit came up.

local-interface-name

Name of the local PE-to-CE interface.

Status

Status of the local interface.

Up

Interface is operational.

Dn

Interface is not operational.

NP

Not present. Interface does not exist.

DS

Disabled. Interface has been administratively disabled.

WE

Wrong encapsulation. The interface is not configured as CCC.

UN

Interface status is initialized.

Encapsulation

Encapsulation of the local interface.

Remote PE

Prefix of the remote PE router.

Negotiated
control-word

Whether the use of the control word has been negotiated for this virtual circuit:
Yes (Null) or No.

Incoming label

Label used by the remote side of the virtual circuit to send packets destined to
the local side. This label is routed to the local virtual circuit interface.

Outgoing label

Label used by the local side of the virtual circuit to send packets to the remote
side of the virtual circuit. Packets originated on the local virtual circuit interface
are encapsulated with this label before being placed on the tunnel LSP to the
neighbor for this virtual circuit. This label is allocated by the neighbor and is
used in demultiplexing incoming packets destined for this virtual circuit.

Negotiated PW
status TLV

Displays the pseudowire status type, length, and value (TLV). TLVs are a method
of encoding variable-length or optional information. If the pseudowire status
TLV is used, the corresponding local or neighbor PE router status code is also
displayed.

local PW status
code

If the pseudowire status TLV is used, displays the local PE router status code.

Neighbor PW status
code

If the pseudowire status TLV is used, displays the neighbor PE router status
code.

Local interface

Name of the local interface used for the Layer 2 circuit connection.

Status

Status of the local interface (Up or Down).

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 232: show l2circuit connections Output Fields (continued)

Field Name

Field Description

Encapsulation

Encapsulation configured for the local interface.

APS-active

Indicates that the interface belongs to the working circuit.

APS-inactive

Indicates that the interface belongs to the protect circuit.

Connection
protection

Whether or not connection protection is configured for the Layer 2 circuit to the
neighbor: Yes or No.

VC bandwidth

Bandwidth requirement of the Layer 2 circuit.

Time

Time at which the event occurred.

Connection History

Event types logged in history.

loc intf upLocal virtual circuit interface went up.

loc intf downLocal virtual circuit interface went down.

In lbl UpdateIncoming label has been updated.

Out lbl UpdateOutgoing label has been updated.

PE route changedRoute to PE router has been updated.

PE route downRoute to PE router is down.

rmt side markedRemote side is marked.

VC DnRemote side indicated that its end of the virtual circuit is down (if the

tunnel LSP from the remote side to the local side is down).

status update timerStatus update timer processing. It computes the state

of the virtual circuit, and determines whether it should be advertised to or

withdrawn from the remote side.

Sample Output
show l2circuit connections
user@host> show l2circuit connections
Layer-2 Circuit Connections:
Legend for connection status (St)
EI -- encapsulation invalid
NP -MM -- mtu mismatch
Dn -EM -- encapsulation mismatch
VC-Dn
CM -- control-word mismatch
Up -VM -- vlan id mismatch
CF -OL -- no outgoing label
IB -NC -- intf encaps not CCC/TCC
TM -BK -- Backup Connection
ST -CB -- rcvd cell-bundle size bad SP -LD -- local site signaled down
RS -RD -- remote site signaled down HS -XX -- unknown

interface h/w not present

down
-- Virtual circuit Down
operational
Call admission control failure
TDM incompatible bitrate
TDM misconfiguration
Standby Connection
Static Pseudowire
remote site standby
hot standby

Legend for interface status

Up -- operational

Copyright 2014, Juniper Networks, Inc.

2219

Interfaces Fundamentals for Routing Devices

Dn -- down
Neighbor: 10.255.245.51
Interface
Type St
Time last up
# Up trans
ge-2/0/2.600(vc 5)
rmt
Up
Dec 7 18:11:18 2009
1
Remote PE: 10.255.245.51, Negotiated control-word: No
Incoming label: 299856, Outgoing label: 299808
Negotiated PW status TLV: No
Local interface: ge-2/0/2.600, Status: Up, Encapsulation: VLAN

Sample Output
show l2circuit connections interface
user@host> show l2circuit connections interface t1-2/0/0:1:1.0
Layer-2 Circuit Connections:
Legend for connection status (St)
EI -- encapsulation invalid
NP -MM -- mtu mismatch
Dn -EM -- encapsulation mismatch
VC-Dn
CM -- control-word mismatch
Up -VM -- vlan id mismatch
CF -OL -- no outgoing label
IB -NC -- intf encaps not CCC/TCC
TM -BK -- Backup Connection
ST -CB -- rcvd cell-bundle size bad SP -LD -- local site signaled down
RS -RD -- remote site signaled down HS -XX -- unknown

interface h/w not present

down
-- Virtual circuit Down
operational
Call admission control failure
TDM incompatible bitrate
TDM misconfiguration
Standby Connection
Static Pseudowire
remote site standby
hot standby

Legend for interface status

Up -- operational
Dn -- down
Neighbor: 10.1.1.1
Interface
Type St
Time last up
# Up trans
t1-2/0/0:1:1.0(vc 1)(SP) rmt
Up
Apr 27 04:21:02 2011
1
Remote PE: 10.1.1.1, Negotiated control-word: Yes (Non-null)
Incoming label: 1010001, Outgoing label: 1000001
Negotiated PW status TLV: No
Local interface: t1-1/0/0:1:1.0, Status: Up, Encapsulation: SATOP-T1,
APS-active
Local interface: t1-2/0/0:1:1.0, Status: Up, Encapsulation: SATOP-T1,
APS-inactive

Sample Output
show l2circuit connections extensive
user@host>show l2circuit connections extensive
Layer-2 Circuit Connections:
Legend for connection status (St)
EI -- encapsulation invalid
NP -MM -- mtu mismatch
Dn -EM -- encapsulation mismatch
VC-Dn
CM -- control-word mismatch
Up -VM -- vlan id mismatch
CF -OL -- no outgoing label
IB -NC -- intf encaps not CCC/TCC
TM -BK -- Backup Connection
ST -CB -- rcvd cell-bundle size bad SP --

2220

interface h/w not present

down
-- Virtual circuit Down
operational
Call admission control failure
TDM incompatible bitrate
TDM misconfiguration
Standby Connection
Static Pseudowire

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

LD -- local site signaled down

RD -- remote site signaled down
XX -- unknown

RS -- remote site standby

HS -- hot standby

Legend for interface status

Up -- operational
Dn -- down
Neighbor: 10.255.49.149
Interface
Type St
Time last up
# Up trans
ae0.0(vc 100)
rmt
Up
Aug 31 09:36:12 2009
1
Remote PE: 10.255.49.149, Negotiated control-word: Yes (Null)
Incoming label: 299824, Outgoing label: 299776
Negotiated PW status TLV: Yes
local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
Local interface: ae0.0, Status: Up, Encapsulation: ETHERNET
Connection protection: Yes
Connection History:
Aug 31 09:36:12 2009 status update timer
Aug 31 09:36:12 2009 PE route changed
Aug 31 09:36:12 2009 Out lbl Update
299776
Aug 31 09:36:12 2009 In lbl Update
299824
Aug 31 09:36:12 2009 loc intf up
ae0.0

Sample Output
show l2circuit connections extensive (Pseudowire Redundancy with Hot Standby)
user@host>show l2circuit connections extensive
Layer-2 Circuit Connections:
Legend for connection status (St)
EI -- encapsulation invalid
NP -MM -- mtu mismatch
Dn -EM -- encapsulation mismatch
VC-Dn
CM -- control-word mismatch
Up -VM -- vlan id mismatch
CF -OL -- no outgoing label
IB -NC -- intf encaps not CCC/TCC
TM -BK -- Backup Connection
ST -CB -- rcvd cell-bundle size bad SP -LD -- local site signaled down
RS -RD -- remote site signaled down HS -XX -- unknown

interface h/w not present

down
-- Virtual circuit Down
operational
Call admission control failure
TDM incompatible bitrate
TDM misconfiguration
Standby Connection
Static Pseudowire
remote site standby
Hot-standby Connection

Legend for interface status

Up -- operational
Dn -- down
Neighbor: 88.0.0.101
Interface
Type St
Time last up
# Up trans
ge-1/3/2.600(vc 1)
rmt
Up
Jan 24 11:00:26 2013
1
Remote PE: 88.0.0.101, Negotiated control-word: Yes (Null)
Incoming label: 299776, Outgoing label: 299776
Negotiated PW status TLV: Yes
local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
Local interface: ge-1/3/2.600, Status: Up, Encapsulation: VLAN
Connection History:
Jan 24 11:00:26 2013 status update timer
Jan 24 11:00:26 2013 PE route changed
Jan 24 11:00:26 2013 Out lbl Update
299776
Jan 24 11:00:26 2013 In lbl Update
299776
Jan 24 11:00:26 2013 loc intf up
ge-1/3/2.600

Copyright 2014, Juniper Networks, Inc.

2221

Interfaces Fundamentals for Routing Devices

Neighbor: 88.0.0.102
Interface
Type St
Time last up
# Up trans
ge-1/3/2.600(vc 2)
rmt
HS
-------Remote PE: 88.0.0.102, Negotiated control-word: Yes (Null)
Incoming label: 299792, Outgoing label: 299776
Negotiated PW status TLV: Yes
local PW status code: 0x00000020, Neighbor PW status code: 0x00000000
Local interface: ge-1/3/2.600, Status: Up, Encapsulation: VLAN

2222

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show l2vpn connections

Syntax

Release Information

Description
Options

show l2vpn connections

<brief | extensive>
<down | up | up-down>
<history>
<instance instance>
<instance-history>
<local-site local-site>
<logical-system (all | logical-system-name)>
<remote-site remote-site>
<status>
<summary>

Command introduced before Junos OS Release 7.4.

instance-history option introduced in Junos OS Release 12.3R2.
Display Layer 2 virtual private network (VPN) connections.
noneDisplay all Layer 2 VPN connections for all routing instances.
brief | extensive(Optional) Display the specified level of output.
down | up | up-down(Optional) Display nonoperational, operational, or both kinds of

connections.
history(Optional) Display information about connection history.
instance instance(Optional) Display connections for the specified routing instance only.
instance-history(Optional) Display information about connection history for a particular

instance.
local-site local-site(Optional) Display connections for the specified Layer 2 VPN local

site name or ID only.

logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

remote-site remote-site(Optional) Display connection for the specified Layer 2 VPN

remote site ID only.

status(Optional) Display information about the connection and interface status.
summary(Optional) Display summary of all Layer 2 VPN connections information.

Required Privilege
Level
List of Sample Output

view

show l2vpn connections on page 2226

show l2vpn connections extensive on page 2227
show l2vpn connections extensive (VPWS) on page 2227

Copyright 2014, Juniper Networks, Inc.

2223

Interfaces Fundamentals for Routing Devices

Output Fields

Table 233 on page 2224 lists the output fields for the show l2vpn connections command.
Output fields are listed in the approximate order in which they appear.

Table 233: show l2vpn connections Output Fields

2224

Field Name

Field Description

Instance

Name of Layer 2 VPN instance.

L2vpn-id

For BGP autodiscovery, a globally unique Layer 2 VPN community identifier for
the instance.

Local-ID

BGP local-address assigned to the local routing device.

Local site

Name of local site.

Local
source-attachment-id

For FEC 129, the VPWS source attachment identifier. The point-to-point nature
of VPWS requires that you specify the source access individual identifier (SAII)
and the target access individual identifier (TAII). This SAII-TAII pair defines a
unique pseudowire between two PE devices.

Target-attachment-id

For FEC 129, the VPWS target attachment identifier. If the configured target
identifier matches a source identifier advertised by a remote PE device by way
of a BGP auto-discovery message, the pseudowire between that source-target
pair is signaled. If there is no match between an advertised source identifier and
the configured target identifier, the pseudowire is not established.

Interface name

Name of interface.

Remote Site ID

Remote site ID.

Label Offset

Numbers within the label block that are skipped to find the next label base.

Label-base

Advertises the first label in a block of labels. A remote PE router uses this first
label when sending traffic toward the advertising PE router.

Range

Advertises the label block size.

status-vector

Bit vector advertising the state of local PE-CE circuits to remote PE routers. A
bit value of 0 indicates that the local circuit and LSP tunnel to the remote PE
router are up, whereas a value of 1 indicates either one or both are down.

connection-site

Name of the connection site.

Type

Type of connection: loc (local) or rmt (remote).

St

Status of the connection. (For a list of possible values, see the Legend for
connection status (St) field.)

Time last up

Time that the connection was last in the Up condition.

# Up trans

Number of transitions from Down to Up condition.

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 233: show l2vpn connections Output Fields (continued)

Field Name

Field Description

Local circuit

Address and status of local circuit.

Remote circuit

Address and status of remote circuit.

St

Status of the Layer 2 VPN connection (corresponds with Legend for Connection
Status):

EIThe local Layer 2 VPN interface is configured with an encapsulation that

is not supported.

EMThe encapsulation type received on this Layer 2 VPN connection from

the neighbor does not match the local Layer 2 VPN connection interface
encapsulation type.

VC-DnThe virtual circuit is currently down.

CMThe two routers do not agree on a control word, which causes a control

word mismatch.

CNThe virtual circuit is not provisioned properly.

ORThe label associated with the virtual circuit is out of range.

OLNo advertisement has been received for this virtual circuit from the

neighbor. There is no outgoing label available for use by this virtual circuit.

LDAll of the CE-facing interfaces to the local site are down. Therefore, the

connection to the local site is signaled as down to the other PE routers. No

pseudowires can be established.

RDAll the interfaces to the remote neighbor are down. Therefore, the remote

site has been signaled as down to the other PE routers. No pseudowires can
be established.

LNThe local site has lost path selection to the remote site and therefore

no pseduowires can be established from this local site.

RNThe remote site has lost path selection to a local site or other remote

site and therefore no pseudowires are established to this remote site.

XXThe Layer 2 VPN connection is down for an unn reason. This is a

programming error.

NCThe interface encapsulation is not configured as an appropriate CCC,

TCC, or Layer 2 VPN encapsulation.

WEThe encapsulation configured for the interface does not match the

encapsulation configured for the associated connection within the Layer 2

VPN routing instance.

NPThe router detects that interface hardware is not present. The hardware

might be offline, a PIC might not be of the desired type, or the interface might
be configured in a different routing instance.

->Only the outbound connection is up.

<-Only the inbound connection is up.

UpThe Layer 2 VPN connection is operational.

DnThe Layer 2 VPN connection is down.

CFThe router cannot find enough bandwidth to the remote router to satisfy

the Layer 2 VPN connection bandwidth requirement.

SCThe local site identifier matches the remote site identifier. No pseudowire

can be established between these two sites. You should configure different
values for the local and remote site identifiers.

Copyright 2014, Juniper Networks, Inc.

2225

Interfaces Fundamentals for Routing Devices

Table 233: show l2vpn connections Output Fields (continued)

Field Name

Field Description

LMThe local site identifier is not the minimum designated, meaning it is not

the lowest. There is another local site with a lower site identifier. Pseudowires
are not being established to this local site. and the associated local site
identifier is not being used to distribute Layer 2 VPN label blocks. However,
this is not an error state. Traffic continues to be forwarded to the PE router
interfaces connected to the local sites when the local sites are in this state.

RMThe remote site identifier is not the minimum designated, meaning it is

not the lowest. There is another remote site connected to the same PE router
which has lower site identifier. The PE router cannot established a pseduowire
to this remote site and the associated remote site identifier cannot be used
to distribute VPLS label blocks. However, this is not an error state. Traffic can
continue to be forwarded to the PE router interface connected to this remote
site when the remote site is in this state.

ILThe incoming packets for the Layer 2 VPN connection have no MPLS

label.
Remote PE

Address of the remote provider edge router.

Incoming label

Name of the incoming label.

Outgoing label

Name of the outgoing label.

Egress Protection

Whether the given PVC is protected by connection protection logic using egress
protection for BGP signaled layer 2 services.

Time

Date and time of Layer 2 VPN connection event.

Event

Type of event.

Interface/Lbl/PE

Interface, label, or PE router.

Sample Output
show l2vpn connections
user@host> show l2vpn connections
L2VPN Connections :
Instance : vpna
Edge protection: Not-Primary
Local site: 2 (ce-2)
offset: 1, range: 3, label-base: 32768
connection-site
Type St Time last up
3 (3)
loc
Up Jul 18 20:45:46 2001
Local circuit: fe-0/0/0.1, Status: Up
Remote circuit: fe-0/0/3.0, Status: Up
1
rmt
Up Jul 18 21:47:25 2001
Local circuit: fe-0/0/0.0, Status: Up
Remote PE: 192.0.2.1
Incoming label: 32768, Outgoing label: 32769
Local site: 3 (ce-3)
offset: 1, range: 2, label-base: 33792
connection-site
Type St Time last up

2226

# Up trans
1

# Up trans

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

2 (ce-b)
loc
Up Jul 18 20:45:46 2001
Local circuit: fe-0/0/0.1, Status: Up
Remote circuit: fe-0/0/3.0, Status: Up
1
rmt
Up Jul 18 21:47:25 2001
Local circuit: fe-0/0/3.1, Status: Up
Remote PE: 192.0.2.1
Incoming label: 33792, Outgoing label: 32770

show l2vpn connections extensive

user@host> show l2vpn connections extensive
L2VPN Connections:
Instance: vpn-a
Edge protection: Not-Primary
Local site: ce-a (1)
Interface name
Remote Site ID
fe-0/0/0.0
2
Label Offset
Offset
Range
32768
1
2
connection-site
Type St Time last up
# Up trans
2
rmt
Up Aug 3 00:08:14 2001
1
Local circuit: fe-0/0/0.0, Status: Up
Remote PE: 192.168.24.1
Incoming label: 32769, Outgoing label: 32768
Egress Protection: Yes
Time
Event
Interface/Lbl/PE
Aug 3 00:08:14 2001 PE route up
Aug 3 00:08:14 2001 Out lbl Update
32768
Aug 3 00:08:14 2001 In lbl Update
32769
Aug 3 00:08:14 2001 ckt0 up
fe-0/0/0.0

show l2vpn connections extensive (VPWS)

user@host> show l2vpn connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid
NC
EM -- encapsulation mismatch
WE
VC-Dn -- Virtual circuit down
NP
CM -- control-word mismatch
->
CN -- circuit not provisioned
<OR -- out of range
Up
OL -- no outgoing label
Dn
LD -- local site signaled down
CF
RD -- remote site signaled down SC
LN -- local site not designated LM
RN -- remote site not designated RM
XX -- unknown connection status IL
MM -- MTU mismatch
MI
BK -- Backup connection
ST
PF -- Profile parse failure
PB
RS -- remote site standby
SN
LB -- Local site not best-site
RB
VM -- VLAN ID mismatch

------------------

interface encapsulation not CCC/TCC/VPLS

interface and instance encaps not same
interface hardware not present
only outbound connection is up
only inbound connection is up
operational
down
call admission control failure
local and remote site ID collision
local site ID not minimum designated
remote site ID not minimum designated
no incoming label
Mesh-Group ID not available
Standby connection
Profile busy
Static Neighbor
Remote site not best-site

Legend for interface status

Up -- operational
Dn -- down
Instance: FEC129-VPWS

Copyright 2014, Juniper Networks, Inc.

2227

Interfaces Fundamentals for Routing Devices

L2vpn-id: 100:100
Number of local interfaces: 1
Number of local interfaces up: 1
ge-2/0/5.0
Local source-attachment-id: 1 (ONE)
Target-attachment-id
Type St
Time last up
# Up trans
2
rmt
Up
Nov 28 16:16:14 2012
1
Remote PE: 198.51.100.2, Negotiated control-word: No
Incoming label: 299792, Outgoing label: 299792
Local interface: ge-2/0/5.0, Status: Up, Encapsulation: ETHERNET
Connection History:
Nov 28 16:16:14 2012 status update timer
Nov 28 16:16:14 2012 PE route changed
Nov 28 16:16:14 2012 Out lbl Update
299792
Nov 28 16:16:14 2012 In lbl Update
299792
Nov 28 16:16:14 2012 loc intf up
ge-2/0/5.0

2228

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show mvpn c-multicast

Syntax

Release Information
Description
Options

show mvpn c-multicast

<extensive | summary>
<instance-name instance-name>

Command introduced in Junos OS Release 8.4.

Display the multicast VPN customer multicast route information.
extensive | summary(Optional) Display the specified level of output.
instance-name instance-name(Optional) Display output for the specified routing

instance.
Required Privilege
Level
List of Sample Output

Output Fields

view

show mvpn c-multicast on page 2230

show mvpn c-multicast summary on page 2230
show mvpn c-multicast extensive on page 2230
Table 234 on page 2229 lists the output fields for the show mvpn c-multicast command.
Output fields are listed in the approximate order in which they appear.

Table 234: show mvpn c-multicast Output Fields

Field Name

Field Description

Level of Output

Instance

Name of the VPN routing instance.

summary extensive

none
C-mcast IPv4 (S:G)

Customer router IPv4 multicast address.

extensive none

Ptnl

Provider tunnel attributes, tunnel type:tunnel source, tunnel destination group.

extensive none

St

State:

extensive none

DSRepresents (S,G) and is created due to (*,G)

RMRemote VPN route learned from the remote PE router

St display blankSSM group join

MVPN instance

Name of the multicast VPN routing instance

extensive none

C-multicast IPv4
route count

Number of customer multicast IPv4 routes associated with the multicast VPN
routing instance.

summary

C-multicast IPv6
route count

Number of customer multicast IPv6 routes associated with the multicast VPN
routing instance.

summary

Copyright 2014, Juniper Networks, Inc.

2229

Interfaces Fundamentals for Routing Devices

Sample Output
show mvpn c-multicast
user@host> show mvpn c-multicast
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.78/32:225.5.5.5/32 PIM-SM:10.255.14.144, 239.1.1.1
MVPN instance:

RM

Legend for provider tunnel

I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.94/32:226.6.6.6/32 PIM-SM:10.255.14.144, 239.2.0.0

RM

show mvpn c-multicast summary

user@host> show mvpn c-multicast summary
MVPN Summary:
Instance: VPN-A
C-multicast IPv4 route count: 1
Instance: VPN-B
C-multicast IPv4 route count: 2

show mvpn c-multicast extensive

user@host> show mvpn c-multicast extensive
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.78/32:225.5.5.5/32 PIM-SM:10.255.14.144, 239.1.1.1
MVPN instance:

RM

Legend for provider tunnel

I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.94/32:226.6.6.6/32 PIM-SM:10.255.14.144, 239.2.0.0

2230

RM

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show mvpn instance

Syntax

Release Information
Description
Options

show mvpn instance

<extensive | summary>
<instance instance-name>

Command introduced in Junos OS Release 8.4.

Display the multicast VPN routing instance information.
extensive | summary(Optional) Display the specified level of output.
instance instance-name(Optional) Display statistics for the specified routing instance.

Required Privilege
Level
List of Sample Output

Output Fields

view

show mvpn instance on page 2232

show mvpn instance on page 2232
show mvpn instance summary on page 2233
show mvpn instance extensive on page 2233
show mvpn instance summary (IPv6) on page 2233
Table 235 on page 2231 lists the output fields for the show mvpn instance command. Output
fields are listed in the approximate order in which they appear.

Table 235: show mvpn instance Output Fields

Field Name

Field Description

Level of Output

MVPN instance

Name of the multicast VPN routing instance

extensive none

Instance

Name of the VPN routing instance.

summary extensive

none
Provider tunnel

Provider tunnel attributes, tunnel type:tunnel source, tunnel destination group.

extensive none

Neighbor

Address, type of provider tunnel (I-P-tnl, inclusive provider tunnel and S-P-tnl,
selective provider tunnel) and provider tunnel for each neighbor.

extensive none

C-mcast IPv4 (S:G)

Customer IPv4 router multicast address.

extensive none

C-mcast IPv6 (S:G)

Customer IPv6 router multicast address.

extensive none

Ptnl

Provider tunnel attributes, tunnel type:tunnel source, tunnel destination group.

extensive none

St

State:

extensive none

DSRepresents (S,G) and is created due to (*,G)

RMRemote VPN route learned from the remote PE router

St display blankSSM group join

Copyright 2014, Juniper Networks, Inc.

2231

Interfaces Fundamentals for Routing Devices

Table 235: show mvpn instance Output Fields (continued)

Field Name

Field Description

Level of Output

Neighbor count

Number of neighbors associated with the multicast VPN routing instance.

summary

C-multicast IPv4
route count

Number of customer multicast IPv4 routes associated with the multicast VPN
routing instance.

summary

C-multicast IPv6
route count

Number of customer multicast IPv6 routes associated with the multicast VPN
routing instance.

summary

Sample Output
show mvpn instance
user@host> show mvpn instance
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Provider tunnel: I-P-tnl:PIM-SM:10.255.14.144, 239.1.1.1
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.1.1.1
10.255.70.17
PIM-SM:10.255.70.17, 239.1.1.1
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.78/32:225.5.5.5/32 PIM-SM:10.255.14.144, 239.1.1.1
MVPN instance:

RM

Legend for provider tunnel

I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
Provider tunnel: I-P-tnl:PIM-SM:10.255.14.144, 239.2.0.0
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.2.0.0
10.255.70.17
PIM-SM:10.255.70.17, 239.2.0.0
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.94/32:226.6.6.6/32 PIM-SM:10.255.14.144, 239.2.0.0

RM

show mvpn instance

user@host> show mvpn instance
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance : vpn-1
MVPN Mode : SPT-ONLY
Provider tunnel: I-P-tnl:LDP-P2MP:10.255.72.162, lsp-id 16777217

2232

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Neighbor
10.255.72.160
10.255.72.166
13054,10.255.72.166
10.255.72.168

I-P-tnl
LDP-P2MP:10.255.72.160, lsp-id 16777217
RSVP-TE P2MP:10.255.72.166,

Sample Output
show mvpn instance summary
user@host> show mvpn instance summary
MVPN Summary:
Instance: VPN-A
Neighbor count: 2
C-multicast IPv4 route count: 1
Instance: VPN-B
Neighbor count: 4
C-multicast IPv4 route count: 2

Sample Output
show mvpn instance extensive
user@host> show mvpn instance extensive
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Provider tunnel: I-P-tnl:PIM-SM:10.255.14.144, 239.1.1.1
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.1.1.1
10.255.70.17
PIM-SM:10.255.70.17, 239.1.1.1
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.78/32:225.5.5.5/32 PIM-SM:10.255.14.144, 239.1.1.1
MVPN instance:

RM

Legend for provider tunnel

I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
Provider tunnel: I-P-tnl:PIM-SM:10.255.14.144, 239.2.0.0
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.2.0.0
10.255.70.17
PIM-SM:10.255.70.17, 239.2.0.0
C-mcast IPv4 (S:G)
Ptnl
St
192.168.195.94/32:226.6.6.6/32 PIM-SM:10.255.14.144, 239.2.0.0

RM

show mvpn instance summary (IPv6)

user@host> show mvpn instance summary
MVPN Summary:
Instance: VPN-A
C-multicast IPv6 route count: 2
Instance: VPN-B
C-multicast IPv6 route count: 2

Copyright 2014, Juniper Networks, Inc.

2233

Interfaces Fundamentals for Routing Devices

2234

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show mvpn neighbor

Syntax

Release Information
Description
Options

show mvpn neighbor

<extensive | summary>
<inet | inet6>
<instance instance-name | neighbor-address address>
<logical-system logical-system-name>

Command introduced in Junos OS Release 8.4.

Display multicast VPN neighbor information.
extensive | summary(Optional) Display the specified level of output for all multicast

VPN neighbors.
inet | inet6(Optional) Display IPv4 or IPv6 information for all multicast VPN neighbors.
instance instance-name | neighbor-address address(Optional) Display multicast VPN

neighbor information for the specified instance or the specified neighbor.

logical-system logical-system-name(Optional) Display multicast VPN neighbor

information for the specified logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show mvpn neighbor on page 2236

show mvpn neighbor extensive on page 2236
show mvpn neighbor extensive on page 2236
show mvpn neighbor instance-name on page 2237
show mvpn neighbor neighbor-address on page 2237
show mvpn neighbor neighbor-address summary on page 2237
show mvpn neighbor neighbor-address extensive on page 2238
show mvpn neighbor neighbor-address instance-name on page 2238
Table 236 on page 2235 lists the output fields for the show mvpn neighbor command. Output
fields are listed in the approximate order in which they appear.

Table 236: show mvpn neighbor Output Fields

Field Name

Field Description

Level of Output

MVPN instance

Name of the multicast VPN routing instance

extensive none

Instance

Name of the VPN routing instance.

summary extensive

none
Neighbor

Address, type of provider tunnel (I-P-tnl, inclusive provider tunnel and S-P-tnl,
selective provider tunnel) and provider tunnel for each neighbor.

extensive none

Provider tunnel

Provider tunnel attributes, tunnel type:tunnel source, tunnel destination group.

extensive none

Copyright 2014, Juniper Networks, Inc.

2235

Interfaces Fundamentals for Routing Devices

Sample Output
show mvpn neighbor
user@host> show mvpn neighbor
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.1.1.1
10.255.70.17
PIM-SM:10.255.70.17, 239.1.1.1
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.2.0.0
10.255.70.17
PIM-SM:10.255.70.17, 239.2.0.0

Sample Output
show mvpn neighbor extensive
user@host> show mvpn neighbor extensive
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.1.1.1
10.255.70.17
PIM-SM:10.255.70.17, 239.1.1.1
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.2.0.0
10.255.70.17
PIM-SM:10.255.70.17, 239.2.0.0

show mvpn neighbor extensive

user@host> show mvpn neighbor extensive

2236

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: mvpn-a
Neighbor
I-P-tnl
10.255.72.45
10.255.72.50
LDP P2MP:10.255.72.50, lsp-id 1

Sample Output
show mvpn neighbor instance-name
user@host> show mvpn neighbor instance-name VPN-A
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.1.1.1
10.255.70.17
PIM-SM:10.255.70.17, 239.1.1.1

Sample Output
show mvpn neighbor neighbor-address
user@host> show mvpn neighbor neighbor-address 10.255.14.160
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.1.1.1
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
Neighbor
I-P-tnl
10.255.14.160
PIM-SM:10.255.14.160, 239.2.0.0

Sample Output
show mvpn neighbor neighbor-address summary
user@host> show mvpn neighbor neighbor-address 10.255.70.17 summary

Copyright 2014, Juniper Networks, Inc.

2237

Interfaces Fundamentals for Routing Devices

MVPN Summary:
Instance: VPN-A
Instance: VPN-B

Sample Output
show mvpn neighbor neighbor-address extensive
user@host> show mvpn neighbor neighbor-address 10.255.70.17 extensive
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Neighbor
I-P-tnl
10.255.70.17
PIM-SM:10.255.70.17, 239.1.1.1
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-B
Neighbor
I-P-tnl
10.255.70.17
PIM-SM:10.255.70.17, 239.2.0.0

Sample Output
show mvpn neighbor neighbor-address instance-name
user@host> show mvpn neighbor neighbor-address 10.255.70.17 instance-name VPN-A
MVPN instance:
Legend for provider tunnel
I-P-tnl -- inclusive provider tunnel S-P-tnl -- selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g)
RM -- remote VPN route
Instance: VPN-A
Neighbor
I-P-tnl
10.255.70.17
PIM-SM:10.255.70.17, 239.1.1.1

2238

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show vpls connections

Syntax

Release Information

Description

Options

show vpls connections

<brief | extensive>
<down | up | up-down>
<history>
<instance instance-name local-site local-site-name remote-site remote-site-name>
<instance-history>
<logical-system (all | logical-system-name)>
<status>
<summary>

Command introduced before Junos OS Release 7.4.

instance-history option introduced in Junos OS Release 12.3R2.
(T Series and M Series routers, except for the M160 router) Display virtual private LAN
service (VPLS) connection information.
noneDisplay information about all VPLS connections for all routing instances.
brief | extensive(Optional) Display the specified level of output.
down | up | up-down(Optional) Display nonoperational, operational, or both types of

connections.
history(Optional) Display information about connection history.
instance instance-name(Optional) Display the VPLS connections for the specified

routing instance only.

instance-history(Optional) Display information about connection history for a particular

instance.
local-site local-site-name(Optional) Display the VPLS connections for the specified

local site name or ID only.

remote-site remote-site-name(Optional) Display the VPLS connections for the specified

remote site name or ID only. Label block size information is always shown as 0 when
using this option.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

status(Optional) Display information about the connection and interface status.
summary(Optional) Display summary of all VPLS connections information.

Required Privilege
Level
List of Sample Output

view

show vpls connections on page 2245

show vpls connections (with multiple pseudowires) on page 2247

Copyright 2014, Juniper Networks, Inc.

2239

Interfaces Fundamentals for Routing Devices

show vpls connections extensive (Static VPLS Neighbors) on page 2248

Output Fields

Table 237 on page 2240 lists the output fields for the show vpls connections command.
Output fields are listed in the approximate order in which they appear.

Table 237: show vpls connections Output Fields

Field Name

Field Description

Instance

Name of the VPLS instance.

Local site

Name of the local site.

VPLS-id

Idenitfier for the VPLS site.

Number of local
interfaces

Number of interfaces configured for the local site.

Number of local
interfaces up

Number of interfaces configured for the local site that are currently up.

IRB interface
present

Indicates whether or not an integrated routing and bridging (IRB) interface is

present (yes or no).

Intf

List of all of the interfaces configured for the local site. The types of interfaces
can include VPLS virtual loopback tunnel interfaces and label-switched
interfaces. Any interface that supports VPLS could be listed here.
Virtual loopback tunnel interfaces are displayed using the vt-fpc/pic/port.nnnnn
format. Label-switched interfaces are displayed using the lsi.nnnnn format. In
both cases, nnnnn is a dynamically generated virtual port used to transport and
receive packets from other provider edge (PE) routers in the VPLS domain.
Each interface might include the following information:

Interface flags

Identification as a VPLS interface

Name of the associated VPLS routing instance

Local site number

Remote site number

VPLS neighbor address

VPLS identifier

Flag associated with the interface. Can include the following:

2240

VC-DownThe virtual circuit associated with this interface is down.

Label-base

First label in a block of labels. A remote PE router uses this first label when
sending traffic toward the advertising PE router.

Offset

Displays the VPLS Edge (VE) block offset in the Layer 2 VPN NLRI. The VE block
offset is used to identify a label block from which a particular label value is
selected to setup a pseduowire for a remote site. The block offset value itself
indicates the starting VE ID that maps to the label base contained in the VPLS
NLRI advertisement.

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 237: show vpls connections Output Fields (continued)

Field Name

Field Description

Size

Label block size. A configurable value that represents the number of label blocks
required to cover all the pseudowires for the remote peer. Acceptable
configuration values are: 2, 4, 8 and 16. The default value is 2. A value of 0 will
be displayed when using the remote-site option.

Range

Label block range.

Preference

Preference value advertised for a VPLS site. When multiple PE routers are
assigned the same VE ID for multihoming, you might need to specify that a
particular PE router acts as the designated forwarder by configuring the site
preference value. The site preference indicates the degree of preference for a
particular customer site. The site preference is one of the tie-breaking criteria
used in a designated forwarder election.

status-vector

Bit vector advertising the state of local PE-CE circuits to remote PE routers. A
bit value of 0 indicates that the local circuit and LSP tunnel to the remote PE
router are up, whereas a value of 1 indicates either one or both are down.

connection-site

Name of the connection site.

Neighbor

IP address and VPLS identifier for the VPLS neighbor. If multiple pseudowires
have been configured, the IP address will also show the PW-specific vpls-id-list
(protocols vpls mesh-group), for example, 10.255.144.4 (vpls-id 200).

Type

Type of connection: loc (local) or rmt (remote).

Copyright 2014, Juniper Networks, Inc.

2241

Interfaces Fundamentals for Routing Devices

Table 237: show vpls connections Output Fields (continued)

Field Name

Field Description

St

2242

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 237: show vpls connections Output Fields (continued)

Field Name

Field Description
Status of the VPLS connection (corresponds with Legend for Connection
Status):

EIThe local VPLS interface is configured with an encapsulation that is not

supported.

EMThe encapsulation type received on this VPLS connection from the

neighbor does not match the local VPLS connection interface encapsulation
type.

VC-DnThe virtual circuit is currently down.

CMThe two routers do not agree on a control word, which causes a control

word mismatch.

CNThe virtual circuit is not provisioned properly.

ORThe label associated with the virtual circuit is out of range.

OLNo advertisement has been received for this virtual circuit from the

neighbor. There is no outgoing label available for use by this virtual circuit.

LDAll of the CE-facing interfaces to the local site are down. Therefore, the

connection to the local site is signaled as down to the other PE routers. No

pseudowires can be established.

RDAll the interfaces to the remote neighbor are down. Therefore, the remote

site has been signaled as down to the other PE routers. No pseudowires can
be established.

LNThe local site has lost path selection to the remote site and therefore

no pseduowires can be established from this local site.

RNThe remote site has lost path selection to a local site or other remote

site and therefore no pseudowires are established to this remote site.

In a multihoming configuration, one multihomed PE site displays the state
LN, and the other multihomed PE site displays the state RN in the following
circumstances:

The multihomed links are both configured to be the backup site.

The two multihomed PE routers have the same site ID, but have a peering
relationship with a route reflector (RR) that has a different site ID.

XXThe VPLS connection is down for an unn reason. This is a programming

error.

MMThe MTU for the local site and the remote site do not match.

BKThe router is using a backup connection.

PFProfile parse failure.

RSThe remote site is in a standby state.

NCThe interface encapsulation is not configured as an appropriate CCC,

TCC, or VPLS encapsulation.

WEThe encapsulation configured for the interface does not match the

encapsulation configured for the associated connection within the VPLS

routing instance.

NPThe router detects that interface hardware is not present. The hardware

might be offline, a PIC might not be of the desired type, or the interface might
be configured in a different routing instance.

Copyright 2014, Juniper Networks, Inc.

->Only the outbound connection is up.

<-Only the inbound connection is up.

UpThe VPLS connection is operational.

2243

Interfaces Fundamentals for Routing Devices

Table 237: show vpls connections Output Fields (continued)

Field Name

Field Description

DnThe VPLS connection is down.

CFThe router cannot find enough bandwidth to the remote router to satisfy

the VPLS connection bandwidth requirement.

SCThe local site identifier matches the remote site identifier. No pseudowire

can be established between these two sites. You should configure different
values for the local and remote site identifiers.

LMThe local site identifier is not the minimum designated, meaning it is not

the lowest. There is another local site with a lower site identifier. Pseudowires
are not being established to this local site. and the associated local site
identifier is not being used to distribute VPLS label blocks. However, this is
not an error state. Traffic continues to be forwarded to the PE router interfaces
connected to the local sites when the local sites are in this state.

RMThe remote site identifier is not the minimum designated, meaning it is

not the lowest. There is another remote site connected to the same PE router
which has lower site identifier. The PE router cannot established a pseduowire
to this remote site and the associated remote site identifier cannot be used
to distribute VPLS label blocks. However, this is not an error state. Traffic can
continue to be forwarded to the PE router interface connected to this remote
site when the remote site is in this state.

ILThe incoming packets for the VPLS connection have no MPLS label.

MIThe configured mesh group identifier is in use by another system in the

network.

2244

STThe router has switched to a standby connection.

PBProfile busy.

SNThe VPLS neighbor is static.

Time last up

Time connection was last in the Up condition.

# Up trans

Number of transitions from Down to Up condition.

Status

Status of the (local or remote circuit) local interface:

UpOperational

DnDown

NPNot present

DSDisabled

WEWrong encapsulation

UNUninitialized

Encapsulation

Type of encapsulation: VPLS.

Remote PE

Address of the remote provider edge router.

Negotiated
control-word

Whether a control word has been negotiated: Yes or No.

Incoming label

Name of the incoming label.

Outgoing label

Name of the outgoing label.

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 237: show vpls connections Output Fields (continued)

Field Name

Field Description

Negotiated PW
status TLV

Indicates whether or not the pseudowire status TLV has been negotiated for
the VPLS connection.

Local interface

Provides the following information about the local interface configured for the
VPLS neighbor:

Name of the local interface

StatusInterface status (Up or Down)

EncapsulationInterface encapsulation (for example, ETHERNET)

DescriptionIncludes the VPLS instance name, the VPLS neighbor address,

and the VPLS identifier

Time

Date and time of VPLS connection event.

Event

Type of event.

Interface/Lbl/PE

Interface, label, or PE router.

Connection History

Each entry can include the date, time, year, and the connection event. Connection
events include any of a variety of events related to VPLS connections, such as
route changes, label updates, and interfaces going down or coming up.

Sample Output
show vpls connections
user@host> show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid
NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch
WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down
NP -- interface hardware not present
CM -- control-word mismatch
-< -- only outbound connection is up
CN -- circuit not provisioned
>- -- only inbound connection is up
OR -- out of range
Up -- operational
OL -- no outgoing label
Dn -- down
LD -- local site signaled down
CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unn connection status IL -- no incoming label
MM -- MTU mismatch
MI -- Mesh-Group ID not availble
BK -- Backup connection
ST -- Standby connection
PF -- Profile parse failure
PB -- Profile busy
Legend for interface status
Up -- operational
Dn -- down
Instance: vpls-1
Local site: 1 (11)
Number of local interfaces: 1

Copyright 2014, Juniper Networks, Inc.

2245

Interfaces Fundamentals for Routing Devices

Number of local interfaces up: 1

IRB interface present: no
lt-1/3/0.10496
vt-1/3/0.1048588
1
Intf - vpls vpls-1 local site 11 remote site 1

2246

vt-1/2/0.1048591

Intf - vpls vpls-1 local site 11 remote site 2

vt-1/2/0.1048585

Intf - vpls vpls-1 local site 11 remote site 3

vt-1/2/0.1048587

Intf - vpls vpls-1 local site 11 remote site 4

vt-1/2/0.1048589

Intf - vpls vpls-1 local site 11 remote site 5

vt-1/3/0.1048586

Intf - vpls vpls-1 local site 11 remote site 6

vt-1/3/0.1048590

Intf - vpls vpls-1 local site 11 remote site 7

vt-1/3/0.1048584

Intf - vpls vpls-1 local site 11 remote site 8

Label-base
Offset
Size Range
Preference
800256
1
16
16
100
Timer Values:
Startup wait time: 120 seconds
New site wait-time: 20 seconds
Collision detect time: 30 seconds
Reclaim wait time: 748 milliseconds
connection-site
Type St
Time last up
# Up trans
1
rmt
Up
Apr 28 13:28:24 2009
2
Remote PE: 124.1.2.1, Negotiated control-word: No
Incoming label: 800256, Outgoing label: 800026
Local interface: vt-1/3/0.1048588, Status: Up, Encapsulation: VPLS
Description: Intf - vpls vpls-1 local site 11 remote site 1
Connection History:
Apr 28 13:28:24 2009 status update timer
Apr 28 13:28:24 2009 PE route down
Apr 28 13:24:27 2009 status update timer
Apr 28 13:24:27 2009 loc intf up
vt-1/3/0.1048588
Apr 28 13:24:27 2009 PE route changed
Apr 28 13:24:27 2009 Out lbl Update
800026
Apr 28 13:24:27 2009 In lbl Update
800256
Apr 28 13:24:27 2009 loc intf down
2
rmt
Up
Apr 28 13:28:24 2009
2
Remote PE: 124.1.7.1, Negotiated control-word: No
Incoming label: 800257, Outgoing label: 800034
Local interface: vt-1/2/0.1048591, Status: Up, Encapsulation: VPLS
Description: Intf - vpls vpls-1 local site 11 remote site 2
Connection History:
Apr 28 13:28:24 2009 status update timer
Apr 28 13:28:24 2009 PE route down
Apr 28 13:24:28 2009 status update timer
Apr 28 13:24:28 2009 loc intf up
vt-1/2/0.1048591
Apr 28 13:24:28 2009 PE route changed
Apr 28 13:24:28 2009 Out lbl Update
800034
Apr 28 13:24:28 2009 In lbl Update
800257
Apr 28 13:24:28 2009 loc intf down
3
rmt
Up
Apr 28 13:28:24 2009
2
Remote PE: 124.1.4.1, Negotiated control-word: No
Incoming label: 800258, Outgoing label: 800026
Local interface: vt-1/2/0.1048585, Status: Up, Encapsulation: VPLS
Description: Intf - vpls vpls-1 local site 11 remote site 3
Connection History:

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Apr
Apr
Apr
Apr
Apr
Apr
Apr
Apr

28
28
28
28
28
28
28
28

13:28:24
13:28:24
13:24:26
13:24:26
13:24:26
13:24:26
13:24:26
13:24:26

2009
2009
2009
2009
2009
2009
2009
2009

status update timer

PE route down
status update timer
loc intf up
vt-1/2/0.1048585
PE route changed
Out lbl Update
800026
In lbl Update
800258
loc intf down
4
rmt
Up
Apr 28 13:28:24 2009
Remote PE: 124.1.6.1, Negotiated control-word: No
Incoming label: 800259, Outgoing label: 800026
Local interface: vt-1/2/0.1048587, Status: Up, Encapsulation: VPLS
Description: Intf - vpls vpls-1 local site 11 remote site 4
Connection History:
Apr 28 13:28:24 2009 status update timer
Apr 28 13:28:24 2009 PE route down
Apr 28 13:24:27 2009 status update timer
Apr 28 13:24:27 2009 loc intf up
vt-1/2/0.1048587
Apr 28 13:24:27 2009 PE route changed
Apr 28 13:24:27 2009 Out lbl Update
800026
Apr 28 13:24:27 2009 In lbl Update
800259
Apr 28 13:24:27 2009 loc intf down
5
rmt
Up
Apr 28 13:28:24 2009
Remote PE: 124.1.3.1, Negotiated control-word: No
Incoming label: 800260, Outgoing label: 800034
Local interface: vt-1/2/0.1048589, Status: Up, Encapsulation: VPLS
Description: Intf - vpls vpls-1 local site 11 remote site 5
Connection History:
Apr 28 13:28:24 2009 status update timer
Apr 28 13:28:24 2009 PE route down
Apr 28 13:24:28 2009 status update timer
Apr 28 13:24:28 2009 loc intf up
vt-1/2/0.1048589
Apr 28 13:24:28 2009 PE route changed
Apr 28 13:24:28 2009 Out lbl Update
800034
Apr 28 13:24:27 2009 In lbl Update
800260
Apr 28 13:24:27 2009 loc intf down

show vpls connections (with multiple pseudowires)

user@host> show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid
NC
EM -- encapsulation mismatch
WE
VC-Dn -- Virtual circuit down
NP
CM -- control-word mismatch
->
CN -- circuit not provisioned
<OR -- out of range
Up
OL -- no outgoing label
Dn
LD -- local site signaled down
CF
RD -- remote site signaled down SC
LN -- local site not designated LM
RN -- remote site not designated RM
XX -- unknown connection status IL
MM -- MTU mismatch
MI
BK -- Backup connection
ST
PF -- Profile parse failure
PB
RS -- remote site standby
SN
LB -- Local site not best-site
RB
VM -- VLAN ID mismatch

Copyright 2014, Juniper Networks, Inc.

------------------

interface encapsulation not CCC/TCC/VPLS

interface and instance encaps not same
interface hardware not present
only outbound connection is up
only inbound connection is up
operational
down
call admission control failure
local and remote site ID collision
local site ID not minimum designated
remote site ID not minimum designated
no incoming label
Mesh-Group ID not available
Standby connection
Profile busy
Static Neighbor
Remote site not best-site

2247

Interfaces Fundamentals for Routing Devices

Legend for interface status

Up -- operational
Dn -- down
Instance: vpls
VPLS-id: 100
Mesh-group connections: __ves__
Neighbor
Type St
Time last up
# Up trans
10.255.114.3 (vpls-id 100) rmt
Up
Apr 11 23:38:38 2013
1
Remote PE: 10.255.114.3, Negotiated control-word: No
Incoming label: 262145, Outgoing label: 262145
Negotiated PW status TLV: No
Local interface: lsi.1049090, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls h-vpls neighbor 10.255.114.3 vpls-id 100
Mesh-group connections: spokes
Neighbor
Type St
Time last up
# Up trans
10.255.114.4 (vpls-id 200) rmt
Up
Apr 11 23:39:25 2013
1
Remote PE: 10.255.114.4, Negotiated control-word: No
Incoming label: 262148, Outgoing label: 304224
Negotiated PW status TLV: Yes
local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
Local interface: lsi.1049091, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls h-vpls neighbor 10.255.114.4 vpls-id 200
10.255.114.4 (vpls-id 201) rmt
Up
Apr 11 23:39:25 2013
1
Remote PE: 10.255.114.4, Negotiated control-word: No
Incoming label: 262149, Outgoing label: 304225
Negotiated PW status TLV: Yes
local PW status code: 0x00000000, Neighbor PW status code: 0x00000000
Local interface: lsi.1049096, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls h-vpls neighbor 10.255.114.4 vpls-id 201

show vpls connections extensive (Static VPLS Neighbors)

user@host> show vpls connections extensive instance red
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid
NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch
WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down
NP -- interface hardware not present
CM -- control-word mismatch
-> -- only outbound connection is up
CN -- circuit not provisioned
<- -- only inbound connection is up
OR -- out of range
Up -- operational
OL -- no outgoing label
Dn -- down
LD -- local site signaled down
CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unn connection status IL -- no incoming label
MM -- MTU mismatch
MI -- Mesh-Group ID not availble
BK -- Backup connection
ST -- Standby connection
PF -- Profile parse failure
PB -- Profile busy
RS -- remote site standby
SN -- Static Neighbor
Legend for interface status
Up -- operational
Dn -- down
Instance: static

2248

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

VPLS-id: 1
Number of local interfaces: 1
Number of local interfaces up: 1
ge-0/0/5.0
lsi.1049344
Intf - vpls static neighbor 10.255.114.3 vpls-id
1
Neighbor
Type St
Time last up
# Up trans
10.255.114.3(vpls-id 1)(SN) rmt Up
Mar 4 08:48:41 2010
1
Remote PE: 10.255.114.3, Negotiated control-word: No
Incoming label: 29696, Outgoing label: 29697
Negotiated PW status TLV: No
Local interface: lsi.1049344, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls static neighbor 10.255.114.3 vpls-id 1
Connection History:
Mar 4 08:48:41 2010 status update timer
Mar 4 08:48:41 2010 PE route changed
Mar 4 08:48:41 2010 Out lbl Update
29697
Mar 4 08:48:41 2010 In lbl Update
29696
Mar 4 08:48:41 2010 loc intf up
lsi.1049344
user@PE1> show vpls connections extensive (Multihoming with FEC 129)
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid
NC
EM -- encapsulation mismatch
WE
VC-Dn -- Virtual circuit down
NP
CM -- control-word mismatch
->
CN -- circuit not provisioned
<OR -- out of range
Up
OL -- no outgoing label
Dn
LD -- local site signaled down
CF
RD -- remote site signaled down SC
LN -- local site not designated LM
RN -- remote site not designated RM
XX -- unknown connection status IL
MM -- MTU mismatch
MI
BK -- Backup connection
ST
PF -- Profile parse failure
PB
RS -- remote site standby
SN
LB -- Local site not best-site
RB
VM -- VLAN ID mismatch

------------------

interface encapsulation not CCC/TCC/VPLS

interface and instance encaps not same
interface hardware not present
only outbound connection is up
only inbound connection is up
operational
down
call admission control failure
local and remote site ID collision
local site ID not minimum designated
remote site ID not minimum designated
no incoming label
Mesh-Group ID not available
Standby connection
Profile busy
Static Neighbor
Remote site not best-site

Legend for interface status

Up -- operational
Dn -- down
Instance: green
L2vpn-id: 100:100
Local-id: 1.1.1.2
Number of local interfaces: 2
Number of local interfaces up: 2
ge-0/3/1.0
ge-0/3/3.0
lsi.101711873
Intf - vpls green local-id 1.1.1.2 remote-id
1.1.1.4 neighbor 1.1.1.4
Remote-id
Type St
Time last up
# Up trans
1.1.1.4
rmt
Up
Jan 31 13:49:52 2012
1
Remote PE: 1.1.1.4, Negotiated control-word: No
Incoming label: 262146, Outgoing label: 262146
Local interface: lsi.101711873, Status: Up, Encapsulation: ETHERNET

Copyright 2014, Juniper Networks, Inc.

2249

Interfaces Fundamentals for Routing Devices

Description: Intf - vpls green local-id 1.1.1.2 remote-id 1.1.1.4 neighbor

1.1.1.4
Connection History:
Jan 31 13:49:52 2012 status update timer
Jan 31 13:49:52 2012 PE route changed
Jan 31 13:49:52 2012 Out lbl Update
262146
Jan 31 13:49:52 2012 In lbl Update
262146
Jan 31 13:49:52 2012 loc intf up
lsi.101711873
Multi-home:
Local-site
Id
Pref
State
test
1
100
Up
Number of interfaces: 1
Number of interfaces up: 1
ge-0/3/1.0
Received multi-homing advertisements:
Remote-PE
Pref
flag
Description
1.1.1.4
100
0x0

2250

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show vpls flood event-queue

Syntax
Release Information
Description
Options
Required Privilege
Level
List of Sample Output
Output Fields

show vpls flood event-queue

Command introduced in Junos OS Release 8.0.

Display the pending events in the VPLS flood queue.
This command has no options.
view

show vpls flood event-queue on page 2251

Table 238 on page 2251 lists the output fields for the show vpls flood event-queue command.
Output fields are listed in the approximate order in which they appear.

Table 238: show vpls flood event-queue Output Fields

Field Name

Field Description

Current Pending Event

Provides information on the current event in the VPLS flood event

queue.

Name

Name of the event.

Owner Name

Name of the interface associated with the flood event.

Pending Op

Pending operation for the event.

Last Error

Name of the last error encountered.

Number of Retries

Number of attempts made to update the event queue.

Pending Event List

List of the events awaiting processing.

Event Name

Name of the event.

Pending Op

Pending operation for the event.

Event Identifier

Name of the interface associated with the flood event.

Sample Output
show vpls flood event-queue
user@host> show vpls flood event-queue
Current Pending Event
Name:
Flood Nexthop
Owner Name:ge-4/3/0.0
Pending Op: ADD

Copyright 2014, Juniper Networks, Inc.

2251

Interfaces Fundamentals for Routing Devices

Last Error:ENOMEM
Number of Retries:3
Pending Event List:
Event Name
Pending Op
Flood Nexthop
ADD
Flood Route
ADD

2252

Event Identifier
ge-4/3/0.0
ge-4/3/0.0

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show vpls flood instance

Syntax

Release Information
Description
Options

show vpls flood instance

<brief | detail | extensive>
<instance-name>
<logical-system logical-system-name>

Command introduced in Junos OS Release 8.0.

Display VPLS information related to the flood process.
noneDisplay VPLS information related to the flood process for all routing instances.
brief | detail | extensive(Optional) Display the specified level of output.
instance-name(Optional) Display VPLS information related to the flood process for

the specified routing instance.

logical-system logical-system-name(Optional) Display VPLS information related to the

flood process for the specified logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show vpls flood instance on page 2254

show vpls flood instance logical-system-name on page 2254
show vpls flood instance detail on page 2254
Table 239 on page 2253 lists the output fields for the show vpls flood instance command.
Output fields are listed in the approximate order in which they appear.

Table 239: show vpls flood instance Output Fields

Field Name

Field Description

Logical system

Name of the logical system.

Name

Name of the VPLS routing instance.

CEs

Number of CE routers connected to the VPLS instance.

VEs

Number of VE routers connected to the VPLS instance.

Flood routes

List of all flood routes associated with the VPLS instance.

Prefix

Prefix for the route.

Type

Type of route.

Owner

VPLS routing instance or interface associated with the route.

Nhtype

Next-hop type. For example, flood for a flood route.

Copyright 2014, Juniper Networks, Inc.

2253

Interfaces Fundamentals for Routing Devices

Table 239: show vpls flood instance Output Fields (continued)

Field Name

Field Description

Nhindex

Next-hop index number for the route.

Sample Output
show vpls flood instance
user@host> show vpls flood instance
Logical system: __juniper_ls1__
Name: green
CEs: 1
VEs: 1
Flood Routes:
Prefix
Type
Owner
default
ALL_CE_FLOOD green
0x47/16
CE_FLOOD
fe-1/2/1.0

NhType
flood
flood

NhIndex
383
388

show vpls flood instance logical-system-name

user@host:__juniper_ls1__> show vpls flood instance juniper_ls1

Logical system: __juniper_ls1__

Name: green
CEs: 1
VEs: 1
Flood Routes:
Prefix
Type
Owner
default
ALL_CE_FLOOD green
0x47/16
CE_FLOOD
fe-1/2/1.0

NhType
flood
flood

NhIndex
383
388

show vpls flood instance detail

user@host:__juniper_ls1__> show vpls flood instance detail

Logical system: __juniper_ls1__

Name: green
CEs: 1
VEs: 1
Flood Routes:
Prefix
Type
Owner
default
ALL_CE_FLOOD green
0x47/16
CE_FLOOD
fe-1/2/1.0

2254

NhType
flood
flood

NhIndex
383
388

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show vpls flood route

Syntax

Release Information
Description

Options

show vpls flood route

(all-ce-flood instance-name instance-name <logical-system-name logical-system-name>
|
ce-flood interface interface-name)

Command introduced in Junos OS Release 8.0.

Display VPLS route information related to the flood process for either the specified routing
instance or the specified interface.
all-ce-floodDisplay the flood next-hop route for all customer edge routers for traffic

coming from the core of the network.

ce-flood interface interface-nameDisplay the flood next-hop route for traffic coming

from the specified customer edge interface.

instance-name instance-nameDisplay the flood routes for the specified instance.
logical-system-name logical-system-name(Optional) Specify the logical system whose

flood routes you want to display. You can only specify the default logical system
name for VPLS. The default logical system name is __juniper_ls1__ (the name must
be entered in the command with the underscore characters).
Required Privilege
Level
List of Sample Output

Output Fields

view

show vpls flood route all-ce-flood on page 2256

show vpls flood route ce-flood on page 2256
Table 240 on page 2255 lists the output for the show vpls flood route command. Output
fields are listed in the approximate order in which they appear.

Table 240: show vpls flood route Output Fields

Field Name

Field Description

Flood route prefix

Prefix for the flood route.

Flood route type

Type of flood route (either CE_FLOOD or ALL_CE_FLOOD).

Flood route owner

VPLS routing instance or interface associated with the flood route.

Nexthop type

Next-hop type. For example, flood for a flood route.

Nexthop index

Next-hop index number for the route.

Interfaces flooding to

Interfaces to which VPLS routes are being flooded.

Name

Name of the interface.

Copyright 2014, Juniper Networks, Inc.

2255

Interfaces Fundamentals for Routing Devices

Table 240: show vpls flood route Output Fields (continued)

Field Name

Field Description

Type

Type of VPLS router (CE or VE).

Nh type

Next-hop type.

Index

Index number for the flood route.

Sample Output
show vpls flood route all-ce-flood
user@host:__juniper_ls1__> show vpls flood route all-ce-flood logical-system-name
__juniper_ls1__instance-name green

Flood route prefix: default

Flood route type: ALL_CE_FLOOD
Flood route owner: green
Nexthop type: flood
Nexthop index: 383
Interfaces Flooding to:
Name
Type
fe-1/2/1.0
CE

NhType

Index

show vpls flood route ce-flood

user@host:__juniper_ls1__> show vpls flood route ce-flood interface fe-1/2/1.0

Flood route prefix: 0x47/16

Flood route type: CE_FLOOD
Flood route owner: fe-1/2/1.0
Nexthop type: flood
Nexthop index: 388
Interfaces Flooding to:
Name
Type
lsi.49152
VE

2256

NhType
indr

Index
262142

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

show vpls mac-table

Syntax

Release Information
Description
Options

show vpls mac-table

<brief | detail | extensive | summary>
<bridge-domain bridge-domain-name>
<instance instance-name>
<interface interface-name>
<logical-system (all | logical-system-name)>
<mac-address>
<vlan-id vlan-id-number>

Command introduced in Junos OS Release 8.5.

Display learned VPLS MAC address information.
noneDisplay all learned VPLS MAC address information.
brief | detail | extensive | summary(Optional) Display the specified level of output.
bridge-domain bridge-domain-name(Optional) Display learned VPLS MAC addresses

for the specified bridge domain.

instance instance-name(Optional) Display learned VPLS MAC addresses for the specified

instance.
interface interface-name(Optional) Display learned VPLS MAC addresses for the

specified instance.
logical-system (all | logical-system-name)(Optional) Display learned VPLS MAC

addresses for all logical systems or for the specified logical system.
mac-address(Optional) Display the specified learned VPLS MAC address information..
vlan-id vlan-id-number(Optional) Display learned VPLS MAC addresses for the specified

VLAN.
Required Privilege
Level
List of Sample Output

Output Fields

view

show vpls mac-table on page 2258

show vpls mac-table (with VXLAN enabled) on page 2259
show vpls mac-table count on page 2259
show vpls mac-table detail on page 2260
show vpls mac-table extensive on page 2260
Table 241 on page 2257 describes the output fields for the show bridge mac-table command.
Output fields are listed in the approximate order in which they appear.

Table 241: show vpls mac-table Output fields

Field Name

Field Description

Routing instance

Name of the routing instance.

Copyright 2014, Juniper Networks, Inc.

2257

Interfaces Fundamentals for Routing Devices

Table 241: show vpls mac-table Output fields (continued)

Field Name

Field Description

Bridging domain

Name of the bridging domain.

MAC address

MAC address or addresses learned on a logical interface.

MAC flags

Status of MAC address learning properties for each interface:

SStatic MAC address configured.

DDynamic MAC address learned.

SEMAC accounting is enabled.

NMNonconfigured MAC.

Logical interface

Name of the logical interface.

MAC count

Number of MAC addresses learned on a specific routing instance or interface.

Learning interface

Logical interface or logical Label Switched Interface (LSI) the address is learned on.

Base learning interface

Base learning interface of the MAC address. This field is introduced in Junos OS Release 14.2.

Learn VLAN ID/VLAN

VLAN ID of the routing instance or bridge domain in which the MAC address was learned.

VXLAN ID/VXLAN

VXLAN Network Identifier (VNI)

Layer 2 flags

Debugging flags signifying that the MAC address is present in various lists.

Epoch

Spanning Tree Protocol epoch number identifying when the MAC address was learned. Used for
debugging.

Sequence number

Sequence number assigned to this MAC address. Used for debugging.

Learning mask

Mask of Packet Forwarding Engines where this MAC address was learned. Used for debugging.

IPC generation

Creation time of the logical interface when this MAC address was learned. Used for debugging.

Sample Output
show vpls mac-table
user@host> show vpls mac-table
MAC flags (S -static MAC, D -dynamic MAC,
SE -Statistics enabled, NM -Non configured MAC)
Routing instance : vpls_ldp1
VLAN : 223
MAC
MAC
address
flags
00:90:69:9c:1c:5d
D

Logical
interface
ge-0/2/5.400

MAC flags (S -static MAC, D -dynamic MAC,

2258

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

SE -Statistics enabled, NM -Non configured MAC)

Routing instance : vpls_red
VLAN : 401
MAC
MAC
address
flags
00:00:aa:12:12:12
D
00:05:85:74:9f:f0
D

Logical
interface
lsi.1051138
lsi.1051138

show vpls mac-table (with VXLAN enabled)

user@host> show vpls mac-table
MAC flags (S -static MAC, D -dynamic MAC, L -locally learned
SE -Statistics enabled, NM -Non configured MAC, R -Remote PE MAC)
Routing instance : vpls_4site:1000
Bridging domain : __vpls_4site:1000__, VLAN : 4094,4093
VXLAN: Id : 300, Multicast group: 226.1.1.3
MAC
MAC
Logical
address
flags
interface
00:01:01:00:01:f4
D,SE
ge-4/2/0.1000
00:02:01:33:01:f4
D,SE
lsi.1052004
00:03:00:32:01:f4
D,SE
lsi.1048840
00:04:00:14:01:f4
D,SE
lsi.1052005
00:02:01:33:02:f7
D,SE
vtep.1052010
00:04:00:14:02:f7
D,SE
vtep.1052011

show vpls mac-table count

user@host> show vpls mac-table count
0 MAC address learned in routing instance __juniper_private1__
MAC address count per interface within routing instance:
Logical interface
MAC count
lc-0/0/0.32769
0
lc-0/1/0.32769
0
lc-0/2/0.32769
0
lc-2/0/0.32769
0
lc-0/3/0.32769
0
lc-2/1/0.32769
0
lc-9/0/0.32769
0
lc-11/0/0.32769
0
lc-2/2/0.32769
0
lc-9/1/0.32769
0
lc-11/1/0.32769
0
lc-2/3/0.32769
0
lc-9/2/0.32769
0
lc-11/2/0.32769
0
lc-11/3/0.32769
0
lc-9/3/0.32769
0
MAC address count per learn VLAN within routing instance:
Learn VLAN ID
MAC count
0
0
1 MAC address learned in routing instance vpls_ldp1
MAC address count per interface within routing instance:
Logical interface
MAC count
lsi.1051137
0
ge-0/2/5.400
1

Copyright 2014, Juniper Networks, Inc.

2259

Interfaces Fundamentals for Routing Devices

MAC address count per learn VLAN within routing instance:

Learn VLAN ID
MAC count
0
1
1 MAC address learned in routing instance vpls_red
MAC address count per interface within routing instance:
Logical interface
MAC count
ge-0/2/5.300
1
MAC address count per learn VLAN within routing instance:
Learn VLAN ID
MAC count
0
1

show vpls mac-table detail

user@host> show vpls mac-table detail
MAC address: 00:90:69:9c:1c:5d
Routing instance: vpls_ldp1
Learning interface: ge-0/2/5.400
Layer 2 flags: in_ifd, in_ifl, in_vlan, kernel
Epoch: 0
Sequence number: 1
Learning mask: 0x1
IPC generation: 0
MAC address: 00:90:69:9c:1c:5d
Routing instance: vpls_red
Learning interface: ge-0/2/5.300
Layer 2 flags: in_ifd, in_ifl, in_vlan, kernel
Epoch: 0
Sequence number: 1
Learning mask: 0x1
IPC generation: 0

show vpls mac-table extensive

user@host> show vpls mac-table extensive
MAC address: 00:10:00:01:00:00
Routing instance: vpls_1
Bridging domain: __vpls_1__, VLAN : NA
Learning interface: lsi.1049165
Base learning interface: lsi.1049165
Layer 2 flags: in_hash,in_ifd,in_ifl,in_vlan,in_rtt,kernel,in_ifbd
Epoch: 0
Sequence number: 1
Learning mask: 0x00000001
MAC address: 00:10:00:01:00:01
Routing instance: vpls_1
Bridging domain: __vpls_1__, VLAN : NA
Learning interface: lsi.1049165
Base learning interface: lsi.1049165
Layer 2 flags: in_hash,in_ifd,in_ifl,in_vlan,in_rtt,kernel,in_ifbd
Epoch: 0
Sequence number: 1
Learning mask: 0x00000001
MAC address: 00:10:00:01:00:02
Routing instance: vpls_1
Bridging domain: __vpls_1__, VLAN : NA
Learning interface: lsi.1049165
Base learning interface: lsi.1049165
Layer 2 flags: in_hash,in_ifd,in_ifl,in_vlan,in_rtt,kernel,in_ifbd
Epoch: 0
Sequence number: 1

2260

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Learning mask: 0x00000001

MAC address: 00:10:00:01:00:03
Routing instance: vpls_1
Bridging domain: __vpls_1__, VLAN : NA
Learning interface: lsi.1049165
Base learning interface: lsi.1049165
Layer 2 flags: in_hash,in_ifd,in_ifl,in_vlan,in_rtt,kernel,in_ifbd
Epoch: 0
Sequence number: 1
Learning mask: 0x00000001

Copyright 2014, Juniper Networks, Inc.

2261

Interfaces Fundamentals for Routing Devices

show vpls statistics

Syntax

Release Information
Description

Options

show vpls statistics

<instance instance-name>
<logical-system (all | logical-system-name)>

Command introduced before Junos OS Release 7.4.

(T Series and M Series routers, except for the M160 router) Display virtual private LAN
service (VPLS) statistics.
noneDisplay VPLS statistics for all routing instances.
instance instance-name(Optional) Display VPLS statistics for a specific VPLS routing

instance only.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical

systems or on a particular logical system.

Required Privilege
Level
List of Sample Output

Output Fields

view

show vpls statistics on page 2263

show vpls statistics instance on page 2263
Table 242 on page 2262 lists the output fields for the show vpls statistics command. Output
fields are listed in the approximate order in which they appear.

Table 242: show vpls statistics Output Fields

2262

Field Name

Field Description

Instance

Name of the VPLS instance.

Local interface

Name of the local VPLS virtual loopback tunnel interface,

vt-fpc/pic/port.nnnnn, where nnnnn is a dynamically generated virtual
port used to transport and receive packets from other provider edge
(PE) routers in the VPLS domain.

Index

Number associated with the next hop.

Remote provider edge router

Address of the remote provider edge router.

Multicast packets

Number of multicast packets received.

Multicast bytes

Number of multicast bytes received.

Flood packets

Number of VPLS flood packets received.

Flood bytes

Number of VPLS flood bytes received.

Copyright 2014, Juniper Networks, Inc.

Chapter 30: VPN Operational Commands

Table 242: show vpls statistics Output Fields (continued)

Field Name

Field Description

Current MAC count

Number of MAC addresses learned by the interface and the

configured maximum limit on the number of MAC addresses that
can be learned.

Sample Output
show vpls statistics
user@host> show vpls statistics
VPLS statistics:
Instance: green
Local interface: fe-2/2/1.0, Index: 69
Multicast packets:
1
Multicast bytes :
60
Flooded packets :
18
Flooded bytes
:
2556
Current MAC count:
1
Local interface: lt-0/3/0.2, Index: 72
Multicast packets:
3
Multicast bytes :
153
Flooded packets :
1
Flooded bytes
:
51
Current MAC count:
1
Local interface: lsi.32769, Index: 75
Current MAC count:

Local interface: lsi.32771, Index: 77

Remote PE: 10.255.14.222
Current MAC count:

Instance: red
Local interface: vt-0/3/0.32768, Index: 74
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0
Flooded bytes
:
0
Current MAC count:
0
Local interface: vt-0/3/0.32770, Index: 76
Multicast packets:
0
Multicast bytes :
0
Flooded packets :
0
Flooded bytes
:
0
Current MAC count:
0

show vpls statistics instance

user@host> show vpls statistics instance red

Copyright 2014, Juniper Networks, Inc.

2263

Interfaces Fundamentals for Routing Devices

Layer-2 VPN Statistics:

Instance: red
Local interface: vt-3/2/0.32768, Index: 73
Remote provider edge router: 10.255.17.35
Multicast packets:
0
Multicast bytes :
0
Flood packets
:
0
Flood bytes
:
0
Current MAC count:
1 (Limit 20)

2264

Copyright 2014, Juniper Networks, Inc.

PART 6

Index

Index on page 2267

Copyright 2014, Juniper Networks, Inc.

2265

Interfaces Fundamentals for Routing Devices

2266

Copyright 2014, Juniper Networks, Inc.

Index
Symbols
#, comments in configuration statements.................xlvii
( ), in syntax descriptions..................................................xlvii
10-Gigabit Ethernet interfaces
MTU sizes........................................................................100
10-Gigabit Ethernet LAN/WAN PIC
no-pre-classifier statement......................................751
oversubscribed Ethernet mode
control queue disable.........................................751
100-Gigabit Ethernet
configuration
sa-multicast.........................................................859
vlan-rule.................................................................974
vlan-steering.........................................................975
forwarding-options
sa-multicast.........................................................859
vlan-steering.........................................................975
vlan-steering
vlan-rule.................................................................974
128-bit IPv6 address............................................................196
32-bit IPv4 address..............................................................194
802.1Q VLANs
dynamic..........................................................................433
mixed VLAN tagging..........................................577, 730
VLAN IDs................................................................967, 971
VLAN tagging................................................................976
802.1Q/Ethernet 802.3 encapsulation
encapsulation overhead.............................................96
802.1Q/Ethernet SNAP encapsulation
encapsulation overhead.............................................96
802.1x Port-Based Network Access Control...............517
802.3ad statement.............................................................396
< >, in syntax descriptions................................................xlvii
[ ], in configuration statements......................................xlvii
{ }, in configuration statements......................................xlvii
| (pipe), in syntax descriptions........................................xlvii

A
accept statement.................................................................397
accept-source-mac statement......................................399

Copyright 2014, Juniper Networks, Inc.

access profile
configuring.......................................................................127
default CHAP secret....................................................128
default PAP password................................................179
access-concentrator statement.....................................401
access-profile statement.................................................402
usage guidelines..................................................126, 129
accounting profiles
logical interfaces...........................................................182
example configuration......................................183
physical interfaces.......................................................155
example configuration.......................................155
accounting statement.......................................................403
usage guidelines...........................................................242
accounting-profile statement.........................................403
usage guidelines..................................................155, 182
acfc statement.....................................................................404
usage guidelines...........................................................133
acknowledge-retries statement....................................405
acknowledge-timer statement......................................406
usage guidelines.........................................................406
action statement
OAM.................................................................................406
policer..............................................................................407
action-profile statement
applying to remote MEP...........................................407
CFM..................................................................................408
LFM..................................................................................409
action-red-differential-delay statement.....................410
usage guidelines...........................................................410
activation-delay statement..............................................410
activation-priority statement............................................411
address and control field compression........................133
address entries.........................................................................51
address statement...............................................................412
usage guidelines.................................................192, 203
Addresses, flags field, content.......................................996
ADSL
ATM-over-ADSL interfaces
status information, displaying.....................1063
advertise-interval statement............................................414
advertisements, displaying .............................................1951
ae
physical part of interface name...............................26
age statement........................................................................414
agent-specifier statement
PPPoE...............................................................................415
aggregate statement
hierarchical policer.......................................................417

2267

Interfaces Fundamentals for Routing Devices

aggregate-ports statement..............................................418
aggregated Ethernet
targeted distribution of subscribers............682, 917
aggregated Ethernet interfaces
CCC.........................................................................268, 270
Layer 2 VPNs.................................................................270
aggregated-ether-options statement..........................419
aggregated-sonet-options statement........................420
alarm statement....................................................................421
alias statement.....................................................................422
example configuration..................................................111
all (tracing flag)
interfaces.........................................................................321
allow-any-vci statement...................................................422
allow-fragmentation statement....................................423
allow-remote-loopback statement..............................423
AMT
displaying..........................................................1553, 1558
protocol, displaying...................................................1556
state
clearing...................................................................1517
statistics
clearing..................................................................1516
tunnel
clearing...................................................................1517
ANCP
clearing statistics........................................................1414
CoS state
displaying ANCP................................................1420
local access loop
displaying.............................................................1438
neighbor
clearing...................................................................1412
neighbor summary
displaying.............................................................1445
neighbors
displaying.............................................................1425
request OAM per interface......................................1418
request OAM per neighbor......................................1419
statistics
displaying.............................................................1433
subscriber
clearing..................................................................1416
subscriber summary
displaying.............................................................1447
subscribers
displaying.............................................................1438
summary
displaying.............................................................1443

2268

annex statement..................................................................424
apply-action-profile statement......................................424
aps statement.......................................................................425
annex-b...........................................................................424
arp option
policers.............................................................................210
arp statement........................................................................426
as
physical part of interface name...............................26
AS paths
distribution of, displaying........................................1931
domain information, displaying...........................1935
matching regular expressions,
displaying.................................................................1958
summary of, displaying...........................................1938
ASN
BGP community routes, displaying....................1966
Asynchronous Transfer Mode See ATM
asynchronous-notification statement................427, 736
at
physical part of interface name...............................26
ATM cell-relay encapsulation
encapsulation overhead.............................................96
ATM encapsulation
ATM PVC encapsulation......................................96, 117
keepalives........................................................................124
Layer 2 switching cross-connects.........................257
ATM interfaces
encapsulation..................................................................117
MTU sizes..........................................................97, 99, 101
status information, displaying..............................1028
ATM PVC encapsulation...............................................96, 117
atm-encapsulation statement........................................427
atm-options statement.....................................................428
ATM-over-ADSL interfaces
status information, displaying..............................1063
ATM-over-SHDSL interfaces
status information, displaying................................1071
atm-scheduler-map statement ....................................429
ATM-to-Ethernet interworking.............................262, 980
VCI range........................................................................965
virtual path identifier.................................................983
VLAN tagging......................................................621, 966
ATM2 IQ interfaces
MTU sizes.................................................................99, 101
authentication statement
dynamic VLAN authentication..............................430
authentication-key statement.........................................431
authentication-profile-name statement.....................431

Copyright 2014, Juniper Networks, Inc.

Index

authenticator statement...................................................432
auto-configure statement................................................433
auto-discovery statement................................................434
auto-negotiation statement
Gigabit Ethernet.................................................435, 738
J Series uPIM.......................................................436, 739
auto-reconnect statement...............................................437
auto-synchronize statement
usage guidelines...........................................................310
autonomous system number See ASN
autonomous system paths See AS paths

B
backup PE groups
multicast, displaying.................................................1616
backup-destination statement.......................................437
backup-interface statement...........................................438
backup-options statement..............................................438
bandwidth statement........................................................439
usage guidelines............................................................172
bandwidth-limit statement
hierarchical policer.....................................................440
policer for Gigabit Ethernet interface...................441
bchannel-allocation statement......................................441
bcm0
internal Ethernet interface............................................4
physical part of interface name...............................26
bearer-bandwidth-limit statement..............................442
BERT
configuring interface diagnostics..........................329
bert-algorithm statement................................................443
usage guidelines..........................................................329
bert-error-rate statement.................................................445
usage guidelines..........................................................329
bert-period statement........................................................447
usage guidelines..........................................................329
best routes, displaying.....................................................1960
BFD
sessions
clearing...................................................................1451
displaying.............................................................1452
BGP
communities
policy, routing........................................................471
community ASN, displaying routes....................1966
community name, displaying routes.................1968
damping parameters
clearing.................................................................1462
displaying..............................................................1501

Copyright 2014, Juniper Networks, Inc.

damping routes, displaying....................................1970

groups
general information, displaying...................1469
traffic statistics, displaying............................1476
neighbors
clearing connections.......................................1463
displaying.............................................................1478
summary information, displaying........................1495
table
clearing.................................................................1465
BGP Monitoring Protocol
displaying
statistics...............................................................1467
Bidirectional Forwarding Detection See BFD
bit error rate test See BERT
BOOTP
accepting packets.......................................................233
bootstrap routers, displaying.........................................1670
borrower interface
unnumbered Ethernet or demux..........................204
br
physical part of interface name...............................26
braces, in configuration statements..............................xlvii
brackets
angle, in syntax descriptions...................................xlvii
square, in configuration statements....................xlvii
bridge domain
Layer 2, displaying......................................................2179
bridge-domain statement................................................448
broadcast statement.........................................................449
usage guidelines...........................................................192
buildout statement
E3 or T3 over ATM interfaces..................................450
T1 interfaces...................................................................451
bundle statement................................................................452
burst-size-limit statement
hierarchical policer......................................................453
policer for Gigabit Ethernet interface..................454
byte encoding........................................................................455
byte-encoding statement.................................................455
bytes statement...................................................................456

C
C-bit parity mode........................................................461, 740
calculation-weight statement.........................................457
callback statement.............................................................458
callback-wait-period statement...................................459
caller statement...................................................................460
calling-number statement................................................461

2269

Interfaces Fundamentals for Routing Devices

cau4
physical part of interface name...............................26
cbit-parity statement................................................461, 740
cbr statement........................................................................462
CCC
aggregated Ethernet........................................268, 270
encapsulation
VLAN-bundled dual-tag logical
interfaces...........................................................977
VLAN-bundled single-tag logical
interfaces..........................................................969
Layer 2 VPNs.................................................................270
ce1
physical part of interface name...............................26
cell-bundle-size statement.............................................463
channel part of interface name.........................................32
channelized DS3-to-DS0 interfaces
status information, displaying..............................1079
channelized DS3-to-DS1 interfaces
status information, displaying.............................1090
channelized E1 interfaces
status information, displaying..............................1097
channelized E1 IQ interfaces
status information, displaying..............................1093
channelized OC12 interfaces
status information, displaying.................................1112
channelized OC12 IQ interfaces
status information, displaying...............................1108
channelized OC12 IQE interfaces
status information, displaying...............................1108
channelized OC3 IQ interfaces
status information, displaying................................1116
channelized OC3 IQE interfaces
status information, displaying................................1116
Channelized SONET/SDH OC3/STM1 (Multi-Rate)
interfaces
MTU sizes.........................................................................101
channelized STM1 interfaces
status information, displaying...............................1138
channelized STM1 IQ interfaces
status information, displaying................................1135
channelized T1 IQ interfaces
status information, displaying................................1153
channelized T3 IQ interfaces
status information, displaying...............................1165
CHAP.................................................................................126, 129
configuring default CHAP secret............................128
example configuration........................................128, 131

2270

chap statement....................................................................464
usage guidelines..................................................126, 129
chap-secret statement......................................................465
ci
physical part of interface name...............................26
circuit cross-connect (CCC)
encapsulation
VLAN-bundled dual-tag logical
interfaces...........................................................977
VLAN-bundled single-tag logical
interfaces..........................................................969
circuit-type statement
dynamic VLAN authentication..............................465
Cisco HDLC encapsulation..................................................117
configuring on physical interfaces...........................117
encapsulation overhead.............................................96
keepalives........................................................................124
Layer 2 switching cross-connect............................257
cisco-interoperability statement...................................466
classifier statement............................................................466
clear (ospf | ospf3) database command..................1852
clear (ospf | ospf3) io-statistics command.............1855
clear (ospf | ospf3) neighbor command...................1856
clear (ospf | ospf3) overload command...................1858
clear (ospf | ospf3) statistics command..................1859
clear amt tunnel command...................................1516, 1517
clear ancp neighbor command......................................1412
clear ancp statistics command......................................1414
clear ancp subscriber command...................................1416
clear bfd adaptation command...................................1450
clear bfd session command............................................1451
clear bgp damping command.......................................1462
clear bgp neighbor command.......................................1463
clear bgp table command...............................................1465
clear bridge mac-table command...............................2176
clear error bpdu command..............................................2177
clear error mac-rewrite command...............................2178
clear esis adjacency command....................................1504
clear esis statistics command.......................................1505
clear firewall command...................................................2154
clear igmp membership command..............................1518
clear igmp snooping membership command..........1521
clear igmp snooping statistics command.................1522
clear igmp statistics command.....................................1523
clear ipv6 neighbors command.....................................1754
clear ipv6 router-advertisement command.............1755
clear isis adjacency command.......................................1762
clear isis database command........................................1764
clear isis overload command.........................................1766

Copyright 2014, Juniper Networks, Inc.

Index

clear isis statistics command.........................................1768

clear lldp neighbor command.......................................1820
clear lldp statistics command........................................1821
clear mld membership command................................1525
clear mld statistics command.......................................1526
clear msdp cache command..........................................1527
clear msdp statistics command...................................1528
clear multicast bandwidth-admission
command..........................................................................1529
clear multicast forwarding-cache command...........1531
clear multicast scope command..................................1532
clear multicast sessions command.............................1533
clear multicast snooping statistics
command..........................................................................1534
clear multicast statistics command............................1535
clear pgm negative-acknowledgments
command..........................................................................1536
clear pgm source-path-messages command.........1537
clear pgm statistics command.....................................1538
clear pim join command..................................................1539
clear pim join-distribution command..........................1541
clear pim register command..........................................1543
clear pim statistics command.......................................1549
clear rip general-statistics command.........................2134
clear rip statistics command..........................................2135
clear ripng general-statistics command...................2144
clear ripng statistics command.....................................2145
clear vpls mac-address command............................2206
clear vpls mac-table command...................................2207
clear-dont-fragment-bit statement.............................467
client statement...................................................................467
clock rates..............................................................................309
clock sources.................................................................116, 469
clock-rate statement.........................................................468
usage guidelines..........................................................309
clocking modes....................................................................308
clocking statement.............................................................469
usage guidelines............................................................116
clocking-mode statement................................................470
usage guidelines..........................................................307
coc1
physical part of interface name...............................26
coc12
physical part of interface name...............................26
coc3
physical part of interface name...............................26
coc48
physical part of interface name...............................26
comments, in configuration statements.....................xlvii

Copyright 2014, Juniper Networks, Inc.

communities
policy, routing.................................................................471
community ASN, displaying routes.............................1966
community name, displaying routes..........................1968
community statement.........................................................471
compatibility-mode statement......................................474
compression............................................................................176
compression statement
usage guidelines...................................................133, 135
compression-device statement......................................476
connections
configuration statements..............................389, 393
connections statement......................................................477
usage guidelines...........................................................261
connectivity-fault management.........................407, 408
connectivity-fault-management statement.............478
container interfaces.................................................................8
container-devices statement.........................................480
device-count................................................................480
container-list statement..................................................480
container-options statement...........................................481
container-type statement.................................................481
continuity-check statement............................................482
control leads
serial interfaces.............................................................310
control-channel statement.............................................483
control-leads statement
usage guidelines...........................................................310
control-polarity statement..............................................484
usage guidelines...........................................................313
control-signal statement..................................................484
usage guidelines...........................................................310
conventions
text and syntax..............................................................xlvi
copy-tos-to-outer-ip-header statement....................485
core-dump statement.............................................485, 740
usage guidelines...........................................................153
CoS
hierarchical scheduling.............................................595
cp
physical part of interface name...............................26
crc-major-alarm-threshold statement.......................486
crc-minor-alarm-threshold statement........................487
cstm1
physical part of interface name...............................26
cstm16
physical part of interface name...............................26
cstm4
physical part of interface name...............................26

2271

Interfaces Fundamentals for Routing Devices

ct1
physical part of interface name...............................26
ct3
physical part of interface name...............................26
cts statement........................................................................488
usage guidelines...........................................................310
cts-polarity statement......................................................488
usage guidelines...........................................................313
curly braces, in configuration statements...................xlvii
current statement...............................................................489
customer support................................................................xlviii
contacting JTAC...........................................................xlviii
cycle-time statement........................................................489

D
damping
interface transitions....................................................149
Damping field, contents....................................................994
damping parameters, BGP
clearing..........................................................................1462
displaying.......................................................................1501
damping routes, BGP
displaying......................................................................1970
damping statement............................................................490
data circuit-terminating equipment See DCE
data terminal equipment See DTE
data-channel statement...................................................492
data-input statement........................................................493
data-tlv-size statement....................................................494
dcd statement.......................................................................495
usage guidelines...........................................................310
dcd-polarity statement.....................................................495
usage guidelines...........................................................313
DCE..................................................................................138, 496
dce statement.......................................................................496
usage guidelines...........................................................138
dce-options statement.....................................................496
deactivation-delay statement.........................................497
default router addresses.....................................................197
default-actions statement...............................................497
default-chap-secret statement.....................................498
default-pap-password statement................................498
delimiter statement
dynamic VLAN authentication..............................499
demux
physical part of interface name...............................26
demux interfaces
unnumbered.................................................................204

2272

demux-destination statement.......................................499
demux interfaces........................................................500
demux-options statement..............................................500
demux-source statement.................................................502
demux interfaces.........................................................501
demux0 statement.............................................................503
dynamic IP demux interface...................................504
description statement.......................................................505
usage guidelines......................................................92, 171
descriptors, interface..............................................................51
Destination class field, contents....................................994
destination statement
tunnels.............................................................................507
usage guidelines.................................................192, 202
destination-class usage
example configuration..............................................246
destination-class-usage statement.............................508
usage guidelines...........................................................242
destination-profile
usage guidelines..........................................................202
destination-profile statement........................................508
usage guidelines...........................................................192
Device flags field, content................................................996
dfc
physical part of interface name...............................26
DHCP
accepting........................................................................233
dial-options statement.....................................................509
dial-string statement..........................................................510
dialer statement....................................................................510
dialer-options statement....................................................511
dialin statement.....................................................................512
direction statement..............................................................512
disable statement.................................................................513
link protection................................................................514
logical interfaces
usage guidelines..................................................184
physical interfaces
usage guidelines..................................................156
disable-mlppp-inner-ppp-pfc statement...................514
disabling
keepalives........................................................................124
logical interfaces..........................................................184
physical interfaces.......................................................156
example configuration.......................................157
discard interface
described.........................................................................277
status information, displaying................................1167
dlci statement........................................................................515

Copyright 2014, Juniper Networks, Inc.

Index

do-not-fragment statement............................................516
documentation
comments on................................................................xlvii
domain-name statement
dynamic VLAN authentication................................516
donor interface
unnumbered Ethernet or demux..........................204
dot1x
configuration statements........................................390
dot1x statement.....................................................................517
authenticator..................................................................517
authentication-profile-name..........................517
interface...................................................................517
See also maximum-requests
See also quiet-period
See also reauthentication
See also retries
See also server-timeout
See also supplicant
See also supplicant-timeout
See also transmit-period
down-count statement......................................................518
Draft-rosen MVPNs
data MDT cache, displaying....................................1701
MDT tunnels
displaying.............................................................1703
drop statement
PPPoE service name tables.....................................519
drop-timeout statement....................................................519
ds
physical part of interface name...............................26
DS interfaces
status information, displaying................................1321
ds0-options statement.....................................................520
DS3 IQ interfaces
MTU sizes..................................................................98, 99
DS3/E3interfaces
MTU sizes.........................................................................101
dsc
physical part of interface name...............................26
dsc interface............................................................................277
described.........................................................................277
See also discard interface
dsl-options statement.......................................................520
dsr statement.........................................................................521
usage guidelines...........................................................310
dsr-polarity statement........................................................521
usage guidelines...........................................................313
dte-options statement.......................................................522

Copyright 2014, Juniper Networks, Inc.

DTR circuit
serial interfaces.............................................................313
dtr statement.........................................................................523
usage guidelines...........................................................310
dtr-circuit statement..........................................................524
usage guidelines...........................................................313
dtr-polarity statement.......................................................524
usage guidelines...........................................................313
dual-tag framing
VLAN ID list.....................................................................977
dump-on-flow-control statement................................525
DVMRP
groups, displaying.....................................................1658
interfaces, displaying.................................................1561
neighbors, displaying................................................1563
prefixes, displaying....................................................1565
prunes, displaying active.........................................1567
Dynamic Host Configuration Protocol See DHCP
dynamic overload bit, resetting for IS-IS...................1766
dynamic PPPoE statements
pppoe-underlying-options.......................................814
dynamic profiles statements
dynamic-profiles...........................................................531
interfaces.........................................................................641
unnumbered-address...............................................955
dynamic subscribers
interfaces statement..................................................641
pppoe-underlying-options statement.................814
dynamic tunnel database, displaying.......................2209
dynamic VLAN authentication statements
authentication..............................................................430
circuit-type....................................................................465
delimiter.........................................................................499
domain-name...............................................................516
interface-name............................................................633
mac-address................................................................695
option-82........................................................................766
radius-realm..................................................................833
user-prefix.....................................................................960
username-include.......................................................961
dynamic VLANs....................................................................433
authenticating..............................................................430
dynamic-call-admission-control statement............526
dynamic-profile statement
MLPPP.............................................................................527
PPP....................................................................................527
PPPoE service name tables....................................528
stacked VLAN ranges.................................................529

2273

Interfaces Fundamentals for Routing Devices

usage guidelines............................................................178
VLAN ranges.................................................................530
dynamic-profiles
interfaces statement..................................................641
dynamic IP demux..............................................641
dynamic-profiles statement.............................................531

E
E-LMI.........................................................................................676
e1
physical part of interface name...............................26
E1 interfaces
MTU sizes...........................................................97, 98, 99
status information, displaying................................1321
e1-options statement.........................................................538
e3
physical part of interface name...............................26
E3 interfaces
encapsulation..................................................................117
MTU sizes...........................................................97, 98, 99
status information, displaying..............................1346
E3 IQ interfaces
MTU sizes..................................................................98, 99
e3-options statement........................................................539
east-interface statement.................................................540
egress-policer-overhead statement..............................541
em
physical part of interface name...............................26
em0...............................................................................................14
management Ethernet interface................................4
management interface.................................................10
physical part of interface name...............................26
em1
internal Ethernet interface............................................4
physical part of interface name...............................26
em2
physical part of interface name...............................26
Enabled field, contents......................................................995
encapsulation...........................................................................117
CCC....................................................................................257
Ethernet 802.3................................................................96
example configuration................................................122
on logical interfaces.....................................................173
on physical interfaces...................................................117
overheads.........................................................................96
See also ATM encapsulation
encapsulation statement
container interface......................................................542
Layer 2 switching cross-connect............................257

2274

logical interfaces..........................................................543
usage guidelines...................................................173
physical interface.........................................................547
physical interfaces
usage guidelines....................................................117
encoding
byte...................................................................................455
line......................................................................................315
encoding statement.............................................................551
usage guidelines...........................................................315
epd-threshold statement
logical interface............................................................552
physical interface........................................................553
es
physical part of interface name...............................26
ES-IS
adjacencies
clearing.................................................................1504
displaying............................................................1506
interfaces, displaying...............................................1508
statistics
clearing.................................................................1505
displaying..............................................................1510
es-options statement.........................................................553
et
physical part of interface name...............................26
Ethernet CCC and TCC encapsulation
physical interfaces.........................................................117
Ethernet CCC encapsulation
encapsulation overhead.............................................96
Ethernet interfaces
dynamic VLANs............................................................433
internal Ethernet interface............................................5
mixed VLAN tagging..........................................577, 730
status information, displaying
Fast Ethernet........................................................1172
Gigabit Ethernet.....................................1003, 1189
internal..................................................................1239
management......................................................1239
PTX Series...........................................................1266
unnumbered.................................................................204
preferred source address.................................816
VLAN IDs.........................................................................967
VLAN tagging................................................................976
Ethernet over ATM encapsulation
encapsulation overhead.............................................96
physical interfaces.........................................................117
Ethernet Ring Protection
configuration statements........................................394

Copyright 2014, Juniper Networks, Inc.

Index

Ethernet SNAP encapsulation

encapsulation overhead.............................................96
ethernet statement.............................................................554
Ethernet TCC
encapsulation
encapsulation overhead....................................96
Ethernet VLAN circuit
VLAN ID list...................................................................969
ethernet-policer-profile statement...............................557
ethernet-ring statement...................................................558
ethernet-switch-profile statement...............................559
eui-64 statement................................................................560
usage guidelines...........................................................192
evcs statement......................................................................561
event (tracing flag)...............................................................321
event statement...................................................................562
interface-status-tlv statement..............................637
port-status-tlv statement.........................................811
rdi statement................................................................836
event-thresholds
frame-error statement..............................................583
frame-period statement..........................................584
frame-period-summary statement.....................585
symbol-period statement........................................907
event-thresholds statement............................................562
export route information, displaying...........................1994
extended VLAN
CCC
encapsulation.........................................................117
encapsulation overhead....................................96
TCC
encapsulation.........................................................117
encapsulation overhead....................................96
external clock sources...............................................116, 469

F
f-max-period statement...................................................564
facility-override statement..............................................564
fail-filter statement.............................................................854
usage guidelines...........................................................224
failover-delay statement...................................................565
family bridge
VLAN ID list....................................................................970
VLAN IDs........................................................................966
family descriptors....................................................................51
Family flags field, content.................................................997
family statement..................................................................568
dynamic profiles..........................................................566
usage guidelines...........................................................190

Copyright 2014, Juniper Networks, Inc.

Fast Ethernet interfaces

dynamic VLANs............................................................433
interface speed..............................................................107
link modes......................................................................109
MTU sizes...........................................................97, 98, 99
status information, displaying................................1172
VLAN IDs.........................................................................967
VLAN tagging................................................................976
fast-aps-switch statement..............................................563
fastether-options statement...........................................572
fcs statement.........................................................................573
fe
physical part of interface name...............................26
feac-loop-respond statement................................574, 741
filter statement............................................................575, 576
usage guidelines...........................................................219
Filters fields, contents........................................................995
firewall
filter version
displaying.............................................................2163
hierarchical-policer....................................................594
statistics
displaying.............................................................2156
firewall filters
applying............................................................................219
example configuration...............................................222
log information, displaying.....................................2164
logical interfaces...........................................................219
policed packets, displaying......................................2171
statistics
clearing..................................................................2154
displaying..............................................................2167
flags
address flags................................................................996
device flags...................................................................996
family flags.....................................................................997
interface flags...............................................................997
link flags.........................................................................998
logical interface flags................................................999
flexible-vlan-tagging statement.....................................577
flooding
Layer 2 bridging, displaying.....................................2181
flow-control statement............................................578, 742
flow-control-options statement....................................579
font conventions....................................................................xlvi
force statement....................................................................579
forward-and-send-to-re statement............................580
forward-only statement.....................................................581

2275

Interfaces Fundamentals for Routing Devices

forwarding table
interfaces, displaying...............................................2032
multicast information, displaying........................1633
multicast snooping information,
displaying..................................................................1651
route entries, displaying..........................................2018
forwarding-class statement
for ATM2 IQ scheduler maps..................................580
fragment-threshold statement......................................582
Frame Relay encapsulation................................................117
DCE..........................................................................138, 496
encapsulation overhead.............................................96
keepalives........................................................................124
Layer 2 switching cross-connect...........................258
physical interfaces.........................................................117
Frame Relay ether type encapsulation
physical interfaces.........................................................117
frame-error statement.......................................................583
frame-period statement...................................................584
frame-period-summary statement..............................585
framing statement
10-Gigabit Ethernet interfaces...............................587
E1, E3, and T1 interfaces............................................586
SONET and SDH interfaces....................................588
from statement.....................................................................801
fxp
physical part of interface name...............................26
fxp0...............................................................................................14
management Ethernet interface................................4
management interface.................................................10
physical part of interface name...............................26
fxp1
internal Ethernet interface............................................4
physical part of interface name...............................26
fxp2
internal Ethernet interface............................................4
physical part of interface name...............................26

G
ge
physical part of interface name...............................26
Gigabit Ethernet interfaces
demultiplexing interface information,
displaying.................................................................1363
dynamic VLANs............................................................433
MTU sizes.................................................97, 98, 99, 100
status information, displaying...................1003, 1189
VLAN IDs................................................................967, 971
VLAN tagging.............................................621, 966, 976

2276

Gigabit Ethernet IQ PIC

traffic and MAC statistics...........................1003, 1266
gigether-options statement............................................589
gr
physical part of interface name...............................26
gratuitous-arp-reply statement...........................590, 743
gre
physical part of interface name...............................26
group option
firewall filters..................................................................219
groups
BGP
general information, displaying...................1469
traffic statistics, displaying............................1476
DVMRP, displaying....................................................1658
IGMP membership, displaying..............................1569
MLD
clearing..................................................................1525
displaying.............................................................1594
PIM
general information, displaying...................1675
usage information, displaying......................1658
guard-interval statement...................................................591

H
hardware-assisted-timestamping statement..........592
HDLC encapsulation
Cisco HDLC encapsulation.........................................117
hello-timer statement........................................................593
hidden routes, displaying................................................2035
hierarchical-policer statement.......................................594
hierarchical-scheduler statement
for subscriber interfaces...........................................595
high-plp-max-threshold statement.............................596
high-plp-threshold statement..............................593, 597
hold-interval statement
connectivity-fault management............................597
Ethernet ring protection switching.......................598
hold-time statement
APS...................................................................................598
damping interface transitions
usage guidelines..................................................149
Physical Interface........................................................599
SONET/SDH Defect Triggers...................................601
host statement.....................................................................602
hostnames
IS-IS, displaying...........................................................1797

Copyright 2014, Juniper Networks, Inc.

Index

I
iccp
configuration statements........................................390
idle-cycle-flag statement.................................................604
serial interfaces
usage guidelines..................................................310
idle-timeout statement.....................................................605
ieee802.1p statement........................................................605
if-exceeding statement
hierarchical policer.....................................................606
IGMP
group membership, displaying.............................1569
interfaces, displaying................................................1573
PIM-to-IGMP message translation information,
displaying.................................................................1629
snooping (interface)..................................................1577
snooping (membership).........................................1582
snooping (statistics)................................................1586
statistics, displaying..................................................1591
IGMP snooping
enabling..........................................................................607
igmp-snooping statement...............................................607
ignore statement.................................................................608
ignore-all statement..........................................................608
usage guidelines...........................................................310
ignore-l3-incompletes statement................................609
ilmi statement......................................................................609
ima-group-options statement........................................610
ima-link-options statement..............................................612
inactivity-timeout statement...........................................612
incoming-called-number statement.............................613
incoming-map statement.................................................614
indication statement...........................................................615
usage guidelines...........................................................310
indication-polarity statement..........................................615
usage guidelines...........................................................313
inet protocol family
interface addresses.....................................................194
inet6 protocol family
interface addresses.....................................................196
ingress-policer-overhead statement............................616
ingress-rate-limit statement............................................616
init-command-string statement.....................................617
usage guidelines...........................................................316
initial-route-check statement..........................................618
inner-tag-protocol-id statement....................................619
inner-vlan-id statement....................................................620
inner-vlan-id-range statement........................................621

Copyright 2014, Juniper Networks, Inc.

input option
firewall filters..................................................................219
policers.............................................................................210
input statement.....................................................................621
input-list statement............................................................622
usage guidelines...........................................................219
input-policer statement....................................................623
input-priority-map statement........................................624
input-three-color statement...........................................625
instance statement..............................................................627
interface addresses
logical interfaces...........................................................192
preferred interface addresses.........................197, 198
primary interface addresses.....................................197
Interface encapsulation on PTX Series Packet
Transport Routers
configuring..............................................................123, 174
Interface flags field, content............................................997
interface groups.....................................................................221
interface learning information
Layer 2, displaying....................................................2200
interface names
conventions..............................................................53, 54
interface naming
chassis, routing matrix.................................................38
routing matrix based on a TX Matrix Plus
router..............................................................................35
routing matrix based on a TX Matrix router.........33
TX Matrix Plus router....................................................35
TX Matrix router..............................................................33
interface range
expanding member and member range
statements..................................................................86
interface ranges.......................................................................82
configuration....................................................................83
inheritance range priorities........................................90
inheriting common configuration............................90
under other hierarchies.................................................91
interface statement
CoS...................................................................................628
IEEE 802.1ag.................................................................630
IEEE 802.1X....................................................................629
IEEE 802.3ah..................................................................631
interface transitions
damping...........................................................................149
interface-down statement......................................497, 632
interface-name statement
dynamic VLAN authentication...............................633

2277

Interfaces Fundamentals for Routing Devices

interface-range statement...............................................634
usage guidelines.............................................................83
interface-set statement
Ethernet interfaces.....................................................635
interface-shared-with statement..................................636
interface-status-tlv statement.......................................637
interface-switch statement.............................................638
usage guidelines..........................................................256
interface-type statement.................................................639
interfaces...................................................................................38
alias name......................................................................422
clock sources........................................................116, 469
configuration statements........................................368
container interfaces.........................................................8
descriptive text............................................................505
descriptors.........................................................................51
disabling.................................................................156, 184
display order in configurations..................................54
encapsulation See encapsulation
firewall filters..................................................................219
interface-range............................................................634
mixed VLAN tagging..........................................577, 730
names.................................................................................26
permanent interfaces.................................................4, 5
services interfaces............................................................6
transient interfaces.....................................................4, 5
unit statement..............................................................945
interfaces statement..........................................................640
dynamic profiles...........................................................641
interfaces, displaying
in the forwarding table............................................2032
interleave-fragments statement...................................645
internal clock sources................................................116, 469
internal Ethernet interface.....................................................5
status information, displaying..............................1239
Internet Protocol Control Protocol See IPCP
interval statement...............................................................645
invalid routes, displaying................................................2058
inverse-arp statement.......................................................646
invert-data statement........................................................647
ip
physical part of interface name...............................26
IP addresses
128-bit..............................................................................196
32-bit................................................................................194
IPCP...................................................................................201
unnumbered interfaces.............................................203

2278

IP IGMP snooping
membership
clearing...................................................................1521
statistics
clearing..................................................................1522
IP multicast
announced sessions, displaying..........................1648
backup PE groups, displaying................................1616
bandwidth admission
clearing.................................................................1529
flow map information, displaying........................1618
forwarding cache, clearing......................................1531
forwarding table, displaying..................................1633
forwarding-cache statistics
displaying.............................................................1620
interface information, displaying.........................1622
network information, displaying..........................1624
next-hop table, displaying.....................................1626
PIM-to-IGMP message translation information,
displaying.................................................................1629
PIM-to-MLD message translation information,
displaying..................................................................1631
RPF calculations, displaying.................................1640
SAP announcements, displaying.........................1749
scope, clearing............................................................1532
scoped information, displaying............................1644
sessions, clearing.......................................................1533
statistics
clearing..................................................................1535
displaying.............................................................1655
IP multicast snooping
forwarding table, displaying...................................1651
statistics
clearing.................................................................1534
displaying............................................................1646
ipc (tracing flag)....................................................................321
IPCP..........................................................................................200
assigning PPP properties.........................................202
configuring IP address................................................201
negotiating IP addresses...........................................201
unnumbered interfaces.............................................202
ipip
physical part of interface name...............................26
ipsec-sa statement.............................................................648
IPv4 Protocol family
interface addresses.....................................................192
Same IP Address on Multiple
Interfaces...........................................................194
on logical interfaces....................................................190

Copyright 2014, Juniper Networks, Inc.

Index

IPv6..............................................................................................191
neighbor cache information
clearing..................................................................1754
displaying.............................................................1756
router advertisements
clearing..................................................................1755
displaying.............................................................1758
standards documents.................................................191
transition..........................................................................192
IPv6 Protocol family
on logical interfaces....................................................190
IS-IS
adjacency database entries, clearing.................1762
authentication, displaying.......................................1774
backup coverage
displaying..............................................................1776
backup MPLS LSPs....................................................1778
backup paths
SPF calculations...............................................1780
dynamic overload bit, resetting............................1766
hostname database, displaying............................1797
interfaces, displaying................................................1799
link-state database entries
clearing..................................................................1764
displaying.............................................................1785
neighbors, displaying................................................1770
routes, displaying......................................................1806
SPF calculations, displaying..................................1810
traffic statistics
clearing..................................................................1768
displaying..............................................................1815
ISDN
B-channel interfaces, displaying...........................1213
BRI interfaces, displaying.........................................1219
D-channel interfaces, displaying..........................1223
dialer interfaces, displaying....................................1229
ISDN interfaces
callback-wait-period.................................................459
caller................................................................................460
calling-number.............................................................461
redial-delay...................................................................840
isdn-options statement....................................................649
ISO Protocol family.....................................................190, 192
iteration-count statement...............................................650
iteration-period statement..............................................650
iw
physical part of interface name...............................26

Copyright 2014, Juniper Networks, Inc.

ixgbe0
internal Ethernet interface............................................4
physical part of interface name...............................26
ixgbe1
internal Ethernet interface............................................4
physical part of interface name...............................26

J
join states, clearing PIM...................................................1539
join states, redistributing..................................................1541

K
keep-address-and-control statement.........................651
usage guidelines..........................................................209
keepalives
disabling...........................................................................124
keepalives statement.........................................................652
usage guidelines...........................................................124
key statement........................................................................653

L
l2tp-interface-id statement.............................................653
label-switched interface See LSI
Label-Switched Interface (LSI)
status information, displaying...............................1401
Label-switched interface (LSI) traffic statistics field,
content................................................................................999
lacp statement
802.3ad..........................................................................654
Aggregated Ethernet..................................................655
Layer 2 BPDU loop prevention
clearing errors...............................................................2177
Layer 2 bridging
bridge domain, displaying.......................................2179
flooding, displaying....................................................2181
interface learning information,
displaying................................................................2200
learning information, displaying................2195, 2197
learning properties, displaying..............................2198
MAC address table, clearing...................................2176
MAC address table, displaying.............................2188
statistics, displaying..................................................2192
Layer 2 circuits
connections, displaying...........................................2216
redundant pseudowires.........................................2208
Layer 2 protocol tunneling
clearing errors..............................................................2178
interface information, displaying........................2202

2279

Interfaces Fundamentals for Routing Devices

Layer 2 switching cross-connect

CCC connections..........................................................261
CCC encapsulation......................................................257
MPLS.................................................................................261
router configuration....................................................256
Layer 2 VPNs
connections, displaying...........................................2223
VPLS connections, displaying..............................2239
VPLS statistics, displaying.....................................2262
Layer 3 incomplete errors.................................................609
Layer 3 VPNs
dynamic tunnel database, displaying...............2209
PIM MDTs, displaying................................................1697
layer2-policer statement...................................................657
lc
physical part of interface name...............................26
LCC................................................................................................33
in a routing matrix based on a TX Matrix Plus
router..............................................................................35
LCP
address and control field compression................133
protocol field compression..............................135, 176
lcp-max-conf-req statement..........................................658
lcp-restart-timer statement............................................658
usage guidelines............................................................176
leaky bucket properties..............................................138, 139
learning information
Layer 2, displaying..........................................2195, 2197
learning properties
Layer 2, displaying.....................................................2198
level statement.....................................................................659
line...............................................................................................315
protocol..........................................................................304
line-card chassis See LCC
line-encoding statement..................................................660
line-protocol statement.....................................................661
usage guidelines..........................................................304
line-rate statement..............................................................661
linear-red-profile statement............................................662
linear-red-profiles statement.........................................663
Link flags field, content.....................................................998
link modes...............................................................................109
link protection
disable statement........................................................514
non-revertive statement............................................757
revertive statement....................................................849
link-adjacency-loss statement.......................................663
link-discovery statement..................................................664
link-down statement.........................................................664

2280

link-event-rate statement................................................665
link-fault management.....................................................409
link-fault-management statement..............................666
link-layer-overhead statement.......................................667
link-mode statement.........................................................668
usage guidelines..................................................107, 109
link-protection statement................................................670
linktrace statement.............................................................673
LLDP
displaying......................................................................1822
local information, displaying.................................1825
neighbor
clearing.................................................................1820
neighbors, displaying...............................................1828
remote global statistics, displaying....................1834
statistics
clearing...................................................................1821
statistics, displaying.................................................1836
LMI packets See keepalives
lmi statement
Ethernet OAM...............................................................676
Frame Relay keepalives.............................................674
lmi-type statement..............................................................677
lo
physical part of interface name...............................26
load-interval statement.....................................................678
load-threshold statement................................................679
Local Management Interface packets See
keepalives
local name, configuring.....................................128, 131, 180
local password, configuring......................................131, 180
local-name statement......................................................680
usage guidelines..................................................126, 129
local-password statement................................................681
lockout statement................................................................681
log-prefix statement...........................................................682
Logical interface flags field..............................................999
logical interface properties, statements for................163
logical interface scheduling.............................................790
logical interface statements
family...............................................................................566
logical interfaces
accounting profiles......................................................182
example configuration......................................183
clear loopback detected timer.................................177
default router addresses............................................197
descriptive text...............................................................171
descriptors.........................................................................51
disabling..........................................................................184

Copyright 2014, Juniper Networks, Inc.

Index

encapsulation See encapsulation

example configuration
dynamic CAC.........................................................182
firewall filters..................................................................219
interface addresses.............................................192, 197
interface bandwidth.....................................................172
Layer 2 switching cross-connect...........................256
multipoint connections..............................................176
point-to-point connections......................................175
policers.............................................................................210
PPP restart timers........................................................176
preferred interface addresses.........................197, 198
primary interface addresses............................197, 198
primary router addresses...........................................197
primary router interfaces...........................................197
protocol families..........................................................190
protocol MTU...............................................................208
protocol redirect messages......................................210
SNMP notifications......................................................183
unit numbers....................................................................171
unnumbered interfaces.............................................203
VLAN IDs................................................................967, 971
VLAN-bundled
dual-tag..................................................................977
single-tag..............................................................969
logical part of interface name............................................32
logical routers See logical systems
logical systems
configuration statements........................................384
interfaces.........................................................................184
logical-interface-fpc-redundancy statement
aggregated Ethernet..................................................682
logical-interface-policer statement.............................683
logical-systems statement..............................................684
usage guidelines...........................................................184
long-buildout statement.........................................684, 745
loop-timing statement......................................................685
loopback capability..............................................................314
serial interfaces
example configuration.......................................315
loopback statement
ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and
T1/T3...........................................................................686
Aggregated Ethernet, Fast Ethernet, and Gigabit
Ethernet...........................................................688, 746
serial................................................................................689
serial interfaces
usage guidelines..................................................314
loopback testing....................................................................327

Copyright 2014, Juniper Networks, Inc.

loopback-clear-timer statement..................................690
usage guidelines............................................................177
loss-priority statement......................................................690
loss-threshold statement..................................................691
low-plp-max-threshold statement...............................691
low-plp-threshold statement.........................................692
lowest-priority-defect statement..................................693
ls
physical part of interface name...............................26
lsi
physical part of interface name...............................26
LSI
traffic statistics............................................................999
lsq-failure-options statement........................................694

M
MAC address table
Layer 2, clearing address information................2176
Layer 2, displaying.....................................................2188
mac statement.....................................................................694
mac-address statement
Accept Source Mac....................................................695
dynamic VLAN authentication..............................695
mac-learn-enable statement................................696, 747
mac-validate statement...................................................697
maintenance-association statement..........................698
maintenance-domain statement.................................699
mip-half-function.......................................................709
virtual-switch...............................................................965
management Ethernet interface
configuring for M Series and T Series
routers..........................................................................106
configuring J Series Gigabit Ethernet
interfaces....................................................................106
interface speed.............................................................106
link modes......................................................................109
overview...............................................................................5
management interface..........................................................14
em0...............................................................................10, 14
fxp0...............................................................................10, 14
manuals
comments on................................................................xlvii
martians, displaying.........................................................2058
master-only statement.....................................................700
maximum transmission unit See MTU
maximum-contexts statement.......................................701
maximum-requests statement.......................................701
maximum-vcs statement.................................................702
mc-ae statement.................................................................703

2281

Interfaces Fundamentals for Routing Devices

MDT
displaying information.............................................1697
MDT join TLV
displaying advertisements received....................1701
media (tracing flag).............................................................321
media MTUs.............................................................................93
See also MTU
media-specific interface information
displaying.....................................................................1404
member interfaces
expanding.........................................................................89
inheritance.......................................................................88
member statement
usage guidelines.............................................................83
member-interface-speed statement...........................705
member-interface-type statement..............................706
member-range statement
usage guidelines.............................................................83
mep statement......................................................................707
minimum-links statement................................................708
mip-half-function statement..........................................709
mixed VLAN tagging..................................................577, 730
ml
physical part of interface name...............................26
MLD
group membership
clearing..................................................................1525
displaying.............................................................1594
interfaces, displaying...............................................1598
PIM-to-MLD message translation information,
displaying..................................................................1631
statistics
clearing.................................................................1526
displaying.............................................................1602
mlfr-uni-nni-bundle-options statement......................710
MLPPP
dynamic profile attachment....................................527
MLPPP statements
dynamic-profile............................................................527
mo
physical part of interface name...............................26
mode statement.....................................................................711
usage guidelines..........................................................229
modem-options statement...............................................712
usage guidelines...........................................................316
monitor-session statement...............................................712
usage guidelines..................................................136, 323
monitoring services interfaces
physical interface properties....................................153

2282

MPLS
labels, displaying routes..........................................2051
Layer 2 switching cross-connect............................261
protocol family.....................................................190, 192
mpls statement......................................................................713
mrru statement......................................................................714
ms
physical part of interface name...............................26
MSDP
cache entries, clearing..............................................1527
general information, displaying...........................1605
message source information, displaying..........1607
peer statistics
clearing.................................................................1528
displaying..............................................................1612
source-active cache, displaying..........................1609
mt
physical part of interface name...............................26
MTU
physical interfaces.........................................................93
mtu statement........................................................................715
logical interfaces
usage guidelines.................................................208
usage guidelines.............................................................93
mtun
physical part of interface name...............................26
MTUs
logical interfaces.........................................................208
protocol MTUs.............................................................208
multi-chassis-protection
peer statement............................................................788
multi-chassis-protection statement.............................719
Multi-Rate Ethernet interfaces
MTU sizes........................................................................100
multicast distribution trees See MDT
multicast VPNs
customer multicast routes, displaying..............2229
neighbors, displaying...............................................2235
routing instances, displaying.................................2231
multicast-dlci statement...................................................720
multicast-only statement.................................................720
usage guidelines............................................................191
multicast-statistics
aggregated Ethernet interfaces...............................721
aggregated SONET interfaces.................................721
multicast-vci statement.....................................................722
multilink-max-classes statement..................................723
multipoint connections.......................................................176

Copyright 2014, Juniper Networks, Inc.

Index

multipoint statement..........................................................723
usage guidelines............................................................176
multipoint-destination statement.................................724
Multiprotocol Label Switching See MPLS
multiservice-options statement.....................................725
usage guidelines...........................................................153
MVPN............................................................................1701, 1703
See also Draft-Rosen MVPNs
MVRP
configuration
show..................................1840, 1842, 1845, 1846
dynamic-vlan-memberships
show......................................................................1844
statistics
show......................................................................1848

N
n391 statement.....................................................................726
n392 statement.....................................................................727
n393 statement....................................................................728
name-format statement...................................................729
names.........................................................................................38
of interfaces.....................................................................26
native-vlan-id statement..................................................730
ncp-max-conf-req statement..........................................731
ncp-restart-timer statement...........................................732
usage guidelines............................................................176
negotiate-address statement.........................................734
usage guidelines...........................................................201
negotiating IP addresses
IPCP...................................................................................201
negotiation-options
allow-remote-loopback statement.....................423
no-allow-link-events statement...........................735
negotiation-options statement......................................734
neighbor
ANCP...............................................................................1412
LLDP...............................................................................1820
neighbor statement.............................................................735
next hops
multicast entries, displaying..................................1626
resolution database, displaying..........................2099
routes sent to, displaying........................................2061
no unidirectional statement............................................944
no-aggregate-delegate-processing
statement...........................................................................736
no-allow-link-events statement....................................735
no-asynchronous-notification statement.........427, 736
no-auto-mdix statement...................................................737

Copyright 2014, Juniper Networks, Inc.

no-auto-negotiation statement
J Series uPIM.......................................................436, 739
no-cbit-parity statement.........................................461, 740
no-core-dump statement......................................485, 740
usage guidelines...........................................................153
no-feac-loop-respond statement.........................574, 741
no-flow-control statement.....................................578, 742
no-gratuitous-arp-reply statement....................590, 743
no-gratuitous-arp-request statement.........................743
no-keepalives statement..................................................744
usage guidelines...........................................................124
no-long-buildout statement..................................684, 745
no-loop-timing statement...............................................685
no-loopback statement..........................................688, 746
no-mac-learn-enable statement.........................696, 747
no-partition statement......................................................748
no-payload-scrambler statement.......................750, 785
no-redirects statement......................................................752
usage guidelines...........................................................210
no-source-filtering statement..............................753, 889
no-syslog statement
usage guidelines...........................................................153
no-termination-request statement...............................754
no-translate-discard-eligible statement...........755, 933
no-translate-fecn-and-becn statement...........755, 934
no-traps statement............................................................938
usage guidelines..................................................154, 183
no-unframed statement.........................................756, 944
no-z0-increment statement..................................756, 992
non-revertive statement....................................................757
nonconfigurable interfaces....................................................4

O
OAM
configuration statements..........................................391
OAM cells See keepalives
oam statement.....................................................................758
oam-liveness statement....................................................761
oam-period statement.......................................................762
oc-slice statement...............................................................763
oc12
physical part of interface name...............................26
oc3
physical part of interface name...............................26
oc48
physical part of interface name...............................26
Open Shortest Path First See OSPF
open-timeout statement..................................................763
operating-mode statement.............................................764

2283

Interfaces Fundamentals for Routing Devices

optics-options statement.................................................765
alarm.................................................................................421
warning...........................................................................984
option-82 statement
dynamic VLAN authentication...............................766
OSPF
backup coverage
displaying..............................................................1861
backup MPLS LSPs
displaying............................................................1864
backup neighbor paths...........................................1866
backup paths
SPF calculations...............................................1868
context identifier, displaying..................................1875
interfaces, displaying................................................1897
link-state database entries, displaying
version 2................................................................1877
version 3...............................................................1886
neighbors
clearing connections.......................................1856
displaying............................................................1908
overview
displaying..............................................................1914
routing table entries, displaying............................1919
SPF calculations, displaying.................................1905
statistics, general
clearing.................................................................1859
displaying.............................................................1925
statistics, I/O
clearing.................................................................1855
displaying.............................................................1903
otn-options statement.......................................................767
output option
firewall filters..................................................................219
policers.............................................................................210
output statement.................................................................768
output-list statement.........................................................769
usage guidelines...........................................................219
output-policer statement.................................................770
output-priority-map statement.......................................771
output-three-color statement.........................................772
output-vlan-map statement
Aggregated Ethernet...................................................773
Gigabit Ethernet IQ......................................................774
overflow statement
configuring......................................................................139
receive bucket................................................................775
transmit bucket.............................................................775
overload bit, resetting for IS-IS......................................1766

2284

override statement
stacked VLAN ranges.................................................776
VLAN ranges..................................................................776

P
pado-advertise statement.................................................777
paired-group statement.....................................................777
PAP
configuring default PAP password.........................179
pap statement.......................................................................778
pap-password statement.................................................779
parentheses, in syntax descriptions..............................xlvii
partition statement.............................................................780
passive access, configuring..............................128, 131, 180
passive statement
CHAP.................................................................................781
PAP.....................................................................................781
usage guidelines..................................................126, 129
passive-monitor-mode statement................................782
password statement
stacked vlan ranges....................................................783
vlan ranges.....................................................................783
path-database-size statement.......................................783
path-trace statement.........................................................784
payload-scrambler statement..............................750, 785
payload-size statement....................................................786
pd
physical part of interface name...............................26
pdu-interval statement.....................................................786
pdu-threshold statement..................................................787
pe
physical part of interface name...............................26
peer statement.....................................................................788
peer-unit statement............................................................789
per-unit scheduling.............................................................790
per-unit-scheduler statement........................................790
performance-monitoring statement.............................791
periodic statement...............................................................792
permanent interfaces.........................................................4, 5
pfc statement........................................................................792
usage guidelines...........................................................135

Copyright 2014, Juniper Networks, Inc.

Index

PGM
negative acknowledgments
clearing.................................................................1536
displaying..............................................................1661
source path messages
clearing..................................................................1537
displaying............................................................1664
statistics
clearing.................................................................1538
displaying............................................................1666
physical interfaces
accounting profiles......................................................155
example configuration.......................................155
byte encoding...............................................................455
C-bit parity mode...............................................461, 740
clock rates......................................................................309
clock sources........................................................116, 469
clocking mode..............................................................308
DCE..........................................................................138, 496
descriptive text.....................................................92, 505
descriptors.........................................................................51
disabling..........................................................................156
DTR circuit.......................................................................313
dynamic VLANs............................................................433
encapsulation..................................................................117
idle cycle flag.................................................................310
keepalives........................................................................124
leaky bucket properties.....................................138, 139
line encoding..................................................................315
line protocol..................................................................304
link modes......................................................................109
loopback capability
serial interfaces....................................................314
meaningful alias name..............................................422
media MTU size..............................................................93
mixed VLAN tagging..........................................577, 730
PPP CHAP..............................................................126, 129
signal polarity.................................................................313
SNMP notifications......................................................154
speed..............................................................106, 107, 108
statements.......................................................................65
transitions, damping...................................................149
unidirectional mode
unidirectional link mode............................141, 142
VLAN tagging................................................................976
physical part of interface name........................................26
pic-type statement..............................................................793

Copyright 2014, Juniper Networks, Inc.

PIM
bootstrap routers, displaying................................1670
groups
general information, displaying...................1675
usage information, displaying......................1658
interfaces
displaying..............................................................1672
join states, clearing....................................................1539
MDTs, displaying.........................................................1697
neighbors, displaying................................................1705
PIM-to-IGMP message translation information,
displaying.................................................................1629
PIM-to-MLD message translation information,
displaying..................................................................1631
prune states, clearing...............................................1539
redistibuting join states............................................1541
register
clearing..................................................................1543
RPF, displaying source state..................................1733
RPs
displaying.............................................................1709
statistics
clearing.................................................................1549
displaying.............................................................1736
pimd
physical part of interface name...............................26
pime
physical part of interface name...............................26
plp-to-clp statement..........................................................793
plp1 statement......................................................................794
point-to-point connections
logical interfaces...........................................................175
unnumbered Ethernet interfaces..........................203
Point-to-Point Protocol encapsulation..........................117
encapsulation overhead.............................................96
keepalives........................................................................124
on physical interfaces...................................................117
PPP CHAP..............................................................126, 129
point-to-point statement.................................................795
usage guidelines............................................................175
policer
interface..........................................................................799
Policer field, content.........................................................1000
policer statement
CFM firewall...................................................................795
CFM global level..........................................................796
CFM session level.........................................................797
CoS...................................................................................798

2285

Interfaces Fundamentals for Routing Devices

interface MAC..............................................................800
usage guidelines...........................................................210
policers
applying...........................................................................210
arp option........................................................................210
burst-size-limit
statement...............................................................210
input option....................................................................210
logical interfaces..........................................................210
output option.................................................................210
policers, displaying...............................................................2171
policy, routing
communities...................................................................471
policy-statement statement............................................801
pool statement.....................................................................805
pop statement
Gigabit Ethernet IQ interfaces...............................806
pop-all-labels statement.................................................807
pop-pop statement
Gigabit Ethernet IQ interfaces...............................808
pop-swap statement
Gigabit Ethernet IQ interfaces...............................809
port statement
voice services.................................................................810
port-priority statement
LACP.................................................................................810
port-status-tlv statement..................................................811
post-service-filter statement............................................811
PPP
address and control field compression................133
dynamic profile attachment....................................527
dynamic-profile.............................................................178
PPP clear loopback detected timer.......................177
protocol field compression.......................................135
restart timer....................................................................176
PPP properties, assigning
IPCP..................................................................................202
PPP statements
dynamic-profile............................................................527
ppp-options statement......................................................812
lcp-max-conf-req.......................................................658
ncp-max-conf-req........................................................731
usage guidelines..................................................126, 129
PPPD processes, trace operations........................137, 324
PPPoE
interfaces, displaying................................................1255
pppoe-options statement.................................................813
pppoe-underlying-options statement
static and dynamic PPPoE.......................................814

2286

preferred interface addresses.................................197, 198

preferred statement.............................................................815
usage guidelines..................................................193, 198
preferred-source-address statement...........................816
example...........................................................................207
usage guidelines..........................................................205
premium
policer...............................................................................818
premium statement
hierarchical policer.......................................................817
output priority map.....................................................818
preserve-interface statement..........................................819
primary interface addresses....................................197, 198
primary router addresses....................................................197
primary router interfaces....................................................197
primary statement
address for interface
usage guidelines..................................................198
address on interface..................................................820
AS PIC or Multiservices PIC interfaces................820
interface for router
usage guidelines...................................................197
priority
schedulers.......................................................................821
priority statement
OAM connectivity-fault management.................821
promiscuous-mode statement......................................822
protect-circuit statement.................................................823
protection-group
configuration statements........................................394
protection-group statement............................................824
protocol families
logical interfaces..........................................................190
protocol MTUs.............................................................208
unnumbered interfaces.............................................203
protocol field compression................................................135
Protocol field, content.....................................................1000
protocol MTUs.........................................................................93
logical interfaces.........................................................208
See also MTU
protocol redirect messages...............................................210
protocol-down statement................................................826
protocols
line....................................................................................304
protocols connections
configuration statements..............................389, 393
protocols dot1x
configuration statements........................................390

Copyright 2014, Juniper Networks, Inc.

Index

protocols Ethernet Ring Protection

configuration statements........................................394
protocols iccp
configuration statements........................................390
protocols OAM
configuration statements..........................................391
protocols statement...........................................................826
protocols VRRP
configuration statements..........................................391
proxy statement....................................................................827
proxy-arp statement..........................................................828
prune states, clearing PIM...............................................1539
prunes, DVMRP, displaying..............................................1567
pseudowires
mixed VLAN tagging...................................................577
redundant switchover.............................................2208
PTX Series interfaces
status information, displaying..............................1266
push statement
Gigabit Ethernet IQ interfaces................................829
push-push statement
Gigabit Ethernet IQ interfaces...............................830

Q
queue-depth statement.....................................................831
queue-length statement...................................................832
queues statement................................................................832
quiet-period statement.....................................................833

R
radius-realm statement
dynamic VLAN authentication...............................833
ranges statement
stacked VLAN...............................................................834
VLAN................................................................................834
rate statement......................................................................835
configuring......................................................................139
rdi statement.........................................................................836
reassemble-packets statement.....................................836
reauthentication statement.............................................837
receive (tracing flag modifier)..........................................321
receive-bucket statement................................................838
configuring......................................................................139
receive-options-packets statement.............................838
receive-ttl-exceeded statement....................................839
red-differential-delay statement..................................839
redial-delay statement.....................................................840
redirect messages.................................................................210

Copyright 2014, Juniper Networks, Inc.

redundancy mechanisms for Virtual Chassis

module............................................................................682
redundancy-options statement......................................841
redundant pseudowires, switchover..........................2208
regular expressions
AS paths, displaying matching routes...............1958
IP multicast scope
clearing..................................................................1532
IP multicast sessions
clearing..................................................................1533
displaying............................................................1648
target communities, displaying............................1997
remote statement................................................................842
remote-loopback statement...........................................842
remote-loopback-respond statement........................843
remote-mep statement....................................................844
remove-when-no-subscribers statement.................844
rendezvous points See RPs
replication
of BGP configuration................................................1492
request ancp oam interface command......................1418
request ancp oam neighbor command......................1419
request l2circuit-switchover command...................2208
request pim multicast-tunnel rebalance
command..........................................................................1552
request statement...............................................................845
required-depth statement...............................................846
retries statement.................................................................848
reverse path forwarding See RPF
revert-time statement.......................................................848
revertive statement.............................................................849
rfc-2615 statement.............................................................849
ring-protection-link-end statement.............................850
ring-protection-link-owner statement........................850
RIP
general statistics
clearing..................................................................2134
displaying.............................................................2136
neighbors
displaying.............................................................2138
statistics
clearing..................................................................2135
displaying.............................................................2140

2287

Interfaces Fundamentals for Routing Devices

RIPng
general statistics
clearing.................................................................2144
displaying.............................................................2146
neighbors
displaying.............................................................2148
statistics
clearing..................................................................2145
displaying.............................................................2150
rlsq
physical part of interface name...............................26
rms
physical part of interface name...............................26
route advertisements, displaying..................................1951
route, displaying
next-hop.......................................................................2061
router advertisements
IPv6
clearing..................................................................1755
displaying.............................................................1758
routers
default addresses.........................................................197
primary addresses........................................................197
primary interfaces.........................................................197
routes, displaying
active.............................................................................1940
active path...................................................................1946
advertising protocol...................................................1951
all.....................................................................................1956
AS paths
distribution of......................................................1931
domain information.........................................1935
regular expressions, matching.....................1958
summary of.........................................................1938
best.................................................................................1960
brief information........................................................1963
CCC.................................................................................1965
community ASN........................................................1966
community name......................................................1968
damping, BGP.............................................................1970
detailed information.................................................1975
extensive information..............................................1999
flow validation............................................................2016
hidden...........................................................................2035
in a prefix range.........................................................2087
in a specific routing table.........................................2115
in the forwarding table............................................2018
inactive path...............................................................2038
inactive prefix..............................................................2041

2288

instances......................................................................2043
learned from a specific address...........................2105
learned from a specific protocol.........................2075
learned from snooping............................................2102
LSP.................................................................................2054
martian.........................................................................2058
matching the specified address...........................1992
MPLS labels.................................................................2051
next-hop resolution.................................................2099
not associated with a community......................2067
policy-based route export.....................................1994
received through a neighbor..................................2091
sent to a specific interface....................................2070
summary statistics......................................................2111
terse information........................................................2129
routing matrix
chassis, interface naming...........................................38
interface naming.....................................................33, 35
routing-instance statement..............................................851
PPPoE service name tables....................................852
RPF
calculations, displaying...........................................1640
PIM source state, displaying...................................1733
RPF Failures field, content...............................................1001
rpf-check statement................................................853, 854
usage guidelines...........................................................224
rpf-loose-mode-discard statement.............................855
RPs
displaying......................................................................1709
rsp
physical part of interface name...............................26
rtp statement........................................................................855
rts statement.........................................................................856
usage guidelines...........................................................310
rts-polarity statement.......................................................856
usage guidelines...........................................................313
rtvbr statement.....................................................................857

S
sa-multicast statement....................................................859
sampling statement...........................................................860
SAP session announcements, displaying..................1749
satop-options
payload-size..................................................................786
satop-options statement..................................................861
SCC...............................................................................................33
scheduler-maps statement
for ATM2 IQ interfaces...............................................863
schedulers statement........................................................863

Copyright 2014, Juniper Networks, Inc.

Index

SDH interfaces
MTU sizes...........................................................97, 98, 99
se
physical part of interface name...............................26
secondary statement.........................................................864
send (tracing flag modifier)..............................................321
send-critical-event statement.......................................864
separators, in interface names...........................................32
serial interfaces
clock rates......................................................................309
clocking mode....................................................307, 308
control leads..................................................................310
correcting phase shift................................................308
default settings............................................................304
DTR circuit.......................................................................313
idle cycle flag.................................................................310
invalid statements......................................................306
line encoding..................................................................315
line protocol..................................................................304
loopback capability.....................................................314
signal polarity.................................................................313
status information, displaying..............................1308
serial-options statement..................................................865
server statement..................................................................866
server-timeout statement...............................................866
service statement
logical interfaces..........................................................867
PPPoE.............................................................................868
service-domain statement..............................................869
service-filter statement.....................................................870
service-name statement..................................................870
service-name-table statement
PPPoE underlying interface......................................871
service-name-tables statement
PPPoE..............................................................................872
service-set statement........................................................873
services interfaces....................................................................6
services statement..............................................................874
services-options statement.............................................875
Session Announcement Protocol See SAP
SFC...............................................................................................35
shaping statement..............................................................876
shared-interface statement............................................862
SHDSL
ATM-over-SHDSL interfaces
status information, displaying.......................1071
shdsl-options statement...................................................877
short-name-format statement......................................878
short-sequence statement..............................................879

Copyright 2014, Juniper Networks, Inc.

shortest path first................................................................1810

show (ospf | ospf3) backup coverage
command..........................................................................1861
show (ospf | ospf3) backup lsp....................................1864
show (ospf | ospf3) backup neighbor.......................1866
show (ospf | ospf3) backup spf...................................1868
show (ospf | ospf3) interface command..................1897
show (ospf | ospf3) io-statistics command............1903
show (ospf | ospf3) log command.............................1905
show (ospf | ospf3) neighbor command.................1908
show (ospf | ospf3) overview command...................1914
show (ospf | ospf3) route command..........................1919
show (ospf | ospf3) statistics command..................1925
show amt statistics command.....................................1553
show amt summary command....................................1556
show amt tunnel command..........................................1558
show ancp cos command...............................................1420
show ancp neighbor command....................................1425
show ancp statistics command....................................1433
show ancp subscriber command.................................1438
show ancp summary command...................................1443
show ancp summary neighbor command...............1445
show ancp summary subscriber command.............1447
show as-path command..................................................1931
show as-path domain command................................1935
show as-path summary command............................1938
show bfd session command..........................................1452
show bgp bmp command...............................................1467
show bgp group command............................................1469
show bgp group traffic-statistics command...........1476
show bgp neighbor command.......................................1478
show bgp replication command...................................1492
show bgp summary command.....................................1495
show bridge domain command....................................2179
show bridge flood command..........................................2181
show bridge mac-table command..............................2188
show bridge statistics command.................................2192
show command..............................1840, 1842, 1845, 1846
show dvmrp interfaces command................................1561
show dvmrp neighbors command...............................1563
show dvmrp prefix command.......................................1565
show dvmrp prunes command.....................................1567
show dynamic-tunnels database command.........2209
show esis adjacency command...................................1506
show esis interface command......................................1508
show esis statistics command.......................................1510
show firewall command..................................................2156
show firewall filter version command........................2163
show firewall log command...........................................2164

2289

Interfaces Fundamentals for Routing Devices

show firewall prefix-action-stats command...........2167

show firewall templates-in-use command..............2169
show igmp group command..........................................1569
show igmp interface command....................................1573
show igmp snooping interface command.................1577
show igmp snooping membership command........1582
show igmp snooping statistics command...............1586
show igmp statistics command....................................1591
show interfaces (10-Gigabit Ethernet)
command.........................................................................1003
show interfaces (ATM) command..............................1028
show interfaces (ATM-over-ADSL)
command.........................................................................1063
show interfaces (ATM-over-SHDSL)
command...........................................................................1071
show interfaces (Channelized DS3-to-DS0)
command..........................................................................1079
show interfaces (Channelized DS3-to-DS1)
command.........................................................................1090
show interfaces (Channelized E1 IQ)
command.........................................................................1093
show interfaces (Channelized E1) command..........1097
show interfaces (Channelized OC12 IQ)
command..........................................................................1108
show interfaces (Channelized OC12)
command............................................................................1112
show interfaces (Channelized OC3 IQ and IQE)
command............................................................................1116
show interfaces (Channelized STM1 IQ)
command...........................................................................1135
show interfaces (Channelized STM1)
command...........................................................................1138
show interfaces (Channelized T1 IQ)
command...........................................................................1153
show interfaces (Channelized T3 IQ)
command...........................................................................1165
show interfaces (discard) command...........................1167
show interfaces (Fast Ethernet) command..............1172
show interfaces (Gigabit Ethernet)
command..........................................................................1189
show interfaces (ISDN B-channel) command.........1213
show interfaces (ISDN BRI) command.......................1219
show interfaces (ISDN D-channel)
command..........................................................................1223
show interfaces (ISDN dialer) command.................1229
show interfaces (M Series and T
Series Management and Internal Ethernet)
command..........................................................................1239
show interfaces (PPPoE) command..........................1255

2290

show interfaces (PTX Series Packet Transport

Routers) command.......................................................1266
show interfaces (Serial) command............................1308
show interfaces (SONET/SDH) command.............1280
show interfaces (T1, E1, or DS) command..................1321
show interfaces (T3 or E3) command.......................1346
show interfaces demux0 (Demux Interfaces)
command..........................................................................1363
show interfaces extensive command..........................1372
show interfaces lsi (Label-Switched Interface)
command..........................................................................1401
show interfaces media command...............................1404
show interfaces terse command..................................1407
show ipv6 neighbors command....................................1756
show ipv6 router-advertisement command............1758
show isis adjacency command......................................1770
show isis authentication command.............................1774
show isis backup coverage..............................................1776
show isis backup spf results...........................................1780
show isis context-identifier command.......................1783
show isis database command.......................................1785
show isis hostname command......................................1797
show isis interface command........................................1799
show isis overview command.......................................1803
show isis route command..............................................1806
show isis spf command....................................................1810
show isis statistics command........................................1815
show isis-backup label-switched-path
command..........................................................................1778
show l2-learning global-information
command..........................................................................2195
show l2-learning global-mac-count
command..........................................................................2197
show l2-learning instance command.........................2198
show l2-learning interface command.......................2200
show l2circuit connections command.......................2216
show l2vpn connections command............................2223
show lldp command..........................................................1822
show lldp local-information command.....................1825
show lldp neighbors command....................................1828
show lldp remote-global-statistics
command.........................................................................1834
show lldp statistics command......................................1836
show mac-rewrite interface command....................2202
show mld group command............................................1594
show mld interface command......................................1598
show mld statistics command.....................................1602
show msdp command.....................................................1605
show msdp source command.......................................1607

Copyright 2014, Juniper Networks, Inc.

Index

show msdp source-active command........................1609

show msdp statistics command...................................1612
show multicast backup-pe-groups
command..........................................................................1616
show multicast flow-map command.........................1618
show multicast forwarding-cache statistics
command.........................................................................1620
show multicast interface command...........................1622
show multicast mrinfo command................................1624
show multicast next-hops command........................1626
show multicast pim-to-igmp-proxy
command.........................................................................1629
show multicast pim-to-mld-proxy command.........1631
show multicast route command..................................1633
show multicast rpf command......................................1640
show multicast scope command................................1644
show multicast sessions command...........................1648
show multicast snooping next-hops
command.........................................................................1646
show multicast snooping route command...............1651
show multicast statistics command..........................1655
show multicast usage command................................1658
show mvpn c-multicast command............................2229
show mvpn instance command....................................2231
show mvpn neighbor command..................................2235
show mvrp statistics command...................................1848
show ospf context-identifier command....................1875
show ospf database command....................................1877
show ospf3 database command.................................1886
show pgm negative-acknowledgments
command..........................................................................1661
show pgm source-path-messages
command.........................................................................1664
show pgm statistics command....................................1666
show pim bootstrap command....................................1670
show pim interfaces command.....................................1672
show pim join command.................................................1675
show pim mdt command................................................1697
show pim mdt data-mdt-joins command.................1701
show pim mdt data-mdt-limit command................1703
show pim neighbors command....................................1705
show pim rps command..................................................1709
show pim source command...........................................1733
show pim statistics command......................................1736
show policer command.....................................................2171
show policy damping command...................................1501
show rip general-statistics command........................2136
show rip neighbor command.........................................2138
show rip statistics command........................................2140

Copyright 2014, Juniper Networks, Inc.

show ripng general-statistics command..................2146

show ripng neighbor command....................................2148
show ripng statistics command...................................2150
show route active-path command.............................1946
show route advertising-protocol command.............1951
show route all command................................................1956
show route aspath-regex command..........................1958
show route best command............................................1960
show route brief command............................................1963
show route ccc command..............................................1965
show route command......................................................1940
show route community command..............................1966
show route community-name command................1968
show route damping command...................................1970
show route detail command..........................................1975
show route exact command..........................................1992
show route export command........................................1994
show route export vrf-target command....................1997
show route extensive command..................................1999
show route flow validation command.......................2016
show route forwarding-table command...................2018
show route forwarding-table interface-name
command.........................................................................2032
show route hidden command......................................2035
show route inactive-path command.........................2038
show route inactive-prefix command........................2041
show route instance command...................................2043
show route label command...........................................2051
show route label-switched-path command..........2054
show route martians command..................................2058
show route next-hop command..................................2061
show route no-community command......................2067
show route output command......................................2070
show route protocol command....................................2075
show route range command.........................................2087
show route receive-protocol command....................2091
show route resolution command...............................2099
show route snooping command...................................2102
show route source-gateway command.....................2105
show route summary command.....................................2111
show route table command............................................2115
show route terse command...........................................2129
show sap listen command..............................................1749
show vpls connections command..............................2239
show vpls flood event-queue command...................2251
show vpls flood instance command..........................2253
show vpls flood route command.................................2255
show vpls mac-table command..................................2257
show vpls statistics command.....................................2262

2291

Interfaces Fundamentals for Routing Devices

si
physical part of interface name...............................26
signal polarity, serial interfaces........................................313
sla-iterator-profile statement........................................880
sla-iterator-profiles statement........................................881
snext statement...................................................................882
snooping (interface)
IGMP................................................................................1577
snooping (membership)
IGMP...............................................................................1582
snooping (statistics)
IGMP...............................................................................1586
snooping routes, displaying............................................2102
snr-margin statement........................................................883
so
physical part of interface name...............................26
SONET interfaces
clock sources...................................................................116
damping interface transitions.................................149
encapsulation..................................................................117
leaky bucket properties.....................................138, 139
MTU sizes...........................................................97, 98, 99
sonet-options statement.................................................884
SONET/SDH interfaces
interface speed.............................................................108
status information, displaying
standard...............................................................1280
Source class field, content..............................................1001
source gateway addresses, displaying.......................2105
source statement................................................................886
source-address-filter statement....................................887
source-class usage
example configuration..............................................246
source-class-usage statement......................................888
usage guidelines...........................................................242
source-filtering statement......................................753, 889
sp
physical part of interface name...............................26
speed statement
Ethernet.........................................................................890
MX Series DPC..............................................................891
SONET/SDH..................................................................892
usage guidelines........................................106, 107, 108
SPF calculations, displaying..........................................1905
spid1 statement....................................................................892
spid2 statement...................................................................893
stacked VLAN-tag framing
VLAN ID list....................................................................979
stacked-vlan-ranges statement....................................894

2292

stacked-vlan-tagging statement..................................895
start-end-flag statement.................................................896
static PPPoE statements
pppoe-underlying-options.......................................814
static routes
unnumbered Ethernet interfaces..........................206
static subscribers
interfaces statement..................................................641
pppoe-underlying-options statement.................814
static-interface statement
PPPoE..............................................................................897
static-tei-val statement....................................................898
statistics
Layer 2 bridging, displaying....................................2192
LLDP................................................................................1821
stm1
physical part of interface name...............................26
stm16
physical part of interface name...............................26
stm4
physical part of interface name...............................26
subscriber
ANCP...............................................................................1416
subscriber interface statements
access-concentrator...................................................401
demux0..........................................................................504
family...............................................................................566
interfaces.........................................................................641
mode...................................................................................711
pppoe-underlying-options.......................................814
rpf-check........................................................................853
unit....................................................................................945
unnumbered-address...............................................955
supplicant statement
single (mode)..............................................................898
supplicant-timeout statement......................................899
support, technical See technical support
swap statement
Gigabit Ethernet IQ interfaces...............................900
swap-push statement
Gigabit Ethernet IQ interfaces................................901
swap-swap statement
Gigabit Ethernet IQ interfaces................................902
switch-card chassis SCC......................................................33
switch-fabric chassis SFC...................................................35
switch-options statement...............................................903
switch-port statement
access switching.........................................................904
switch-type statement......................................................905

Copyright 2014, Juniper Networks, Inc.

Index

switching-mode statement............................................906
symbol-period statement................................................907
syntax conventions...............................................................xlvi
syslog statement
usage guidelines...........................................................153
system processes
configuration statements........................................395
system-priority statement
LACP................................................................................909

T
t1
physical part of interface name...............................26
T1 interfaces
byte encoding...............................................................455
MTU sizes...........................................................97, 98, 99
status information, displaying................................1321
t1-options statement..........................................................910
T1600 routers
configured in a routing matrix...................................35
t3
physical part of interface name...............................26
T3 interfaces
C-bit parity mode...............................................461, 740
encapsulation..................................................................117
MTU sizes...........................................................97, 98, 99
status information, displaying..............................1346
t3-options statement..........................................................913
t310 statement........................................................................911
t391 statement........................................................................911
t392 statement......................................................................912
T640 routers.............................................................................33
tag-protocol-id statement
TPID to rewrite..............................................................915
TPIDs expected to be sent or received................914
tap
physical part of interface name...............................26
targeted traffic distribution
Virtual Chassis...............................................................917
targeted-broadcast statement.......................................916
targeted-distribution statement
aggregated Ethernet....................................................917
TCC
encapsulation.................................................................121
technical support
contacting JTAC...........................................................xlviii
tei-option statement............................................................917
terminate statement
PPPoE service name tables.....................................918

Copyright 2014, Juniper Networks, Inc.

test msdp command..........................................................1751

then statement......................................................................801
hierarchical policer......................................................918
threshold statement............................................................919
configuring......................................................................139
timeslots statement...........................................................920
tlv statement..........................................................................477
tm statement..........................................................................921
usage guidelines...........................................................310
tm-polarity statement........................................................921
usage guidelines...........................................................313
to statement...........................................................................801
traceoptions statement
ICCP.................................................................................603
interface processes....................................................924
interfaces........................................................................922
LACP................................................................................926
PPPD................................................................................928
PPPD processes..................................................137, 324
PPPoE...............................................................................931
tracing flags
all........................................................................................321
event..................................................................................321
ipc.......................................................................................321
media................................................................................321
tracing operations
PPPD........................................................................137, 324
traffic distribution mechanisms for Virtual Chassis
targeted distribution....................................................917
transient interfaces..............................................................4, 5
transitions
damping...........................................................................149
translate-discard-eligible statement..................755, 933
translate-fecn-and-becn statement..................755, 934
translate-plp-control-word-de statement................934
translational cross-connect encapsulation See TCC,
encapsulation
transmit clock sources.........................................................116
transmit-bucket statement.............................................935
configuring......................................................................139
transmit-clock statement................................................935
usage guidelines..........................................................308
transmit-period statement..............................................936
transmit-weight statement
ATM2 IQ CoS Forwarding Class.............................937
ATM2 IQ Virtual Circuit..............................................938
traps statement....................................................................938
usage guidelines..................................................154, 183

2293

Interfaces Fundamentals for Routing Devices

Tri-Rate Ethernet interfaces

interface speed..............................................................107
MTU sizes........................................................................100
trigger statement.................................................................939
trigger-link-failure statement.........................................940
Trivial Network Protocol family
interface addresses.....................................................192
on logical interfaces....................................................190
trunk port
VLAN ID list....................................................................970
trunk-bandwidth statement...........................................940
trunk-id statement...............................................................941
ttl statement...........................................................................941
tunnel statement.................................................................942
TX Matrix Plus router
interface naming............................................................35
chassis.......................................................................38
TX Matrix router
interface naming............................................................33
chassis.......................................................................38

IPCP..................................................................................202
point-to-point...............................................................203
unnumbered-address statement
demux interface..........................................................954
dynamic profiles..........................................................955
Ethernet...........................................................................957
PPP...................................................................................958
preferred source address
usage guidelines.................................................205
usage guidelines................................................202, 204
unnumbered-interface statement
usage guidelines..........................................................202
up-count statement...........................................................959
USB modem
configuring......................................................................316
user-prefix statement
dynamic VLAN authentication..............................960
username-include statement
dynamic VLAN authentication...............................961

V
U
umd
physical part of interface name...............................26
underlying-interface statement.....................................943
unframed statement................................................756, 944
unicast RPF.............................................................................224
example configuration.....................................233, 234
fail filters.......................................................227, 233, 234
loose mode....................................................................229
routing asymmetry......................................................227
strict mode.....................................................................227
VPNs.................................................................................232
example configuration......................................232
unicast-reverse-path statement
usage guidelines..........................................................234
unidirectional link mode.....................................................142
overview............................................................................141
unidirectional statement..................................................944
unit numbers.............................................................................171
unit statement......................................................................948
interfaces........................................................................945
logical interfaces
usage guidelines....................................................171
unnumbered interfaces
demux.............................................................................204
Ethernet..........................................................................204
preferred source address.................................816

2294

vbr statement........................................................................962
vc-cos-mode statement...................................................963
vc4
physical part of interface name...............................26
vci statement........................................................................964
vci-range statement...........................................................965
verification
static route......................................................................241
Virtual Chassis
module redundancy...................................................682
redundancy
module...................................................................682
targeted traffic distribution.......................................917
virtual private LAN service See VPLS
virtual-switch statement..................................................965
VLAN CCC encapsulation
encapsulation overhead.............................................96
physical interfaces.........................................................117
VLAN IDs...................................................................................971
VLAN tagging.........................................................................976
vlan-id statement
802.1Q VLANs...............................................................967
ATM-to-Ethernet cross-connect..........................966
Ethernet interfaces.....................................................967
interface in bridge domain......................................966
rewriting at ingress or egress..................................968

Copyright 2014, Juniper Networks, Inc.

Index

vlan-id-list statement
bridge domain..............................................................970
Ethernet VLAN circuit................................................969
vlan-id-range statement....................................................971
Ethernet interfaces.......................................................971
vlan-ranges statement.......................................................972
vlan-rewrite statement......................................................973
vlan-rule statement.............................................................974
vlan-steering statement....................................................975
vlan-tagging statement.....................................................976
vlan-tags statement
dual-tag framing..........................................................977
stacked VLAN tags.....................................................979
vlan-tags-outer statement..............................................980
vlan-vci-ccc encapsulation
ATM-to-Ethernet interworking...............................262
vlan-vci-tagging statement............................................980
ATM-to-Ethernet interworking...............................262
VLANs
automatically removing subscribers...................844
configuring VLAN ranges................................894, 972
voice over IP
dynamic CAC..................................................................182
vpi statement
ATM CCC cell-relay promiscuous mode.............981
Logical Interface and Interworking.......................983
virtual path....................................................................982
VPLS
connections, displaying..........................................2239
statistics, displaying.................................................2262
vpls protocol family
interface addresses.....................................................192
on logical interfaces....................................................190
VPN routing and forwarding See VRF
VPNs
unicast RPF....................................................................232
VRF
route export, displaying...........................................1997
VRF table label
traffic statistics............................................................999
VRRP
configuration statements..........................................391
vrrp
failover-delay................................................................565
vsp
physical part of interface name...............................26
vt
physical part of interface name...............................26
vtmapping statement........................................................983

Copyright 2014, Juniper Networks, Inc.

W
warning statement..............................................................984
watch-list statement.........................................................985
wavelength statement......................................................986
west-interface statement................................................990
working-circuit statement.................................................991

X
xe
physical part of interface name...............................26
xt
physical part of interface name...............................26

Y
yellow-differential-delay statement.............................991

Z
z0-increment statement.........................................756, 992

2295

Interfaces Fundamentals for Routing Devices

2296

Copyright 2014, Juniper Networks, Inc.