0% found this document useful (0 votes)

161 views524 pages

Junos® OS Protocol-Independent Routing Properties Feature Guide

Uploaded by

ayheyt

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

161 views524 pages

Junos® OS Protocol-Independent Routing Properties Feature Guide

Uploaded by

ayheyt

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 524

Junos® OS

Protocol-Independent Routing Properties Feature

Guide

Modified: 2017-08-16

Copyright © 2017, Juniper Networks, Inc.

Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. and/or its affiliates in
the United States and other countries. All other trademarks may be 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 Protocol-Independent Routing Properties Feature Guide
Copyright © 2017 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/. By downloading, installing or using such software, you agree to the terms and conditions of that
EULA.

ii Copyright © 2017, Juniper Networks, Inc.

Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Part 1 Overview
Chapter 1 Introduction to Protocol-Independent Routing Properties . . . . . . . . . . . . . . . 3
Protocol-Independent Routing Properties Overview . . . . . . . . . . . . . . . . . . . . . . . . 3
Routing Table Features in Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Part 2 Configuring Protocol-Independent Routing Properties

Chapter 2 Configuring Routing Tables and Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . 9
Understanding Basic Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Examples: Configuring Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Understanding Basic Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Example: Configuring a Basic Set of Static Routes for Connecting to Stub
Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Example: Configuring IPv6 Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Example: Configuring a Basic Set of Static Routes for Connecting to Stub
Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Example: Configuring IPv6 Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Example: Configuring Static Routes Between Logical Systems Within the Same
Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Understanding Static Route Preferences and Qualified Next Hops . . . . . . . . . . . . 35
Example: Configuring Static Route Preferences and Qualified Next Hops to
Control Static Route Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Understanding Static Route Control in Routing and Forwarding Tables . . . . . . . . 42
Route Retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Readvertisement Prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Forced Rejection of Passive Route Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Example: Preventing a Static Route from Being Readvertised . . . . . . . . . . . . . . . . 43
Understanding Junos OS Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Copyright © 2017, Juniper Networks, Inc. iii

Protocol-Independent Routing Properties Feature Guide

Example: Creating Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Example: Importing Direct and Static Routes Into a Routing Instance . . . . . . . . . 53
Example: Exporting Specific Routes from One Routing Table Into Another Routing
Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Verifying the Static Route Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
IPv4 Address Conservation Method for Hosting Providers . . . . . . . . . . . . . . . . . . . 64
The Issue, Illustrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Chapter 3 Configuring Static Routes for CLNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Understanding Static Routes for CLNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Example: Configuring Static Routes for CLNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 4 Configuring Route Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Understanding Route Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring a Metric Value for Aggregate Routes . . . . . . . . . . . . . . . . . . . . . . 76
Configuring a Preference Value for Aggregate Routes . . . . . . . . . . . . . . . . . . . 76
Configuring the Next Hop for Aggregate Routes . . . . . . . . . . . . . . . . . . . . . . . 77
Associating BGP Communities with Aggregate Routes . . . . . . . . . . . . . . . . . . 77
Associating AS Paths with Aggregate Routes . . . . . . . . . . . . . . . . . . . . . . . . . 78
Including AS Numbers in Aggregate Route Paths . . . . . . . . . . . . . . . . . . . . . . 79
Configuring a Tag Value for Aggregate Routes . . . . . . . . . . . . . . . . . . . . . . . . 80
Controlling Retention of Inactive Aggregate Routes in the Routing and
Forwarding Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Example: Summarizing Static Routes Through Route Aggregation . . . . . . . . . . . . 81
Chapter 5 Configuring RSVP-Signaled Point-to-Multipoint LSP . . . . . . . . . . . . . . . . . . 89
Understanding Point-to-Multipoint LSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Example: Configuring a Collection of Paths to Create an RSVP-Signaled
Point-to-Multipoint LSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 6 Configuring Bidirectional Forwarding Detection for Static Routes . . . . . . . 111
Understanding BFD for Static Routes for Faster Network Failure Detection . . . . . 111
Example: Configuring BFD for Static Routes for Faster Network Failure
Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Understanding BFD Authentication for Static Route Security . . . . . . . . . . . . . . . 122
BFD Authentication Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Security Authentication Keychains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Strict Versus Loose Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Example: Configuring BFD Authentication for Securing Static Routes . . . . . . . . . 124
Example: Enabling BFD on Qualified Next Hops in Static Routes for Route
Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Chapter 7 Configuring Packet Forwarding Behavior for Protocol-Independent
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Understanding the Default Routing Table Groups for Interface Routes on Packet
Transport Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Understanding Indirect Next Hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on
the Packet Forwarding Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

iv Copyright © 2017, Juniper Networks, Inc.

Table of Contents

Understanding Unicast Reverse Path Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . 149

Example: Configuring Unicast Reverse-Path-Forwarding Check . . . . . . . . . . . . . 150
Chapter 8 Configuring Martian Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Understanding Martian Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Example: Configuring Class E Martian Addresses for Routing . . . . . . . . . . . . . . . 160

Part 3 Troubleshooting
Chapter 9 Troubleshooting Network Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Working with Problems on Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Isolating a Broken Network Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Identifying the Symptoms of a Broken Network Connection . . . . . . . . . . . . 169
Isolating the Causes of a Network Problem . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Taking Appropriate Action for Resolving the Network Problem . . . . . . . . . . . 171
Evaluating the Solution to Check Whether the Network Problem Is
Resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Identifying the Symptoms of a Broken Network Connection . . . . . . . . . . . . . . . . 173
Isolating the Causes of a Network Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Taking Appropriate Action for Resolving the Network Problem . . . . . . . . . . . . . . 175
Evaluating the Solution to Check Whether the Network Problem Is Resolved . . . 175
Chapter 10 Debugging and Trace Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Understanding Global Routing Protocol Tracing Operations . . . . . . . . . . . . . . . . . 177
Example: Tracing Global Routing Protocol Operations . . . . . . . . . . . . . . . . . . . . . 178

Part 4 Configuration Statements and Operational Commands

Chapter 11 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
access (Static Access Routes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
access-internal (Static Access-Internal Routes) . . . . . . . . . . . . . . . . . . . . . . . . . 189
active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
aggregate (Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
as-path (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
auto-export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
autonomous-system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
bfd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
bfd-liveness-detection (Routing Options Static Route) . . . . . . . . . . . . . . . . . . . 203
brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
community (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
confederation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
destination-networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
disable (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
dynamic-tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
export (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
export-rib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
fate-sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Copyright © 2017, Juniper Networks, Inc. v

Protocol-Independent Routing Properties Feature Guide

firewall-install-disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
forwarding-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
generate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
graceful-restart (Enabling Globally) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
import-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
import-rib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
independent-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
indirect-next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
indirect-next-hop-change-acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . 236
input (Routing Options RIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
install (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
instance-export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
instance-import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
interface (Multicast Scoping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
interface (Multicast Static Routes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
interface-routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
krt-nexthop-ack-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
longest-match (Static Routes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
lsp-next-hop (Static Routes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
martians . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
maximum-paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
maximum-prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
med-igp-update-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
metric (Aggregate, Generated, or Static Route) . . . . . . . . . . . . . . . . . . . . . . . . . . 256
metric (Qualified Next Hop on Static Route) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
multicast (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
next-hop (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
next-hop (Access Internal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
no-delegate-processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
nonstop-routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
options (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
p2mp-ldp-next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
p2mp-lsp-next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
passive (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
policy (Aggregate and Generated Routes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
ppm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
precision-timers-max-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
preference (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
preference (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
qualified-next-hop (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
qualified-next-hop (Access-Internal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
qualified-next-hop (Static Routes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
readvertise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

vi Copyright © 2017, Juniper Networks, Inc.

Table of Contents

resolution-ribs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
resolve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
restart-duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
restart-duration (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
retain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
rib (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
rib (Route Resolution) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
rib-group (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
rib-groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
route (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
route (Access-Internal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
route-distinguisher-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
route-record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
router-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
routing-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
source-address (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
source-routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
ssm-groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
static (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
tag (Access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
tag (Routing Options) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
threshold (Multicast Forwarding Cache) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
traceoptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
unicast-reverse-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Chapter 12 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
clear bfd adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
clear bfd session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
show bfd session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
show as-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
show as-path domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
show as-path summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
show interfaces routing summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
show route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
show route active-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
show route all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
show route best . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
show route brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
show route cumulative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
show route detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
show route exact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
show route export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
show route export vrf-target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
show route forwarding-table interface-name . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
show route hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
show route inactive-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
show route instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
show route label-switched-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Copyright © 2017, Juniper Networks, Inc. vii

Protocol-Independent Routing Properties Feature Guide

show route localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

show route martians . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
show route next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
show route protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
show route range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
show route resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
show route snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
show route source-gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
show route summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
show route table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
show route terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

viii Copyright © 2017, Juniper Networks, Inc.

List of Figures
Part 2 Configuring Protocol-Independent Routing Properties
Chapter 2 Configuring Routing Tables and Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 1: Customer Routes Connected to a Service Provider . . . . . . . . . . . . . . . . . . 11
Figure 2: Customer Routes Connected to a Service Provider . . . . . . . . . . . . . . . . . 16
Figure 3: Customer Routes Connected to a Service Provider . . . . . . . . . . . . . . . . . 20
Figure 4: Customer Routes Connected to a Service Provider . . . . . . . . . . . . . . . . . 25
Figure 5: Static Routes Between Logical Systems . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 6: Controlling Static Route Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 7: Customer Routes Connected to a Service Provider . . . . . . . . . . . . . . . . . 44
Figure 8: Inefficient Use of IP Address Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 9: Configuration Using the Shared Address Space . . . . . . . . . . . . . . . . . . . 66
Chapter 4 Configuring Route Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 10: Aggregate Route Advertised to an ISP . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Chapter 5 Configuring RSVP-Signaled Point-to-Multipoint LSP . . . . . . . . . . . . . . . . . . 89
Figure 11: Point-to-Multipoint LSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 12: RSVP-Signaled Point-to-Multipoint LSP . . . . . . . . . . . . . . . . . . . . . . . . 92
Chapter 6 Configuring Bidirectional Forwarding Detection for Static Routes . . . . . . . 111
Figure 13: Customer Routes Connected to a Service Provider . . . . . . . . . . . . . . . . 117
Figure 14: Customer Routes Connected to a Service Provider . . . . . . . . . . . . . . . . 125
Figure 15: BFD Enabled on Qualified Next Hops . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Chapter 7 Configuring Packet Forwarding Behavior for Protocol-Independent
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Figure 16: Route to Forwarding Next-Hop Bindings . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 17: Route to Forwarding Indirect Next-Hop Bindings . . . . . . . . . . . . . . . . . 139
Figure 18: Sample Topology for Indirect Next Hops . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 19: Unicast RPF Sample Topoolgy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Part 3 Troubleshooting
Chapter 9 Troubleshooting Network Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Figure 20: Process for Diagnosing Problems in Your Network . . . . . . . . . . . . . . . 168
Figure 21: Network with a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Copyright © 2017, Juniper Networks, Inc. ix

Protocol-Independent Routing Properties Feature Guide

x Copyright © 2017, Juniper Networks, Inc.

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

Part 1 Overview
Chapter 1 Introduction to Protocol-Independent Routing Properties . . . . . . . . . . . . . . . 3
Table 3: Routing Table Route Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Part 3 Troubleshooting
Chapter 9 Troubleshooting Network Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 4: Checklist for Working with Problems on Your Network . . . . . . . . . . . . . . 167

Part 4 Configuration Statements and Operational Commands

Chapter 11 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Table 5: Converted IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Chapter 12 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Table 6: show bfd session Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Table 7: show as-path Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Table 8: show as-path domain Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Table 9: show as-path summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Table 10: show interfaces routing summary Output Fields . . . . . . . . . . . . . . . . . 336
Table 11: show route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Table 12: show route detail Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Table 13: Next-hop Types Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Table 14: State Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Table 15: Communities Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Table 16: show route export Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Table 17: show route export vrf-target Output Fields . . . . . . . . . . . . . . . . . . . . . . 395
Table 18: show route forwarding-table interface-name Output Fields . . . . . . . . 397
Table 19: show route instance Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Table 20: show route localization Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Table 21: show route martians Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Table 22: show route resolution Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Table 23: show route summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Table 24: show route table Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Table 25: Next-hop Types Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Table 26: State Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Table 27: Communities Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

Copyright © 2017, Juniper Networks, Inc. xi

Protocol-Independent Routing Properties Feature Guide

Table 28: show route terse Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

xii Copyright © 2017, Juniper Networks, Inc.

About the Documentation

• Documentation and Release Notes on page xiii

• Supported Platforms on page xiii
• Using the Examples in This Manual on page xiv
• Documentation Conventions on page xv
• Documentation Feedback on page xvii
• Requesting Technical Support on page xviii

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

• SRX Series

• T Series

• MX Series

• M Series

• PTX Series

Copyright © 2017, Juniper Networks, Inc. xiii

Protocol-Independent Routing Properties Feature Guide

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

xiv Copyright © 2017, 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 CLI Explorer.

Documentation Conventions

Table 1 on page xvi defines notice icons used in this guide.

Copyright © 2017, Juniper Networks, Inc. xv

Protocol-Independent Routing Properties Feature Guide

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 xvi defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

Convention Description Examples

Bold text like this Represents text that you type. To enter configuration mode, type the
configure command:

user@host> configure

Fixed-width text like this Represents output that appears on the user@host> show chassis alarms
terminal screen.
No alarms currently active

Italic text like this • Introduces or emphasizes important • A policy term is a named structure
new terms. that defines match conditions and
• Identifies guide names. actions.
• Junos OS CLI User Guide
• Identifies RFC and Internet draft titles.
• RFC 1997, BGP Communities Attribute

Italic text like this Represents variables (options for which Configure the machine’s domain name:
you substitute a value) in commands or
configuration statements. [edit]
root@# set system domain-name
domain-name

xvi Copyright © 2017, Juniper Networks, Inc.

About the Documentation

Table 2: Text and Syntax Conventions (continued)

Convention Description Examples

Text like this Represents names of configuration • To configure a stub area, include the
statements, commands, files, and stub statement at the [edit protocols
directories; configuration hierarchy levels; ospf area area-id] hierarchy level.
or labels on routing platform • The console port is labeled CONSOLE.
components.

< > (angle brackets) Encloses optional keywords or variables. stub <default-metric metric>;

| (pipe symbol) Indicates a choice between the mutually broadcast | multicast

exclusive keywords or variables on either
side of the symbol. The set of choices is (string1 | string2 | string3)
often enclosed in parentheses for clarity.

# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS only
same line as the configuration statement
to which it applies.

[ ] (square brackets) Encloses a variable for which you can community name members [
substitute one or more values. community-ids ]

Indention and braces ( { } ) Identifies a level in the configuration [edit]

hierarchy. routing-options {
static {
route default {
; (semicolon) Identifies a leaf statement at a
nexthop address;
configuration hierarchy level.
retain;
}
}
}

GUI Conventions
Bold text like this Represents graphical user interface (GUI) • In the Logical Interfaces box, select
items you click or select. All Interfaces.
• To cancel the configuration, click
Cancel.

> (bold right angle bracket) Separates levels in a hierarchy of menu In the configuration editor hierarchy,
selections. 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 system—On any page of the Juniper Networks TechLibrary 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
http://www.juniper.net/techpubs/feedback/.

Copyright © 2017, Juniper Networks, Inc. xvii

Protocol-Independent Routing Properties Feature Guide

• E-mail—Send 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 Partner Support Service
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 policies—For 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 warranties—For product warranty information, visit

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

• JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:

• Find CSC offerings: 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.

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

xviii Copyright © 2017, 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 © 2017, Juniper Networks, Inc. xix

Protocol-Independent Routing Properties Feature Guide

xx Copyright © 2017, Juniper Networks, Inc.

PART 1

Overview
• Introduction to Protocol-Independent Routing Properties on page 3

Copyright © 2017, Juniper Networks, Inc. 1

Protocol-Independent Routing Properties Feature Guide

2 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 1

Introduction to Protocol-Independent
Routing Properties

• Protocol-Independent Routing Properties Overview on page 3

• Routing Table Features in Junos OS on page 3

Protocol-Independent Routing Properties Overview

In Junos OS, routing capabilities and features that are not specific to any particular routing
protocol are collectively called protocol-independent routing properties. These features
often interact with routing protocols. In many cases, you combine protocol-independent
properties and routing policy to achieve a goal. For example, you define a static route
using protocol-independent properties, and then, using a routing policy, you can
redistribute the static route into a routing protocol, such as BGP, OSPF, or IS-IS.

Protocol-independent routing properties include:

• Static, aggregate, and generated routes

• Bidirectional Forwarding Detection on static routes

• Global preference

• Martian routes

• Routing tables and routing information base (RIB) groups

Routing Table Features in Junos OS

Junos OS maintains two databases for routing information:

• Routing table—Contains all the routing information learned by all routing protocols.
(Some vendors refer to this kind of table as a routing information base [RIB].)

• Forwarding table—Contains the routes actually used to forward packets. (Some vendors
refer to this kind of table as a forwarding information base [FIB].)

By default, Junos OS maintains three routing tables: one for IP version 4 (IPv4) unicast
routes, a second for multicast routes, and a third for MPLS. You can configure additional
routing tables.

Copyright © 2017, Juniper Networks, Inc. 3

Protocol-Independent Routing Properties Feature Guide

The Junos OS maintains separate routing tables for IPv4 and IP version 6 (IPv6) routes.

The Junos OS installs all active routes from the routing table into the forwarding table.
The active routes are routes that are used to forward packets to their destinations. The
Junos operating system kernel maintains a master copy of the forwarding table. It copies
the forwarding table to the Packet Forwarding Engine, which is the component responsible
for forwarding packets.

The Junos routing protocol process generally determines the active route by selecting
the route with the lowest preference value. The Junos OS provides support for alternate
and tiebreaker preferences, and some of the routing protocols, including BGP and MPLS,
use these additional preferences.

You can add martian addresses and static, aggregate, and generated routes to the Junos
routing tables, configuring the routes with one or more of the properties shown in
Table 3 on page 4.

Table 3: Routing Table Route Properties

Description Static Aggregate Generated

Destination address X X X

Default route to the destination X X X

IP address or interface of the next hop to the destination X – –

Label-switched path (LSP) as next hop X – –

Drop the packets, install a reject route for this destination, X X X

and send Internet Control Message Protocol (ICMP)
unreachable messages

Drop the packets, install a reject route for this destination, X X X

but do not send ICMP unreachable messages

Cause packets to be received by the local router X – –

Associate a metric value with the route X X X

Type of route X X X

Preference values X X X

Additional preference values X X X

Independent preference (qualified-next-hop statement) X – –

BGP community information to associate with the route X X X

Autonomous system (AS) path information to associate X X X

with the route

4 Copyright © 2017, Juniper Networks, Inc.

Chapter 1: Introduction to Protocol-Independent Routing Properties

Table 3: Routing Table Route Properties (continued)

Description Static Aggregate Generated

OSPF tag strings to associate with the route X X X

Do not install active static routes into the forwarding table X – –

Install the route into the forwarding table X – –

Permanently retain a static route in the forwarding table X – –

Include only the longest common leading sequences from – X –

the contributing AS paths

Include all AS numbers for a specific route – X –

Retain an inactive route in the routing and forwarding tables X X X

Remove an inactive route from the routing and forwarding X X X

tables

Active policy to associate with the route – X X

Specify that a route is ineligible for readvertisement X – –

Specify route to a prefix that is not a directly connected X – –

next hop

Copyright © 2017, Juniper Networks, Inc. 5

Protocol-Independent Routing Properties Feature Guide

6 Copyright © 2017, Juniper Networks, Inc.

PART 2

Configuring Protocol-Independent Routing

Properties
• Configuring Routing Tables and Static Routes on page 9
• Configuring Static Routes for CLNS on page 69
• Configuring Route Aggregation on page 73
• Configuring RSVP-Signaled Point-to-Multipoint LSP on page 89
• Configuring Bidirectional Forwarding Detection for Static Routes on page 111
• Configuring Packet Forwarding Behavior for Protocol-Independent Routing on page 137
• Configuring Martian Addresses on page 159

Copyright © 2017, Juniper Networks, Inc. 7

Protocol-Independent Routing Properties Feature Guide

8 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 2

Configuring Routing Tables and Static

Routes

• Understanding Basic Static Routing on page 9

• Examples: Configuring Static Routes on page 10
• Example: Configuring a Basic Set of Static Routes for Connecting to Stub
Networks on page 19
• Example: Configuring IPv6 Static Routes on page 24
• Example: Configuring Static Routes Between Logical Systems Within the Same
Router on page 29
• Understanding Static Route Preferences and Qualified Next Hops on page 35
• Example: Configuring Static Route Preferences and Qualified Next Hops to Control
Static Route Selection on page 36
• Understanding Static Route Control in Routing and Forwarding Tables on page 42
• Example: Preventing a Static Route from Being Readvertised on page 43
• Understanding Junos OS Routing Tables on page 49
• Example: Creating Routing Tables on page 51
• Example: Importing Direct and Static Routes Into a Routing Instance on page 53
• Example: Exporting Specific Routes from One Routing Table Into Another Routing
Table on page 58
• Verifying the Static Route Configuration on page 63
• IPv4 Address Conservation Method for Hosting Providers on page 64

Understanding Basic Static Routing

Routes that are permanent fixtures in the routing and forwarding tables are often
configured as static routes. These routes generally do not change, and often include only
one or very few paths to the destination.

To create a static route in the routing table, you must, at minimum, define the route as
static and associate a next-hop address with it. The static route in the routing table is
inserted into the forwarding table when the next-hop address is reachable. All traffic
destined for the static route is transmitted to the next-hop address for transit.

Copyright © 2017, Juniper Networks, Inc. 9

Protocol-Independent Routing Properties Feature Guide

You can specify options that define additional information about static routes that is
included with the route when it is installed in the routing table. All static options are
optional.

Related • Example: Configuring a Basic Set of Static Routes for Connecting to Stub Networks
Documentation on page 10

Examples: Configuring Static Routes

• Understanding Basic Static Routing on page 10

• Example: Configuring a Basic Set of Static Routes for Connecting to Stub
Networks on page 10
• Example: Configuring IPv6 Static Routes on page 15

Understanding Basic Static Routing

You can specify options that define additional information about static routes that is
included with the route when it is installed in the routing table. All static options are
optional.

Example: Configuring a Basic Set of Static Routes for Connecting to Stub Networks
This example shows how to configure a basic set of static routes.

• Requirements on page 10
• Overview on page 10
• Configuration on page 11
• Verification on page 13

Requirements

In this example, no special configuration beyond device initialization is required.

Overview

There are many practical applications for static routes. Static routing is often used at the
network edge to support attachment to stub networks, which, given their single point of
entry and egress, are well suited to the simplicity of a static route. In Junos OS, static
routes have a global preference of 5. Static routes are activated if the specified next hop
is reachable.

10 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

In this example, you configure the static route 192.168.47.0/24 from the provider network
to the customer network, using the next-hop address of 172.16.1.2. You also configure a
static default route of 0.0.0.0/0 from the customer network to the provider network,
using a next-hop address of 172.16.1.1.

For demonstration purposes, some loopback interfaces are configured on Device B and
Device D. These loopback interfaces provide addresses to ping and thus verify that the
static routes are working.

Figure 1 on page 11 shows the sample network.

Figure 1: Customer Routes Connected to a Service Provider

Provider network
10.0.0.1
10.0.0.2
...

172.16.1.0/24
.2

Customer network
192.168.47.5
192.168.47.6
g041171

...

Configuration

CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration 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.

Device B set interfaces ge-1/2/0 unit 0 description B->D

Device D set interfaces ge-1/2/0 unit 1 description D->B

Copyright © 2017, Juniper Networks, Inc. 11

Protocol-Independent Routing Properties Feature Guide

Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.

To configure basic static routes:

1. On Device B, configure the interfaces.

[edit interfaces]
user@B# set ge-1/2/0 unit 0 description B->D
user@B# set ge-1/2/0 unit 0 family inet address 172.16.1.1/24
user@B# set lo0 unit 57 family inet address 10.0.0.1/32
user@B# set lo0 unit 57 family inet address 10.0.0.2/32

2. On Device B, create a static route and set the next-hop address.

[edit routing-options]
user@B# set static route 192.168.47.0/24 next-hop 172.16.1.2

3. If you are done configuring Device B, commit the configuration.

[edit interfaces]
user@B# commit

4. On Device D, configure the interfaces.

[edit interfaces]
user@D# set ge-1/2/0 unit 1 description D->B
user@D# set ge-1/2/0 unit 1 family inet address 172.16.1.2/24
user@D# set lo0 unit 2 family inet address 192.168.47.5/32
user@D# set lo0 unit 2 family inet address 192.168.47.6/32

5. On Device D, create a static route and set the next-hop address.

[edit routing-options]
user@D# set static route 0.0.0.0/0 next-hop 172.16.1.1

6. If you are done configuring Device D, commit the configuration.

[edit]
user@D# commit

Results

Confirm your configuration by issuing the show interfaces and show routing-options
commands. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.

Device B user@B# show interfaces

ge-1/2/0 {
unit 0 {
description B->D;
family inet {

12 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

address 172.16.1.1/24;
}
}
}
lo0 {
unit 57 {
family inet {
address 10.0.0.1/32;
address 10.0.0.2/32;
}
}
}

user@B# show routing-options

static {
route 192.168.47.0/24 next-hop 172.16.1.2;
}

Device D user@D# show interfaces

ge-1/2/0 {
unit 1 {
description D->B;
family inet {
address 172.16.1.2/24;
}
}
}
lo0 {
unit 2 {
family inet {
address 192.168.47.5/32;
address 192.168.47.6/32;
}
}
}

user@D# show routing-options

static {
route 0.0.0.0/0 next-hop 172.16.1.1;
}

Verification

Confirm that the configuration is working properly.

• Checking the Routing Tables on page 13

• Pinging the Remote Addresses on page 14

Checking the Routing Tables

Purpose Make sure that the static routes appear in the routing tables of Device B and Device D.

Copyright © 2017, Juniper Networks, Inc. 13

Protocol-Independent Routing Properties Feature Guide

Action user@B> show route

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.0.1/32 *[Direct/0] 00:29:43

> via lo0.57
10.0.0.2/32 *[Direct/0] 00:29:43
> via lo0.57
172.16.1.0/24 *[Direct/0] 00:34:40
> via ge-1/2/0.0
172.16.1.1/32 *[Local/0] 00:34:40
Local via ge-1/2/0.0
192.168.47.0/24 *[Static/5] 00:31:23
> to 172.16.1.2 via ge-1/2/0.0

user@D> show route

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[Static/5] 00:31:24

> to 172.16.1.1 via ge-1/2/0.1
172.16.1.0/24 *[Direct/0] 00:35:21
> via ge-1/2/0.1
172.16.1.2/32 *[Local/0] 00:35:21
Local via ge-1/2/0.1
192.168.47.5/32 *[Direct/0] 00:35:22
> via lo0.2
192.168.47.6/32 *[Direct/0] 00:35:21
> via lo0.2

Meaning The static routes are in the routing tables.

Pinging the Remote Addresses

Purpose Verify that the static routes are working.

From Device B, ping one of the loopback interface addresses on Device D.

From Device D, ping one of the loopback interface addresses on Device B.

14 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Action user@B> ping 192.168.47.5

PING 192.168.47.5 (192.168.47.5): 56 data bytes
64 bytes from 192.168.47.5: icmp_seq=0 ttl=64 time=156.126 ms
64 bytes from 192.168.47.5: icmp_seq=1 ttl=64 time=120.393 ms
64 bytes from 192.168.47.5: icmp_seq=2 ttl=64 time=175.361 ms

user@D> ping 10.0.0.1

PING 10.0.0.1 (10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=1.315 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=31.819 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=1.268 ms

Example: Configuring IPv6 Static Routes

This example shows how to configure static routes when the interfaces have IPv6
addresses.

• Requirements on page 15
• Overview on page 15
• Configuration on page 16
• Verification on page 18

Requirements

In this example, no special configuration beyond device initialization is required.

Overview

In this example, you configure a static default route of ::/0, using a next-hop address
2001:db8:0:1:2a0:a502:0:1da.

For demonstration purposes, some loopback interfaces are configured on Device A and
Device E. These loopback interfaces provide addresses to ping and thus verify that the
static routes are working.

Figure 2 on page 16 shows the sample network.

Copyright © 2017, Juniper Networks, Inc. 15

Protocol-Independent Routing Properties Feature Guide

Figure 2: Customer Routes Connected to a Service Provider

Provider network
2001:db8::1/128

2001:db8:0:1::/64

Customer network
2001:db8::5/128

g041176

Configuration

Device A set interfaces fe-1/2/0 unit 1 description to-E

set interfaces fe-1/2/0 unit 1 family inet6 address 2001:db8:0:1:2a0:a502:0:1da/64
set interfaces lo0 unit 1 family inet6 address 2001:db8::1/128 primary
set interfaces lo0 unit 1 family inet6 address 2001:db8::2/128
set interfaces lo0 unit 1 family inet6 address 2001:db8::3/128
set routing-options rib inet6.0 static route 2001:db8::5/128 next-hop
2001:db8:0:1:2a0:a502:0:19da

Device E set interfaces fe-1/2/0 unit 25 description to-A

set interfaces fe-1/2/0 unit 25 family inet6 address 2001:db8:0:1:2a0:a502:0:19da/64
set interfaces lo0 unit 5 family inet6 address 2001:db8::5/128
set routing-options rib inet6.0 static route ::/0 next-hop 2001:db8:0:1:2a0:a502:0:1da

To configure basic static routes:

1. On Device A, configure the interfaces.

[edit interfaces]
user@A# set fe-1/2/0 unit 1 description to-E
user@A# set fe-1/2/0 unit 1 family inet6 address 2001:db8:0:1:2a0:a502:0:1da/64

16 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

user@A# set lo0 unit 1 family inet6 address 2001:db8::1/128 primary

user@A# set lo0 unit 1 family inet6 address 2001:db8::2/128
user@A# set lo0 unit 1 family inet6 address 2001:db8::3/128

2. On Device A, create a static route to Device E’s loopback address and set the
next-hop address.

This ensures that Device A has a route back to Device E.

[edit routing-options]
user@A# set rib inet6.0 static route 2001:db8::5/128 next-hop
2001:db8:0:1:2a0:a502:0:19da

3. If you are done configuring Device A, commit the configuration.

[edit interfaces]
user@A# commit

4. On Device E, configure the interfaces.

[edit]
user@E# set interfaces fe-1/2/0 unit 25 description to-A
user@E# set interfaces fe-1/2/0 unit 25 family inet6 address
2001:db8:0:1:2a0:a502:0:19da/64
user@E# set interfaces lo0 unit 5 family inet6 address 2001:db8::5/128

5. On Device E, create a static default route and set the next-hop address.

[edit routing-options]
user@E# set rib inet6.0 static route ::/0 next-hop 2001:db8:0:1:2a0:a502:0:1da

6. If you are done configuring Device E, commit the configuration.

[edit]
user@E# commit

Results

Device A user@A# show interfaces

fe-1/2/0 {
unit 1 {
description to-E;
family inet6 {
address 2001:db8:0:1:2a0:a502:0:1da/64;
}
}
}
lo0 {
unit 1 {

Copyright © 2017, Juniper Networks, Inc. 17

Protocol-Independent Routing Properties Feature Guide

family inet6 {
address 2001:db8::1/128 {
primary;
}
address 2001:db8::2/128;
address 2001:db8::3/128;
}
}
}

user@A# show routing-options

rib inet6.0 {
static {
route 2001:db8::5/128 next-hop 2001:db8:0:1:2a0:a502:0:19da;
}
}

Device E user@E# show interfaces

fe-1/2/0 {
unit 25 {
description to-A;
family inet6 {
address 2001:db8:0:1:2a0:a502:0:19da/64;
}
}
}
lo0 {
unit 5 {
family inet6 {
address 2001:db8::5/128;
}
}
}

user@E# show routing-options

rib inet6.0 {
static {
route ::/0 next-hop 2001:db8:0:1:2a0:a502:0:1da;
}
}

Verification

Confirm that the configuration is working properly.

• Checking the Routing Tables on page 18

• Pinging the Remote Addresses on page 19

Checking the Routing Tables

Purpose Make sure that the static routes appear in the routing tables of Device A and Device E.

18 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Action user@A> show route protocol static

inet6.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2001:db8::5/128 *[Static/5] 00:27:46

> to 2001:db8:0:1:2a0:a502:0:19da via fe-1/2/0.1

user@E> show route protocol static

inet6.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

::/0 *[Static/5] 00:19:11

> to 2001:db8:0:1:2a0:a502:0:1da via fe-1/2/0.25

Meaning The static routes are in the routing tables.

Pinging the Remote Addresses

Purpose Verify that the static routes are working.

From Device A, ping one of the loopback interface addresses on Device E.

From Device E, ping one of the loopback interface addresses on Device A.

Action user@A> ping 2001:db8::5

PING6(56=40+8+8 bytes) 2001:db8:0:1:2a0:a502:0:1da --> 2001:db8::5
16 bytes from 2001:db8::5, icmp_seq=0 hlim=64 time=1.790 ms
16 bytes from 2001:db8::5, icmp_seq=1 hlim=64 time=1.529 ms
16 bytes from 2001:db8::5, icmp_seq=2 hlim=64 time=1.531 ms

user@E> ping 2001:db8::3

PING6(56=40+8+8 bytes) 2001:db8:0:1:2a0:a502:0:19da --> 2001:db8::3
16 bytes from 2001:db8::3, icmp_seq=0 hlim=64 time=2.146 ms
16 bytes from 2001:db8::3, icmp_seq=1 hlim=64 time=1.964 ms
16 bytes from 2001:db8::3, icmp_seq=2 hlim=64 time=1.550 ms

Example: Configuring a Basic Set of Static Routes for Connecting to Stub Networks

This example shows how to configure a basic set of static routes.

• Requirements on page 19
• Overview on page 20
• Configuration on page 20
• Verification on page 23

Requirements
In this example, no special configuration beyond device initialization is required.

Copyright © 2017, Juniper Networks, Inc. 19

Protocol-Independent Routing Properties Feature Guide

Overview
There are many practical applications for static routes. Static routing is often used at the
network edge to support attachment to stub networks, which, given their single point of
entry and egress, are well suited to the simplicity of a static route. In Junos OS, static
routes have a global preference of 5. Static routes are activated if the specified next hop
is reachable.

For demonstration purposes, some loopback interfaces are configured on Device B and
Device D. These loopback interfaces provide addresses to ping and thus verify that the
static routes are working.

Figure 1 on page 11 shows the sample network.

Figure 3: Customer Routes Connected to a Service Provider

Provider network
10.0.0.1
10.0.0.2
...

172.16.1.0/24
.2

Customer network
192.168.47.5
192.168.47.6
g041171

...

Configuration

Device B set interfaces ge-1/2/0 unit 0 description B->D

20 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Device D set interfaces ge-1/2/0 unit 1 description D->B

To configure basic static routes:

1. On Device B, configure the interfaces.

2. On Device B, create a static route and set the next-hop address.

[edit routing-options]
user@B# set static route 192.168.47.0/24 next-hop 172.16.1.2

3. If you are done configuring Device B, commit the configuration.

[edit interfaces]
user@B# commit

4. On Device D, configure the interfaces.

5. On Device D, create a static route and set the next-hop address.

[edit routing-options]
user@D# set static route 0.0.0.0/0 next-hop 172.16.1.1

6. If you are done configuring Device D, commit the configuration.

[edit]
user@D# commit

Copyright © 2017, Juniper Networks, Inc. 21

Protocol-Independent Routing Properties Feature Guide

Results

Device B user@B# show interfaces

ge-1/2/0 {
unit 0 {
description B->D;
family inet {
address 172.16.1.1/24;
}
}
}
lo0 {
unit 57 {
family inet {
address 10.0.0.1/32;
address 10.0.0.2/32;
}
}
}

user@B# show routing-options

static {
route 192.168.47.0/24 next-hop 172.16.1.2;
}

Device D user@D# show interfaces

ge-1/2/0 {
unit 1 {
description D->B;
family inet {
address 172.16.1.2/24;
}
}
}
lo0 {
unit 2 {
family inet {
address 192.168.47.5/32;
address 192.168.47.6/32;
}
}
}

user@D# show routing-options

static {
route 0.0.0.0/0 next-hop 172.16.1.1;
}

22 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Verification
Confirm that the configuration is working properly.

• Checking the Routing Tables on page 23

• Pinging the Remote Addresses on page 23

Checking the Routing Tables

Purpose Make sure that the static routes appear in the routing tables of Device B and Device D.

Action user@B> show route

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.0.1/32 *[Direct/0] 00:29:43

user@D> show route

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[Static/5] 00:31:24

Meaning The static routes are in the routing tables.

Pinging the Remote Addresses

Purpose Verify that the static routes are working.

From Device B, ping one of the loopback interface addresses on Device D.

From Device D, ping one of the loopback interface addresses on Device B.

Copyright © 2017, Juniper Networks, Inc. 23

Protocol-Independent Routing Properties Feature Guide

Action user@B> ping 192.168.47.5

user@D> ping 10.0.0.1

Related • Understanding Basic Static Routing on page 9

Documentation
• Verifying the Static Route Configuration on page 63

• Example: Configuring IPv6 Static Routes on page 15

Example: Configuring IPv6 Static Routes

This example shows how to configure static routes when the interfaces have IPv6
addresses.

• Requirements on page 24
• Overview on page 24
• Configuration on page 25
• Verification on page 27

Requirements
In this example, no special configuration beyond device initialization is required.

In this example, you configure a static default route of ::/0, using a next-hop address
2001:db8:0:1:2a0:a502:0:1da.

For demonstration purposes, some loopback interfaces are configured on Device A and
Device E. These loopback interfaces provide addresses to ping and thus verify that the
static routes are working.

Figure 2 on page 16 shows the sample network.

24 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Figure 4: Customer Routes Connected to a Service Provider

Provider network
2001:db8::1/128

2001:db8:0:1::/64

Customer network
2001:db8::5/128

g041176

Configuration

Device A set interfaces fe-1/2/0 unit 1 description to-E

Device E set interfaces fe-1/2/0 unit 25 description to-A

To configure basic static routes:

1. On Device A, configure the interfaces.

[edit interfaces]
user@A# set fe-1/2/0 unit 1 description to-E
user@A# set fe-1/2/0 unit 1 family inet6 address 2001:db8:0:1:2a0:a502:0:1da/64

Copyright © 2017, Juniper Networks, Inc. 25

Protocol-Independent Routing Properties Feature Guide

user@A# set lo0 unit 1 family inet6 address 2001:db8::1/128 primary

user@A# set lo0 unit 1 family inet6 address 2001:db8::2/128
user@A# set lo0 unit 1 family inet6 address 2001:db8::3/128

2. On Device A, create a static route to Device E’s loopback address and set the
next-hop address.

This ensures that Device A has a route back to Device E.

[edit routing-options]
user@A# set rib inet6.0 static route 2001:db8::5/128 next-hop
2001:db8:0:1:2a0:a502:0:19da

3. If you are done configuring Device A, commit the configuration.

[edit interfaces]
user@A# commit

4. On Device E, configure the interfaces.

5. On Device E, create a static default route and set the next-hop address.

[edit routing-options]
user@E# set rib inet6.0 static route ::/0 next-hop 2001:db8:0:1:2a0:a502:0:1da

6. If you are done configuring Device E, commit the configuration.

[edit]
user@E# commit

Results

Device A user@A# show interfaces

fe-1/2/0 {
unit 1 {
description to-E;
family inet6 {
address 2001:db8:0:1:2a0:a502:0:1da/64;
}
}
}
lo0 {
unit 1 {

26 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

family inet6 {
address 2001:db8::1/128 {
primary;
}
address 2001:db8::2/128;
address 2001:db8::3/128;
}
}
}

user@A# show routing-options

rib inet6.0 {
static {
route 2001:db8::5/128 next-hop 2001:db8:0:1:2a0:a502:0:19da;
}
}

Device E user@E# show interfaces

fe-1/2/0 {
unit 25 {
description to-A;
family inet6 {
address 2001:db8:0:1:2a0:a502:0:19da/64;
}
}
}
lo0 {
unit 5 {
family inet6 {
address 2001:db8::5/128;
}
}
}

user@E# show routing-options

rib inet6.0 {
static {
route ::/0 next-hop 2001:db8:0:1:2a0:a502:0:1da;
}
}

Verification
Confirm that the configuration is working properly.

• Checking the Routing Tables on page 27

• Pinging the Remote Addresses on page 28

Checking the Routing Tables

Purpose Make sure that the static routes appear in the routing tables of Device A and Device E.

Copyright © 2017, Juniper Networks, Inc. 27

Protocol-Independent Routing Properties Feature Guide

Action user@A> show route protocol static

inet6.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2001:db8::5/128 *[Static/5] 00:27:46

> to 2001:db8:0:1:2a0:a502:0:19da via fe-1/2/0.1

user@E> show route protocol static

inet6.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

::/0 *[Static/5] 00:19:11

> to 2001:db8:0:1:2a0:a502:0:1da via fe-1/2/0.25

Meaning The static routes are in the routing tables.

Pinging the Remote Addresses

Purpose Verify that the static routes are working.

From Device A, ping one of the loopback interface addresses on Device E.

From Device E, ping one of the loopback interface addresses on Device A.

Action user@A> ping 2001:db8::5

user@E> ping 2001:db8::3

Related • Example: Configuring a Basic Set of Static Routes for Connecting to Stub Networks
Documentation on page 10

• Example: Configuring Static Routes Between Logical Systems Within the Same Router
on page 29

28 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Example: Configuring Static Routes Between Logical Systems Within the Same Router

This example shows how to configure static routes between logical systems. The logical
systems are configured in a single physical router and are connected by logical tunnel
interfaces.

• Requirements on page 29
• Overview on page 29
• Configuration on page 30
• Verification on page 33

Requirements
You must connect the logical systems by using logical tunnel (lt) interfaces. See Example:
Connecting Logical Systems Within the Same Device Using Logical Tunnel Interfaces on
MX Series Routers and EX Series Switches.

Overview
A static route is a hard-coded path in the device that specifies how the route gets to a
certain subnet by using a certain path. Routers that are connected to stub networks are
often configured to use static routes. A stub network is a network with no knowledge of
other networks. Stub networks send non-local traffic by way of a single path, with the
network aware only of a default route to non-local destinations. In this example, you
configure Logical System LS1 with a static route to the 10.10.10.0/30 network and define
the next-hop address as 192.168.10.2. You also configure Logical System LS1 with a static
route to the 192.168.10.0/30 network and define a next-hop address of 10.10.10.1.

Figure 5 on page 30 shows the sample network.

Copyright © 2017, Juniper Networks, Inc. 29

Protocol-Independent Routing Properties Feature Guide

Figure 5: Static Routes Between Logical Systems

Router R1

lt-1/2/0.0 lt-1/2/0.1 lt-1/2/0.9 lt-1/2/0.10

LS1 LS2 LS3
.1 .2 .1 .2
192.168.10.0/30 10.10.10.0/30

g040566
Configuration

set logical-systems LS1 interfaces lt-1/2/0 unit 0 description LS1->LS2

set logical-systems LS1 interfaces lt-1/2/0 unit 0 encapsulation ethernet
set logical-systems LS1 interfaces lt-1/2/0 unit 0 peer-unit 1
set logical-systems LS1 interfaces lt-1/2/0 unit 0 family inet address 192.168.10.1/30
set logical-systems LS2 interfaces lt-1/2/0 unit 1 description LS2->LS1
set logical-systems LS2 interfaces lt-1/2/0 unit 1 encapsulation ethernet
set logical-systems LS2 interfaces lt-1/2/0 unit 1 peer-unit 0
set logical-systems LS2 interfaces lt-1/2/0 unit 1 family inet address 192.168.10.2/30
set logical-systems LS2 interfaces lt-1/2/0 unit 9 description LS2->LS3
set logical-systems LS2 interfaces lt-1/2/0 unit 9 encapsulation ethernet
set logical-systems LS2 interfaces lt-1/2/0 unit 9 peer-unit 10
set logical-systems LS2 interfaces lt-1/2/0 unit 9 family inet address 10.10.10.1/30
set logical-systems LS3 interfaces lt-1/2/0 unit 10 description LS3->LS2
set logical-systems LS3 interfaces lt-1/2/0 unit 10 encapsulation ethernet
set logical-systems LS3 interfaces lt-1/2/0 unit 10 peer-unit 9
set logical-systems LS3 interfaces lt-1/2/0 unit 10 family inet address 10.10.10.2/30
set logical-systems LS1 routing-options static route 10.10.10.0/30 next-hop 192.168.10.2
set logical-systems LS3 routing-options static route 192.168.10.0/30 next-hop 10.10.10.1

30 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

To configure static routes between logical systems:

1. Run the show interfaces terse command to verify that the router has a logical tunnel
(lt) interface.

user@host> show interfaces terse

Interface Admin Link Proto Local Remote
so-0/0/0 up down
so-0/0/1 up down
so-0/0/2 up down
so-0/0/3 up down
gr-1/2/0 up up
ip-1/2/0 up up
lt-1/2/0 up up
...

2. Configure the logical tunnel interface on Logical System LS1 connecting to Logical
System LS2.

[edit]
user@host# set logical-systems LS1 interfaces lt-1/2/0 unit 0 description LS1->LS2
user@host# set logical-systems LS1 interfaces lt-1/2/0 unit 0 encapsulation ethernet
user@host# set logical-systems LS1 interfaces lt-1/2/0 unit 0 peer-unit 1
user@host# set logical-systems LS1 interfaces lt-1/2/0 unit 0 family inet address
192.168.10.1/30

3. Configure the logical tunnel interface on Logical System LS2 connecting to Logical
System LS1.

[edit]
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 1 description LS2->LS1
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 1 encapsulation ethernet
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 1 peer-unit 0
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 1 family inet address
192.168.10.2/30

4. Configure the logical tunnel interface on Logical System LS2 connecting to Logical
System LS3.

[edit]
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 9 description LS2->LS3
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 9 encapsulation ethernet
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 9 peer-unit 10
user@host# set logical-systems LS2 interfaces lt-1/2/0 unit 9 family inet address
10.10.10.1/30

5. Configure the logical tunnel interface on Logical System LS3 connecting to Logical
System LS2.

[edit]
user@host# set logical-systems LS3 interfaces lt-1/2/0 unit 10 description LS3->LS2

Copyright © 2017, Juniper Networks, Inc. 31

Protocol-Independent Routing Properties Feature Guide

user@host# set logical-systems LS3 interfaces lt-1/2/0 unit 10 encapsulation

ethernet
user@host# set logical-systems LS3 interfaces lt-1/2/0 unit 10 peer-unit 9
user@host# set logical-systems LS3 interfaces lt-1/2/0 unit 10 family inet address
10.10.10.2/30

6. Configure the static route on Logical System LS1 connecting to the 10.10.10.0/30
network.

[edit]
user@host# set logical-systems LS1 routing-options static route 10.10.10.0/30
next-hop 192.168.10.2

7. Configure the static route on Logical System LS3 connecting to the 192.168.10.0/30
network.

[edit]
user@host# set logical-systems LS3 routing-options static route 192.168.10.0/30
next-hop 10.10.10.1

8. If you are done configuring the device, commit the configuration.

[edit]
user@host# commit

Results

Confirm your configuration by issuing the show logical-systems command. If the output
does not display the intended configuration, repeat the instructions in this example to
correct the configuration.

user@host# show logical-systems

LS1 {
interfaces {
lt-1/2/0 {
unit 0 {
description LS1->LS2;
encapsulation ethernet;
peer-unit 1;
family inet {
address 192.168.10.1/30;
}
}
}
}
routing-options {
static {
route 10.10.10.0/30 next-hop 192.168.10.2;
}
}
}
LS2 {

32 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

interfaces {
lt-1/2/0 {
unit 1 {
description LS2->LS1;
encapsulation ethernet;
peer-unit 0;
family inet {
address 192.168.10.2/30;
}
}
unit 9 {
description LS2->LS3;
encapsulation ethernet;
peer-unit 10;
family inet {
address 10.10.10.1/30;
}
}
}
}
}
LS3 {
interfaces {
lt-1/2/0 {
unit 10 {
description LS3->LS2;
encapsulation ethernet;
peer-unit 9;
family inet {
address 10.10.10.2/30;
}
}
}
}
routing-options {
static {
route 192.168.10.0/30 next-hop 10.10.10.1;
}
}
}

Verification
Confirm that the configuration is working properly.

• Verifying That the Logical Systems Are Up on page 33

• Verifying Connectivity Between the Logical Systems on page 34

Verifying That the Logical Systems Are Up

Purpose Make sure that the interfaces are properly configured.

Copyright © 2017, Juniper Networks, Inc. 33

Protocol-Independent Routing Properties Feature Guide

Action user@host> show interfaces terse

Interface Admin Link Proto Local Remote
...
lt-1/2/0 up up
lt-1/2/0.0 up up inet 192.168.10.1/30
lt-1/2/0.1 up up inet 192.168.10.2/30
lt-1/2/0.9 up up inet 10.10.10.1/30
lt-1/2/0.10 up up inet 10.10.10.2/30
...

Verifying Connectivity Between the Logical Systems

Purpose Make sure that the static routes appear in the routing tables of Logical Systems LS1 and
LS3. Also, make sure that the logical systems can ping each other.

34 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Action user@host> show route logical-system LS1

inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.10.10.0/30 *[Static/5] 18:43:25

> to 192.168.10.2 via lt-1/2/0.0
192.168.10.0/30 *[Direct/0] 18:43:25
> via lt-1/2/0.0
192.168.10.1/32 *[Local/0] 18:43:25
Local via lt-1/2/0.0

user@host> show route logical-system LS3

inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.10.10.0/30 *[Direct/0] 23:11:21

> via lt-1/2/0.10
10.10.10.2/32 *[Local/0] 23:11:21
Local via lt-1/2/0.10
192.168.10.0/30 *[Static/5] 00:23:31
> to 10.10.10.1 via lt-1/2/0.10

From LS1, Ping LS3

user@host> set cli logical-system LS1

user@host:LS1> ping 10.10.10.2

PING 10.10.10.2 (10.10.10.2): 56 data bytes
64 bytes from 10.10.10.2: icmp_seq=0 ttl=63 time=1.263 ms
64 bytes from 10.10.10.2: icmp_seq=1 ttl=63 time=1.086 ms
64 bytes from 10.10.10.2: icmp_seq=2 ttl=63 time=1.077 ms

From LS3, Ping LS1

user@host> set cli logical-system LS3

user@host:LS3> ping 192.168.10.1

PING 192.168.10.1 (192.168.10.1): 56 data bytes
64 bytes from 192.168.10.1: icmp_seq=0 ttl=63 time=10.781 ms
64 bytes from 192.168.10.1: icmp_seq=1 ttl=63 time=1.167 ms
64 bytes from 192.168.10.1: icmp_seq=2 ttl=63 time=1.152 ms

Related • Example: Creating an Interface on a Logical System

Documentation
• Example: Connecting Logical Systems Within the Same Device Using Logical Tunnel
Interfaces on MX Series Routers and EX Series Switches

Understanding Static Route Preferences and Qualified Next Hops

A static route destination address can have multiple next hops associated with it. In this
case, multiple routes are inserted into the routing table, and route selection must occur.
Because the primary criterion for route selection is the route preference, you can control
the routes that are used as the primary route for a particular destination by setting the

Copyright © 2017, Juniper Networks, Inc. 35

Protocol-Independent Routing Properties Feature Guide

route preference associated with a particular next hop. The routes with a lower route
preference are always used to route traffic. When you do not set a preferred route, the
Junos OS chooses in a random fashion one of the next-hop addresses to install into the
forwarding table.

In general, the default properties assigned to a static route apply to all the next-hop
addresses configured for the static route. If, however, you want to configure two possible
next-hop addresses for a particular route and have them treated differently, you can
define one as a qualified next hop.

Qualified next hops allow you to associate one or more properties with a particular
next-hop address. You can set an overall preference for a particular static route and then
specify a different preference for the qualified next hop. For example, suppose two
next-hop addresses (10.10.10.10 and 10.10.10.7) are associated with the static route
192.168.47.5/32. A general preference is assigned to the entire static route, and then a
different preference is assigned to only the qualified next-hop address 10.10.10.7. For
example:

route 192.168.47.5/32 {
next-hop 10.10.10.10;
qualified-next-hop 10.10.10.7 {
preference 6;
}
preference 2;
}

In this example, the qualified next hop 10.10.10.7 is assigned the preference 6, and the
next-hop 10.10.10.10 is assigned the preference 2.

NOTE: The preference and metric options in the [edit route route
qualified-next-hop] hierarchy only apply to the qualified next hops. The
qualified next-hop preference and metric override the route preference and
metric for that specific qualified next hop only, similar to how the route
preference overrides the default preference and metric (for that specific
route).

Related • Example: Configuring Static Route Preferences and Qualified Next Hops to Control
Documentation Static Route Selection on page 36

Example: Configuring Static Route Preferences and Qualified Next Hops to Control
Static Route Selection

This example shows how to control static route selection.

• Requirements on page 37
• Overview on page 37
• Configuration on page 37
• Verification on page 40

36 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Requirements
In this example, no special configuration beyond device initialization is required.

Overview
In this example, the static route 192.168.47.0/24 has two possible next hops. Because
one link has higher bandwidth, this link is the preferred path. To enforce this preference,
the qualified-next-hop statement is included in the configuration on both devices. See
Figure 6 on page 37.

Figure 6: Controlling Static Route Selection

Provider network
10.0.0.1
10.0.0.2
...

.1 .1
Fast Ethernet Gigabit Ethernet
192.168.2.0/24 172.16.1.0/24
.2 .2

Customer network
192.168.47.5
192.168.47.6
g041172

...

Configuration

Device B in Provider set interfaces ge-1/2/0 unit 0 description B->D

Network set interfaces ge-1/2/0 unit 0 family inet address 172.16.1.1/24
set interfaces fe-1/2/1 unit 2 description secondary-B->D
set interfaces fe-1/2/1 unit 2 family inet address 192.168.2.1/24
set interfaces lo0 unit 57 family inet address 10.0.0.1/32
set interfaces lo0 unit 57 family inet address 10.0.0.2/32
set routing-options static route 192.168.47.0/24 next-hop 172.16.1.2
set routing-options static route 192.168.47.0/24 qualified-next-hop 192.168.2.2 preference
25

Device D in Customer set interfaces ge-1/2/0 unit 1 description D->B

Network set interfaces ge-1/2/0 unit 1 family inet address 172.16.1.2/24
set interfaces fe-1/2/1 unit 3 description secondary-D->B

Copyright © 2017, Juniper Networks, Inc. 37

Protocol-Independent Routing Properties Feature Guide

set interfaces fe-1/2/1 unit 3 family inet address 192.168.2.2/24

set interfaces lo0 unit 2 family inet address 192.168.47.5/32
set interfaces lo0 unit 2 family inet address 192.168.47.6/32
set routing-options static route 0.0.0.0/0 next-hop 172.16.1.1
set routing-options static route 0.0.0.0/0 qualified-next-hop 192.168.2.1 preference 25

Step-by-Step The following example requires you to navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.

To control static route selection:

1. On Device B, configure the interfaces.

[edit interfaces]
user@B# set ge-1/2/0 unit 0 description B->D
user@B# set ge-1/2/0 unit 0 family inet address 172.16.1.1/24
user@B# set fe-1/2/1 unit 2 description secondary-B->D
user@B# set fe-1/2/1 unit 2 family inet address 192.168.2.1/24
user@B# set lo0 unit 57 family inet address 10.0.0.1/32
user@B# set lo0 unit 57 family inet address 10.0.0.2/32

2. On Device B, configure a static route to the customer network.

[edit routing-options static route 192.168.47.0/24]

user@B# set next-hop 172.16.1.2

3. On Device B, configure a backup route to the customer network.

[edit routing options static route 192.168.47.0/24]

user@B# set qualified-next-hop 192.168.2.2 preference 25

4. On Device D, configure the interfaces.

[edit interfaces]
user@D# set ge-1/2/0 unit 1 description D->B
user@D# set ge-1/2/0 unit 1 family inet address 172.16.1.2/24
user@D# set fe-1/2/1 unit 3 description secondary-D->B
user@D# set fe-1/2/1 unit 3 family inet address 192.168.2.2/24
user@D# set lo0 unit 2 family inet address 192.168.47.5/32
user@D# set lo0 unit 2 family inet address 192.168.47.6/32

5. On Device D, configure a static default route to external networks.

[edit routing options static route 0.0.0.0/0]

user@D# set next-hop 172.16.1.1

6. On Device D, configure a backup static default route to external networks.

[edit routing options static route 0.0.0.0/0]

user@D# set qualified-next-hop 192.168.2.1 preference 25

38 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Results Confirm your configuration by issuing the show interfaces and show routing-options
commands. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.

user@B# show interfaces

ge-1/2/0 {
unit 0 {
description B->D;
family inet {
address 172.16.1.1/24;
}
}
}
fe-1/2/1 {
unit 2 {
description secondary-B->D;
family inet {
address 192.168.2.1/24;
}
}
}
lo0 {
unit 57 {
family inet {
address 10.0.0.1/32;
address 10.0.0.2/32;
}
}
}

user@B# show routing-options

static {
route 192.168.47.0/24 {
next-hop 172.16.1.2;
qualified-next-hop 192.168.2.2 {
preference 25;
}
}
}

user@D# show interfaces

ge-1/2/0 {
unit 1 {
description D->B;
family inet {
address 172.16.1.2/24;
}
}
}
fe-1/2/1 {
unit 3 {
description secondary-D->B;
family inet {
address 192.168.2.2/24;
}
}

Copyright © 2017, Juniper Networks, Inc. 39

Protocol-Independent Routing Properties Feature Guide

}
lo0 {
unit 2 {
family inet {
address 192.168.47.5/32;
address 192.168.47.6/32;
}
}
}

user@D# show routing-options

static {
route 0.0.0.0/0 {
next-hop 172.16.1.1;
qualified-next-hop 192.168.2.1 {
preference 25;
}
}
}

If you are done configuring the devices, enter commit from configuration mode on both
devices.

Verification
Confirm that the configuration is working properly.

• Checking the Routing Tables on page 40

• Pinging the Remote Addresses on page 41
• Making Sure That the Backup Route Becomes the Active Route on page 41

Checking the Routing Tables

Purpose Make sure that the static routes appear in the routing tables of Device B and Device D.

40 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Action user@B> show route protocol static

inet.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.47.0/24 *[Static/5] 02:02:03

> to 172.16.1.2 via ge-1/2/0.0
[Static/25] 01:58:21
> to 192.168.2.2 via fe-1/2/1.2

user@D> show route protocol static

inet.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[Static/5] 02:02:12

> to 172.16.1.1 via ge-1/2/0.1
[Static/25] 01:58:31
> to 192.168.2.1 via fe-1/2/1.3

Meaning The asterisks (*) in the routing tables show the active routes. The backup routes are
listed next.

Pinging the Remote Addresses

Purpose Verify that the static routes are working.

From Device B, ping one of the loopback interface addresses on Device D.

From Device D, ping one of the loopback interface addresses on Device B.

Action user@B> ping 192.168.47.5

user@D> ping 10.0.0.1

Making Sure That the Backup Route Becomes the Active Route

Purpose If the primary route becomes unusable, make sure that the backup secondary route
becomes active.

Action 1. Disable the active route by deactivating the ge-1/2/0.0 interface on Device B.

user@B# deactivate interfaces ge-1/2/0 unit 0 family inet address 172.16.1.1/24

Copyright © 2017, Juniper Networks, Inc. 41

Protocol-Independent Routing Properties Feature Guide

user@B# commit

2. Check Device B’s routing table.

user@B> show route protocol static

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.47.0/24 *[Static/25] 02:06:24

> to 192.168.2.2 via fe-1/2/1.2

Meaning The backup route has become the active route.

Related • Understanding Static Route Preferences and Qualified Next Hops on page 35
Documentation
• Verifying the Static Route Configuration on page 63

Understanding Static Route Control in Routing and Forwarding Tables

You can control the importation of static routes into the routing and forwarding tables
in a number of ways. Primary ways include assigning one or more of the following
attributes to the route:

• retain—Keeps the route in the forwarding table after the routing process shuts down
or the device reboots.

• no-readvertise—Prevents the route from being readvertised to other routing protocols.

• passive—Rejects traffic destined for the route.

This topic includes the following sections:

• Route Retention on page 42

• Readvertisement Prevention on page 42
• Forced Rejection of Passive Route Traffic on page 43

Route Retention
By default, static routes are not retained in the forwarding table when the routing process
shuts down. When the routing process starts up again, any routes configured as static
routes must be added to the forwarding table again. To avoid this latency, routes can be
flagged as retain, so that they are kept in the forwarding table even after the routing
process shuts down. Retention ensures that the routes are always in the forwarding table,
even immediately after a system reboot.

Readvertisement Prevention
Static routes are eligible for readvertisement by other routing protocols by default. In a
stub area where you might not want to readvertise these static routes under any
circumstances, you can flag the static routes as no-readvertise.

42 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Forced Rejection of Passive Route Traffic

Generally, only active routes are included in the routing and forwarding tables. If a static
route's next-hop address is unreachable, the route is marked passive, and it is not included
in the routing or forwarding tables. To force a route to be included in the routing tables
regardless of next-hop reachability, you can flag the route as passive. If a route is flagged
passive and its next-hop address is unreachable, the route is included in the routing table,
and all traffic destined for the route is rejected.

Related • Example: Preventing a Static Route from Being Readvertised on page 43

Documentation

Example: Preventing a Static Route from Being Readvertised

This example shows how to prevent a static route from being readvertised into OSPF,
thereby preventing the route from appearing in the routing and forwarding tables.

• Requirements on page 43
• Overview on page 43
• Configuration on page 44
• Verification on page 48

Requirements
In this example, no special configuration beyond device initialization is required.

Overview
This example shows how to configure a routing policy that readvertises static routes into
OSPF, with the exception of one static route that is not readvertised because it is tagged
with the no-readvertise statement.

Figure 7 on page 44 shows the sample network.

Copyright © 2017, Juniper Networks, Inc. 43

Protocol-Independent Routing Properties Feature Guide

Figure 7: Customer Routes Connected to a Service Provider

AS 23

EBGP 10.0.3.0/30
.1

B
.1 10.0.2.2/30
AS 17 .2

g041173
OSPF

Configuration

Device A set interfaces fe-1/2/0 unit 4 description A->B

set interfaces fe-1/2/0 unit 4 family inet address 10.0.2.2/30
set protocols ospf area 0.0.0.0 interface fe-1/2/0.4

Device B set interfaces fe-1/2/0 unit 3 description B->A

set interfaces fe-1/2/0 unit 3 family inet address 10.0.2.1/30
set interfaces fe-1/2/1 unit 6 description B->C
set interfaces fe-1/2/1 unit 6 family inet address 10.0.3.1/30
set protocols bgp group ext type external
set protocols bgp group ext peer-as 23
set protocols bgp group ext neighbor 10.0.3.2
set protocols ospf export send-static
set protocols ospf area 0.0.0.0 interface fe-1/2/0.3
set policy-options policy-statement send-static from protocol static
set policy-options policy-statement send-static then accept
set routing-options static route 0.0.0.0/0 next-hop 10.0.3.2
set routing-options static route 192.168.0.0/24 next-hop 10.0.3.2
set routing-options static route 192.168.0.0/24 no-readvertise
set routing-options autonomous-system 17

Device C set interfaces fe-1/2/0 unit 7 description B->C

set interfaces fe-1/2/0 unit 7 family inet address 10.0.3.2/30
set interfaces lo0 unit 5 family inet address 192.168.0.1/32
set protocols bgp group ext type external
set protocols bgp group ext peer-as 17
set protocols bgp group ext neighbor 10.0.3.1

44 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

set routing-options autonomous-system 23

To configure Device A:

1. Configure the interface to Device B.

[edit interfaces fe-1/2/0 unit 4]

user@A# set description A->B
user@A# set family inet address 10.0.2.2/30

2. Configure OSPF to form an OSPF peer relationship with Device B.

[edit protocols ospf area 0.0.0.0]

user@A# set interface fe-1/2/0.4

Step-by-Step To configure Device B:

Procedure
1. Configure the interfaces to Device A and Device C.

[edit interfaces]
user@B# set fe-1/2/0 unit 3 description B->A
user@B# set fe-1/2/0 unit 3 family inet address 10.0.2.1/30
user@B# set fe-1/2/1 unit 6 description B->C
user@B# set fe-1/2/1 unit 6 family inet address 10.0.3.1/30

2. Configure one or more static routes and the autonomous system (AS) number.

[edit routing-options]
user@B# set static route 0.0.0.0/0 next-hop 10.0.3.2
user@B# set static route 192.168.0.0/24 next-hop 10.0.3.2
user@B# set autonomous-system 17

3. Configure the routing policy.

This policy exports static routes from the routing table into OSPF.

[edit policy-options policy-statement send-static]

user@B# set from protocol static
user@B# set then accept

4. Include the no-readvertise statement to prevent the 192.168.0.0/24 route from being
exported into OSPF.

[edit routing-options]
user@B# set static route 192.168.0.0/24 no-readvertise

5. Configure the routing protocols.

Copyright © 2017, Juniper Networks, Inc. 45

Protocol-Independent Routing Properties Feature Guide

The BGP configuration forms an external BGP (EBGP) peer relationship with Device
C.

The OSPF configuration forms an OSPF peer relationship with Device A and applies
the send-static routing policy.

[edit protocols]
user@B# set bgp group ext type external
user@B# set bgp group ext peer-as 23
user@B# set bgp group ext neighbor 10.0.3.2
user@B# set ospf export send-static
user@B# set ospf area 0.0.0.0 interface fe-1/2/0.3

Step-by-Step To configure Device C:

Procedure
1. Create the interface to Device B, and configure the loopback interface.

[edit interfaces ]
user@C# set fe-1/2/0 unit 7 description B->C
user@C# set fe-1/2/0 unit 7 family inet address 10.0.3.2/30
user@C# set lo0 unit 5 family inet address 192.168.0.1/32

2. Configure the EBGP peering session with Device B.

[edit protocols bgp group ext]

user@C# set type external
user@C# set peer-as 17
user@C# set neighbor 10.0.3.1

3. Configure the AS number.

[edit routing-options]
user@C# set autonomous-system 23

Results Confirm your configuration by issuing the show interfaces, show policy-options, show
protocols, and show routing-options commands. If the output does not display the intended
configuration, repeat the instructions in this example to correct the configuration.

Device A user@A# show interfaces

fe-1/2/0 {
unit 4 {
description A->B;
family inet {
address 10.0.2.2/30;
}
}
}

user@A# show protocols

ospf {
area 0.0.0.0 {
interface fe-1/2/0.4;

46 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

}
}

Device B user@B# show interfaces

interfaces {
fe-1/2/0 {
unit 3 {
description B->A;
family inet {
address 10.0.2.1/30;
}
}
}
fe-1/2/1 {
unit 6 {
description B->C;
family inet {
address 10.0.3.1/30;
}
}
}
}

user@B# show policy-options

policy-statement send-static {
from protocol static;
then accept;
}

user@B# show protocols

bgp {
group ext {
type external;
peer-as 23;
neighbor 10.0.3.2;
}
}
ospf {
export send-static;
area 0.0.0.0 {
interface fe-1/2/0.3;
}
}

user@B# show routing-options

static {
route 0.0.0.0/0 next-hop 10.0.3.2;
route 192.168.0.0/24 {
next-hop 10.0.3.2;
no-readvertise;
}
}
autonomous-system 17;

Device C user@C# show interfaces

fe-1/2/0 {

Copyright © 2017, Juniper Networks, Inc. 47

Protocol-Independent Routing Properties Feature Guide

unit 7 {
description B->C;
family inet {
address 10.0.3.2/30;
}
}
}
lo0 {
unit 5 {
family inet {
address 192.168.0.1/32;
}
}
}

user@C# show protocols

bgp {
group ext {
type external;
peer-as 17;
neighbor 10.0.3.1;
}
}

user@C# show routing-options

autonomous-system 23;

If you are done configuring the devices, enter commit from configuration mode.

Verification
Confirm that the configuration is working properly.

Checking the Routing Table

Purpose Make sure that the no-readvertise statement is working.

Action 1. On Device A, run the show route protocol ospf command to make sure that the
192.168.0.0/24 route does not appear in Device A’s routing table.

user@A> show route protocols ospf

inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[OSPF/150] 00:03:15, metric 0, tag 0

> to 10.0.2.1 via fe-1/2/0.4
224.0.0.5/32 *[OSPF/10] 00:04:07, metric 1
MultiRecv

2. On Device B, deactivate the no-readvertise statement.

user@B# deactivate routing-options static route 192.168.0.0/24 no-readvertise

3. On Device A, rerun the show route protocol ospf command to make sure that the
192.168.0.0/24 route appears in Device A’s routing table.

48 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

user@A> show route protocols ospf

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[OSPF/150] 00:04:24, metric 0, tag 0

> to 10.0.2.1 via fe-1/2/0.4
192.168.0.0/24 *[OSPF/150] 00:00:15, metric 0, tag 0
> to 10.0.2.1 via fe-1/2/0.4
224.0.0.5/32 *[OSPF/10] 00:05:16, metric 1
MultiRecv

Meaning The no-readvertise statement is working as expected.

Related • Understanding Static Route Control in Routing and Forwarding Tables on page 42
Documentation
• Verifying the Static Route Configuration on page 63

Understanding Junos OS Routing Tables

Junos OS automatically creates and maintains several routing tables. Each routing table
is used for a specific purpose. In addition to these automatically created routing tables,
you can create your own routing tables.

Each routing table populates a portion of the forwarding table. Thus, the forwarding table
is partitioned based on routing tables. This allows for specific forwarding behavior for
each routing table. For example, for VPNs, each VPN-based routing table has its own
VPN-specific partition in the forwarding table.

It is common for the routing software to maintain unicast routes and multicast routes in
different routing tables. You also might have policy considerations that would lead you
to create separate routing tables to manage the propagation of routing information.

Creating routing tables is optional. If you do not create any, Junos OS uses its default
routing tables, which are as follows:

• inet.0—For IP version 4 (IPv4) unicast routes. This table stores interface local and
direct routes, static routes, and dynamically learned routes.

• inet.1—For the IPv4 multicast forwarding cache. This table stores the IPv4 (S,G) group
entries that are dynamically created as a result of join state information.

• inet.2—For subsequent address family indicator (SAFI) 2 routes, when multiprotocol

BGP (MBGP) is enabled. This table stores unicast routes that are used for multicast
reverse-path-forwarding (RPF) lookup. The routes in this table can be used by the
Distance Vector Multicast Routing Protocol (DVMRP), which requires a specific RPF
table. In contrast, Protocol Independent Multicast (PIM) does not need this table
because it can perform RPF checks against the inet.0 table. You can import routes
from inet.0 into inet.2 using routing information base (RIB) groups, or install routes
directly into inet.2 from a multicast routing protocol.

Copyright © 2017, Juniper Networks, Inc. 49

Protocol-Independent Routing Properties Feature Guide

• inet.3—For IPv4 MPLS. This table stores the egress address of an MPLS label-swiched
path (LSP), the LSP name, and the outgoing interface name. This routing table is used
only when the local device is the ingress node to an LSP.

• inet6.0—For IP version 6 (IPv6) unicast routes. This table stores interface local and
direct routes, static routes, and dynamically learned routes.

• inet6.1—For IPv6 multicast forwarding cache. This table stores the IPv6 (S,G) group
entries that are dynamically created as a result of join state information.

• instance-name.inet.0—If you configure a routing instance, Junos OS creates the default

unicast routing table instance-name.inet.0.

• instance-name.inet.2—If you configure routing-instances instance-name protocols bgp

family inet multicast in a routing instance of type VRF, Junos OS creates the
instance-name.inet.2 table.

Another way to create the instance-name.inet.2 table is to use the rib-group statement.
See “Example: Exporting Specific Routes from One Routing Table Into Another Routing
Table” on page 58.

NOTE: Importing inet-vpn multicast routes from the bgp.l3vpn.2 table into
the instance-name.inet.2 table does not create the instance-name.inet.2
table. The import operation works only if the instance-name.inet.2 table
already exists.

• instance-name.inetflow.0—If you configure a flow route, Junos OS creates the flow

routing table instance-name.inetflow.0.

• bgp.l2vpn.0—For Layer 2 VPN routes learned from BGP. This table stores routes learned
from other provider edge (PE) routers. The Layer 2 routing information is copied into
Layer 2 VPN routing and forwarding instances (VRFs) based on target communities.

• bgp.l3vpn.0—For Layer 3 VPN routes learned from BGP. This table stores routes learned
from other PE routers. Routes in this table are copied into a Layer 3 VRF when there is
a matching route table.

• l2circuit.0—For l2circuit routes learned from LDP. Routes in this table are used to send
or receive l2circuit signaling messages.

• mpls.0—For MPLS label switching operations. This table is used when the local device
is a transit router.

• iso.0—For IS-IS routes. When you are using IS-IS to support IP routing, this table contains
only the local device’s network entity title (NET).

• juniper_private—For Junos OS to communicate internally between the Routing Engine

and PIC hardware.

Related • Example: Creating Routing Tables on page 51

Documentation
• Example: Exporting Specific Routes from One Routing Table Into Another Routing
Table on page 58

50 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Example: Creating Routing Tables

This example shows how to create a custom routing table.

• Requirements on page 51
• Overview on page 51
• Configuration on page 51
• Verification on page 52

Requirements
In this example, no special configuration beyond device initialization is required.

Overview
Creating routing tables is optional. You might have policy considerations that would lead
you to create separate routing tables to manage the propagation of routing information.
This capability is rarely used, but it is demonstrated here for completeness.

If you do not create any routing tables, Junos OS uses its default routing tables.

NOTE: If you want to add static, aggregate, generated, or martian routes only
to the default IPv4 unicast routing table (inet.0), you do not have to create
any routing tables because, by default, these routes are added to inet.0. You
can add these routes by including the static, aggregate, generate, and martians
statements.

To explicitly create a routing table, include the rib statement and child statements under
the rib statement.

The routing table name, routing-table-name, includes the protocol family, optionally
followed by a period and a number. The protocol family can be inet for the IPv4 family,
inet6 for the IPv6 family, or iso for the International Standards Organization (ISO) protocol
family. The number represents the routing instance. The first instance is 0.

This example shows how to configure a custom IPv4 routing table called inet.14. The
example also shows how to populate the routing table with a single static route.

NOTE: On EX Series switches, only dynamically learned routes can be

imported from one routing table group to another.

Configuration

CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network

Copyright © 2017, Juniper Networks, Inc. 51

Protocol-Independent Routing Properties Feature Guide

configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy
level.

set routing-options rib inet.14 static route 10.2.0.0/16 discard

To create a routing table:

1. Configure the routing table.

[edit routing-options]
user@host# set rib inet.14 static route 10.2.0.0/16 discard

2. If you are done configuring the device, commit the configuration.

[edit]
user@host# commit

Results

Confirm your configuration by issuing the show routing-options command. If the output
does not display the intended configuration, repeat the instructions in this example to
correct the configuration.

user@host# show routing-options

rib inet.14 {
static {
route 10.2.0.0/16 discard;
}
}

Verification
Confirm that the configuration is working properly.

• Checking the Routing Table on page 52

Checking the Routing Table

Purpose Make sure that the static route appears in the custom routing table.

52 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Action user@host> show route table inet.14

inet.14: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both

10.2.0.0/16 *[Static/5] 00:00:09

Discard

Meaning The static route is in the custom routing table.

Related • Understanding Junos OS Routing Tables on page 49

Documentation

Example: Importing Direct and Static Routes Into a Routing Instance

This example shows how to populate the routing table that is created when you configure
a virtual router.

• Requirements on page 53
• Overview on page 53
• Configuration on page 54
• Verification on page 57

Requirements
In this example, no special configuration beyond device initialization is required.

Overview
You can install routes into more than one routing table. For example, you might want a
simple configuration that allows you to install a static route into the default routing table
inet.0, as well as a second routing table vpna.inet.0. Instead of configuring the same
static route for each routing table, you can use routing table groups to insert the route
into multiple tables. To create a routing table group, include the rib-groups statement.

This example shows how to export static routes, direct routes, and local routes from the
default IPv4 unicast routing table (inet.0) and import them into the IPv4 unicast routing
table of a virtual router called vpna (vpna.inet.0).

NOTE: To explicitly create a routing table, include the rib statement. In this
case, you do not need to use the rib statement because when you configure
a routing instance, Junos OS automatically creates the routing table
instance-nameinet.0.

In this example, Device A and Device B are directly connected to each other. Device A
also has a virtual router configured called vpna. Device A’s inet.0 routing table has direct
and local routes (also known as interface routes). These routes are imported into vpna’s

Copyright © 2017, Juniper Networks, Inc. 53

Protocol-Independent Routing Properties Feature Guide

inet.0 routing table (vpna.inet.0). Device A also has a static route configured. This static
route is also imported into vpna.inet.0.

Configuration

Device A set interfaces fe-1/2/0 unit 4 description A->B

set interfaces fe-1/2/0 unit 4 family inet address 10.0.2.2/30
set interfaces lo0 unit 1 family inet address 1.1.1.1/32
set routing-instances vpna instance-type virtual-router
set routing-options interface-routes rib-group inet group1
set routing-options static rib-group group1
set routing-options static route 192.168.1.0/24 discard
set routing-options rib-groups group1 import-rib inet.0
set routing-options rib-groups group1 import-rib vpna.inet.0

Device B set interfaces fe-1/2/0 unit 3 description B->A

set interfaces fe-1/2/0 unit 3 family inet address 10.0.2.1/30
set interfaces lo0 unit 2 family inet address 2.2.2.2/32

To configure this example:

1. Configure the routing instance.

[edit routing-instances]
user@A# set vpna instance-type virtual-router

2. Configure the interfaces.

[edit interfaces]
user@A# set fe-1/2/0 unit 4 description A->B
user@A# set fe-1/2/0 unit 4 family inet address 10.0.2.2/30
user@A# set lo0 unit 1 family inet address 1.1.1.1/32

3. Configure one or more static routes.

[edit routing-options]
user@A# set static route 192.168.1.0/24 discard

4. Include the direct and local routes in a routing table group called group1.

The interface-routes statement specifies direct and local routes to match against.
For an example of how to configure and apply a routing policy that specifies

54 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

particular routes for import and export, see “Example: Exporting Specific Routes
from One Routing Table Into Another Routing Table” on page 58.

[edit routing-options]
user@A# set interface-routes rib-group inet group1

5. Include all static routes in the group1 routing table group.

The static statement specifies the protocol (static) to match against.

[edit routing-options]
user@A# set static rib-group group1

6. Configure the primary routing table for group1.

The primary routing table determines the address family of the routing table group.
To configure an IPv4 group, specify inet.0 as the primary table. To configure an IPv6
group, specify inet6.0 as the primary routing table.

[edit routing-options]
user@A# set rib-groups group1 import-rib inet.0

7. Configure the secondary routing table for group1.

[edit routing-options]
user@A# set rib-groups group1 import-rib vpna.inet.0

8. If you are done configuring the device, commit the configuration.

[edit routing-options]
user@A# commit

To configure Device B:

1. Configure the interfaces.

[edit interfaces]
user@B# set fe-1/2/0 unit 3 description B->A
user@B# set fe-1/2/0 unit 3 family inet address 10.0.2.1/30

user@B# set lo0 unit 2 family inet address 2.2.2.2/32

2. If you are done configuring the device, commit the configuration.

[edit]
user@B# commit

Copyright © 2017, Juniper Networks, Inc. 55

Protocol-Independent Routing Properties Feature Guide

Results

Confirm your configuration by issuing the show interfaces, show routing-instances, and
show routing-options commands. If the output does not display the intended configuration,
repeat the instructions in this example to correct the configuration.

user@A# show interfaces

fe-1/2/0 {
unit 4 {
description A->B;
family inet {
address 10.0.2.2/30;
}
}
}
lo0 {
unit 1 {
family inet {
address 1.1.1.1/32;
}
}
}

user@A# show routing-instances

vpna {
instance-type virtual-router;
}

user@A# show routing-options

interface-routes {
rib-group inet group1;
}
static {
rib-group group1;
route 192.168.1.0/24 discard;
}
rib-groups {
group1 {
import-rib [ inet.0 vpna.inet.0 ];
}
}

user@B# show interfaces

fe-1/2/0 {
unit 3 {
description B->A;
family inet {
address 10.0.2.1/30;
}
}
}
lo0 {
unit 2 {
family inet {
address 2.2.2.2/32;
}

56 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

}
}

Verification
Confirm that the configuration is working properly.

Checking the Routing Tables

Purpose Make sure that the expected routes appear in the routing tables.

Action user@A> show route table inet.0

inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

1.1.1.1/32 *[Direct/0] 02:51:24

> via lo0.1
10.0.2.0/30 *[Direct/0] 03:19:06
> via fe-1/2/0.4
10.0.2.2/32 *[Local/0] 03:19:07
Local via fe-1/2/0.4
192.168.1.0/24 *[Static/5] 00:44:21
Discard

user@A> show route table vpna.inet.0

vpna.inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

1.1.1.1/32 *[Direct/0] 02:35:39

> via lo0.1
10.0.2.0/30 *[Direct/0] 02:35:39
> via fe-1/2/0.4
10.0.2.2/32 *[Local/0] 02:35:39
Local via fe-1/2/0.4
192.168.1.0/24 *[Static/5] 00:44:28
Discard

Meaning The static route and the interface routes appear in both routing tables.

Related • Understanding Junos OS Routing Tables on page 49

Documentation
• Example: Exporting Specific Routes from One Routing Table Into Another Routing
Table on page 58

Copyright © 2017, Juniper Networks, Inc. 57

Protocol-Independent Routing Properties Feature Guide

Example: Exporting Specific Routes from One Routing Table Into Another Routing
Table

This example shows how to duplicate specific routes from one routing table into another
routing table within the same routing instance.

• Requirements on page 58
• Overview on page 58
• Configuration on page 58
• Verification on page 62

Requirements
No special configuration beyond device initialization is required before configuring this
example.

Overview
This example uses the auto-export statement and the rib-group statement to accomplish
the goal of exporting specific routes from one routing table to another.

Consider the following points:

• When auto-export is configured in a routing instance, the vrf-import and vrf-export

policies are examined. Based on the route target and community information in the
policies, the auto-export function performs route leaking among the local routing
instance inet.0 tables.

• You can use the rib-group statement if it is necessary to import routes into tables other
than instance.inet.0. To use a RIB group with auto-export, the routing instance should
specify explicit vrf-import and vrf-export policies. The vrf-import and vrf-export policies
can be extended to contain additional terms to filter routes as needed for the RIB group.

In this example, access-internal routes are added into the vpna.inet.0 routing table. The
access-internal routes are also duplicated into the vpna.inet.2 routing table.

Configuration
• Configuring Specific Route Export Between Routing Tables on page 59

set interfaces fe-1/3/1 vlan-tagging

set interfaces fe-1/3/1 unit 0 vlan-id 512
set interfaces fe-1/3/1 unit 0 family inet address 10.168.100.3/24
set interfaces lo0 unit 0 family inet address 192.168.3.3/32
set routing-options rib-groups rib-group-vpna-access-internal import-rib vpna.inet.2
set routing-options autonomous-system 63000

58 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

set policy-options policy-statement vpna-export term a from protocol bgp

set policy-options policy-statement vpna-export term a then community add vpna-comm
set policy-options policy-statement vpna-export term a then accept
set policy-options policy-statement vpna-export term b from protocol access-internal
set policy-options policy-statement vpna-export term b then accept
set policy-options policy-statement vpna-export term c then reject
set policy-options policy-statement vpna-import term a from protocol bgp
set policy-options policy-statement vpna-import term a from community vpna-comm
set policy-options policy-statement vpna-import term a then accept
set policy-options policy-statement vpna-import term b from instance vpna
set policy-options policy-statement vpna-import term b from protocol access-internal
set policy-options policy-statement vpna-import term b then accept
set policy-options policy-statement vpna-import term c then reject
set policy-options community vpna-comm members target:63000:100
set routing-instances vpna instance-type vrf
set routing-instances vpna interface fe-1/3/1.1
set routing-instances vpna route-distinguisher 100:1
set routing-instances vpna vrf-import vpna-import
set routing-instances vpna vrf-export vpna-export
set routing-instances vpna routing-options auto-export family inet unicast rib-group
rib-group-vpna-access-internal
set routing-instances vpna protocols bgp group bgp-vpna type external
set routing-instances vpna protocols bgp group bgp-vpna family inet multicast
set routing-instances vpna protocols bgp group bgp-vpna peer-as 100
set routing-instances vpna protocols bgp group bgp-vpna neighbor 10.0.0.10

Configuring Specific Route Export Between Routing Tables

To configure the device:

1. Configure the interfaces.

[edit interfaces fe-1/3/1]

user@host# set vlan-tagging
user@host# set unit 0 vlan-id 512
user@host# set unit 0 family inet address 10.168.100.3/24

[edit interfaces lo0 unit 0]

user@host# set family inet address 192.168.3.3/32

2. Configure the routing policy that specifies particular routes for import into vpna.inet.0
and export from vpna.inet.0.

[edit policy-options policy-statement vpna-export]

user@host# set term a from protocol bgp
user@host# set term a then community add vpna-comm
user@host# set term a then accept
user@host# set term b from protocol access-internal
user@host# set term b then accept
user@host# set term c then reject

Copyright © 2017, Juniper Networks, Inc. 59

Protocol-Independent Routing Properties Feature Guide

[edit policy-options policy-statement vpna-import]

user@host# set term a from protocol bgp
user@host# set term a from community vpna-comm
user@host# set term a then accept
user@host# set term b from instance vpna
user@host# set term b from protocol access-internal
user@host# set term b then accept
user@host# set term c then reject

[edit policy-options]
user@host# set community vpna-comm members target:63000:100

3. Configure the routing instance.

[edit routing-instances vpna]

user@host# set instance-type vrf
user@host# set interface fe-1/3/1.1
user@host# set route-distinguisher 100:1
user@host# set vrf-import vpna-import
user@host# set vrf-export vpna-export

The vrf-import and vrf-export statements are used to apply the vpna-import and
vpna-export routing policies configured in 2.

4. Configure the RIB group, and import routes into the vpna.inet.2 routing table.

[edit routing-options]
user@host# set rib-groups rib-group-vpna-access-internal import-rib vpna.inet.2

5. Configure the auto-export statement to enable the routes to be exported from one
routing table into another.

[edit routing-options]
user@host# set auto-export family inet unicast rib-group
rib-group-vpna-access-internal

6. Configure BGP.

[edit routing-instances vpna protocols bgp group bgp-vpna]

user@host# set type external
user@host# set family inet multicast
user@host# set peer-as 100
user@host# set neighbor 100.0.0.10

7. Configure the autonomous system (AS) number.

[edit routing-options]
user@host# set autonomous-system 63000

Results From configuration mode, confirm your configuration by entering the show interfaces,
show policy-options, show routing-options, and show routing-instances commands. If the

60 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

output does not display the intended configuration, repeat the instructions in this example
to correct the configuration.

user@host# show interfaces

fe-1/3/1 {
vlan-tagging;
unit 0 {
vlan-id 512;
family inet {
address 10.168.100.3/24;
}
}
}
lo0 {
unit 0 {
family inet {
address 192.168.3.3/32;
}
}
}

user@host# show policy-options

policy-statement vpna-export {
term a {
from {
protocol bgp;
}
then {
community add vpna-comm;
accept;
}
}
term b {
from protocol access-internal;
then accept;
}
term c {
then reject;
}
}
policy-statement vpna-import {
term a {
from {
protocol bgp;
community vpna-comm;
}
then accept;
}
term b {
from {
instance vpna;
protocol access-internal;
}
then accept;
}
term c {

Copyright © 2017, Juniper Networks, Inc. 61

Protocol-Independent Routing Properties Feature Guide

then reject;
}
}
community vpna-comm members target:63000:100;

user@host# show routing-options

rib-groups {
rib-group-vpna-access-internal {
import-rib vpna.inet.2;
}
}
autonomous-system 63000;

user@host# show routing-instances

vpna {
instance-type vrf;
interface fe-1/3/1.1;
route-distinguisher 100:1;
vrf-import vpna-import;
vrf-export vpna-export;
routing-options {
auto-export {
family inet {
unicast {
rib-group rib-group-vpna-access-internal;
}
}
}
}
protocols {
bgp {
group bgp-vpna {
type external;
family inet {
multicast;
}
peer-as 100;
neighbor 100.0.0.10;
}
}
}
}

If you are done configuring the device, enter commit from configuration mode.

Verification
Confirm that the configuration is working properly by running the show table route
vpna.inet.0 and show route table vpna.inet.2 commands.

62 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Verifying the Static Route Configuration

Purpose Verify that the static routes are in the routing table and that those routes are active.

Action From the CLI, enter the show route terse command.

Sample Output

user@host> show route terse

inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

* 192.168.47.5/32 S 5 Reject
* 172.16.0.0/12 S 5 >192.168.71.254
* 192.168.0.0/18 S 5 >192.168.71.254
* 192.168.40.0/22 S 5 >192.168.71.254
* 192.168.64.0/18 S 5 >192.168.71.254
* 192.168.64.0/21 D 0 >fxp0.0
* 192.168.71.246/32 L 0 Local
* 192.168.220.4/30 D 0 >ge-0/0/1.0
* 192.168.220.5/32 L 0 Local
* 192.168.220.8/30 D 0 >ge-0/0/2.0
* 192.168.220.9/32 L 0 Local
* 192.168.220.12/30 D 0 >ge-0/0/3.0
* 192.168.220.13/32 L 0 Local
* 192.168.220.17/32 L 0 Reject
* 192.168.220.21/32 L 0 Reject
* 192.168.220.24/30 D 0 >at-1/0/0.0
* 192.168.220.25/32 L 0 Local
* 192.168.220.28/30 D 0 >at-1/0/1.0
* 192.168.220.29/32 L 0 Local
* 224.0.0.9/32 R 100 1 MultiRecv

Meaning The output shows a list of the routes that are currently in the inet.0 routing table. Verify
the following information:

• Each configured static route is present. Routes are listed in ascending order by IP
address. Static routes are identified with an S in the protocol (P) column of the output.

• Each static route is active. Routes that are active show the next-hop IP address in the
Next hop column. If a route's next-hop address is unreachable, the next-hop address
is identified as Reject. These routes are not active routes, but they appear in the routing
table because the passive attribute is set.

• The preference for each static route is correct. The preference for a particular route is
listed in the Prf column of the output.

Related • show route terse on page 502 in the CLI Explorer

Documentation

Copyright © 2017, Juniper Networks, Inc. 63

Protocol-Independent Routing Properties Feature Guide

IPv4 Address Conservation Method for Hosting Providers

Hosting providers host multiple servers for multiple customers and want to conserve the
usage of their IP address space. Traditionally, when a hosting provider client adds new
servers, the servers are allocated a small block of IP addresses, such as a /29 block, and
the client’s servers are all located in that block of IP addresses.

• The Issue, Illustrated on page 64

• Solution on page 65
• Configuration on page 66

The Issue, Illustrated

For example, Customer A might need three servers and is assigned the block 10.3.3.0/29
(10.3.3.0 through 10.3.3.7). In this scenario, several IP addresses are consumed. These
include the network and broadcast IP addresses (10.3.3.0 and 10.3.3.7), the addresses
for the router gateway that the servers are connected to, and the addresses of the
individual servers. To allocate three servers, eight IP addresses have to be allocated.
Breaking up a single /24 network into 32 /29 networks results in 96 IP addresses out of
the 256, in that /24 is being consumed by the network, broadcast, and gateway addresses.
When this effect is multiplied across thousands of hosting providers, IP address space
is far from being used efficiently. Figure 8 on page 65 illustrates the issue.

64 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

Figure 8: Inefficient Use of IP Address Space

In this configuration, each customer is allocated a /29 block of address space. For each
block, the network, broadcast, and gateway addresses are not available for server IP
addressing, which results in three IP addresses being used inefficiently. In addition, the
blocks consume unused IP addresses for future expansion.

Solution
This issue can be resolved by configuring the interface on the router with an address from
the reserved IPv4 prefix for shared address space (RFC 6598) and by using static routes
pointed at interfaces. IANA has recorded the allocation of an IPv4 /10 for use as shared
address space. The shared address space address range is 100.64.0.0/10.

The interface in the router gets allocated an IP address from the RFC 6598 space, so it
is not consuming publicly routable address space, and connectivity is handled with static
routes on an interface. The interface in the server is configured with a publicly routable
address, but the router interfaces are not. Network and broadcast addresses are consumed
out of the RFC 6598 space rather than the publicly routable address space.

This feature is supported on QFX10000 switches starting with Junos OS 17.1R1.

Figure 9 on page 66 shows the efficient use of IP address space.

Copyright © 2017, Juniper Networks, Inc. 65

Protocol-Independent Routing Properties Feature Guide

Figure 9: Configuration Using the Shared Address Space

In this configuration, each customer gets allocated individual IP addresses per server.
There is a static route that can be configured as a host route. The interface in the router
gets allocated an IP address from the RFC 6598 space, so it does not consume publicly
routable address space, and connectivity is handled with static routes out to an interface.

Configuration
The configuration would look like this for Customer A on the gateway router:

interfaces {
ge-1/0/1 {
unit 0 {
family inet {
address 100.64.0.1/30;
}
}
}
}

routing-options {
static {
route 203.0.113.10/32 {
qualified-next-hop ge-1/0/1.0;
}

66 Copyright © 2017, Juniper Networks, Inc.

Chapter 2: Configuring Routing Tables and Static Routes

route 203.0.113.11 {
qualified-next-hop ge-1/0/1.0;
}
}
}

With this configuration, no publicly routable IP addresses are wasted. It is worth noting
that when a packet is forwarded in this configuration from the router to the server of
Customer A’s server 203.0.113.10, the route is forwarded out to the interface ge-1/0/1.0
which has an IP address of 100.64.0.1.

The servers for customer A would be configured as follows:

ifconfig eth0 203.0.113.10 netmask 255.255.255.255

route add -host 100.64.0.1/32 dev eth0 route add default gw 100.64.0.1

ifconfig eth0 203.0.113.11 netmask 255.255.255.255

route add -host 100.64.0.1/32 dev eth0 route add default gw 100.64.0.1

This example shows a single host route per server, which is a 1:1 mapping. This could
equate to a large number of static host routes, if maintained. For scaling purposes, we
need to support nonhost routes in this environment. For example, if there were a Customer
C in this configuration that had eight servers, it would be much more efficient to allocate
a /29 route on the router that points out the interface on which the eight servers are
connected. If Customer C were allocated server IPs from 203.0.114.8 through 203.0.114.15
and these were connected via interface ge-1/0/2.0, this would look like:

user@host# set routing-options static route 203.0.114.8/29 qualified-next-hop ge-1/0/2.0

Release History Table Release Description

17.1R1 This feature is supported on QFX10000 switches starting with Junos

OS 17.1R1.

Copyright © 2017, Juniper Networks, Inc. 67

Protocol-Independent Routing Properties Feature Guide

68 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 3

Configuring Static Routes for CLNS

• Understanding Static Routes for CLNS on page 69

• Example: Configuring Static Routes for CLNS on page 69

Understanding Static Routes for CLNS

The Connectionless Network Service (CLNS) is an ISO Layer 3 protocol that uses network
service access point (NSAP) reachability information instead of IPv4 or IPv6 prefixes.

You can configure static routes to exchange CLNS routes within a CLNS island. A CLNS
island is typically an IS-IS level 1 area that is part of a single IGP routing domain. An island
can contain more than one area. CLNS islands can be connected by VPNs.

Related • Example: Configuring Static Routes for CLNS on page 69

Documentation

Example: Configuring Static Routes for CLNS

This example shows how to configure static routes for CLNS.

• Requirements on page 69
• Overview on page 69
• Configuration on page 70
• Verification on page 71

Requirements
Before you begin, configure the network interfaces. See Interfaces Feature Guide for
Security Devices.

Overview
In this example, you configure static routes for CLNS. In the absence of an interior gateway
protocol (IGP) on a certain link, a routing device might need to be configured with static
routes for CLNS prefixes to be reachable by way of that link. This might be useful, for
example, at an autonomous system (AS) boundary.

Copyright © 2017, Juniper Networks, Inc. 69

Protocol-Independent Routing Properties Feature Guide

When you configure static routes for CLNS, consider the following tasks:

• Specify the iso.0 routing table option to configure a primary instance CLNS static route.

• Specify the instance-name.iso.0 routing table option to configure a CLNS static route
for a particular routing instance.

• Specify the route nsap-prefix statement to configure the destination for the CLNS static
route.

• Specify the next-hop (interface-name | iso-net) statement to configure the next hop,
specified as an ISO network entity title (NET) or interface name.

• Include the qualified-next-hop (interface-name | iso-net) statement to configure a

secondary backup next hop, specified as an ISO network entity title or interface name.

Configuration

CLI Quick To quickly configure this example, copy the following commands, paste them into a text
Configuration file, remove any line breaks, change any details necessary to match your network
configuration, copy and paste the commands into the CLI at the [edit] hierarchy level,
and then enter commit from configuration mode.

set routing-options rib iso.0 static iso-route 47.0005.80ff.f800.0000.ffff.ffff/152 next-hop

47.0005.80ff.f800.0000.0108.0001.1921.6800.4212
set routing-options rib iso.0 static iso-route
47.0005.80ff.f800.0000.0108.0001.1921.6800.4212/152 next-hop t1-0/2/2.0
set routing-options rib iso.0 static iso-route 47.0005.80ff.f800.0000.eee0/152
qualified-next-hop 47.0005.80ff.f800.0000.0108.0001.1921.6800.4002 preference
20
set routing-options rib iso.0 static iso-route 47.0005.80ff.f800.0000.eee0/152
qualified-next-hop 47.0005.80ff.f800.0000.0108.0001.1921.6800.4002 metric 10

Step-by-Step To configure static routes for CLNS:

Procedure
1. Configure the routes.

[edit routing-options rib iso.0 static]

user@host# set iso-route 47.0005.80ff.f800.0000.ffff.ffff/152 next-hop
47.0005.80ff.f800.0000.0108.0001.1921.6800.4212
user@host# set iso-route 47.0005.80ff.f800.0000.0108.0001.1921.6800.4212/152
next-hop t1-0/2/2.0
user@host# set iso-route 47.0005.80ff.f800.0000.eee0/152 qualified-next-hop
47.0005.80ff.f800.0000.0108.0001.1921.6800.4002 preference 20
user@host# set iso-route 47.0005.80ff.f800.0000.eee0/152 qualified-next-hop
47.0005.80ff.f800.0000.0108.0001.1921.6800.4002 metric 10

2. If you are done configuring the device, commit the configuration.

[edit]
user@host# commit

70 Copyright © 2017, Juniper Networks, Inc.

Chapter 3: Configuring Static Routes for CLNS

Results Confirm your configuration by issuing the show routing-options command. If the output
does not display the intended configuration, repeat the instructions in this example to
correct the configuration.

user@host# show routing-options

rib iso.0 {
static {
iso-route 47.0005.80ff.f800.0000.ffff.ffff/152 next-hop
47.0005.80ff.f800.0000.0108.0001.1921.6800.4212;
iso-route 47.0005.80ff.f800.0000.0108.0001.1921.6800.4212/152 next-hop t1-0/2/2.0;
iso-route 47.0005.80ff.f800.0000.eee0/152 {
qualified-next-hop 47.0005.80ff.f800.0000.0108.0001.1921.6800.4002 {
preference 20;
metric 10;
}
}
}
}

Verification

Checking the Routing Table

Purpose Make sure that the expected routes appear in the routing table.

Action user@host> show route table iso.0

iso.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

47.0005.80ff.f800.0000.0108.0001.1921.6800.4212/152
*[Static/5] 00:00:25
> via t1-0/2/2.0
47.0005.80ff.f800.0000.eee0/84
*[Static/20] 00:04:01, metric 10, metric2 10
> to #75 0.12.0.34.0.56 via fe-0/0/1.0
47.0005.80ff.f800.0000.ffff.ffff/104
*[Static/5] 00:04:01, metric2 0
> via t1-0/2/2.0

Meaning The static routes appear in the routing table.

Related • CLNS Configuration Overview

Documentation
• Understanding Static Routes for CLNS on page 69

Copyright © 2017, Juniper Networks, Inc. 71

Protocol-Independent Routing Properties Feature Guide

72 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 4

Configuring Route Aggregation

• Understanding Route Aggregation on page 73

• Example: Summarizing Static Routes Through Route Aggregation on page 81

Understanding Route Aggregation

The route aggregation methodology helps minimize the number of routing tables in an
IP network by consolidating selected multiple routes into a single route advertisement.
This approach is in contrast to non-aggregation routing, in which every routing table
contains a unique entry for each route. The aggregation methodology does not help
reduce the size of the routing-table on the router that does the aggregation. When you
configure an export policy that only advertises the aggregate but not the contributing
routes anymore, you then have the aggregation effect on the routers that receive updates.

An aggregate route becomes active when it has one or more contributing routes. A
contributing route is an active route that is a more specific match for the aggregate
destination. For example, for the aggregate destination 128.100.0.0/16, routes to
128.100.192.0/19 and 128.100.67.0/24 are contributing routes, but routes to 128.0.0.0./8
and 128.0.0.0/16 are not.

A route can only contribute to a single aggregate route. However, an active aggregate
route can recursively contribute to a less-specific matching aggregate route. For example,
an aggregate route to the destination 128.100.0.0/16 can contribute to an aggregate
route to 128.96.0.0/13.

When an aggregate route becomes active, it is installed in the routing table with the
following information:

• Reject next hop—If a more-specific packet does not match a more-specific route, the
packet is rejected and an ICMP unreachable message is sent to the packet’s originator.

• Metric value as configured with the aggregate statement.

• Preference value that results from the policy filter on the primary contributor, if a filter is
specified.

• AS path as configured in the aggregate statement, if any. Otherwise, the path is

computed by aggregating the paths of all contributing routes.

• Community as configured in the aggregate statement, if any is specified.

Copyright © 2017, Juniper Networks, Inc. 73

Protocol-Independent Routing Properties Feature Guide

NOTE: You can configure only one aggregate route for each destination
prefix.

To configure aggregate routes in the default routing table (inet.0), include the
aggregate statement:

aggregate {
defaults {
... aggregate-options ...
}
route destination-prefix {
policy policy-name;
... aggregate-options ...
}
}

To configure aggregate routes in one of the other routing tables, or to explicitly configure
aggregate routes in the default routing table (inet.0), include the aggregate statement:

rib routing-table-name {
aggregate {
defaults {
... aggregate-options ...
}
route destination-prefix {
policy policy-name;
... aggregate-options ...
}
}
}

NOTE: You cannot configure aggregate routes for the IPv4 multicast routing
table (inet.1) nor the IPv6 multicast routing table (inet6.1).

The aggregate statement consists of two parts:

• defaults—(Optional) Here you specify global aggregate route options. These are treated
as global defaults and apply to all the aggregate routes you configure in the aggregate
statement.

• route—Here you configure individual aggregate routes. In this part of the aggregate
statement, you optionally can configure aggregate route options. These options apply
to the individual destination only and override any options you configured in the defaults
part of the aggregate statement.

When you configure an individual aggregate route in the route part of the aggregate
statement, specify the destination of the route (in route destination-prefix) in one of the
following ways:

74 Copyright © 2017, Juniper Networks, Inc.

Chapter 4: Configuring Route Aggregation

• network/mask-length, where network is the network portion of the IP address and

mask-length is the destination prefix length.

• default if this is the default route to the destination. This is equivalent to specifying an
IP address of 0.0.0.0/0.

After you have configured aggregate routes, you can have a protocol advertise the routes
by configuring a policy that is then exported by a routing protocol.

You can associate a routing policy when configuring an aggregate route’s destination
prefix in the routes part of the aggregate statement. Doing so provides the equivalent of
an import routing policy filter for the destination prefix. That is, each potential contributor
to an aggregate route, along with any aggregate options, is passed through the policy
filter. The policy then can accept or reject the route as a contributor to the aggregate
route and, if the contributor is accepted, the policy can modify the default preferences.

The following algorithm is used to compare two aggregate contributing routes in order
to determine which one is the primary or preferred contributor:

1. Compare the protocol’s preferences of the contributing routes. The lower the
preference, the better the route. This is similar to the comparison that is done while
determining the best route for the routing table.

2. Compare the protocol’s preferences2 of the contributing routes. The lower preference2
value is better. If only one route has preferences2, then this route is preferred.

3. The preference values are the same. Proceed with a numerical comparison of the
prefix values.

a. The primary contributor is the numerically smallest prefix value.

b. If the two prefixes are numerically equal, the primary contributor is the route that
has the smallest prefix length value.

4. At this point, the two routes are the same. The primary contributor does not change.
An additional next hop is available for the existing primary contributor.

A rejected contributor still can contribute to a less specific aggregate route. If you do not
specify a policy filter, all candidate routes contribute to an aggregate route.

To associate a routing policy with an aggregate route, include the policy statement when
configuring the route:

aggregate (defaults | route) {

policy policy-name;
}

In the defaults and route parts of the aggregate statement, you can specify
aggregate-options, which define additional information about aggregate routes that is
included with the route when it is installed in the routing table. All aggregate options are

Copyright © 2017, Juniper Networks, Inc. 75

Protocol-Independent Routing Properties Feature Guide

optional. Aggregate options that you specify in the defaults part of the aggregate
statement are treated as global defaults and apply to all the aggregate routes you
configure in the aggregate statement. Aggregate options that you specify in the route
part of the aggregate statement override any global aggregate options and apply to that
destination only.

To configure aggregate route options, include one or more of them in the defaults or route
part of the aggregate statement:

[edit]
routing-options {
aggregate {
(defaults | route) {
(active | passive);
as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> <aggregator
as-number in-address>;
community [ community-ids ];
discard;
(brief | full);
(metric | metric2 | metric3 | metric4) metric <type type>;
(preference | preference2 | color | color2) preference <type type>;
tag metric type number;
}
}
}

Configuring a Metric Value for Aggregate Routes

You can specify up to four metric values, starting with metric (for the first metric value)
and continuing with metric2, metric3, and metric4 by including one or more of the following
statements:

aggregate (defaults | route) {

(metric | metric2 | metric3 | metric4) metric <type type>;
}

For a list of hierarchy levels at which you can include these statements, see the statement
summary sections for these statements.

In the type option, you can specify the type of route.

Configuring a Preference Value for Aggregate Routes

By default, aggregate routes have a preference value of 130. If the routing table contains
a dynamic route to a destination that has a better (lower) preference value than this,
the dynamic route is chosen as the active route and is installed in the forwarding table.

To modify the default preference value, specify a primary preference value (preference).
You also can specify secondary preference value (preference2); and colors, which are
even finer-grained preference values (color and color2). To do this, include one or more
of the following statements:

aggregate (defaults | route) {

(preference | preference2 | color | color2) preference <type type>;
}

76 Copyright © 2017, Juniper Networks, Inc.

Chapter 4: Configuring Route Aggregation

For a list of hierarchy levels at which you can include these statements, see the statement
summary sections for these statements.
32
The preference value can be a number in the range from 0 through 4,294,967,295 (2 – 1)
with a lower number indicating a more preferred route. For more information about
preference values, see Route Preferences Overview.

In the type option, you can specify the type of route.

Configuring the Next Hop for Aggregate Routes

By default, when aggregate routes are installed in the routing table, the next hop is
configured as a reject route. That is, the packet is rejected and an ICMP unreachable
message is sent to the packet’s originator.

When you configure an individual route in the route part of the aggregate statement, or
when you configure the defaults for aggregate routes, you can specify a discard next hop.
This means that if a more specific packet does not match a more specific route, the
packet is rejected and a reject route for this destination is installed in the routing table,
but ICMP unreachable messages are not sent.

Being able to discard next hops allows you to originate a summary route, which can be
advertised through dynamic routing protocols, and allows you to discard received traffic
that does not match a more specific route than the summary route. To discard next hops,
include the discard option:

discard;

For a list of hierarchy levels at which you can include this statement, see the statement
summary section for this statement.

Associating BGP Communities with Aggregate Routes

By default, no BGP community information is associated with aggregate routes. To
associate community information with the routes, include the community option:

aggregate (defaults | route) {

community [ community-ids ];
}

For a list of hierarchy levels at which you can include this statement, see the statement
summary section for this statement. community-value is the community identifier and
can be a number in the range from 0 through 65,535.

community-ids is one or more community identifiers for either communities or extended

communities.

The format for community identifiers is:

as-number:community-value

as-number is the AS number and can be a value in the range from 1 through 65,534.

You also can specify community-ids for communities as one of the following well-known
community names, which are defined in RFC 1997:

Copyright © 2017, Juniper Networks, Inc. 77

Protocol-Independent Routing Properties Feature Guide

• no-export—Routes containing this community name are not advertised outside a

BGP confederation boundary.

• no-advertise—Routes containing this community name are not advertised to other

BGP peers.

• no-export-subconfed—Routes containing this community name are not advertised to

external BGP peers, including peers in other members’ ASs inside a BGP confederation.

You can explicitly exclude BGP community information with an aggregate route using
the none option. Include none when configuring an individual route in the route portion
of the aggregate statement to override a community option specified in the defaults
portion of the statement.

NOTE: Extended community attributes are not supported at the [edit

routing-options] hierarchy level. You must configure extended communities
at the [edit policy-options] hierarchy level. For information about configuring
extended communities information, see the “Configuring the Extended
Communities Attribute” section in the Routing Policies, Firewall Filters, and
Traffic Policers Feature Guide. For information about configuring 4-byte AS
numbers and extended communities, see Using 4-Byte Autonomous System
Numbers in BGP Networks.

Associating AS Paths with Aggregate Routes

By default, the AS path for aggregate routes is built from the component routes. To
manually specify the AS path and associate AS path information with the routes, include
the as-path option:

aggregate (defaults | route) {

as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> <aggregator
as-number in-address>;
}

For a list of hierarchy levels at which you can include this statement, see the statement
summary section for this statement.

as-path is the AS path to include with the route. It can include a combination of individual
AS path numbers and AS sets. Enclose sets in brackets ( [ ] ). The first AS number in the
path represents the AS immediately adjacent to the local AS. Each subsequent number
represents an AS that is progressively farther from the local AS, heading toward the origin
of the path.

78 Copyright © 2017, Juniper Networks, Inc.

Chapter 4: Configuring Route Aggregation

NOTE: In Junos OS Release 9.1 and later, the numeric AS range is extended
to provide BGP support for 4-byte AS numbers, as defined in RFC 4893, BGP
Support for Four-octet AS Number Space. For the AS number, you can configure
a value from 1 through 4,294,967,295. All releases of Junos OS support 2-byte
AS numbers. The 2-byte AS number range is 1 through 65,535 (this is a subset
of the 4-byte range).

In Junos OS Release 9.2 and later, you can also configure a 4-byte AS number
using the AS-dot notation format of two integer values 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 of 65,546 in plain-number format is
represented as 1.10 in the AS-dot notation format. You can specify a value in
the range from 0.0 through 65535.65535 in AS-dot notation format.

You also can specify the AS path using the BGP origin attribute, which indicates the origin
of the AS path information:

• egp—Path information originated in another AS.

• igp—Path information originated within the local AS.

• incomplete—Path information was learned by some other means.

To attach the BGP ATOMIC_AGGREGATE path attribute to the aggregate route, specify
the atomic-aggregate option. This path attribute indicates that the local system selected
a less specific route rather than a more specific route.

To attach the BGP AGGREGATOR path attribute to the aggregate route, specify the
aggregator option. When using this option, you must specify the last AS number that
formed the aggregate route (encoded as two octets), followed by the IP address of the
BGP system that formed the aggregate route.

NOTE: Starting with Junos OS 13.2R1, a BGP route is hidden when the AS path
of an aggregate route—built from contributing routes— is more than half of
the maximum BGP packet size (4096 bytes). Such AS paths have the
OverflowASPathSize flag set for them. If you would like to leak such a BGP
route, whose AS path length can overflow, we recommend to add the AS
path statically in the default route configuration. For example:

[edit routing-instances instance-name routing options]

user@host# set aggregate route 0.0.0.0/0 as-path path 1267

Including AS Numbers in Aggregate Route Paths

By default, all AS numbers from all contributing paths are included in the aggregate
route’s path. To include only the longest common leading sequences from the contributing
AS paths, include the brief option when configuring the route. If doing this results in AS
numbers being omitted from the aggregate route, the BGP ATOMIC_ATTRIBUTE path
attribute is included with the aggregate route.

Copyright © 2017, Juniper Networks, Inc. 79

Protocol-Independent Routing Properties Feature Guide

aggregate (defaults | route) {

brief;
}

To explicitly have all AS numbers from all contributing paths be included in the aggregate
route’s path, include the full option when configuring routes. Include this option when
configuring an individual route in the route portion of the aggregate statement to override
a retain option specified in the defaults portion of the statement.

aggregate (defaults | route) {

full;
}

For a list of hierarchy levels at which you can include these statements, see the statement
summary sections for these statements.

Configuring a Tag Value for Aggregate Routes

By default, no tag values are associated with aggregate routes. You can specify a tag
value by including the tag option:

aggregate (defaults | route) {

tag metric type number;
}

For a list of hierarchy levels at which you can include this statement, see the statement
summary section for this statement.

Controlling Retention of Inactive Aggregate Routes in the Routing and Forwarding Tables
Static routes are only removed from the routing table if the next hop becomes
unreachable, which happens if there are no contributing routes. To have an aggregate
route remain continually installed in the routing and forwarding tables, include the passive
option when configuring the route:

aggregate (defaults | route) {

passive;
}

Routes that have been configured to remain continually installed in the routing and
forwarding tables are marked with reject next hops when they are inactive.

To explicitly remove aggregate routes when they become inactive, include the active
option when configuring routes. Include this option when configuring an individual route
in the route portion of the aggregate statement to override a passive option specified in
the defaults portion of the statement.

aggregate (defaults | route) {

active;
}

80 Copyright © 2017, Juniper Networks, Inc.

Chapter 4: Configuring Route Aggregation

Release History Table Release Description

13.2R1 Starting with Junos OS 13.2R1, a BGP route is hidden when the AS path of an
aggregate route—built from contributing routes— is more than half of the
maximum BGP packet size (4096 bytes).

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• Understanding Conditionally Generated Routes

• Example: Configuring a Conditional Default Route Policy

Example: Summarizing Static Routes Through Route Aggregation

This example shows how to summarize routes by configuring aggregate routes.

• Requirements on page 81
• Overview on page 81
• Configuration on page 82
• Verification on page 86

Requirements
No special configuration beyond device initialization is required before configuring this
example.

Overview
In this example, Device R1 is connected to customer networks 10.200.1.0/24 and
10.200.2.0/24. For demonstration purposes, these routes are represented in this example
as loopback interfaces on Device R1.

Device R2 has static routes configured to reach Device R1’s customer networks. Device
R2 also has a routing policy configured to advertise all static routes to its neighbors in
autonomous system (AS) 65001.

Device R3 is in AS 65001 and receives the static routes from Device R2. When Device R3
sends information about these routes to Device ISP, the information is summarized as
a single aggregate route. The aggregate route is 10.200.0.0/16.

Device ISP injects a default route into AS 65001, and Device R3 advertises the default
route.

This example shows the configuration for all of the devices and the step-by-step
configuration on Device R3.

Figure 10 on page 82 shows the sample network.

Copyright © 2017, Juniper Networks, Inc. 81

Protocol-Independent Routing Properties Feature Guide

Figure 10: Aggregate Route Advertised to an ISP

10.200.1.0/24
10.200.2.0/24
lo0:172.16.3.3
AS 65001

10.0.0.1/30 10.0.2.2/30
R1 R2 R3
10.0.0.2/30 10.0.2.1/30
10.0.45.2/30
AS 65003 AS 65001
lo0:172.16.2.2

10.0.45.1/30

ISP

g041179
AS 65000

Configuration

Device R1 set interfaces ge-1/2/0 unit 2 description R1->R2

set interfaces ge-1/2/0 unit 2 family inet address 10.0.0.1/30
set interfaces lo0 unit 1 family inet address 10.200.1.1/32
set interfaces lo0 unit 1 family inet address 10.200.2.2/32
set protocols bgp group ext type external
set protocols bgp group ext peer-as 65001
set protocols bgp group ext neighbor 10.0.0.2
set protocols ospf area 0.0.0.0 interface ge-1/2/0.2
set routing-options autonomous-system 65003

Device R2 set interfaces ge-1/2/0 unit 1 description R2->R1

set interfaces ge-1/2/0 unit 1 family inet address 10.0.0.2/30
set interfaces ge-1/2/1 unit 4 description R2->R3
set interfaces ge-1/2/1 unit 4 family inet address 10.0.2.2/30
set interfaces lo0 unit 2 family inet address 172.16.2.2/32
set protocols bgp group int type internal
set protocols bgp group int local-address 172.16.2.2
set protocols bgp group int export send-customer-routes
set protocols bgp group int neighbor 172.16.3.3
set protocols bgp group ext type external
set protocols bgp group ext peer-as 65003
set protocols bgp group ext neighbor 10.0.0.1
set protocols ospf area 0.0.0.0 interface ge-1/2/0.1
set protocols ospf area 0.0.0.0 interface ge-1/2/1.4
set protocols ospf area 0.0.0.0 interface lo0.2 passive
set policy-options policy-statement send-customer-routes from protocol static

82 Copyright © 2017, Juniper Networks, Inc.

Chapter 4: Configuring Route Aggregation

set policy-options policy-statement send-customer-routes then accept

set routing-options static route 10.200.1.0/24 next-hop 10.0.0.1
set routing-options static route 10.200.2.0/24 next-hop 10.0.0.1
set routing-options autonomous-system 65001

Device R3 set interfaces ge-1/2/0 unit 3 description R3->R2

set interfaces ge-1/2/0 unit 3 family inet address 10.0.2.1/30
set interfaces ge-1/2/1 unit 6 description R3->ISP
set interfaces ge-1/2/1 unit 6 family inet address 10.0.45.2/30
set interfaces lo0 unit 3 family inet address 172.16.3.3/32
set protocols bgp group ext type external
set protocols bgp group ext export send-aggregate
set protocols bgp group ext peer-as 65000
set protocols bgp group ext neighbor 10.0.45.1
set protocols bgp group int type internal
set protocols bgp group int local-address 172.16.3.3
set protocols bgp group int neighbor 172.16.2.2
set protocols ospf export send-default
set protocols ospf area 0.0.0.0 interface ge-1/2/0.3
set protocols ospf area 0.0.0.0 interface lo0.3 passive
set policy-options policy-statement send-aggregate term 1 from protocol aggregate
set policy-options policy-statement send-aggregate term 1 then accept
set policy-options policy-statement send-aggregate term suppress-specific-routes from
route-filter 10.200.0.0/16 longer
set policy-options policy-statement send-aggregate term suppress-specific-routes then
reject
set policy-options policy-statement send-default from route-filter 0.0.0.0/0 exact
set policy-options policy-statement send-default then accept
set routing-options aggregate route 10.200.0.0/16
set routing-options autonomous-system 65001

Device ISP set interfaces ge-1/2/0 unit 7 family inet address 10.0.45.1/30
set protocols bgp group ext type external
set protocols bgp group ext export advertise-default
set protocols bgp group ext peer-as 65001
set protocols bgp group ext neighbor 10.0.45.2
set policy-options policy-statement advertise-default term 1 from route-filter 0.0.0.0/0
exact
set policy-options policy-statement advertise-default term 1 then accept
set routing-options static route 0.0.0.0/0 discard
set routing-options autonomous-system 65000

To configure Device R3:

1. Configure the interfaces.

[edit interfaces]
user@R3# set ge-1/2/0 unit 3 description R3->R2
user@R3# set ge-1/2/0 unit 3 family inet address 10.0.2.1/30

Copyright © 2017, Juniper Networks, Inc. 83

Protocol-Independent Routing Properties Feature Guide

user@R3# set ge-1/2/1 unit 6 description R3->ISP

user@R3# set ge-1/2/1 unit 6 family inet address 10.0.45.2/30

user@R3# set lo0 unit 3 family inet address 172.16.3.3/32

2. Configure the AS number.

[edit routing-options]
user@R3# set autonomous-system 65001

3. Configure the BGP session with the ISP device.

[edit protocols bgp group ext]

user@R3# set type external
user@R3# set peer-as 65000
user@R3# set neighbor 10.0.45.1

4. Configure the BGP session with Device R2.

[edit protocols bgp group int]

user@R3# set type internal
user@R3# set local-address 172.16.3.3
user@R3# set neighbor 172.16.2.2

5. Configure OSPF.

[edit protocols ospf area 0.0.0.0]

user@R3# set interface ge-1/2/0.3
user@R3# set interface lo0.3 passive

6. Configure the aggregate route.

[edit routing-options]
user@R3# set aggregate route 10.200.0.0/16

7. Configure the routing policy to advertise the aggregate route.

The first term in this policy advertises the aggregate route. The second term prevents
more specific routes from being advertised.

[edit policy-options policy-statement send-aggregate]

user@R3# set term 1 from protocol aggregate
user@R3# set term 1 then accept
user@R3# set term suppress-specific-routes from route-filter 10.200.0.0/16 longer
user@R3# set term suppress-specific-routes then reject

8. Apply the aggregate route policy to the external BGP session with Device ISP.

[edit protocols bgp group ext]

user@R3# set export send-aggregate

84 Copyright © 2017, Juniper Networks, Inc.

Chapter 4: Configuring Route Aggregation

9. Configure the routing policy to advertise the default route from Device ISP.

[edit policy-options policy-statement send-default]

user@R3# set from route-filter 0.0.0.0/0 exact
user@R3# set then accept

10. Apply the default routing policy to OSPF.

[edit protocols ospf]

user@R3# set export send-default

11. If you are done configuring the device, commit the configuration.

[edit]
user@R3# commit

Results

Confirm your configuration by issuing the show interfaces, show protocols, show
policy-options, and show routing-options commands. If the output does not display the
intended configuration, repeat the instructions in this example to correct the configuration.

user@R3# show interfaces

ge-1/2/0 {
unit 3 {
description R3->R2;
family inet {
address 10.0.2.1/30;
}
}
}
ge-1/2/1 {
unit 6 {
description R3->ISP;
family inet {
address 10.0.45.2/30;
}
}
}
lo0 {
unit 3 {
family inet {
address 172.16.3.3/32;
}
}
}
user@R3# show protocols
bgp {
group ext {
type external;
export send-aggregate;
peer-as 65000;
neighbor 10.0.45.1;

Copyright © 2017, Juniper Networks, Inc. 85

Protocol-Independent Routing Properties Feature Guide

}
group int {
type internal;
local-address 172.16.3.3;
neighbor 172.16.2.2;
}
}
ospf {
export send-default;
area 0.0.0.0 {
interface ge-1/2/0.3;
interface lo0.3 {
passive;
}
}
}
user@R3# show policy-options
policy-statement send-aggregate {
term 1 {
from protocol aggregate;
then accept;
}
term suppress-specific-routes {
from {
route-filter 10.200.0.0/16 longer;
}
then reject;
}
}
policy-statement send-default {
from {
route-filter 0.0.0.0/0 exact;
}
then accept;
}
user@R3# show routing-options
aggregate {
route 10.200.0.0/16;
}
autonomous-system 65001;

Verification
Confirm that the configuration is working properly.

• Verifying That Device R3 Has the Expected Routes on page 86

• Verifying That Device R3 Advertises the Aggregate Route to Device ISP on page 87

Verifying That Device R3 Has the Expected Routes

Purpose Make sure that Device R3 has the specific static routes.

86 Copyright © 2017, Juniper Networks, Inc.

Chapter 4: Configuring Route Aggregation

Action user@R3>show route terse protocol bgp

inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

* 0.0.0.0/0 B 170 100 >10.0.45.1 65000 I
* 10.200.1.0/24 B 170 100 >10.0.2.2 I
* 10.200.2.0/24 B 170 100 >10.0.2.2 I

Meaning The output shows that Device R3 has the specific routes to the 10.200.1.0/24 and
10.200.2.0/24 networks.

Verifying That Device R3 Advertises the Aggregate Route to Device ISP

Purpose Make sure that Device R3 does not send the specific static routes and only sends the
summarized aggregate route.

Action user@R3>show route advertising-protocol bgp 10.0.45.1

inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 10.200.0.0/16 Self I

Meaning The output shows that Device R3 sends only the summarized route to Device ISP.

Related • Understanding Route Aggregation on page 73

Documentation

Copyright © 2017, Juniper Networks, Inc. 87

Protocol-Independent Routing Properties Feature Guide

88 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 5

Configuring RSVP-Signaled
Point-to-Multipoint LSP

• Understanding Point-to-Multipoint LSPs on page 89

• Example: Configuring a Collection of Paths to Create an RSVP-Signaled
Point-to-Multipoint LSP on page 91

Understanding Point-to-Multipoint LSPs

A point-to-multipoint MPLS label-switched path (LSP) is an LDP-signaled or

RSVP-signaled LSP with a single source and multiple destinations. By taking advantage
of the MPLS packet replication capability of the network, point-to-multipoint LSPs avoid
unnecessary packet replication at the inbound (ingress) router. Packet replication takes
place only when packets are forwarded to two or more different destinations requiring
different network paths.

This process is illustrated in Figure 11 on page 90. Device PE1 is configured with a
point-to-multipoint LSP to Routers PE2, PE3, and PE4. When Device PE1 sends a packet
on the point-to-multipoint LSP to Routers P1 and P2, Device P1 replicates the packet and
forwards it to Routers PE2 and PE3. Device P2 sends the packet to Device PE4.

Copyright © 2017, Juniper Networks, Inc. 89

Protocol-Independent Routing Properties Feature Guide

Figure 11: Point-to-Multipoint LSPs

Following are some of the properties of point-to-multipoint LSPs:

• A point-to-multipoint LSP allows you to use MPLS for point-to-multipoint data

distribution. This functionality is similar to that provided by IP multicast.

• You can add and remove branch LSPs from a main point-to-multipoint LSP without
disrupting traffic. The unaffected parts of the point-to-multipoint LSP continue to
function normally.

• You can configure a node to be both a transit and an outbound (egress) router for
different branch LSPs of the same point-to-multipoint LSP.

• You can enable link protection on a point-to-multipoint LSP. Link protection can provide
a bypass LSP for each of the branch LSPs that make up the point-to-multipoint LSP.
If any primary paths fail, traffic can be quickly switched to the bypass.

• You can configure subpaths either statically or dynamically.

• You can enable graceful restart on point-to-multipoint LSPs.

Related • MPLS Traffic Engineering and Signaling Protocols Overview

Documentation
• Point-to-Multipoint LSP Configuration Overview

90 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

Example: Configuring a Collection of Paths to Create an RSVP-Signaled

Point-to-Multipoint LSP

This example shows how to configure a collection of paths to create an RSVP-signaled

point-to-multipoint label-switched path (LSP).

• Requirements on page 91
• Overview on page 91
• Configuration on page 92
• Verification on page 108

Requirements
In this example, no special configuration beyond device initialization is required.

Overview
In this example, multiple routing devices serve as the transit, branch, and leaf nodes of
a single point-to-multipoint LSP. On the provider edge (PE), Device PE1 is the ingress
node. The branches go from PE1 to PE2, PE1 to PE3, and PE1 to PE4. Static unicast routes
on the ingress node (PE1) point to the egress nodes.

This example also demonstrates static routes with a next hop that is a point-to-multipoint
LSP, using the p2mp-lsp-next-hop statement. This is useful when implementing
filter-based forwarding.

NOTE: Another option is to use the lsp-next-hop statement to configure a

regular point-to-point LSP to be the next hop. Though not shown in this
example, you can optionally assign an independent preference and metric
to the next hop.

Topology Diagram

Figure 12 on page 92 shows the topology used in this example.

Copyright © 2017, Juniper Networks, Inc. 91

Protocol-Independent Routing Properties Feature Guide

Figure 12: RSVP-Signaled Point-to-Multipoint LSP

P2 PE2 CE2

CE1 PE1 P3 PE3 CE3

P4 PE4 CE4

g041174
Configuration

Device PE1 set interfaces ge-2/0/2 unit 0 description PE1-to-CE1

set interfaces ge-2/0/2 unit 0 family inet address 10.0.244.10/30
set interfaces fe-2/0/10 unit 1 description PE1-to-P2
set interfaces fe-2/0/10 unit 1 family inet address 2.2.2.1/24
set interfaces fe-2/0/10 unit 1 family mpls
set interfaces fe-2/0/9 unit 8 description PE1-to-P3
set interfaces fe-2/0/9 unit 8 family inet address 6.6.6.1/24
set interfaces fe-2/0/9 unit 8 family mpls
set interfaces fe-2/0/8 unit 9 description PE1-to-P4
set interfaces fe-2/0/8 unit 9 family inet address 3.3.3.1/24
set interfaces fe-2/0/8 unit 9 family mpls
set interfaces lo0 unit 1 family inet address 100.10.10.10/32
set protocols rsvp interface fe-2/0/10.1
set protocols rsvp interface fe-2/0/9.8
set protocols rsvp interface fe-2/0/8.9
set protocols rsvp interface lo0.1
set protocols mpls traffic-engineering bgp-igp
set protocols mpls label-switched-path PE1-PE2 to 100.50.50.50
set protocols mpls label-switched-path PE1-PE2 link-protection
set protocols mpls label-switched-path PE1-PE2 p2mp p2mp1
set protocols mpls label-switched-path PE1-PE3 to 100.70.70.70
set protocols mpls label-switched-path PE1-PE3 link-protection
set protocols mpls label-switched-path PE1-PE3 p2mp p2mp1
set protocols mpls label-switched-path PE1-PE4 to 100.40.40.40

92 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

set protocols mpls label-switched-path PE1-PE4 link-protection

set protocols mpls label-switched-path PE1-PE4 p2mp p2mp1
set protocols mpls interface fe-2/0/10.1
set protocols mpls interface fe-2/0/9.8
set protocols mpls interface fe-2/0/8.9
set protocols mpls interface lo0.1
set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface ge-2/0/2.0
set protocols ospf area 0.0.0.0 interface fe-2/0/10.1
set protocols ospf area 0.0.0.0 interface fe-2/0/9.8
set protocols ospf area 0.0.0.0 interface fe-2/0/8.9
set protocols ospf area 0.0.0.0 interface lo0.1
set routing-options static route 5.5.5.0/24 p2mp-lsp-next-hop p2mp1
set routing-options static route 7.7.7.0/24 p2mp-lsp-next-hop p2mp1
set routing-options static route 4.4.4.0/24 p2mp-lsp-next-hop p2mp1
set routing-options router-id 100.10.10.10

Device CE1 set interfaces ge-1/3/2 unit 0 family inet address 10.0.244.9/30
set interfaces ge-1/3/2 unit 0 description CE1-to-PE1
set routing-options static route 10.0.104.8/30 next-hop 10.0.244.10
set routing-options static route 10.0.134.8/30 next-hop 10.0.244.10
set routing-options static route 10.0.224.8/30 next-hop 10.0.244.10

Device CE2 set interfaces ge-1/3/3 unit 0 family inet address 10.0.224.9/30
set interfaces ge-1/3/3 unit 0 description CE2-to-PE2
set routing-options static route 10.0.244.8/30 next-hop 10.0.224.10

Device CE3 set interfaces ge-2/0/1 unit 0 family inet address 10.0.134.9/30
set interfaces ge-2/0/1 unit 0 description CE3-to-PE3
set routing-options static route 10.0.244.8/30 next-hop 10.0.134.10

Device CE4 set interfaces ge-3/1/3 unit 0 family inet address 10.0.104.10/30
set interfaces ge-3/1/3 unit 0 description CE4-to-PE4
set routing-options static route 10.0.244.8/30 next-hop 10.0.104.9

Configuring the Ingress Label-Switched Router (LSR) (Device PE1)

Step-by-Step To configure Device PE1:

Procedure
1. Configure the interfaces, interface encapsulation, and protocol families.

[edit interfaces]
user@PE1# set ge-2/0/2 unit 0 description PE1-to-CE1
user@PE1# set ge-2/0/2 unit 0 family inet address 10.0.244.10/30
user@PE1# set fe-2/0/10 unit 1 description PE1-to-P2
user@PE1# set fe-2/0/10 unit 1 family inet address 2.2.2.1/24
user@PE1# set fe-2/0/10 unit 1 family mpls
user@PE1# set fe-2/0/9 unit 8 description PE1-to-P3
user@PE1# set fe-2/0/9 unit 8 family inet address 6.6.6.1/24
user@PE1# set fe-2/0/9 unit 8 family mpls
user@PE1# set fe-2/0/8 unit 9 description PE1-to-P4
user@PE1# set fe-2/0/8 unit 9 family inet address 3.3.3.1/24
user@PE1# set fe-2/0/8 unit 9 family mpls

Copyright © 2017, Juniper Networks, Inc. 93

Protocol-Independent Routing Properties Feature Guide

user@PE1# set lo0 unit 1 family inet address 100.10.10.10/32

2. Enable RSVP, MPLS, and OSPF on the interfaces.

[edit protocols]
user@PE1# set rsvp interface fe-2/0/10.1
user@PE1# set rsvp interface fe-2/0/9.8
user@PE1# set rsvp interface fe-2/0/8.9
user@PE1# set rsvp interface lo0.1
user@PE1# set mpls interface fe-2/0/10.1
user@PE1# set mpls interface fe-2/0/9.8
user@PE1# set mpls interface fe-2/0/8.9
user@PE1# set mpls interface lo0.1
user@PE1# set ospf area 0.0.0.0 interface ge-2/0/2.0
user@PE1# set ospf area 0.0.0.0 interface fe-2/0/10.1
user@PE1# set ospf area 0.0.0.0 interface fe-2/0/9.8
user@PE1# set ospf area 0.0.0.0 interface fe-2/0/8.9
user@PE1# set ospf area 0.0.0.0 interface lo0.1

3. Configure the MPLS point-to-multipoint LSPs.

[edit protocols]
user@PE1# set mpls label-switched-path PE1-PE2 to 100.50.50.50
user@PE1# set mpls label-switched-path PE1-PE2 p2mp p2mp1
user@PE1# set mpls label-switched-path PE1-PE3 to 100.70.70.70
user@PE1# set mpls label-switched-path PE1-PE3 p2mp p2mp1
user@PE1# set mpls label-switched-path PE1-PE4 to 100.40.40.40
user@PE1# set mpls label-switched-path PE1-PE4 p2mp p2mp1

4. (Optional) Enable link protection on the LSPs.

Link protection helps to ensure that traffic sent over a specific interface to a
neighboring router can continue to reach the router if that interface fails.

[edit protocols]
user@PE1# set mpls label-switched-path PE1-PE2 link-protection
user@PE1# set mpls label-switched-path PE1-PE3 link-protection
user@PE1# set mpls label-switched-path PE1-PE4 link-protection

5. Enable MPLS to perform traffic engineering for OSPF.

[edit protocols]
user@PE1# set mpls traffic-engineering bgp-igp

This causes the ingress routes to be installed in the inet.0 routing table. By default,
MPLS performs traffic engineering for BGP only. You need to enable MPLS traffic
engineering on the ingress LSR only.

6. Enable traffic engineering for OSPF.

[edit protocols]
user@PE1# set ospf traffic-engineering

94 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

This causes the shortest-path first (SPF) algorithm to take into account the LSPs
configured under MPLS.

7. Configure the router ID.

[edit routing-options]
user@PE1# set router-id 100.10.10.10

8. Configure static IP unicast routes with the point-to-multipoint LSP name as the
next hop for each route.

[edit routing-options]
user@PE1# set static route 5.5.5.0/24p2mp-lsp-next-hop p2mp1
user@PE1# set static route 7.7.7.0/24 p2mp-lsp-next-hop p2mp1
user@PE1# set static route 4.4.4.0/24 p2mp-lsp-next-hop p2mp1

9. If you are done configuring the device, commit the configuration.

[edit]
user@PE1# commit

Configuring the Transit and Egress LSRs (Devices P2, P3, P4, PE2, PE3, and PE4)

Step-by-Step To configure the transit and egress LSRs:

Procedure
1. Configure the interfaces, interface encapsulation, and protocol families.

[edit]
user@P2# set interfaces fe-2/0/10 unit 2 description P2-to-PE1
user@P2# set interfaces fe-2/0/10 unit 2 family inet address 2.2.2.2/24
user@P2# set interfaces fe-2/0/10 unit 2 family mpls
user@P2# set interfaces fe-2/0/9 unit 10 description P2-to-PE2
user@P2# set interfaces fe-2/0/9 unit 10 family inet address 5.5.5.1/24
user@P2# set interfaces fe-2/0/9 unit 10 family mpls
user@P2# set interfaces lo0 unit 2 family inet address 100.20.20.20/32

user@PE2# set interfaces ge-2/0/3 unit 0 description PE2-to-CE2

user@PE2# set interfaces ge-2/0/3 unit 0 family inet address 10.0.224.10/30
user@PE2# set interfaces fe-2/0/10 unit 5 description PE2-to-P2
user@PE2# set interfaces fe-2/0/10 unit 5 family inet address 5.5.5.2/24
user@PE2# set interfaces fe-2/0/10 unit 5 family mpls
user@PE2# set interfaces lo0 unit 5 family inet address 100.50.50.50/32

user@P3# set interfaces fe-2/0/10 unit 6 description P3-to-PE1

user@P3# set interfaces fe-2/0/10 unit 6 family inet address 6.6.6.2/24
user@P3# set interfaces fe-2/0/10 unit 6 family mpls
user@P3# set interfaces fe-2/0/9 unit 11 description P3-to-PE3
user@P3# set interfaces fe-2/0/9 unit 11 family inet address 7.7.7.1/24
user@P3# set interfaces fe-2/0/9 unit 11 family mpls
user@P3# set interfaces lo0 unit 6 family inet address 100.60.60.60/32

user@PE3# set interfaces ge-2/0/1 unit 0 description PE3-to-CE3

Copyright © 2017, Juniper Networks, Inc. 95

Protocol-Independent Routing Properties Feature Guide

user@PE3# set interfaces ge-2/0/1 unit 0 family inet address 10.0.134.10/30

user@PE3# set interfaces fe-2/0/10 unit 7 description PE3-to-P3
user@PE3# set interfaces fe-2/0/10 unit 7 family inet address 7.7.7.2/24
user@PE3# set interfaces fe-2/0/10 unit 7 family mpls
user@PE3# set interfaces lo0 unit 7 family inet address 100.70.70.70/32

user@P4# set interfaces fe-2/0/10 unit 3 description P4-to-PE1

user@P4# set interfaces fe-2/0/10 unit 3 family inet address 3.3.3.2/24
user@P4# set interfaces fe-2/0/10 unit 3 family mpls
user@P4# set interfaces fe-2/0/9 unit 12 description P4-to-PE4
user@P4# set interfaces fe-2/0/9 unit 12 family inet address 4.4.4.1/24
user@P4# set interfaces fe-2/0/9 unit 12 family mpls
user@P4# set interfaces lo0 unit 3 family inet address 100.30.30.30/32

user@PE4# set interfaces ge-2/0/0 unit 0 description PE4-to-CE4

user@PE4# set interfaces ge-2/0/0 unit 0 family inet address 10.0.104.9/30
user@PE4# set interfaces fe-2/0/10 unit 4 description PE4-to-P4
user@PE4# set interfaces fe-2/0/10 unit 4 family inet address 4.4.4.2/24
user@PE4# set interfaces fe-2/0/10 unit 4 family mpls
user@PE4# set interfaces lo0 unit 4 family inet address 100.40.40.40/32

2. Enable RSVP, MPLS, and OSPF on the interfaces.

[edit]
user@P2# set protocols rsvp interface fe-2/0/10.2
user@P2# set protocols rsvp interface fe-2/0/9.10
user@P2# set protocols rsvp interface lo0.2
user@P2# set protocols mpls interface fe-2/0/10.2
user@P2# set protocols mpls interface fe-2/0/9.10
user@P2# set protocols mpls interface lo0.2
user@P2# set protocols ospf area 0.0.0.0 interface fe-2/0/10.2
user@P2# set protocols ospf area 0.0.0.0 interface fe-2/0/9.10
user@P2# set protocols ospf area 0.0.0.0 interface lo0.2

user@PE2# set protocols rsvp interface fe-2/0/10.5

user@PE2# set protocols rsvp interface lo0.5
user@PE2# set protocols mpls interface fe-2/0/10.5
user@PE2# set protocols mpls interface lo0.5
user@PE2# set protocols ospf area 0.0.0.0 interface ge-2/0/3.0
user@PE2# set protocols ospf area 0.0.0.0 interface fe-2/0/10.5
user@PE2# set protocols ospf area 0.0.0.0 interface lo0.5

user@P3# set protocols rsvp interface fe-2/0/10.6

user@P3# set protocols rsvp interface fe-2/0/9.11
user@P3# set protocols rsvp interface lo0.6
user@P3# set protocols mpls interface fe-2/0/10.6
user@P3# set protocols mpls interface fe-2/0/9.11
user@P3# set protocols mpls interface lo0.6
user@P3# set protocols ospf area 0.0.0.0 interface fe-2/0/10.6
user@P3# set protocols ospf area 0.0.0.0 interface fe-2/0/9.11
user@P3# set protocols ospf area 0.0.0.0 interface lo0.6

user@PE3# set protocols rsvp interface fe-2/0/10.7

96 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

user@PE3# set protocols rsvp interface lo0.7

user@PE3# set protocols mpls interface fe-2/0/10.7
user@PE3# set protocols mpls interface lo0.7
user@PE3# set protocols ospf area 0.0.0.0 interface ge-2/0/1.0
user@PE3# set protocols ospf area 0.0.0.0 interface fe-2/0/10.7
user@PE3# set protocols ospf area 0.0.0.0 interface lo0.7

user@P4# set protocols rsvp interface fe-2/0/10.3

user@P4# set protocols rsvp interface fe-2/0/9.12
user@P4# set protocols rsvp interface lo0.3
user@P4# set protocols mpls interface fe-2/0/10.3
user@P4# set protocols mpls interface fe-2/0/9.12
user@P4# set protocols mpls interface lo0.3
user@P4# set protocols ospf area 0.0.0.0 interface fe-2/0/10.3
user@P4# set protocols ospf area 0.0.0.0 interface fe-2/0/9.12
user@P4# set protocols ospf area 0.0.0.0 interface lo0.3

user@PE4# set protocols rsvp interface fe-2/0/10.4

user@PE4# set protocols rsvp interface lo0.4
user@PE4# set protocols mpls interface fe-2/0/10.4
user@PE4# set protocols mpls interface lo0.4
user@PE4# set protocols ospf area 0.0.0.0 interface ge-2/0/0.0
user@PE4# set protocols ospf area 0.0.0.0 interface fe-2/0/10.4
user@PE4# set protocols ospf area 0.0.0.0 interface lo0.4

3. Enable traffic engineering for OSPF.

[edit]
user@P2# set protocols ospf traffic-engineering

user@P3# set protocols ospf traffic-engineering

user@P4# set protocols ospf traffic-engineering

user@PE2# set protocols ospf traffic-engineering

user@PE3# set protocols ospf traffic-engineering

user@PE4# set protocols ospf traffic-engineering

This causes the shortest-path first (SPF) algorithm to take into account the LSPs
configured under MPLS.

4. Configure the router IDs.

[edit]
user@P2# set routing-options router-id 100.20.20.20

user@P3# set routing-options router-id 100.60.60.60

user@P4# set routing-options router-id 100.30.30.30

Copyright © 2017, Juniper Networks, Inc. 97

Protocol-Independent Routing Properties Feature Guide

user@PE2# set routing-options router-id 100.50.50.50

user@PE3# set routing-options router-id 100.70.70.70

user@PE4# set routing-options router-id 100.40.40.40

5. If you are done configuring the devices, commit the configuration.

[edit]
user@host# commit

Results From configuration mode, confirm your configuration by entering the show interfaces,
show protocols, and show routing-options commands. If the output does not display the
intended configuration, repeat the instructions in this example to correct the configuration.

Device PE1 user@PE1# show interfaces

ge-2/0/2 {
unit 0 {
description R1-to-CE1;
family inet {
address 10.0.244.10/30;
}
}
}
fe-2/0/10 {
unit 1 {
description PE1-to-P2;
family inet {
address 2.2.2.1/24;
}
family mpls;
}
}
fe-2/0/9 {
unit 8 {
description PE1-to-P2;
family inet {
address 6.6.6.1/24;
}
family mpls;
}
}
fe-2/0/8 {
unit 9 {
description PE1-to-P3;
family inet {
address 3.3.3.1/24;
}
family mpls;
}
}
lo0 {

98 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

unit 1 {
family inet {
address 100.10.10.10/32;
}
}
}

user@PE1# show protocols

rsvp {
interface fe-2/0/10.1;
interface fe-2/0/9.8;
interface fe-2/0/8.9;
interface lo0.1;
}
mpls {
traffic-engineering bgp-igp;
label-switched-path PE1-to-PE2 {
to 100.50.50.50;
link-protection;
p2mp p2mp1;
}
label-switched-path PE1-to-PE3 {
to 100.70.70.70;
link-protection;
p2mp p2mp1;
}
label-switched-path PE1-to-PE4 {
to 100.40.40.40;
link-protection;
p2mp p2mp1;
}
interface fe-2/0/10.1;
interface fe-2/0/9.8;
interface fe-2/0/8.9;
interface lo0.1;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-2/0/2.0;
interface fe-2/0/10.1;
interface fe-2/0/9.8;
interface fe-2/0/8.9;
interface lo0.1;
}
}

user@PE1# show routing-options

static {
route 5.5.5.0/24 {
p2mp-lsp-next-hop p2mp1;
}
route 7.7.7.0/24 {
p2mp-lsp-next-hop p2mp1;
}
route 4.4.4.0/24 {

Copyright © 2017, Juniper Networks, Inc. 99

Protocol-Independent Routing Properties Feature Guide

p2mp-lsp-next-hop p2mp1;
}
}
router-id 100.10.10.10;

Device P2 user@P2# show interfaces

fe-2/0/10 {
unit 2 {
description P2-to-PE1;
family inet {
address 2.2.2.2/24;
}
family mpls;
}
fe-2/0/9 {
unit 10 {
description P2-to-PE2;
family inet {
address 5.5.5.1/24;
}
family mpls;
}
}
lo0 {
unit 2 {
family inet {
address 100.20.20.20/32;
}
}
}

user@P2# show protocols

rsvp {
interface fe-2/0/10.2;
interface fe-2/0/9.10;
interface lo0.2;
}
mpls {
interface fe-2/0/10.2;
interface fe-2/0/9.10;
interface lo0.2;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface fe-2/0/10.2;
interface fe-2/0/9.10;
interface lo0.2;
}
}

user@P2# show routing-options

router-id 100.20.20.20;

Device P3 user@P3# show interfaces

fe-2/0/10 {

100 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

unit 6 {
description P3-to-PE1;
family inet {
address 6.6.6.2/24;
}
family mpls;
}
}
fe-2/0/9 {
unit 11 {
description P3-to-PE3;
family inet {
address 7.7.7.1/24;
}
family mpls;
}
}
lo0 {
unit 6 {
family inet {
address 100.60.60.60/32;
}
}
}

user@P3# show protocols

rsvp {
interface fe-2/0/10.6;
interface fe-2/0/9.11;
interface lo0.6;
}
mpls {
interface fe-2/0/10.6;
interface fe-2/0/9.11;
interface lo0.6;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface fe-2/0/10.6;
interface fe-2/0/9.11;
interface lo0.6;
}
}

user@P2# show routing-options

router-id 100.60.60.60;

Device P4 user@P4# show interfaces

fe-2/0/10 {
unit 3 {
description P4-to-PE1;
family inet {
address 3.3.3.2/24;
}
family mpls;

Copyright © 2017, Juniper Networks, Inc. 101

Protocol-Independent Routing Properties Feature Guide

}
}
fe-2/0/9 {
unit 12 {
description P4-to-PE4;
family inet {
address 4.4.4.1/24;
}
family mpls;
}
}
lo0 {
unit 3 {
family inet {
address 100.30.30.30/32;
}
}
}

user@P4# show protocols

rsvp {
interface fe-2/0/10.3;
interface fe-2/0/9.12;
interface lo0.3;
}
mpls {
interface fe-2/0/10.3;
interface fe-2/0/9.12;
interface lo0.3;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface fe-2/0/10.3;
interface fe-2/0/9.12;
interface lo0.3;
}
}

user@P3# show routing-options

router-id 100.30.30.30;

Device PE2 user@PE2# show interfaces

ge-2/0/3 {
unit 0 {
description PE2-to-CE2;
family inet {
address 10.0.224.10/30;
}
}
}
fe-2/0/10 {
unit 5 {
description PE2-to-P2;
family inet {
address 5.5.5.2/24;

102 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

}
family mpls;
}
}
lo0 {
unit 5 {
family inet {
address 100.50.50.50/32;
}
}
}
}

user@PE2# show protocols

rsvp {
interface fe-2/0/10.5;
interface lo0.5;
}
mpls {
interface fe-2/0/10.5;
interface lo0.5;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-2/0/3.0;
interface fe-2/0/10.5;
interface lo0.5;
}
}

user@PE2# show routing-options

router-id 100.50.50.50;

Device PE3 user@PE3# show interfaces

ge-2/0/1 {
unit 0 {
description PE3-to-CE3;
family inet {
address 10.0.134.10/30;
}
}
}
fe-2/0/10 {
unit 7 {
description PE3-to-P3;
family inet {
address 7.7.7.2/24;
}
family mpls;
}
}
lo0 {
unit 7 {
family inet {
address 100.70.70.70/32;

Copyright © 2017, Juniper Networks, Inc. 103

Protocol-Independent Routing Properties Feature Guide

}
}
}
}

user@PE3# show protocols

rsvp {
interface fe-2/0/10.7;
interface lo0.7;
}
mpls {
interface fe-2/0/10.7;
interface lo0.7;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-2/0/1.0;
interface fe-2/0/10.7;
interface lo0.7;
}
}

user@PE3# show routing-options

router-id 100.70.70.70;

Device PE4 user@PE4# show interfaces

ge-2/0/0 {
unit 0 {
description PE4-to-CE4;
family inet {
address 10.0.104.9/30;
}
}
}
fe-2/0/10 {
unit 4 {
description PE4-to-P4;
family inet {
address 4.4.4.2/24;
}
family mpls;
}
}
lo0 {
unit 4 {
family inet {
address 100.40.40.40/32;
}
}
}
}

user@PE4# show protocols

rsvp {
interface fe-2/0/10.4;

104 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

interface lo0.4;
}
mpls {
interface fe-2/0/10.4;
interface lo0.4;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface ge-2/0/0.0;
interface fe-2/0/10.4;
interface lo0.4;
}
}

user@PE4# show routing-options

router-id 100.40.40.40;

Configuring Device CE1

Step-by-Step To configure Device CE1:

Procedure
1. Configure an interface to Device PE1.

[edit interfaces]
user@CE1# set ge-1/3/2 unit 0 family inet address 10.0.244.9/30
user@CE1# set ge-1/3/2 unit 0 description CE1-to-PE1

2. Configure static routes from Device CE1 to the three other customer networks, with
Device PE1 as the next hop.

[edit routing-options]
user@CE1# set static route 10.0.104.8/30 next-hop 10.0.244.10
user@CE1# set static route 10.0.134.8/30 next-hop 10.0.244.10
user@CE1# set static route 10.0.224.8/30 next-hop 10.0.244.10

3. If you are done configuring the device, commit the configuration.

[edit]
user@CE1# commit

Results From configuration mode, confirm your configuration by entering the show interfaces and
show routing-options commands. If the output does not display the intended configuration,
repeat the instructions in this example to correct the configuration.

user@CE1# show interfaces

ge-1/3/2 {
unit 0 {
family inet {
address 10.0.244.9/30;
description CE1-to-PE1;
}
}

Copyright © 2017, Juniper Networks, Inc. 105

Protocol-Independent Routing Properties Feature Guide

user@CE1# show routing-options

static {
route 10.0.104.8/30 next-hop 10.0.244.10;
route 10.0.134.8/30 next-hop 10.0.244.10;
route 10.0.224.8/30 next-hop 10.0.244.10;
}

Configuring Device CE2

Step-by-Step To configure Device CE2:

Procedure
1. Configure an interface to Device PE2.

[edit interfaces]
user@CE2# set ge-1/3/3 unit 0 family inet address 10.0.224.9/30
user@CE2# set ge-1/3/3 unit 0 description CE2-to-PE2

2. Configure a static route from Device CE2 to CE1, with Device PE2 as the next hop.

[edit routing-options]
user@CE2# set static route 10.0.244.8/30 next-hop 10.0.224.10

3. If you are done configuring the device, commit the configuration.

[edit]
user@CE2# commit

user@CE2# show interfaces

ge-1/3/3 {
unit 0 {
family inet {
address 10.0.224.9/30;
description CE2-to-PE2;
}
}
}

user@CE2# show routing-options

static {
route 10.0.244.8/30 next-hop 10.0.224.10;
}

106 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

Configuring Device CE3

Step-by-Step To configure Device CE3:

Procedure
1. Configure an interface to Device PE3.

[edit interfaces]
user@CE3# set ge-2/0/1 unit 0 family inet address 10.0.134.9/30
user@CE3# set ge-2/0/1 unit 0 description CE3-to-PE3

2. Configure a static route from Device CE3 to CE1, with Device PE3 as the next hop.

[edit routing-options]
user@CE3# set static route 10.0.244.8/30 next-hop 10.0.134.10

3. If you are done configuring the device, commit the configuration.

[edit]
user@CE3# commit

user@CE3# show interfaces

ge-2/0/1 {
unit 0 {
family inet {
address 10.0.134.9/30;
description CE3-to-PE3;
}
}
}

user@CE3# show routing-options

static {
route 10.0.244.8/30 next-hop 10.0.134.10;
}

Configuring Device CE4

Step-by-Step To configure Device CE4:

Procedure
1. Configure an interface to Device PE4.

[edit interfaces]
user@CE4# set ge-3/1/3 unit 0 family inet address 10.0.104.10/30
user@CE4# set ge-3/1/3 unit 0 description CE4-to-PE4

2. Configure a static route from Device CE4 to CE1, with Device PE4 as the next hop.

[edit routing-options]

Copyright © 2017, Juniper Networks, Inc. 107

Protocol-Independent Routing Properties Feature Guide

user@CE4# set static route 10.0.244.8/30 next-hop 10.0.104.9

3. If you are done configuring the device, commit the configuration.

[edit]
user@CE4# commit

user@CE4# show interfaces

ge-3/1/3 {
unit 0 {
family inet {
address 10.0.104.10/30;
description CE4-to-PE4;
}
}
}

user@CE4# show routing-options

static {
route 10.0.244.8/30 next-hop 10.0.104.9;
}

Verification
Confirm that the configuration is working properly.

• Verifying Connectivity on page 108

• Verifying the State of the Point-to-Multipoint LSP on page 109
• Checking the Forwarding Table on page 110

Verifying Connectivity

Purpose Make sure that the devices can ping each other.

108 Copyright © 2017, Juniper Networks, Inc.

Chapter 5: Configuring RSVP-Signaled Point-to-Multipoint LSP

Action Run the ping command from CE1 to the interface on CE2 connecting to PE2.

user@CE1> ping 10.0.224.9

PING 10.0.224.9 (10.0.224.9): 56 data bytes
64 bytes from 10.0.224.9: icmp_seq=0 ttl=61 time=1.387 ms
64 bytes from 10.0.224.9: icmp_seq=1 ttl=61 time=1.394 ms
64 bytes from 10.0.224.9: icmp_seq=2 ttl=61 time=1.506 ms
^C
--- 10.0.224.9 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.387/1.429/1.506/0.055 ms

Run the ping command from CE1 to the interface on CE3 connecting to PE3.

user@CE1> ping 10.0.134.9

PING 10.0.134.9 (10.0.134.9): 56 data bytes
64 bytes from 10.0.134.9: icmp_seq=0 ttl=61 time=1.068 ms
64 bytes from 10.0.134.9: icmp_seq=1 ttl=61 time=1.062 ms
64 bytes from 10.0.134.9: icmp_seq=2 ttl=61 time=1.053 ms
^C
--- 10.0.134.9 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.053/1.061/1.068/0.006 ms

Run the ping command from CE1 to the interface on CE4 connecting to PE4.

user@CE1> ping 10.0.104.10

PING 10.0.104.10 (10.0.104.10): 56 data bytes
64 bytes from 10.0.104.10: icmp_seq=0 ttl=61 time=1.079 ms
64 bytes from 10.0.104.10: icmp_seq=1 ttl=61 time=1.048 ms
64 bytes from 10.0.104.10: icmp_seq=2 ttl=61 time=1.070 ms
^C
--- 10.0.104.10 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.048/1.066/1.079/0.013 ms

Verifying the State of the Point-to-Multipoint LSP

Purpose Make sure that the ingress, transit, and egress LSRs are in the Up state.

Copyright © 2017, Juniper Networks, Inc. 109

Protocol-Independent Routing Properties Feature Guide

Action Run the show mpls lsp p2mp command on all of the LSRs. Only the ingress LSR is shown
here.

user@PE1> show mpls lsp p2mp

Ingress LSP: 1 sessions
P2MP name: p2mp1, P2MP branch count: 3
To From State Rt P ActivePath LSPname
100.40.40.40 100.10.10.10 Up 0 * PE1-PE4
100.70.70.70 100.10.10.10 Up 0 * PE1-PE3
100.50.50.50 100.10.10.10 Up 0 * PE1-PE2
Total 3 displayed, Up 3, Down 0
...

Checking the Forwarding Table

Purpose Make sure that the routes are set up as expected by running the show route
forwarding-table command. Only the routes to the remote customer networks are shown
here.

Action user@PE1> show route forwarding-table

Routing table: default.inet
Internet:
Destination Type RtRef Next hop Type Index NhRef Netif
...
10.0.104.8/30 user 0 3.3.3.2 ucst 1006 6 fe-2/0/8.9
10.0.134.8/30 user 0 6.6.6.2 ucst 1010 6 fe-2/0/9.8
10.0.224.8/30 user 0 2.2.2.2 ucst 1008 6 fe-2/0/10.1
...

Related • MPLS Applications Feature Guide

Documentation

110 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 6

Configuring Bidirectional Forwarding

Detection for Static Routes

• Understanding BFD for Static Routes for Faster Network Failure Detection on page 111
• Example: Configuring BFD for Static Routes for Faster Network Failure
Detection on page 116
• Understanding BFD Authentication for Static Route Security on page 122
• Example: Configuring BFD Authentication for Securing Static Routes on page 124
• Example: Enabling BFD on Qualified Next Hops in Static Routes for Route
Selection on page 130

Understanding BFD for Static Routes for Faster Network Failure Detection

The Bidirectional Forwarding Detection (BFD) protocol is a simple hello mechanism that
detects failures in a network. BFD works with a wide variety of network environments
and topologies. A pair of routing devices exchanges BFD packets. Hello packets are sent
at a specified, regular interval. A neighbor failure is detected when the routing device
stops receiving a reply after a specified interval. The BFD failure detection timers have
shorter time limits than the static route failure detection mechanisms, so they provide
faster detection.

The BFD failure detection timers can be adjusted to be faster or slower. The lower the
BFD failure detection timer value, the faster the failure detection and vice versa. For
example, the timers can adapt to a higher value if the adjacency fails (that is, the timer
detects failures more slowly). Or a neighbor can negotiate a higher value for a timer than
the configured value. The timers adapt to a higher value when a BFD session flap occurs
more than three times in a span of 15 seconds. A back-off algorithm increases the receive
(Rx) interval by two if the local BFD instance is the reason for the session flap. The
transmission (Tx) interval is increased by two if the remote BFD instance is the reason
for the session flap. You can use the clear bfd adaptation 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.

By default, BFD is supported on single-hop static routes.

To enable failure detection, include the bfd-liveness-detection statement in the static

route configuration.

Copyright © 2017, Juniper Networks, Inc. 111

Protocol-Independent Routing Properties Feature Guide

NOTE: Starting with Junos OS Release 15.1X49-D70 and Junos OS Release

17.3R1, the bfd-liveness-detection command includes the description field.
The description is an attribute under the bfd-liveness-detection object and
it is supported only on SRX Series devices. This field is applicable only for the
static routes.

In Junos OS Release 9.1 and later, the BFD protocol is supported for IPv6 static routes.
Global unicast and link-local IPv6 addresses are supported for static routes. The BFD
protocol is not supported on multicast or anycast IPv6 addresses. For IPv6, the BFD
protocol supports only static routes and only in Junos OS Release 9.3 and later. IPv6 for
BFD is also supported for the eBGP protocol.

NOTE: Inline BFD is supported on PTX5000 routers with third-generation

FPCs starting in Junos OS Release 15.1F3 and 16.1R2. Inline BFD is supported
on PTX3000 routers with third-generation FPCs starting in Junos OS
Release 15.1F6 and 16.1R2.

There are three types of BFD sessions based on the source from which BFD packets are
sent to the neighbors. Different types of BFD sessions and their descriptions are:

Type of BFD session Description

Non-distributed BFD BFD sessions running completely on the Routing

Engine.

Distributed BFD BFD sessions running completely on the Packet

Forwarding Engine.

Inline BFD BFD sessions running on the FPC hardware.

NOTE: Starting in Junos OS Release 13.3, inline BFD is supported only on

static MX Series routers with MPCs/MICs that have configured
enhanced-ip.

NOTE: Starting in Junos OS Release 16.1R1, the inline BFD sessions are
supported on integrated routing and bridging (IRB) interfaces.

To configure the BFD protocol for IPv6 static routes, include the bfd-liveness-detection
statement at the [edit routing-options rib inet6.0 static route destination-prefix] hierarchy
level.

In Junos OS Release 8.5 and later, you can configure a hold-down interval to specify how
long the BFD session must remain up before a state change notification is sent.

To specify the hold-down interval, include the holddown-interval statement in the BFD
configuration.

112 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

You can configure a number in the range from 0 through 255,000 milliseconds. The
default is 0. If the BFD session goes down and then comes back up during the hold-down
interval, the timer is restarted.

NOTE: If a single BFD session includes multiple static routes, the hold-down
interval with the highest value is used.

To specify the minimum transmit and receive intervals for failure detection, include the
minimum-interval statement in the BFD configuration.

This value represents both the minimum interval after which the local routing device
transmits hello packets and the minimum interval after which the routing device expects
to receive a reply from the neighbor with which it has established a BFD session. You can
configure a number in the range from 1 through 255,000 milliseconds. Optionally, instead
of using this statement, you can configure the minimum transmit and receive intervals
separately using the transmit-interval minimum-interval and minimum-receive-interval
statements.

NOTE: BFD is an intensive protocol that consumes system resources.

Specifying a minimum interval for BFD of less than 100 ms for Routing
Engine-based sessions and 10 ms for distributed BFD sessions can cause
undesired BFD flapping.

Depending on your network environment, these additional recommendations

might apply:

• For large-scale network deployments with a large number of BFD sessions,

specify a minimum interval of 300 ms for Routing Engine-based sessions
and 100 ms for distributed BFD sessions.

• For very large-scale network deployments with a large number of BFD

sessions, contact Juniper Networks customer support for more information.

• For BFD sessions to remain up during a Routing Engine switchover event

when nonstop active routing (NSR) is configured, specify a minimum
interval of 2500 ms for Routing Engine-based sessions. For distributed
BFD sessions with NSR configured, the minimum interval recommendations
are unchanged and depend only on your network deployment.

To specify the minimum receive interval for failure detection, include the
minimum-receive-interval statement in the BFD configuration. This value represents the
minimum interval after which the routing device expects to receive a reply from a neighbor
with which it has established a BFD session. You can configure a number in the range
from 1 through 255,000 milliseconds. Optionally, instead of using this statement, you
can configure the minimum receive interval using the minimum-interval statement at the
[edit routing-options static route destination-prefix bfd-liveness-detection] hierarchy level.

Copyright © 2017, Juniper Networks, Inc. 113

Protocol-Independent Routing Properties Feature Guide

To specify the number of hello packets not received by the neighbor that causes the
originating interface to be declared down, include the multiplier statement in the BFD
configuration.

The default value is 3. You can configure a number in the range from 1 through 255.

To specify a threshold for detecting the adaptation of the detection time, include the
threshold statement in the BFD configuration.

When the BFD session detection time adapts to a value equal to or higher than the
threshold, a single trap and a system log message are sent. The detection time is based
on the multiplier of the minimum-interval or the minimum-receive-interval value. The
threshold must be a higher value than the multiplier for either of these configured values.
For example if the minimum-receive-interval is 300 ms and the multiplier is 3, the total
detection time is 900 ms. Therefore, the detection time threshold must have a value
higher than 900.

To specify the minimum transmit interval for failure detection, include the transmit-interval
minimum-interval statement in the BFD configuration.

This value represents the minimum interval after which the local routing device transmits
hello packets to the neighbor with which it has established a BFD session. You can
configure a value in the range from 1 through 255,000 milliseconds. Optionally, instead
of using this statement, you can configure the minimum transmit interval using the
minimum-interval statement at the [edit routing-options static route destination-prefix
bfd-liveness-detection] hierarchy level.

To specify the threshold for the adaptation of the transmit interval, include the
transmit-interval threshold statement in the BFD configuration.

The threshold value must be greater than the transmit interval. When the BFD session
transmit time adapts to a value greater than the threshold, a single trap and a system
log message are sent. The detection time is based on the multiplier of the value for the
minimum-interval or the minimum-receive-interval statement at the [edit routing-options
static route destination-prefix bfd-liveness-detection] hierarchy level. The threshold must
be a higher value than the multiplier for either of these configured values.

To specify the BFD version, include the version statement in the BFD configuration. The
default is to have the version detected automatically.

To include an IP address for the next hop of the BFD session, include the neighbor
statement in the BFD configuration.

NOTE: You must configure the neighbor statement if the next hop specified
is an interface name. If you specify an IP address as the next hop, that address
is used as the neighbor address for the BFD session.

In Junos OS Release 9.0 and later, you can configure BFD sessions not to adapt to
changing network conditions.

114 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

To disable BFD adaptation, include the no-adaptation statement in the BFD configuration.

NOTE: We recommend that you not disable BFD adaptation unless it is

preferable not to have BFD adaptation in your network.

NOTE: If BFD is configured only on one end of a static route, the route is
removed from the routing table. BFD establishes a session when BFD is
configured on both ends of the static route.

BFD is not supported on ISO address families in static routes. BFD does
support IS-IS.

If you configure graceful Routing Engine switchover (GRES) at the same time
as BFD, GRES does not preserve the BFD state information during a failover.

Release History Table Release Description

16.1R1 Starting in Junos OS Release 16.1R1, the inline BFD sessions are supported on
integrated routing and bridging (IRB) interfaces.

15.1X49-D70 Starting with Junos OS Release 15.1X49-D70 and Junos OS Release 17.3R1, the
bfd-liveness-detection command includes the description field. The
description is an attribute under the bfd-liveness-detection object and it is
supported only on SRX Series devices. This field is applicable only for the static
routes.

15.1F6 Inline BFD is supported on PTX3000 routers with third-generation FPCs starting
in Junos OS Release 15.1F6 and 16.1R2.

15.1F3 Inline BFD is supported on PTX5000 routers with third-generation FPCs starting
in Junos OS Release 15.1F3 and 16.1R2.

13.3 Starting in Junos OS Release 13.3, inline BFD is supported only on static MX
Series routers with MPCs/MICs that have configured enhanced-ip.

Related • Enabling Distributed BFD

Documentation
• Example: Configuring BFD for Static Routes for Faster Network Failure Detection on
page 116

• Example: Enabling BFD on Qualified Next Hops in Static Routes for Route Selection
on page 130

Copyright © 2017, Juniper Networks, Inc. 115

Protocol-Independent Routing Properties Feature Guide

Example: Configuring BFD for Static Routes for Faster Network Failure Detection

This example shows how to configure Bidirectional Forwarding Detection (BFD) for static
routes.

• Requirements on page 116

• Overview on page 116
• Configuration on page 117
• Verification on page 120

Requirements
In this example, no special configuration beyond device initialization is required.

For demonstration purposes, some loopback interfaces are configured on Device B and
Device D. These loopback interfaces provide addresses to ping and thus verify that the
static routes are working.

Figure 13 on page 117 shows the sample network.

116 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

Figure 13: Customer Routes Connected to a Service Provider

Provider network
10.0.0.1
10.0.0.2
...

172.16.1.0/24
.2

Customer network
192.168.47.5
192.168.47.6
... g041171

Configuration

Device B set interfaces ge-1/2/0 unit 0 description B->D

Device D set interfaces ge-1/2/0 unit 1 description D->B

Copyright © 2017, Juniper Networks, Inc. 117

Protocol-Independent Routing Properties Feature Guide

Step-by-Step The following example requires that you navigate various levels in the configuration
Procedure hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.

To configure BFD for static routes:

1. On Device B, configure the interfaces.

2. On Device B, create a static route and set the next-hop address.

[edit routing-options]
user@B# set static route 192.168.47.0/24 next-hop 172.16.1.2

3. On Device B, configure BFD for the static route.

[edit routing-options]
user@B# set static route 192.168.47.0/24 bfd-liveness-detection minimum-interval
1000
set routing-options static route 192.168.47.0/24 bfd-liveness-detection description
Site-xxx

4. On Device B, configure tracing operations for BFD.

[edit protocols]
user@B# set bfd traceoptions file bfd-trace
user@B# set bfd traceoptions flag all

5. If you are done configuring Device B, commit the configuration.

[edit]
user@B# commit

6. On Device D, configure the interfaces.

7. On Device D, create a static route and set the next-hop address.

[edit routing-options]
user@D# set static route 0.0.0.0/0 next-hop 172.16.1.1

8. On Device D, configure BFD for the static route.

[edit routing-options]

118 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

user@D# set static route 0.0.0.0/0 bfd-liveness-detection minimum-interval 1000

9. On Device D, configure tracing operations for BFD.

[edit protocols]
user@D# set bfd traceoptions file bfd-trace
user@D# set bfd traceoptions flag all

10. If you are done configuring Device D, commit the configuration.

[edit]
user@D# commit

Results

Confirm your configuration by issuing the show interfaces, show protocols, and show
routing-options commands. If the output does not display the intended configuration,
repeat the instructions in this example to correct the configuration.

Device B user@B# show interfaces

ge-1/2/0 {
unit 0 {
description B->D;
family inet {
address 172.16.1.1/24;
}
}
}
lo0 {
unit 57 {
family inet {
address 10.0.0.1/32;
address 10.0.0.2/32;
}
}
}

user@D# show protocols

bfd {
traceoptions {
file bfd-trace;
flag all;
}
}

user@B# show routing-options

static {
route 192.168.47.0/24 {
next-hop 172.16.1.2;
bfd-liveness-detection {
description Site- xxx;
minimum-interval 1000;
}

Copyright © 2017, Juniper Networks, Inc. 119

Protocol-Independent Routing Properties Feature Guide

}
}

Device D user@D# show interfaces

ge-1/2/0 {
unit 1 {
description D->B;
family inet {
address 172.16.1.2/24;
}
}
}
lo0 {
unit 2 {
family inet {
address 192.168.47.5/32;
address 192.168.47.6/32;
}
}
}

user@D# show routing-options

static {
route 0.0.0.0/0 {
next-hop 172.16.1.1;
bfd-liveness-detection {
description Site - xxx;
minimum-interval 1000;
}
}
}

Verification
Confirm that the configuration is working properly.

• Verifying That BFD Sessions Are Up on page 120

• Viewing Detailed BFD Events on page 121

Verifying That BFD Sessions Are Up

Purpose Verify that the BFD sessions are up, and view details about the BFD sessions.

Action From operational mode, enter the show bfd session extensive command.

user@B> show bfd session extensive

Detect Transmit
Address State Interface Time Interval Multiplier
172.16.1.2 Up lt-1/2/0.0 3.000 1.000 3
Client Static, description Site-xxx, TX interval 1.000, RX interval 1.000
Session up time 00:14:30
Local diagnostic None, remote diagnostic None
Remote state Up, version 1
Replicated, routing table index 172

120 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

Min async interval 1.000, min slow interval 1.000

Adaptive async TX interval 1.000, RX interval 1.000
Local min TX interval 1.000, minimum RX interval 1.000, multiplier 3
Remote min TX interval 1.000, min RX interval 1.000, multiplier 3
Local discriminator 2, remote discriminator 1
Echo mode disabled/inactive

1 sessions, 1 clients
Cumulative transmit rate 1.0 pps, cumulative receive rate 1.0 pps

NOTE: The description Site- <xxx> is supported only on the SRX Series
devices.

If each client has more than one description field, then it displays "and more"
along with the first description field.

user@D> show bfd session extensive

Detect Transmit
Address State Interface Time Interval Multiplier
172.16.1.1 Up lt-1/2/0.1 3.000 1.000 3
Client Static, TX interval 1.000, RX interval 1.000
Session up time 00:14:35
Local diagnostic None, remote diagnostic None
Remote state Up, version 1
Replicated, routing table index 170
Min async interval 1.000, min slow interval 1.000
Adaptive async TX interval 1.000, RX interval 1.000
Local min TX interval 1.000, minimum RX interval 1.000, multiplier 3
Remote min TX interval 1.000, min RX interval 1.000, multiplier 3
Local discriminator 1, remote discriminator 2
Echo mode disabled/inactive

1 sessions, 1 clients
Cumulative transmit rate 1.0 pps, cumulative receive rate 1.0 pps

Meaning The TX interval 1.000, RX interval 1.000 output represents the setting configured with the
minimum-interval statement. All of the other output represents the default settings for
BFD. To modify the default settings, include the optional statements under the
bfd-liveness-detection statement.

Viewing Detailed BFD Events

Purpose View the contents of the BFD trace file to assist in troubleshooting, if needed.

Action From operational mode, enter the file show /var/log/bfd-trace command.

user@B> file show /var/log/bfd-trace

Nov 23 14:26:55 Data (9) len 35: (hex) 42 46 44 20 70 65 72 69 6f 64 69 63 20
78 6d 69 74 20 72
Nov 23 14:26:55 PPM Trace: BFD periodic xmit rt tbl index 172

Copyright © 2017, Juniper Networks, Inc. 121

Protocol-Independent Routing Properties Feature Guide

Nov 23 14:26:55 Received Downstream TraceMsg (22) len 108:

Nov 23 14:26:55 IfIndex (3) len 4: 0
Nov 23 14:26:55 Protocol (1) len 1: BFD
Nov 23 14:26:55 Data (9) len 83: (hex) 70 70 6d 64 5f 62 66 64 5f 73 65 6e 64
6d 73 67 20 3a 20
Nov 23 14:26:55 PPM Trace: ppmd_bfd_sendmsg : socket 12 len 24, ifl 78 src
172.16.1.1 dst 172.16.1.2 errno 65
Nov 23 14:26:55 Received Downstream TraceMsg (22) len 93:
Nov 23 14:26:55 IfIndex (3) len 4: 0
Nov 23 14:26:55 Protocol (1) len 1: BFD
Nov 23 14:26:55 Data (9) len 68: (hex) 42 46 44 20 70 65 72 69 6f 64 69 63 20
78 6d 69 74 20 74

Meaning BFD messages are being written to the trace file.

Related • Understanding BFD for Static Routes for Faster Network Failure Detection on page 111
Documentation

Understanding BFD Authentication for Static Route Security

Bidirectional Forwarding Detection (BFD) enables rapid detection of communication

failures between adjacent systems. By default, authentication for BFD sessions is disabled.
However, when you run BFD over Network Layer protocols, the risk of service attacks can
be significant.

NOTE: We strongly recommend using authentication if you are running BFD

over multiple hops or through insecure tunnels.

Beginning with Junos OS Release 9.6, Junos OS supports authentication for BFD sessions
running over IPv4 and IPv6 static routes. BFD authentication is not supported on MPLS
OAM sessions. BFD authentication is only supported in the Canada and United States
version of the Junos OS image and is not available in the export version.

NOTE: EX3300 supports BFD over static routes only.

You authenticate BFD sessions by specifying an authentication algorithm and keychain,

and then associating that configuration information with a security authentication
keychain using the keychain name.

The following sections describe the supported authentication algorithms, security

keychains, and level of authentication that can be configured:

• BFD Authentication Algorithms on page 123

• Security Authentication Keychains on page 123
• Strict Versus Loose Authentication on page 124

122 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

BFD Authentication Algorithms

Junos OS supports the following algorithms for BFD authentication:

• simple-password—Plain-text password. One to 16 bytes of plain text are used to

authenticate the BFD session. One or more passwords can be configured. This method
is the least secure and should be used only when BFD sessions are not subject to packet
interception.

• keyed-md5—Keyed Message Digest 5 hash algorithm for sessions with transmit and
receive intervals greater than 100 ms. To authenticate the BFD session, keyed MD5
uses one or more secret keys (generated by the algorithm) and a sequence number
that is updated periodically. With this method, packets are accepted at the receiving
end of the session if one of the keys matches and the sequence number is greater than
or equal to the last sequence number received. Although more secure than a simple
password, this method is vulnerable to replay attacks. Increasing the rate at which the
sequence number is updated can reduce this risk.

• meticulous-keyed-md5—Meticulous keyed Message Digest 5 hash algorithm. This

method works in the same manner as keyed MD5, but the sequence number is updated
with every packet. Although more secure than keyed MD5 and simple passwords, this
method might take additional time to authenticate the session.

• keyed-sha-1—Keyed Secure Hash Algorithm I for sessions with transmit and receive
intervals greater than 100 ms. To authenticate the BFD session, keyed SHA uses one
or more secret keys (generated by the algorithm) and a sequence number that is
updated periodically. The key is not carried within the packets. With this method,
packets are accepted at the receiving end of the session if one of the keys matches
and the sequence number is greater than the last sequence number received.

• meticulous-keyed-sha-1—Meticulous keyed Secure Hash Algorithm I. This method

works in the same manner as keyed SHA, but the sequence number is updated with
every packet. Although more secure than keyed SHA and simple passwords, this method
might take additional time to authenticate the session.

NOTE: Nonstop active routing (NSR) is not supported with

meticulous-keyed-md5 and meticulous-keyed-sha-1 authentication
algorithms. BFD sessions using these algorithms might go down after a
switchover.

Security Authentication Keychains

The security authentication keychain defines the authentication attributes used for
authentication key updates. When the security authentication keychain is configured and
associated with a protocol through the keychain name, authentication key updates can
occur without interrupting routing and signaling protocols.

The authentication keychain contains one or more keychains. Each keychain contains
one or more keys. Each key holds the secret data and the time at which the key becomes
valid. The algorithm and keychain must be configured on both ends of the BFD session,

Copyright © 2017, Juniper Networks, Inc. 123

Protocol-Independent Routing Properties Feature Guide

and they must match. Any mismatch in configuration prevents the BFD session from
being created.

BFD allows multiple clients per session, and each client can have its own keychain and
algorithm defined. To avoid confusion, we recommend specifying only one security
authentication keychain.

Strict Versus Loose Authentication

By default, strict authentication is enabled, and authentication is checked at both ends
of each BFD session. Optionally, to smooth migration from nonauthenticated sessions
to authenticated sessions, you can configure loose checking. When loose checking is
configured, packets are accepted without authentication being checked at each end of
the session. This feature is intended for transitional periods only.

Related • Example: Configuring BFD Authentication for Securing Static Routes on page 124
Documentation

Example: Configuring BFD Authentication for Securing Static Routes

This example shows how to configure Bidirectional Forwarding Detection (BFD)

authentication for static routes.

• Requirements on page 124

• Overview on page 124
• Configuration on page 125
• Verification on page 128

Requirements
Junos OS Release 9.6 or later (Canda and United States version).

BFD authentication is only supported in the Canada and United States version of the
Junos OS image and is not available in the export version.

Overview
You can configure authentication for BFD sessions running over IPv4 and IPv6 static
routes. Routing instances and logical systems are also supported.

The following steps are needed to configure authentication on a BFD session:

1. Specify the BFD authentication algorithm for the static route.

2. Associate the authentication keychain with the static route.

3. Configure the related security authentication keychain. This must be configured on

the main router.

TIP: We recommend that you specify loose authentication checking if you

are transitioning from nonauthenticated sessions to authenticated sessions.

124 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

[edit]
user@host> set routing-options static route ipv4 bfd-liveness-detection
authentication loose-check

Figure 14 on page 125 shows the sample network.

Figure 14: Customer Routes Connected to a Service Provider

Provider network
10.0.0.1
10.0.0.2
...

172.16.1.0/24
.2

Customer network
192.168.47.5
192.168.47.6
g041171

...

Configuration

Device B set interfaces ge-1/2/0 unit 0 description B->D

set interfaces ge-1/2/0 unit 0 family inet address 172.16.1.1/24
set interfaces lo0 unit 57 family inet address 10.0.0.1/32
set interfaces lo0 unit 57 family inet address 10.0.0.2/32
set routing-options static route 192.168.47.0/24 next-hop 172.16.1.2
set routing-options static route 192.168.47.0/24 bfd-liveness-detection minimum-interval
1000
set routing-options static route 192.168.47.0/24 bfd-liveness-detection description
Site-xxx
set routing-options static route 192.168.47.0/24 bfd-liveness-detection authentication
key-chain bfd-kc4
set routing-options static route 192.168.47.0/24 bfd-liveness-detection authentication
algorithm keyed-sha-1
set security authentication-key-chains key-chain bfd-kc4 key 5 secret
"$ABC123$ABC123$ABC123"
set security authentication-key-chains key-chain bfd-kc4 key 5 start-time
"2011-1-1.12:00:00 -0800"

Copyright © 2017, Juniper Networks, Inc. 125

Protocol-Independent Routing Properties Feature Guide

Device D set interfaces ge-1/2/0 unit 1 description D->B

set interfaces ge-1/2/0 unit 1 family inet address 172.16.1.2/24
set interfaces lo0 unit 2 family inet address 192.168.47.5/32
set interfaces lo0 unit 2 family inet address 192.168.47.6/32
set routing-options static route 0.0.0.0/0 next-hop 172.16.1.1
set routing-options static route 0.0.0.0/0 bfd-liveness-detection minimum-interval 1000
set routing-options static route 0.0.0.0/0 bfd-liveness-detection authentication key-chain
bfd-kc4
set routing-options static route 0.0.0.0/0 bfd-liveness-detection authentication algorithm
keyed-sha-1
set security authentication-key-chains key-chain bfd-kc4 key 5 secret
"$ABC123$ABC123$ABC123"
set security authentication-key-chains key-chain bfd-kc4 key 5 start-time
"2011-1-1.12:00:00 -0800"

To configure BFD for static routes:

1. On Device B, configure the interfaces.

[edit interfaces]
user@B# set ge-1/2/0 unit 0 description B->D
user@B# set ge-1/2/0 unit 0 family inet address 172.16.1.1/24

user@B# set lo0 unit 57 family inet address 10.0.0.1/32

user@B# set lo0 unit 57 family inet address 10.0.0.2/32

2. On Device B, create a static route and set the next-hop address.

[edit routing-options]
user@B# set static route 192.168.47.0/24 next-hop 172.16.1.2

3. On Device B, configure BFD for the static route.

4. On Device B, specify the algorithm (keyed-md5, keyed-sha-1, meticulous-keyed-md5,

meticulous-keyed-sha-1, or simple-password) to use for BFD authentication on the
static route.

[edit routing-options]
user@B# set static route 192.168.47.0/24 bfd-liveness-detection authentication
algorithm keyed-sha-1

126 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

NOTE: Nonstop active routing (NSR) is not supported with the

meticulous-keyed-md5 and meticulous-keyed-sha-1 authentication
algorithms. BFD sessions using these algorithms might go down after
a switchover.

5. On Device B, specify the keychain to be used to associate BFD sessions on the

specified route with the unique security authentication keychain attributes.

This should match the keychain name configured at the [edit security authentication
key-chains] hierarchy level.

[edit routing-options]
user@B# set static route 192.168.47.0/24 bfd-liveness-detection authentication
key-chain bfd-kc4

6. On Device B, specify the unique security authentication information for BFD sessions:

• The matching keychain name as specified in Step 5.

• At least one key, a unique integer between 0 and 63. Creating multiple keys allows
multiple clients to use the BFD session.

• The secret data used to allow access to the session.

• The time at which the authentication key becomes active, in the format
yyyy-mm-dd.hh:mm:ss.

[edit security authentication-key-chains key-chain bfd-kc4]

user@B# set key 5 secret "$ABC123$ABC123$ABC123"
user@B# set key 5 start-time "2011-1-1.12:00:00 -0800"

7. If you are done configuring Device B, commit the configuration.

[edit]
user@B# commit

8. Repeat the configuration on Device D.

The algorithm and keychain must be configured on both ends of the BFD session,
and they must match. Any mismatch in configuration prevents the BFD session
from being created.

Results

Confirm your configuration by issuing the show interfaces, show routing-options, and show
security commands. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.

Device B user@B# show interfaces

Copyright © 2017, Juniper Networks, Inc. 127

Protocol-Independent Routing Properties Feature Guide

ge-1/2/0 {
unit 0 {
description B->D;
family inet {
address 172.16.1.1/24;
}
}
}
lo0 {
unit 57 {
family inet {
address 10.0.0.1/32;
address 10.0.0.2/32;
}
}
}

user@B# show routing-options

static {
route 192.168.47.0/24 {
next-hop 172.16.1.2;
bfd-liveness-detection {
description Site- xxx;
minimum-interval 1000;
authentication {
key-chain bfd-kc4;
algorithm keyed-sha-1;
}
}
}
}

user@B# show security

authentication-key-chains {
key-chain bfd-kc4 {
key 5 {
secret "$ABC123$ABC123$ABC123"; ## SECRET-DATA
start-time "2011-1-1.12:00:00 -0800";
}
}
}

Verification
Confirm that the configuration is working properly.

• Verifying That BFD Sessions Are Up on page 128

• Viewing Details About the BFD Session on page 129
• Viewing Extensive BFD Session Information on page 129

Verifying That BFD Sessions Are Up

Purpose Verify that the BFD sessions are up.

128 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

Action From operational mode, enter the show bfd session command.

user@B> show bfd session

Detect Transmit
Address State Interface Time Interval Multiplier
172.16.1.2 Up ge-1/2/0.0 3.000 1.000 3

1 sessions, 1 clients
Cumulative transmit rate 1.0 pps, cumulative receive rate 1.0 pps

Meaning The command output shows that the BFD session is up.

Viewing Details About the BFD Session

Purpose View details about the BFD sessions and make sure that authentication is configured.

Action From operational mode, enter the show bfd session detail command.

user@B> show bfd session detail

Detect Transmit
Address State Interface Time Interval Multiplier
172.16.1.2 Up ge-1/2/0.0 3.000 1.000 3
Client Static, TX interval 1.000, RX interval 1.000, Authenticate
Session up time 00:53:58
Local diagnostic NbrSignal, remote diagnostic None
Remote state Up, version 1
Logical system 9, routing table index 22

1 sessions, 1 clients
Cumulative transmit rate 1.0 pps, cumulative receive rate 1.0 pps

Meaning In the command output, Authenticate is displayed to indicate that BFD authentication is
configured.

Viewing Extensive BFD Session Information

Purpose View more detailed information about the BFD sessions.

Action From operational mode, enter the show bfd session extensive command.

user@B> show bfd session extensive

Address State Interface Time Interval Multiplier
172.16.1.2 Up ge-1/2/0.0 3.000 1.000 3
Client Static, description Site-xxx, TX interval 1.000, RX interval 1.000,
Authenticate
keychain bfd-kc4, algo keyed-sha-1, mode strict
Session up time 01:39:45
Local diagnostic NbrSignal, remote diagnostic None
Remote state Up, version 1
Logical system 9, routing table index 22
Min async interval 1.000, min slow interval 1.000

Copyright © 2017, Juniper Networks, Inc. 129

Protocol-Independent Routing Properties Feature Guide

Adaptive async TX interval 1.000, RX interval 1.000

Local min TX interval 1.000, minimum RX interval 1.000, multiplier 3
Remote min TX interval 1.000, min RX interval 1.000, multiplier 3
Local discriminator 3, remote discriminator 4
Echo mode disabled/inactive
Authentication enabled/active, keychain bfd-kc4, algo keyed-sha-1, mode strict

1 sessions, 1 clients
Cumulative transmit rate 1.0 pps, cumulative receive rate 1.0 pps

Meaning In the command output, Authenticate is displayed to indicate that BFD authentication is
configured. The output for the extensive command provides the keychain name, the
authentication algorithm, and the mode for each client in the session.

NOTE: The description Site- <xxx> is supported only on the SRX Series
devices.

If each client has more than one description field, then it displays "and more"
along with the first description field.

Related • Understanding BFD Authentication for Static Route Security on page 122
Documentation

Example: Enabling BFD on Qualified Next Hops in Static Routes for Route Selection

This example shows how to configure a static route with multiple possible next hops.
Each next hop has Bidirectional Forwarding Detection (BFD) enabled.

• Requirements on page 130

• Overview on page 130
• Configuration on page 131
• Verification on page 134

Requirements
In this example, no special configuration beyond device initialization is required.

Overview
In this example, Device B has the static route 192.168.47.0/24 with two possible next
hops. The two next hops are defined using two qualified-next-hop statements. Each next
hop has BFD enabled.

BFD is also enabled on Device D because BFD must be enabled on both ends of the
connection.

130 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

A next hop is included in the routing table if the BFD session is up. The next hop is removed
from the routing table if the BFD session is down.

See Figure 15 on page 131.

Figure 15: BFD Enabled on Qualified Next Hops

Provider network
10.0.0.1
10.0.0.2
...

.1 .1
Fast Ethernet Gigabit Ethernet
192.168.2.0/24 172.16.1.0/24
.2 .2

Customer network
192.168.47.5
192.168.47.6
g041172

...

Configuration

Device B set interfaces fe-0/1/0 unit 2 description secondary-B->D

set interfaces fe-0/1/0 unit 2 family inet address 192.168.2.1/24
set interfaces ge-1/2/0 unit 0 description B->D
set interfaces ge-1/2/0 unit 0 family inet address 172.16.1.1/24
set routing-options static route 192.168.47.0/24 qualified-next-hop 192.168.2.2
bfd-liveness-detection minimum-interval 60
set routing-options static route 192.168.47.0/24 qualified-next-hop 172.16.1.2
bfd-liveness-detection minimum-interval 60

Device D set interfaces fe-0/1/0 unit 3 description secondary-D->B

set interfaces fe-0/1/0 unit 3 family inet address 192.168.2.2/24
set interfaces ge-1/2/0 unit 1 description D->B
set interfaces ge-1/2/0 unit 1 family inet address 172.16.1.2/24
set routing-options static route 0.0.0.0/0 qualified-next-hop 192.168.2.1
set routing-options static route 0.0.0.0/0 qualified-next-hop 172.16.1.1
set routing-options static route 0.0.0.0/0 bfd-liveness-detection minimum-interval 60

Copyright © 2017, Juniper Networks, Inc. 131

Protocol-Independent Routing Properties Feature Guide

Step-by-Step The following example requires that you navigate various levels in the configuration
Procedure hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.

To configure a static route with two possible next hops, both with BFD enabled:

1. On Device B, configure the interfaces.

[edit interfaces fe-0/1/0]

user@B# set unit 2 description secondary-B->D
user@B# set unit 2 family inet address 192.168.2.1/24

[edit interfaces ge-1/2/0]

user@B# set unit 0 description B->D
user@B# set unit 0 family inet address 172.16.1.1/24

2. On Device B, configure the static route with two next hops, both with BFD enabled.

[edit routing-options static route 192.168.47.0/24]

user@B# set qualified-next-hop 192.168.2.2 bfd-liveness-detection minimum-interval
60
user@B# set qualified-next-hop 172.16.1.2 bfd-liveness-detection minimum-interval
60

3. On Device D, configure the interfaces.

[edit interfaces fe-0/1/0]

user@D# set unit 3 description secondary-D->B
user@D# set unit 3 family inet address 192.168.2.2/24

[edit interfaces ge-1/2/0]

user@D# set unit 1 description D->B
user@D# set unit 1 family inet address 172.16.1.2/24

4. On Device D, configure a BFD-enabled default static route with two next hops to
the provider network.

In this case, BFD is enabled on the route, not on the next hops.

[edit routing-options static route 0.0.0.0/0]

user@D# set qualified-next-hop 192.168.2.1
user@D# set qualified-next-hop 172.16.1.1
user@D# set bfd-liveness-detection minimum-interval 60

user@B# show interfaces

fe-0/1/0 {
unit 2 {
description secondary-B->D;
family inet {

132 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

address 192.168.2.1/24;
}
}
}
ge-1/2/0 {
unit 0 {
description B->D;
family inet {
address 172.16.1.1/24;
}
}
}

user@B# show routing-options

static {
route 192.168.47.0/24 {
qualified-next-hop 192.168.2.2 {
bfd-liveness-detection {
minimum-interval 60;
}
}
qualified-next-hop 172.16.1.2 {
bfd-liveness-detection {
minimum-interval 60;
}
}
}
}

user@D# show interfaces

fe-0/1/0 {
unit 3 {
description secondary-D->B;
family inet {
address 192.168.2.2/24;
}
}
}
ge-1/2/0 {
unit 1 {
description D->B;
family inet {
address 172.16.1.2/24;
}
}
}

user@D# show routing-options

static {
route 0.0.0.0/0 {
qualified-next-hop 192.168.2.1;
qualified-next-hop 172.16.1.1;
bfd-liveness-detection {
minimum-interval 60;
}
}
}

Copyright © 2017, Juniper Networks, Inc. 133

Protocol-Independent Routing Properties Feature Guide

If you are done configuring the devices, enter commit from configuration mode.

Verification
Confirm that the configuration is working properly.

• Checking the Routing Tables on page 134

• Verifying the BFD Sessions on page 134
• Removing BFD from Device D on page 135
• Removing BFD from One Next Hop on page 135

Checking the Routing Tables

Purpose Make sure that the static route appears in the routing table on Device B with two possible
next hops.

Action user@B> show route 192.168.47.0 extensive

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
192.168.47.0/24 (1 entry, 1 announced)
TSI:
KRT in-kernel 192.168.47.0/24 -> {192.168.2.2}
*Static Preference: 5
Next hop type: Router
Address: 0x9334010
Next-hop reference count: 1
Next hop: 172.16.1.2 via ge-1/2/0.0
Next hop: 192.168.2.2 via fe-0/1/0.2, selected
State: <Active Int Ext>
Age: 9
Task: RT
Announcement bits (1): 3-KRT
AS path: I

Meaning Both next hops are listed. The next hop 192.168.2.2 is the selected route.

Verifying the BFD Sessions

Purpose Make sure that the BFD sessions are up.

134 Copyright © 2017, Juniper Networks, Inc.

Chapter 6: Configuring Bidirectional Forwarding Detection for Static Routes

Action user@B> show bfd session

Detect Transmit
Address State Interface Time Interval Multiplier
172.16.1.2 Up ge-1/2/0.0 0.720 0.240 3
192.168.2.2 Up fe-0/1/0.2 0.720 0.240 3

2 sessions, 2 clients
Cumulative transmit rate 8.3 pps, cumulative receive rate 8.3 pps

Meaning The output shows that the BFD sessions are up.

Removing BFD from Device D

Purpose Demonstrate what happens when the BFD session is down for both next hops.

Action 1. Deactivate BFD on Device D.

[edit routing-options static route 0.0.0.0/0]

user@D# deactivate bfd-liveness-detection
user@D# commit

2. Rerun the show bfd session command on Device B.

user@B> show bfd session

Detect Transmit
Address State Interface Time Interval Multiplier
172.16.1.2 Down ge-1/2/0.0 3.000 1.000 3
192.168.2.2 Down fe-0/1/0.2 3.000 1.000 3

2 sessions, 2 clients
Cumulative transmit rate 2.0 pps, cumulative receive rate 2.0 pps

3. Rerun the show route 192.168.47.0 command on Device B.

user@B> show route 192.168.47.0

Meaning As expected, when the BFD sessions are down, the static route is removed from the
routing table.

Removing BFD from One Next Hop

Purpose Demonstrate what happens when only one next hop has BFD enabled.

Action 1. If it is not already deactivated, deactivate BFD on Device D.

[edit routing-options static route 0.0.0.0/0]

user@D# deactivate bfd-liveness-detection
user@D# commit

Copyright © 2017, Juniper Networks, Inc. 135

Protocol-Independent Routing Properties Feature Guide

2. Deactivate BFD on one of the next hops on Device B.

[edit routing-options static route 192.168.47.0/24 qualified-next-hop 172.16.1.2]

user@B# deactivate bfd-liveness-detection
user@B# commit

3. Rerun the show bfd session command on Device B.

user@B> show bfd session

Detect Transmit
Address State Interface Time Interval Multiplier
192.168.2.2 Down fe-0/1/0.2 3.000 1.000 3

4. Rerun the show route 192.168.47.0 extensive command on Device B.

user@B> show route 192.168.47.0 extensive

inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)

192.168.47.0/24 (1 entry, 1 announced)
TSI:
KRT in-kernel 192.168.47.0/24 -> {172.16.1.2}
*Static Preference: 5
Next hop type: Router, Next hop index: 624
Address: 0x92f0178
Next-hop reference count: 3
Next hop: 172.16.1.2 via ge-1/2/0.0, selected
State: <Active Int Ext>
Age: 2:36
Task: RT
Announcement bits (1): 3-KRT
AS path: I

Meaning As expected, the BFD session is down for the 192.168.2.2 next hop. The 172.16.1.2 next hop
remains in the routing table, and the route remains active, because BFD is not a condition
for this next hop to remain valid.

Related • Example: Configuring Static Route Preferences and Qualified Next Hops to Control
Documentation Static Route Selection on page 36

• Understanding Static Route Preferences and Qualified Next Hops on page 35

• Understanding BFD for Static Routes for Faster Network Failure Detection on page 111

• Verifying the Static Route Configuration on page 63

136 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 7

Configuring Packet Forwarding Behavior

for Protocol-Independent Routing

• Understanding the Default Routing Table Groups for Interface Routes on Packet
Transport Routers on page 137
• Understanding Indirect Next Hops on page 138
• Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the
Packet Forwarding Engine on page 139
• Understanding Unicast Reverse Path Forwarding on page 149
• Example: Configuring Unicast Reverse-Path-Forwarding Check on page 150

Understanding the Default Routing Table Groups for Interface Routes on Packet
Transport Routers

On PTX Series Packet Transport Routers, the default interface-route routing table groups
differ from that of other Junos OS routing devices.

The PTX Series routers are MPLS transit platforms that do IP forwarding, typically using
interior gateway protocol (IGP) routes. Interface routes are directly connected and local
routes.

PTX Series routers are unlike other Junos OS routing devices in that they force an indirect
next-hop resolution. PTX Series routers need the indirect next hop be resolved to create
the chained composite next hop. This can cause routes to be hidden when the next-hop
type is unusable.

To prevent routes from being hidden, PTX Series platforms automatically copy the routes
in inet.0 into inet.2 and inet.3, and the routes in inet6.0 into inet6.2 and inet6.3.

The default interface routing table configuration on the PTX Series routers is as follows:

user@host# show routing-options | display inheritance defaults

##
## 'interface-routes' was inherited from group 'junos-defaults'
##
interface-routes {
##
## 'rib-group' was inherited from group 'junos-defaults'
##

Copyright © 2017, Juniper Networks, Inc. 137

Protocol-Independent Routing Properties Feature Guide

rib-group {
##
## 'junos-ifrg-inet0-to-inet2-and-inet3' was inherited from group 'junos-defaults'
##
inet junos-ifrg-inet0-to-inet2-and-inet3;
##
## 'junos-ifrg-inet60-to-inet62-and-inet63' was inherited from group 'junos-defaults'
##
inet6 junos-ifrg-inet60-to-inet62-and-inet63;
}
}
rib-groups {
##
## 'junos-ifrg-inet0-to-inet2-and-inet3' was inherited from group 'junos-defaults'
##
junos-ifrg-inet0-to-inet2-and-inet3 {
##
## 'inet.0' was inherited from group 'junos-defaults'
## 'inet.2' was inherited from group 'junos-defaults'
## 'inet.3' was inherited from group 'junos-defaults'
##
import-rib [ inet.0 inet.2 inet.3 ];
}
##
## 'junos-ifrg-inet60-to-inet62-and-inet63' was inherited from group 'junos-defaults'
##
junos-ifrg-inet60-to-inet62-and-inet63 {
##
## 'inet6.0' was inherited from group 'junos-defaults'
## 'inet6.2' was inherited from group 'junos-defaults'
## 'inet6.3' was inherited from group 'junos-defaults'
##
import-rib [ inet6.0 inet6.2 inet6.3 ];
}
}

Related • Chained Composite Next Hops for Transit Devices for VPNs
Documentation
• Example: Overriding the Default BGP Routing Policy on PTX Series Packet Transport
Routers

Understanding Indirect Next Hops

Junos OS supports the concept of an indirect next hop for all routing protocols that
support indirectly connected next hops, also known as third-party next hops.

Because routing protocols such as internal BGP (IBGP) can send routing information
about indirectly connected routes, Junos OS relies on routes from intra-AS routing
protocols (OSPF, IS-IS, RIP, and static) to resolve the best directly connected next hop.
The Routing Engine performs route resolution to determine the best directly connected
next hop and installs the route to the Packet Forwarding Engine.

138 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

By default, Junos OS does not maintain the route for indirect next hop to forwarding
next-hop binding on the Packet Forwarding Engine forwarding table. As a result, when
a rerouting event occurs, potentially thousands of route to forwarding next-hop bindings
must be updated, which increases the route convergence time. Figure 16 on page 139
illustrates the route to forwarding next-hop bindings with indirect next hop disabled.

Figure 16: Route to Forwarding Next-Hop Bindings

You can enable Junos OS to maintain the indirect next hop to forwarding next-hop binding
on the Packet Forwarding Engine forwarding table. As a result, fewer route to forwarding
next-hop bindings need to be updated, which improves the route convergence time.
Figure 17 on page 139 illustrates the route to forwarding next-hop bindings with indirect
next hop enabled.

Figure 17: Route to Forwarding Indirect Next-Hop Bindings

Related • Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the
Documentation Packet Forwarding Engine on page 139

Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the

Packet Forwarding Engine

This example shows how to use indirect next hops to promote faster network convergence
(for example, in BGP networks) by decreasing the number of forwarding table changes
required when a change in the network topology occurs.

• Requirements on page 139

• Overview on page 140
• Configuration on page 140
• Verification on page 148

Requirements
No special configuration beyond device initialization is required before configuring this
example.

Copyright © 2017, Juniper Networks, Inc. 139

Protocol-Independent Routing Properties Feature Guide

Overview
In this example, several devices are connected over unequal-cost paths. From Device R1
to Device R2, the path through Device R3 has a higher IGP metric than the path through
Device R4. Device R1 has an internal BGP connection to Device R2. Device R0 injects
multiple routes into the network, and Device R1 advertises those routes to Device R2.
Because Device R2 is not directly connected to Device R1, Device R2’s forwarding table
contains indirect next hops. An interior gateway protocol, in this case OSPF, is running
on the internal links among Devices R1, R2, R3, and R4. Each router is advertising its
loopback interface IPv4 address.

On Device R2, the indirect-next-hop statement enables Junos OS to maintain the indirect
next hop to forwarding next-hop binding on the Packet Forwarding Engine forwarding
table. As a result, fewer route to forwarding next-hop bindings need to be updated, which
improves the route convergence time if a path fails.

Figure 18 on page 140 shows the sample network.

R0 R1 R2 R5

g041189
The “CLI Quick Configuration” on page 140 section shows the full configuration on all of
the devices in Figure 18 on page 140. Otherwise, the example focuses on Device R0, Device
R1, and Device R2.

Configuration

Device R0 set interfaces fe-1/2/0 unit 1 family inet address 10.0.0.1/30

set interfaces lo0 unit 1 family inet address 1.1.0.1/32
set interfaces lo0 unit 1 family inet address 1.1.0.2/32
set interfaces lo0 unit 1 family inet address 1.1.0.3/32
set interfaces lo0 unit 1 family inet address 1.1.0.4/32
set interfaces lo0 unit 1 family inet address 1.1.0.5/32
set interfaces lo0 unit 1 family inet address 1.1.0.6/32
set interfaces lo0 unit 1 family inet address 1.1.0.7/32
set interfaces lo0 unit 1 family inet address 1.1.0.8/32

140 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

set interfaces lo0 unit 1 family inet address 1.1.0.9/32

set routing-options static route 0.0.0.0/0 next-hop 10.0.0.2

Device R1 set interfaces fe-1/2/0 unit 2 family inet address 10.0.0.2/30

set interfaces fe-1/2/1 unit 5 family inet address 10.0.0.5/30
set interfaces fe-1/2/2 unit 9 family inet address 10.0.0.9/30
set interfaces lo0 unit 2 family inet address 1.1.1.1/32
set protocols bgp export send-local
set protocols bgp export send-static
set protocols bgp group int type internal
set protocols bgp group int local-address 1.1.1.1
set protocols bgp group int neighbor 2.2.2.2
set protocols ospf area 0.0.0.0 interface fe-1/2/1.5
set protocols ospf area 0.0.0.0 interface fe-1/2/2.9
set protocols ospf area 0.0.0.0 interface lo0.2
set policy-options policy-statement send-local from protocol local
set policy-options policy-statement send-local from protocol direct
set policy-options policy-statement send-local then accept
set policy-options policy-statement send-static from protocol static
set policy-options policy-statement send-static then accept
set routing-options static route 1.1.0.2/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.1/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.3/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.4/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.5/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.6/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.7/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.8/32 next-hop 10.0.0.1
set routing-options static route 1.1.0.9/32 next-hop 10.0.0.1
set routing-options autonomous-system 65500

Device R2 set interfaces fe-1/2/0 unit 14 family inet address 10.0.0.14/30

set interfaces fe-1/2/1 unit 18 family inet address 10.0.0.18/30
set interfaces fe-1/2/2 unit 21 family inet
set interfaces lo0 unit 3 family inet address 2.2.2.2/32
set protocols bgp export send-local
set protocols bgp group int type internal
set protocols bgp group int local-address 2.2.2.2
set protocols bgp group int family inet unicast
set protocols bgp group int family inet-vpn unicast
set protocols bgp group int neighbor 1.1.1.1
set protocols ospf area 0.0.0.0 interface fe-1/2/0.14
set protocols ospf area 0.0.0.0 interface fe-1/2/1.18
set protocols ospf area 0.0.0.0 interface lo0.3
set policy-options policy-statement send-local from protocol local
set policy-options policy-statement send-local from protocol direct
set policy-options policy-statement send-local then accept
set routing-options autonomous-system 65500
set routing-options forwarding-table indirect-next-hop

Device R3 set interfaces fe-1/2/0 unit 6 family inet address 10.0.0.6/30

set interfaces fe-1/2/1 unit 13 family inet address 10.0.0.13/30
set interfaces lo0 unit 4 family inet address 3.3.3.3/32
set protocols ospf area 0.0.0.0 interface fe-1/2/0.6 metric 5000

Copyright © 2017, Juniper Networks, Inc. 141

Protocol-Independent Routing Properties Feature Guide

set protocols ospf area 0.0.0.0 interface fe-1/2/1.13 metric 5000

set protocols ospf area 0.0.0.0 interface lo0.4

Device R4 set interfaces fe-1/2/0 unit 10 family inet address 10.0.0.10/30

set interfaces fe-1/2/1 unit 17 family inet address 10.0.0.17/30
set interfaces lo0 unit 5 family inet address 4.4.4.4/32
set protocols ospf area 0.0.0.0 interface fe-1/2/0.10
set protocols ospf area 0.0.0.0 interface fe-1/2/1.17
set protocols ospf area 0.0.0.0 interface lo0.5

Device R5 set interfaces fe-1/2/0 unit 22 family inet address 10.0.0.22/30

set interfaces lo0 unit 6 family inet address 5.5.5.5/32

Configuring Device R0

To configure Device R0:

1. Configure the interfaces, including multiple routes that can be injected into the
network for demonstration purposes.

[edit interfaces]
user@R0# set fe-1/2/0 unit 1 family inet address 10.0.0.1/30

user@R0# set lo0 unit 1 family inet address 1.1.0.1/32

user@R0# set lo0 unit 1 family inet address 1.1.0.2/32
user@R0# set lo0 unit 1 family inet address 1.1.0.3/32
user@R0# set lo0 unit 1 family inet address 1.1.0.4/32
user@R0# set lo0 unit 1 family inet address 1.1.0.5/32
user@R0# set lo0 unit 1 family inet address 1.1.0.6/32
user@R0# set lo0 unit 1 family inet address 1.1.0.7/32
user@R0# set lo0 unit 1 family inet address 1.1.0.8/32
user@R0# set lo0 unit 1 family inet address 1.1.0.9/32

2. Configure a static default route for network reachability.

[edit routing-options]
user@R0# set static route 0.0.0.0/0 next-hop 10.0.0.2

3. If you are done configuring the device, commit the configuration.

[edit]
user@R0# commit

142 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

Configuring Device R1

To configure Device R1:

1. Configure the interfaces, including multiple routes that can be injected into the
network for demonstration purposes.

[edit interfaces]
user@R1# set fe-1/2/0 unit 2 family inet address 10.0.0.2/30
user@R1# set fe-1/2/1 unit 5 family inet address 10.0.0.5/30
user@R1# set fe-1/2/2 unit 9 family inet address 10.0.0.9/30

user@R1# set lo0 unit 2 family inet address 1.1.1.1/32

2. Configure BGP.

[edit protocols]
user@R1# set bgp export send-local
user@R1# set bgp export send-static
user@R1# set bgp group int type internal
user@R1# set bgp group int local-address 1.1.1.1
user@R1# set bgp group int neighbor 2.2.2.2

3. Configure OSPF.

[edit protocols]
user@R1# set ospf area 0.0.0.0 interface fe-1/2/1.5
user@R1# set ospf area 0.0.0.0 interface fe-1/2/2.9
user@R1# set ospf area 0.0.0.0 interface lo0.2

4. Configure the routing policies.

[edit]
user@R1# set policy-options policy-statement send-local from protocol local
user@R1# set policy-options policy-statement send-local from protocol direct
user@R1# set policy-options policy-statement send-local then accept

user@R1# set policy-options policy-statement send-static from protocol static

user@R1# set policy-options policy-statement send-static then accept

5. Configure a set of static routes to the set of interfaces configured on Device R0.

[edit]
user@R1# set routing-options static route 1.1.0.2/32 next-hop 10.0.0.1
user@R1# set routing-options static route 1.1.0.1/32 next-hop 10.0.0.1
user@R1# set routing-options static route 1.1.0.3/32 next-hop 10.0.0.1
user@R1# set routing-options static route 1.1.0.4/32 next-hop 10.0.0.1
user@R1# set routing-options static route 1.1.0.5/32 next-hop 10.0.0.1
user@R1# set routing-options static route 1.1.0.6/32 next-hop 10.0.0.1

Copyright © 2017, Juniper Networks, Inc. 143

Protocol-Independent Routing Properties Feature Guide

user@R1# set routing-options static route 1.1.0.7/32 next-hop 10.0.0.1

user@R1# set routing-options static route 1.1.0.8/32 next-hop 10.0.0.1
user@R1# set routing-options static route 1.1.0.9/32 next-hop 10.0.0.1

6. Configure the autonomous system (AS) identifier.

[edit]
user@R1# set routing-options autonomous-system 65500

7. If you are done configuring the device, commit the configuration.

[edit]
user@R1# commit

Configuring Device R2

To configure Device R2:

1. Configure the interfaces, including multiple routes that can be injected into the
network for demonstration purposes.

[edit interfaces]
user@R2# set fe-1/2/0 unit 14 family inet address 10.0.0.14/30
user@R2# set fe-1/2/1 unit 18 family inet address 10.0.0.18/30
user@R2# set fe-1/2/2 unit 21 family inet address 10.0.0.21/30;

user@R2# set lo0 unit 3 family inet address 2.2.2.2/32

2. Configure BGP.

[edit]
user@R2# set protocols bgp export send-local
user@R2# set protocols bgp group int type internal
user@R2# set protocols bgp group int local-address 2.2.2.2
user@R2# set protocols bgp group int family inet unicast
user@R2# set protocols bgp group int family inet-vpn unicast
user@R2# set protocols bgp group int neighbor 1.1.1.1

3. Configure OSPF.

[edit]
user@R2# set protocols ospf area 0.0.0.0 interface fe-1/2/0.14
user@R2# set protocols ospf area 0.0.0.0 interface fe-1/2/1.18
user@R2# set protocols ospf area 0.0.0.0 interface lo0.3

4. Configure the routing policies.

[edit]

144 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

user@R2# set policy-options policy-statement send-local from protocol local

user@R2# set policy-options policy-statement send-local from protocol direct
user@R2# set policy-options policy-statement send-local then accept

5. Configure the AS identifier.

[edit]
user@R2# set routing-options autonomous-system 65500

6. Enable indirect next hops in the forwarding plane.

[edit]
user@R2# set routing-options forwarding-table indirect-next-hop

7. If you are done configuring the device, commit the configuration.

[edit]
user@R2# commit

Results

Device R0 user@R0# show interfaces

fe-1/2/0 {
unit 1 {
family inet {
address 10.0.0.1/30;
}
}
}
lo0 {
unit 1 {
family inet {
address 1.1.0.1/32;
address 1.1.0.2/32;
address 1.1.0.3/32;
address 1.1.0.4/32;
address 1.1.0.5/32;
address 1.1.0.6/32;
address 1.1.0.7/32;
address 1.1.0.8/32;
address 1.1.0.9/32;
}
}
}

user@R0# show routing-options

static {
route 0.0.0.0/0 next-hop 10.0.0.2;
}

Copyright © 2017, Juniper Networks, Inc. 145

Protocol-Independent Routing Properties Feature Guide

Device R1 user@R1# show interfaces

fe-1/2/0 {
unit 2 {
family inet {
address 10.0.0.2/30;
}
}
}
fe-1/2/1 {
unit 5 {
family inet {
address 10.0.0.5/30;
}
}
}
fe-1/2/2 {
unit 9 {
family inet {
address 10.0.0.9/30;
}
}
}
lo0 {
unit 2 {
family inet {
address 1.1.1.1/32;
}
}
}

user@R1# show protocols

bgp {
export [ send-local send-static ];
group int {
type internal;
local-address 1.1.1.1;
neighbor 2.2.2.2;
}
}
ospf {
area 0.0.0.0 {
interface fe-1/2/1.5;
interface fe-1/2/2.9;
interface lo0.2;
}
}

user@R1# show policy-options

policy-statement send-local {
from protocol [ local direct ];
then accept;
}
policy-statement send-static {
from protocol static;
then accept;
}

146 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

user@R1# show routing-options

static {
route 1.1.0.2/32 next-hop 10.0.0.1;
route 1.1.0.1/32 next-hop 10.0.0.1;
route 1.1.0.3/32 next-hop 10.0.0.1;
route 1.1.0.4/32 next-hop 10.0.0.1;
route 1.1.0.5/32 next-hop 10.0.0.1;
route 1.1.0.6/32 next-hop 10.0.0.1;
route 1.1.0.7/32 next-hop 10.0.0.1;
route 1.1.0.8/32 next-hop 10.0.0.1;
route 1.1.0.9/32 next-hop 10.0.0.1;
}
autonomous-system 65500;

Device R2 user@R2# show interfaces

fe-1/2/0 {
unit 14 {
family inet {
address 10.0.0.14/30;
}
}
}
fe-1/2/1 {
unit 18 {
family inet {
address 10.0.0.18/30;
}
}
}
fe-1/2/2 {
unit 21 {
family inet {
address 10.0.0.21/30
}
}
}
lo0 {
unit 3 {
family inet {
address 2.2.2.2/32;
}
}
}

user@R2# show protocols

bgp {
export send-local;
group int {
type internal;
local-address 2.2.2.2;
family inet {
unicast;
}
family inet-vpn {
unicast;

Copyright © 2017, Juniper Networks, Inc. 147

Protocol-Independent Routing Properties Feature Guide

}
neighbor 1.1.1.1;
}
}
ospf {
area 0.0.0.0 {
interface fe-1/2/0.14;
interface fe-1/2/1.18;
interface lo0.3;
}
}

user@R2# show policy-options

policy-statement send-local {
from protocol [ local direct ];
then accept;
}

user@R2# show routing-options

autonomous-system 65500;
forwarding-table {
indirect-next-hop;
}

Configure Device R3, Device R4, and Device R5, as shown in “CLI Quick Configuration” on
page 140.

Verification
Confirm that the configuration is working properly.

Verifying That the Routes Have the Expected Indirect-Next-Hop Flag

Purpose Make sure that Device R2 is configured to maintain the indirect next hop to forwarding
next-hop binding on the Packet Forwarding Engine forwarding table.

148 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

Action user@R2> show krt indirect-next-hop

show krt indirect-next-hop
Indirect Nexthop:
Index: 1048575 Protocol next-hop address: 10.255.3.1
RIB Table: __mpls-oam__.mpls.0
Label: Swap 299968
Policy Version: 0 References: 1
Locks: 2 0x95bc514
Flags: 0x3
INH Session ID: 0xa
INH Version ID: 1
Ref RIB Table: unknown
Next hop: 50.50.244.9 via ge-2/0/2.0
Label operation: Swap 299968, Push 299792(top)
Label TTL action: no-prop-ttl, no-prop-ttl(top)
Session Id: 0x9
IGP FRR Interesting proto count : 0

Meaning The 0x3 flag in the output indicates that Device R2 is configured to maintain the indirect
next hop to forwarding next-hop binding on the Packet Forwarding Engine forwarding
table. When the indirect-next-hop statement is deleted or deactivated from the
configuration, this flag changes to 0x2. Junos MX series routers with Trio Modular Port
Concentrator (MPC) chipset supports indirect-next-hop by default and can not be
disabled. Thus, even if indirect-next-hop is not configured under forwarding-options, the
feature will work by default. Thus, 0x3 flag is not applicable for Trio Modular Port
Concentrator (MPCs).

NOTE: The show krt indirect-next-hop command is hidden and is therefore

undocumented. The show krt indirect-next-hop command is shown here
because this is the only command that verifies the indirect next-hop feature.
The best verification method is, of course, monitoring network performance
during reconvergence after a path failure.

Related • Understanding Indirect Next Hops on page 138

Documentation

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 destination’s 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 packet’s 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

Copyright © 2017, Juniper Networks, Inc. 149

Protocol-Independent Routing Properties Feature Guide

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.

Related • Example: Configuring Unicast Reverse-Path-Forwarding Check on page 150

Documentation

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 150

• Overview on page 150
• Configuration on page 151
• Verification on page 157

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

150 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

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 B’s 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 19 on page 151 shows the sample network.

Figure 19: Unicast RPF Sample Topoolgy

D E

10.0.0.18 10.0.0.22

10.0.0.17 10.0.0.21
10.0.0.1 10.0.0.2 10.0.0.9 10.0.0.10
A B C
10.0.0.5 10.0.0.6 10.0.0.13 10.0.0.14
10.0.0.29 10.0.0.25 10.0.0.26 10.0.0.30

g041186
Configuration

Device A 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
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

Copyright © 2017, Juniper Networks, Inc. 151

Protocol-Independent Routing Properties Feature Guide

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

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

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.

152 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

[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

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

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

Copyright © 2017, Juniper Networks, Inc. 153

Protocol-Independent Routing Properties Feature Guide

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 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;
}
}
}

154 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

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 © 2017, Juniper Networks, Inc. 155

Protocol-Independent Routing Properties Feature Guide

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

156 Copyright © 2017, Juniper Networks, Inc.

Chapter 7: Configuring Packet Forwarding Behavior for Protocol-Independent Routing

Verification
Confirm that the configuration is working properly.

• Confirm That Unicast RPF Is Enabled on page 157

• Confirm That the Source Addresses Are Blocked on page 157
• Confirm That the Source Addresses Are Unblocked on page 158

Confirm That Unicast RPF Is Enabled

Purpose Make sure that the interfaces on Device B have unicast RPF enabled.

Action 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

Meaning The uRPF flag confirms that unicast RPF is enabled on this interface.

Confirm That the Source Addresses Are Blocked

Purpose Use the ping command to make sure that Device B blocks traffic from unexpected source
addresses.

Copyright © 2017, Juniper Networks, Inc. 157

Protocol-Independent Routing Properties Feature Guide

Action From Device A, ping Device B’s 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.

Confirm That the Source Addresses Are Unblocked

Purpose Use the ping command to make sure that Device B does not block traffic when the RPF
check is deactivated.

Action 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 As expected, the ping operation succeeds.

Related • Understanding Unicast Reverse Path Forwarding on page 149

Documentation

158 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 8

Configuring Martian Addresses

• Understanding Martian Addresses on page 159

• Example: Configuring Class E Martian Addresses for Routing on page 160

Understanding Martian Addresses

Martian addresses are host or network addresses about which all routing information is
ignored. When received by the routing device, these routes are ignored. They commonly
are sent by improperly configured systems on the network and have destination addresses
that are obviously invalid.

In IPv6, the loopback address and the multicast resolve and discard routes are the default
martian addresses.

In Junos OS Release 10.4R5 and later, the reserved IPv6 multicast address space (ff00::/8
and ff02::/16) is added to the list of martian addresses.

In Junos OS Release 9.6 and later, you can configure Class E addresses on interfaces.
Class E addresses are treated like any other unicast address for the purpose of forwarding.
To allow Class E addresses to be configured on interfaces, you must remove the Class
E prefix from the list of martian addresses. To remove the Class E prefix from the list of
martian addresses include the martians 240/4 orlonger allow statement at the [edit
routing-options] hierarchy level.

To view the default and configured martian routes, run the show route martians command.

IPv4 Martian Addresses

user@host> show route martians table inet.

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

Copyright © 2017, Juniper Networks, Inc. 159

Protocol-Independent Routing Properties Feature Guide

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

IPv6 Martian Addresses

user@host> show route martians table inet6
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

Related • Example: Configuring Class E Martian Addresses for Routing on page 160
Documentation

Example: Configuring Class E Martian Addresses for Routing

This example shows how to remove the Class E prefix from the list of martian addresses.

• Requirements on page 161

• Overview on page 161
• Configuration on page 161
• Verification on page 162

160 Copyright © 2017, Juniper Networks, Inc.

Chapter 8: Configuring Martian Addresses

Requirements
No special configuration beyond device initialization is required before configuring this
example.

Overview
In this example, Junos OS defaults are modified to allow the 240.0.0.0/4 address block.
This block of addresses is known as the experimental Class E addresses. In Junos OS
Release 9.6 and later, you can configure Class E addresses on interfaces and use them
for forwarding traffic. However, to do this, you must first allow routing on this address
block.

This example also shows how to modify the martian addresses in the IPv6 routing table,
inet6.0.

Configuration

set routing-options rib inet.1 martians 240.0.0.0/4 orlonger allow

set routing-options rib inet6.0 martians fd00::/8 orlonger
set routing-options rib inet.3 martians 240.0.0.0/4 orlonger allow
set routing-options rib inet.2 martians 240.0.0.0/4 orlonger allow
set routing-options martians 240.0.0.0/4 orlonger allow

To configure martian routes:

1. Allow Class E addresses in the default unicast routing table.

[edit routing-options]
user@host# set martians 240.0.0.0/4 orlonger allow

2. Allow Class E addresses in the routing table that is used for the IPv4 multicast
forwarding cache.

[edit routing-options]
user@host# set rib inet.1 martians 240.0.0.0/4 orlonger allow

3. Allow Class E addresses in the routing table that is used for multicast reverse path
forwarding (RPF) lookup.

[edit routing-options]
user@host# set rib inet.2 martians 240.0.0.0/4 orlonger allow

Copyright © 2017, Juniper Networks, Inc. 161

Protocol-Independent Routing Properties Feature Guide

4. Allow Class E addresses in the routing table that stores MPLS LSP information.

[edit routing-options]
user@host# set rib inet.3 martians 240.0.0.0/4 orlonger allow

5. Add a disallowed martian route to the IPv6 unicast routing table.

[edit routing-options]
user@host# set rib inet6.0 martians fd00::/8 orlonger

6. If you are done configuring the device, commit the configuration.

[edit]
user@host# commit

Results

user@host# show routing-options

rib inet.1 {
martians {
240.0.0.0/4 orlonger allow;
}
}
rib inet6.0 {
martians {
fd00::/8 orlonger;
}
}
rib inet.3 {
martians {
240.0.0.0/4 orlonger allow;
}
}
rib inet.2 {
martians {
240.0.0.0/4 orlonger allow;
}
}
martians {
240.0.0.0/4 orlonger allow;
}

Verification
Confirm that the configuration is working properly.

• Verifying That the 240.0.0.0/4 Routes Are Now Accepted on page 163
• Verifying That the fd00::/8 Routes Are Now Rejected on page 163

162 Copyright © 2017, Juniper Networks, Inc.

Chapter 8: Configuring Martian Addresses

Verifying That the 240.0.0.0/4 Routes Are Now Accepted

Purpose Make sure that the 240.0.0.0/4 route appears in the routing tables as allowed.

Action user@host> show route martians table inet.

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

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 -- allowed
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 -- allowed
224.0.0.0/4 exact -- disallowed
224.0.0.0/24 exact -- disallowed

Meaning The output shows that the 240.0.0.0/4 route is allowed.

Verifying That the fd00::/8 Routes Are Now Rejected

Purpose Make sure that the fd00::/8 route appears in the IPv6 unicast routing table as disallowed.

Copyright © 2017, Juniper Networks, Inc. 163

Protocol-Independent Routing Properties Feature Guide

Action user@host> show route martians table inet6.0

inet6.0:
::1/128 exact -- disallowed
ff00::/8 exact -- disallowed
ff02::/16 exact -- disallowed
fd00::/8 orlonger -- disallowed

Meaning The output shows that the fd00::/8 route is disallowed.

Related • Understanding Martian Addresses on page 159

Documentation
• Example: Creating an Interface on a Logical System

• Example: Configuring an OSPF Default Route Policy on Logical Systems

164 Copyright © 2017, Juniper Networks, Inc.

PART 3

Troubleshooting
• Troubleshooting Network Issues on page 167
• Debugging and Trace Operations on page 177

Copyright © 2017, Juniper Networks, Inc. 165

Protocol-Independent Routing Properties Feature Guide

166 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 9

Troubleshooting Network Issues

• Working with Problems on Your Network on page 167

• Isolating a Broken Network Connection on page 168
• Identifying the Symptoms of a Broken Network Connection on page 173
• Isolating the Causes of a Network Problem on page 174
• Taking Appropriate Action for Resolving the Network Problem on page 175
• Evaluating the Solution to Check Whether the Network Problem Is Resolved on page 175

Working with Problems on Your Network

Problem Description: This checklist provides links to troubleshooting basics, an example network,
and includes a summary of the commands you might use to diagnose problems with the
router and network.

Table 4: Checklist for Working with Problems on Your Network

Solution

Tasks Command or Action

“Isolating a Broken Network Connection” on page 168

1. Identifying the Symptoms of a Broken Network Connection on ping (ip-address | hostname)
page 169 show route (ip-address | hostname)
traceroute (ip-address | hostname)

2. Isolating the Causes of a Network Problem on page 170 show < configuration | interfaces | protocols | route >

3. Taking Appropriate Action for Resolving the Network Problem [edit]

on page 171 delete routing options static route destination-prefix
commit and-quit
show route destination-prefix

4. Evaluating the Solution to Check Whether the Network Problem show route (ip-address | hostname)
Is Resolved on page 172 ping (ip-address | hostname) count 3
traceroute (ip-address | hostname)

Copyright © 2017, Juniper Networks, Inc. 167

Protocol-Independent Routing Properties Feature Guide

Isolating a Broken Network Connection

By applying the standard four-step process illustrated in Figure 20 on page 168, you can
isolate a failed node in the network. Note that the functionality described in this section
is not supported in versions 15.1X49, 15.1X49-D30, or 15.1X49-D40.

Figure 20: Process for Diagnosing Problems in Your Network

Before you embark on the four-step process, however, it is important that you are prepared
for the inevitable problems that occur on all networks. While you might find a solution
to a problem by simply trying a variety of actions, you can reach an appropriate solution
more quickly if you are systematic in your approach to the maintenance and monitoring
of your network. To prepare for problems on your network, understand how the network
functions under normal conditions, have records of baseline network activity, and carefully
observe the behavior of your network during a problem situation.

Figure 21 on page 168 shows the network topology used in this topic to illustrate the process
of diagnosing problems in a network.

Figure 21: Network with a Problem

AS 65001 AS 65002
Aggregate Routes:
100.100.1.0/24
100.100.2.0/24
100.100.3.0/24
lo0: .1 100.100.4.0/24 lo0: .2 lo0: .3

so-0/0/0–.12.2 so-0/0/1–.23.1
R1 R2 R3
so-0/0/0–.12.1 so-0/0/1–.23.2

so-0/0/1–.15.1 so-0/0/2–.26.1 so-0/0/3–.36.1

so-0/0/1–.15.2

so-0/0/2–.26.2 so-0/0/3–.36.2
R5 R6
g003255

lo0: .5 lo0: .6

I-BGP
Key:
so-0/0/X: 10.1.x.x/30 E-BGP
lo0: 10.0.0.x/32

The network in Figure 21 on page 168 consists of two autonomous systems (ASs). AS
65001 includes two routers, and AS 65002 includes three routers. The border router (R1)
in AS 65001 announces aggregated prefixes 100.100/24 to the AS 65002 network. The

168 Copyright © 2017, Juniper Networks, Inc.

Chapter 9: Troubleshooting Network Issues

problem in this network is that R6 does not have access to R5 because of a loop between
R2 and R6.

To isolate a failed connection in your network, follow these steps:

1. Identifying the Symptoms of a Broken Network Connection on page 169

2. Isolating the Causes of a Network Problem on page 170

3. Taking Appropriate Action for Resolving the Network Problem on page 171

4. Evaluating the Solution to Check Whether the Network Problem Is Resolved on page 172

Identifying the Symptoms of a Broken Network Connection

Problem Description: The symptoms of a problem in your network are usually quite obvious, such
as the failure to reach a remote host.

Solution To identify the symptoms of a problem on your network, start at one end of your network
and follow the routes to the other end, entering all or one of the following Junos OS
command-line interfaces (CLI) operational mode commands:

user@host> ping (ip-address | host-name)

user@host> show route (ip-address | host-name)
user@host> traceroute (ip-address | host-name)

Sample Output
user@R6> ping 10.0.0.5
PING 10.0.0.5 (10.0.0.5): 56 data bytes
36 bytes from 10.1.26.1: Time to live exceeded
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 e2db 0 0000 01 01 a8c6 10.1.26.2 10.0.0.5

36 bytes from 10.1.26.1: Time to live exceeded

Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 e2de 0 0000 01 01 a8c3 10.1.26.2 10.0.0.5

36 bytes from 10.1.26.1: Time to live exceeded

Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 e2e2 0 0000 01 01 a8bf 10.1.26.2 10.0.0.5

^C
--- 10.0.0.5 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

user@R6> show route 10.0.0.5

inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[IS-IS/165] 00:02:39, metric 10

> to 10.1.26.1 via so-0/0/2.0

user@R6> traceroute 10.0.0.5

traceroute to 10.0.0.5 (10.0.0.5), 30 hops max, 40 byte packets
1 10.1.26.1 (10.1.26.1) 0.649 ms 0.521 ms 0.490 ms
2 10.1.26.2 (10.1.26.2) 0.521 ms 0.537 ms 0.507 ms

Copyright © 2017, Juniper Networks, Inc. 169

Protocol-Independent Routing Properties Feature Guide

3 10.1.26.1 (10.1.26.1) 0.523 ms 0.536 ms 0.514 ms

4 10.1.26.2 (10.1.26.2) 0.528 ms 0.551 ms 0.523 ms
5 10.1.26.1 (10.1.26.1) 0.531 ms 0.550 ms 0.524 ms

Meaning

The sample output shows an unsuccessful ping command in which the packets are being
rejected because the time to live is exceeded. The output for the show route command
shows the interface (10.1.26.1) that you can examine further for possible problems. The
traceroute command shows the loop between 10.1.26.1 (R2) and 10.1.26.2 (R6), as indicated
by the continuous repetition of the two interface addresses.

Isolating the Causes of a Network Problem

Problem Description: A particular symptom can be the result of one or more causes. Narrow down
the focus of your search to find each individual cause of the unwanted behavior.

Solution To isolate the cause of a particular problem, enter one or all of the following Junos OS
CLI operational mode command:

Your particular problem may require the use of more than just the commands listed
above. See the appropriate command reference for a more exhaustive list of commonly
used operational mode commands.

Sample Output
user@R6> show interfaces terse
Interface Admin Link Proto Local Remote
so-0/0/0 up up
so-0/0/0.0 up up inet 10.1.56.2/30
iso
so-0/0/2 up up
so-0/0/2.0 up up inet 10.1.26.2/30
iso
so-0/0/3 up up
so-0/0/3.0 up up inet 10.1.36.2/30
iso
[...Output truncated...]

The following sample output is from R2:

user@R2> show route 10.0.0.5

inet.0: 22 destinations, 25 routes (22 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[Static/5] 00:16:21

> to 10.1.26.2 via so-0/0/2.0
[BGP/170] 3d 20:23:35, MED 5, localpref 100
AS path: 65001 I
> to 10.1.12.1 via so-0/0/0.0

170 Copyright © 2017, Juniper Networks, Inc.

Chapter 9: Troubleshooting Network Issues

Meaning

The sample output shows that all interfaces on R6 are up. The output from R2 shows
that a static route [Static/5] configured on R2 points to R6 (10.1.26.2) and is the preferred
route to R5 because of its low preference value. However, the route is looping from R2
to R6, as indicated by the missing reference to R5 (10.1.15.2).

Taking Appropriate Action for Resolving the Network Problem

Problem Description: The appropriate action depends on the type of problem you have isolated.
In this example, a static route configured on R2 is deleted from the [routing-options]
hierarchy level. Other appropriate actions might include the following:

Solution • Check the local router’s configuration and edit it if appropriate.

• Troubleshoot the intermediate router.

• Check the remote host configuration and edit it if appropriate.

• Troubleshoot routing protocols.

• Identify additional possible causes.

To resolve the problem in this example, enter the following Junos OS CLI commands:

[edit]
user@R2# delete routing-options static route destination-prefix
user@R2# commit and-quit
user@R2# show route destination-prefix

Sample Output
[edit]
user@R2# delete routing-options static route 10.0.0.5/32

[edit]
user@R2# commit and-quit
commit complete
Exiting configuration mode

user@R2> show route 10.0.0.5

inet.0: 22 destinations, 24 routes (22 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[BGP/170] 3d 20:26:17, MED 5, localpref 100

AS path: 65001 I
> to 10.1.12.1 via so-0/0/0.0

Meaning

The sample output shows the static route deleted from the [routing-options] hierarchy
and the new configuration committed. The output for the show route command now
shows the BGP route as the preferred route, as indicated by the asterisk (*).

Copyright © 2017, Juniper Networks, Inc. 171

Protocol-Independent Routing Properties Feature Guide

Evaluating the Solution to Check Whether the Network Problem Is Resolved

Problem Description: If the problem is solved, you are finished. If the problem remains or a new
problem is identified, start the process over again.
You can address possible causes in any order. In relation to the network in “Isolating a
Broken Network Connection” on page 168, we chose to work from the local router toward
the remote router, but you might start at a different point, particularly if you have reason
to believe that the problem is related to a known issue, such as a recent change in
configuration.

Solution To evaluate the solution, enter the following Junos OS CLI commands:

user@host> show route (ip-address |host-name)

user@host> ping (ip-address | host-name)
user@host> traceroute (ip-address | host-name)

Sample Output
user@R6> show route 10.0.0.5

inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[BGP/170] 00:01:35, MED 5, localpref 100, from 10.0.0.2

AS path: 65001 I
> to 10.1.26.1 via so-0/0/2.0

user@R6> ping 10.0.0.5

PING 10.0.0.5 (10.0.0.5): 56 data bytes
64 bytes from 10.0.0.5: icmp_seq=0 ttl=253 time=0.866 ms
64 bytes from 10.0.0.5: icmp_seq=1 ttl=253 time=0.837 ms
64 bytes from 10.0.0.5: icmp_seq=2 ttl=253 time=0.796 ms
^C
--- 10.0.0.5 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.796/0.833/0.866/0.029 ms

user@R6> traceroute 10.0.0.5

traceroute to 10.0.0.5 (10.0.0.5), 30 hops max, 40 byte packets
1 10.1.26.1 (10.1.26.1) 0.629 ms 0.538 ms 0.497 ms
2 10.1.12.1 (10.1.12.1) 0.534 ms 0.538 ms 0.510 ms
3 10.0.0.5 (10.0.0.5) 0.776 ms 0.705 ms 0.672 ms

Meaning

The sample output shows that there is now a connection between R6 and R5. The show
route command shows that the BGP route to R5 is preferred, as indicated by the asterisk
(*). The ping command is successful and the traceroute command shows that the path
from R6 to R5 is through R2 (10.1.26.1), and then through R1 (10.1.12.1).

172 Copyright © 2017, Juniper Networks, Inc.

Chapter 9: Troubleshooting Network Issues

Identifying the Symptoms of a Broken Network Connection

Problem Description: The symptoms of a problem in your network are usually quite obvious, such
as the failure to reach a remote host.

user@host> ping (ip-address | host-name)

user@host> show route (ip-address | host-name)
user@host> traceroute (ip-address | host-name)

36 bytes from 10.1.26.1: Time to live exceeded

Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 e2de 0 0000 01 01 a8c3 10.1.26.2 10.0.0.5

36 bytes from 10.1.26.1: Time to live exceeded

Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 0054 e2e2 0 0000 01 01 a8bf 10.1.26.2 10.0.0.5

^C
--- 10.0.0.5 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

user@R6> show route 10.0.0.5

inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[IS-IS/165] 00:02:39, metric 10

> to 10.1.26.1 via so-0/0/2.0

user@R6> traceroute 10.0.0.5

traceroute to 10.0.0.5 (10.0.0.5), 30 hops max, 40 byte packets
1 10.1.26.1 (10.1.26.1) 0.649 ms 0.521 ms 0.490 ms
2 10.1.26.2 (10.1.26.2) 0.521 ms 0.537 ms 0.507 ms
3 10.1.26.1 (10.1.26.1) 0.523 ms 0.536 ms 0.514 ms
4 10.1.26.2 (10.1.26.2) 0.528 ms 0.551 ms 0.523 ms
5 10.1.26.1 (10.1.26.1) 0.531 ms 0.550 ms 0.524 ms

Meaning

Copyright © 2017, Juniper Networks, Inc. 173

Protocol-Independent Routing Properties Feature Guide

traceroute command shows the loop between 10.1.26.1 (R2) and 10.1.26.2 (R6), as indicated
by the continuous repetition of the two interface addresses.

Isolating the Causes of a Network Problem

Problem Description: A particular symptom can be the result of one or more causes. Narrow down
the focus of your search to find each individual cause of the unwanted behavior.

Solution To isolate the cause of a particular problem, enter one or all of the following Junos OS
CLI operational mode command:

Your particular problem may require the use of more than just the commands listed
above. See the appropriate command reference for a more exhaustive list of commonly
used operational mode commands.

The following sample output is from R2:

user@R2> show route 10.0.0.5

inet.0: 22 destinations, 25 routes (22 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[Static/5] 00:16:21

> to 10.1.26.2 via so-0/0/2.0
[BGP/170] 3d 20:23:35, MED 5, localpref 100
AS path: 65001 I
> to 10.1.12.1 via so-0/0/0.0

Meaning

174 Copyright © 2017, Juniper Networks, Inc.

Chapter 9: Troubleshooting Network Issues

Taking Appropriate Action for Resolving the Network Problem

Solution • Check the local router’s configuration and edit it if appropriate.

• Troubleshoot the intermediate router.

• Check the remote host configuration and edit it if appropriate.

• Troubleshoot routing protocols.

• Identify additional possible causes.

To resolve the problem in this example, enter the following Junos OS CLI commands:

[edit]
user@R2# delete routing-options static route destination-prefix
user@R2# commit and-quit
user@R2# show route destination-prefix

Sample Output
[edit]
user@R2# delete routing-options static route 10.0.0.5/32

[edit]
user@R2# commit and-quit
commit complete
Exiting configuration mode

user@R2> show route 10.0.0.5

inet.0: 22 destinations, 24 routes (22 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[BGP/170] 3d 20:26:17, MED 5, localpref 100

AS path: 65001 I
> to 10.1.12.1 via so-0/0/0.0

Meaning

Evaluating the Solution to Check Whether the Network Problem Is Resolved

Problem Description: If the problem is solved, you are finished. If the problem remains or a new
problem is identified, start the process over again.

Copyright © 2017, Juniper Networks, Inc. 175

Protocol-Independent Routing Properties Feature Guide

You can address possible causes in any order. In relation to the network in “Isolating a
Broken Network Connection” on page 168, we chose to work from the local router toward
the remote router, but you might start at a different point, particularly if you have reason
to believe that the problem is related to a known issue, such as a recent change in
configuration.

Solution To evaluate the solution, enter the following Junos OS CLI commands:

user@host> show route (ip-address |host-name)

user@host> ping (ip-address | host-name)
user@host> traceroute (ip-address | host-name)

Sample Output
user@R6> show route 10.0.0.5

inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.5/32 *[BGP/170] 00:01:35, MED 5, localpref 100, from 10.0.0.2

AS path: 65001 I
> to 10.1.26.1 via so-0/0/2.0

user@R6> ping 10.0.0.5

user@R6> traceroute 10.0.0.5

Meaning

176 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 10

Debugging and Trace Operations

• Understanding Global Routing Protocol Tracing Operations on page 177

• Example: Tracing Global Routing Protocol Operations on page 178

Understanding Global Routing Protocol Tracing Operations

Global routing protocol tracing operations track all general routing operations and record
them in a log file. To set protocol-specific tracing operations and to modify the global
tracing operations for an individual protocol, configure tracing for that protocol.

Using the traceoptions statement, you can specify the following global routing protocol
tracing flags:

• all—All tracing operations

• condition-manager—Condition manager events

• config-internal—Configuration internals

• general—All normal operations and routing table changes (a combination of the normal
and route trace operations)

• graceful-restart—Graceful restart operations

• normal—All normal operations

• nsr-synchronization—Nonstop routing synchronization events

• parse—Configuration parsing

• policy—Policy operations and actions

• regex-parse—Regular expression parsing

• route—Routing table changes

• state—State transitions

• task—Interface transactions and processing

• timer—Timer usage

Copyright © 2017, Juniper Networks, Inc. 177

Protocol-Independent Routing Properties Feature Guide

NOTE: Use the all flag with caution. This flag might cause the CPU to become
very busy.

Related • Example: Tracing Global Routing Protocol Operations on page 178

Documentation
• Junos OS Administration Library

Example: Tracing Global Routing Protocol Operations

This example shows how to list and view files that are created when you enable global
routing trace operations.

• Requirements on page 178

• Overview on page 178
• Configuration on page 179
• Verification on page 182

Requirements
You must have the view privilege.

Overview
To configure global routing protocol tracing, include the traceoptions statement at the
[edit routing-options] hierarchy level:

traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <disable>;
}

The flags in a traceoptions flag statement are identifiers. When you use the set command
to configure a flag, any flags that might already be set are not modified. In the following
example, setting the timer tracing flag has no effect on the already configured task flag.
Use the delete command to delete a particular flag.

[edit routing-options traceoptions]

user@host# show
flag task;
user@host# set traceoptions flag timer
user@host# show
flag task;
flag timer;
user@host# delete traceoptions flag task
user@host# show
flag timer;

This example shows how to configure and view a trace file that tracks changes in the
routing table. The steps can be adapted to apply to trace operations for any Junos OS
hierarchy level that supports trace operations.

178 Copyright © 2017, Juniper Networks, Inc.

Chapter 10: Debugging and Trace Operations

TIP: To view a list of hierarchy levels that support tracing operations, enter
the help apropos traceoptions command in configuration mode.

Configuration

set routing-options traceoptions file routing-table-changes

set routing-options traceoptions file size 10m
set routing-options traceoptions file files 10
set routing-options traceoptions flag route
set routing-options static route 1.1.1.2/32 next-hop 10.0.45.6

Configuring Trace Operations

To configure the trace operations:

1. Configure trace operations.

[edit routing-options traceoptions]

user@host# set file routing-table-changes
user@host# set file size 10m
user@host# set file files 10
user@host# set flag route

2. Configure a static route to cause a change in the routing table.

[edit routing-options static]

user@host# set route 1.1.1.2/32 next-hop 10.0.45.6

3. If you are done configuring the device, commit the configuration.

[edit]
user@host# commit

Copyright © 2017, Juniper Networks, Inc. 179

Protocol-Independent Routing Properties Feature Guide

Viewing the Trace File

Step-by-Step To view the trace file:

Procedure
1. In operational mode, list the log files on the system.

user@host> file list /var/log

/var/log:
...
routing-table-changes
...

2. View the contents of the routing-table-changes file.

user@host> file show /var/log/routing-table-changes

Dec 15 11:09:29 trace_on: Tracing to "/var/log/routing-table-changes" started
Dec 15 11:09:29.496507
Dec 15 11:09:29.496507 Tracing flags enabled: route
Dec 15 11:09:29.496507
Dec 15 11:09:29.533203 inet_routerid_notify: Router ID: 192.168.4.1
Dec 15 11:09:29.533334 inet_routerid_notify: No Router ID assigned
Dec 15 11:09:29.533381 inet_routerid_notify: No Router ID assigned
Dec 15 11:09:29.533420 inet_routerid_notify: No Router ID assigned
Dec 15 11:09:29.534915 inet_routerid_notify: Router ID: 192.168.4.1
Dec 15 11:09:29.542934 inet_routerid_notify: No Router ID assigned
Dec 15 11:09:29.549253 inet_routerid_notify: No Router ID assigned
Dec 15 11:09:29.556878 inet_routerid_notify: No Router ID assigned
Dec 15 11:09:29.582990 rt_static_reinit: examined 3 static nexthops, 0
unreferenced
Dec 15 11:09:29.589920
Dec 15 11:09:29.589920 task_reconfigure reinitializing done
...

3. Filter the output of the log file.

user@host> file show /var/log/routing-table-changes | match 1.1.1.2

Dec 15 11:15:30.780314 ADD 1.1.1.2/32 nhid 0 gw 10.0.45.6
Static pref 5/0 metric at-0/2/0.0 <ctive Int Ext>
Dec 15 11:15:30.782276 KRT Request: send len 216 v104 seq 0 ADD route/user
af 2 table 0 infot 0 addr 1.1.1.2 nhop-type unicast nhindex 663

4. View the tracing operations in real time by running the monitor start command with
an optional match condition.

user@host> monitor start routing-table-changes | match 1.1.1.2

Aug 10 19:21:40.773467 BGP RECV 0.0.0.0/0
Aug 10 19:21:40.773685 bgp_rcv_nlri: 0.0.0.0/0
Aug 10 19:21:40.773778 bgp_rcv_nlri: 0.0.0.0/0 belongs to meshgroup
Aug 10 19:21:40.773832 bgp_rcv_nlri: 0.0.0.0/0 qualified bnp->ribact 0x0
l2afcb 0x0

5. Deactivate the static route.

user@host# deactivate routing-options static route 1.1.1.2/32

user@host# commit

180 Copyright © 2017, Juniper Networks, Inc.

Chapter 10: Debugging and Trace Operations

* routing-table-changes *

Dec 15 11:42:59.355557 CHANGE 1.1.1.2/32 nhid 663 gw 10.0.45.6
Static pref 5/0 metric at-0/2/0.0 <Delete Int Ext>
Dec 15 11:42:59.426887 KRT Request: send len 216 v104 seq 0 DELETE route/user
af 2 table 0 infot 0 addr 1.1.1.2 nhop-type discard filtidx 0
Dec 15 11:42:59.427366 RELEASE 1.1.1.2/32 nhid 663 gw 10.0.45.6
Static pref 5/0 metric at-0/2/0.0 <Release Delete Int Ext>

6. Halt the monitor command by pressing Enter and typing monitor stop.

[Enter]
user@host> monitor stop

7. When you are finished troubleshooting, consider deactivating trace logging to avoid
any unnecessary impact to system resources.

When configuration is deactivated, it appears in the configuration with the inactive

tag.

[edit routing-options]
user@host# deactivate traceoptions
user@host# commit

[edit routing-options]
user@host# show

inactive: traceoptions {
file routing-table-changes size 10m files 10;
flag route;
}
static {
inactive: route 1.1.1.2/32 next-hop 10.0.45.6;
}

8. To reactivate trace operations, use the activate configuration-mode statement.

[edit routing-options]
user@host# activate traceoptions
user@host# commit

Results

From configuration mode, confirm your configuration by entering the show routing-options
command. If the output does not display the intended configuration, repeat the
instructions in this example to correct the configuration.

user@host# show routing-options

traceoptions {
file routing-table-changes size 10m files 10;
flag route;
}
static {
route 1.1.1.2/32 next-hop 10.0.45.6;
}

Copyright © 2017, Juniper Networks, Inc. 181

Protocol-Independent Routing Properties Feature Guide

Verification
Confirm that the configuration is working properly.

Verifying That the Trace Log File Is Operating

Purpose Make sure that events are being written to the log file.

Action user@host> show log routing-table-changes

Dec 15 11:09:29 trace_on: Tracing to "/var/log/routing-table-changes" started

Related • Understanding Global Routing Protocol Tracing Operations on page 177

Documentation
• CLI Explorer

182 Copyright © 2017, Juniper Networks, Inc.

PART 4

Configuration Statements and

Operational Commands
• Configuration Statements on page 185
• Operational Commands on page 311

Copyright © 2017, Juniper Networks, Inc. 183

Protocol-Independent Routing Properties Feature Guide

184 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 11

Configuration Statements

• access (Static Access Routes) on page 188

• access-internal (Static Access-Internal Routes) on page 189
• active on page 190
• aggregate (Routing) on page 192
• as-path (Routing Options) on page 194
• auto-export on page 196
• autonomous-system on page 198
• bfd on page 201
• bfd-liveness-detection (Routing Options Static Route) on page 203
• brief on page 207
• color on page 209
• community (Routing Options) on page 211
• confederation on page 213
• destination-networks on page 214
• disable (Routing Options) on page 215
• discard on page 216
• dynamic-tunnels on page 217
• export (Routing Options) on page 218
• export-rib on page 219
• fate-sharing on page 222
• filter on page 223
• firewall-install-disable on page 224
• flow on page 225
• forwarding-table on page 226
• full on page 227
• generate on page 228
• graceful-restart (Enabling Globally) on page 230
• import on page 231

Copyright © 2017, Juniper Networks, Inc. 185

Protocol-Independent Routing Properties Feature Guide

• import-policy on page 232

• import-rib on page 233
• independent-domain on page 234
• indirect-next-hop on page 235
• indirect-next-hop-change-acknowledgements on page 236
• input (Routing Options RIB) on page 237
• install (Routing Options) on page 238
• instance-export on page 239
• instance-import on page 239
• interface (Multicast Scoping) on page 240
• interface (Multicast Static Routes) on page 241
• interface-routes on page 243
• krt-nexthop-ack-timeout on page 245
• longest-match (Static Routes) on page 246
• lsp-next-hop (Static Routes) on page 248
• martians on page 249
• maximum-paths on page 251
• maximum-prefixes on page 253
• med-igp-update-interval on page 255
• metric on page 255
• metric (Aggregate, Generated, or Static Route) on page 256
• metric (Qualified Next Hop on Static Route) on page 257
• multicast (Routing Options) on page 258
• next-hop (Access) on page 259
• next-hop (Access Internal) on page 259
• no-delegate-processing on page 260
• nonstop-routing on page 261
• options (Routing Options) on page 262
• p2mp-ldp-next-hop on page 263
• p2mp-lsp-next-hop on page 264
• passive (Routing Options) on page 264
• policy (Aggregate and Generated Routes) on page 265
• ppm on page 267
• precision-timers-max-period on page 268
• preference (Access) on page 268
• preference (Routing Options) on page 269
• prefix on page 270

186 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

• qualified-next-hop (Access) on page 271

• qualified-next-hop (Access-Internal) on page 271
• qualified-next-hop (Static Routes) on page 272
• readvertise on page 274
• resolution on page 275
• resolution-ribs on page 277
• resolve on page 278
• restart-duration on page 279
• restart-duration (Routing Options) on page 280
• retain on page 281
• rib (General) on page 283
• rib (Route Resolution) on page 285
• rib-group (Routing Options) on page 286
• rib-groups on page 287
• route (Access) on page 289
• route (Access-Internal) on page 289
• route-distinguisher-id on page 290
• route-record on page 291
• router-id on page 292
• routing-options on page 293
• scope on page 294
• source-address (Routing Options) on page 295
• source-routing on page 296
• ssm-groups on page 297
• static (Routing Options) on page 298
• tag (Access) on page 304
• tag (Routing Options) on page 305
• threshold (Multicast Forwarding Cache) on page 306
• traceoptions on page 308
• unicast-reverse-path on page 310

Copyright © 2017, Juniper Networks, Inc. 187

Protocol-Independent Routing Properties Feature Guide

access (Static Access Routes)

Syntax access {
route ip-prefix</prefix-length> {
metric route-cost;
next-hop next-hop;
preference route-distance;
qualified-next-hop next-hop;
tag tag-number
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure access routes.

The remaining statements are explained separately.

Required Privilege routing—To view this statement in the configuration.

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

188 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

access-internal (Static Access-Internal Routes)

Syntax access-internal {
route ip-prefix</prefix-length> {
next-hop next-hop;
qualified-next-hop next-hop
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure parameters for internal access routes.

The remaining statements are explained separately.

Required Privilege routing—To view this statement in the configuration.

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

Related • Configuring Dynamic Access-Internal Routes for DHCP Subscriber Management

Documentation
• Configuring Dynamic Access-Internal Routes for PPP Subscriber Management

Copyright © 2017, Juniper Networks, Inc. 189

Protocol-Independent Routing Properties Feature Guide

active

Syntax (active | passive);

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Determine whether static, aggregate, or generated routes are removed from the routing
and forwarding tables when they become inactive. Static routes are only removed from
the routing table if the next hop becomes unreachable. This can occur if the local or
neighbor interface goes down. Routes that have been configured to remain continually
installed in the routing and forwarding tables are marked with reject next hops when they
are inactive.

• active—Remove a route from the routing and forwarding tables when it becomes
inactive.

• passive—Have a route remain continually installed in the routing and forwarding tables
even when it becomes inactive.

Include the active statement when configuring an individual route in the route portion of
the static statement to override a passive option specified in the defaults portion of the
statement.

Default active

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation

190 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

• Example: Configuring a Conditional Default Route Policy

Copyright © 2017, Juniper Networks, Inc. 191

Protocol-Independent Routing Properties Feature Guide

aggregate (Routing)

Syntax aggregate {
defaults {
... aggregate-options ...
}
route destination-prefix {
policy policy-name;
... aggregate-options ...
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options rib routing-table-name],
[edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-options rib routing-table-name],
[edit routing-instances routing-instance-name routing-options],
[edit routing-instances routing-instance-name routing-options rib routing-table-name],
[edit routing-options],
[edit routing-options rib routing-table-name]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure aggregate routes.

Options aggregate-options—Additional information about aggregate routes that is included with

the route when it is installed in the routing table. Specify zero or more of the following
options in aggregate-options. Each option is explained separately.

• active(— Removes inactive routes from the forwarding table.

• passive— Retains inactive routes in the forwarding table.

• as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate>

<aggregator as-number ip-address>;

• (brief | full);

• community [ community-ids ];

• discard;

• (metric | metric2 | metric3 | metric4) value <type type>;

• (preference | preference2 | color | color2) preference <type type>;

• tag metric type number;

192 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

defaults—Specify global aggregate route options. These options only set default attributes
inherited by all newly created aggregate routes. These are treated as global defaults
and apply to all the aggregate routes you configure in the aggregate statement. This
part of the aggregate statement is optional.

route destination-prefix—Configure a nondefault aggregate route:

• default—For the default route to the destination. This is equivalent to specifying an IP

address of 0.0.0.0/0.

• destination-prefix/prefix-length—destination-prefix is the network portion of the IP

address, and prefix-length is the destination prefix length.

The policy statement is explained separately.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation

Copyright © 2017, Juniper Networks, Inc. 193

Protocol-Independent Routing Properties Feature Guide

as-path (Routing Options)

Syntax as-path <as-path> <aggregator as-number ip-address> <atomic-aggregate> <origin (egp |

igp | incomplete)>;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Associate BGP autonomous system (AS) path information with a static, aggregate, or
generated route.

In Junos OS Release 9.1 and later, the numeric range for the AS number is extended to
provide BGP support for 4-byte AS numbers as defined in RFC 4893, BGP Support for
Four-octet AS Number Space. RFC 4893 introduces two new optional transitive BGP
attributes, AS4_PATH and AS4_AGGREGATOR. These new attributes are used to
propagate 4-byte AS path information across BGP speakers that do not support 4-byte
AS numbers. RFC 4893 also introduces a reserved, well-known, 2-byte AS number, AS
23456. This reserved AS number is called AS_TRANS in RFC 4893. All releases of Junos
OS support 2-byte AS numbers.

In Junos OS Release 9.2 and later, you can also configure a 4-byte AS number using the
AS-dot notation format of two integer values 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
of 65,546 in plain-number format is represented as 1.10 in the AS-dot notation format.
You can specify a value in the range from 0.0 through 65535.65535 in AS-dot notation
format.

Default No AS path information is associated with static routes.

Options aggregator—(Optional) Attach the BGP aggregator path attribute to the aggregate route.
You must specify the last AS number that formed the aggregate route (encoded as

194 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

two octets) for as-number, followed by the IP address of the BGP system that formed
the aggregate route for ip-address.

as-path—(Optional) AS path to include with the route. It can include a combination of

individual AS path numbers and AS sets. Enclose sets in brackets ( [ ] ). The first AS
number in the path represents the AS immediately adjacent to the local AS. Each
subsequent number represents an AS that is progressively farther from the local AS,
heading toward the origin of the path. You cannot specify a regular expression for
as-path. You must use a complete, valid AS path.

atomic-aggregate—(Optional) Attach the BGP atomic-aggregate path attribute to the

aggregate route. This path attribute indicates that the local system selected a less
specific route instead of a more specific route.

origin egp—(Optional) BGP origin attribute that indicates that the path information
originated in another AS.

origin igp—(Optional) BGP origin attribute that indicates that the path information
originated within the local AS.

origin incomplete—(Optional) BGP origin attribute that indicates that the path information
was learned by some other means.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• Using 4-Byte Autonomous System Numbers in BGP Networks Technology Overview

Copyright © 2017, Juniper Networks, Inc. 195

Protocol-Independent Routing Properties Feature Guide

auto-export

Syntax auto-export {
disable;
family inet {
disable;
flow {
disable;
rib-group rib-group;
}
multicast {
disable;
rib-group rib-group;
}
unicast {
disable;
rib-group rib-group;
}
}
family inet6 {
disable;
multicast {
disable;
rib-group rib-group;
}
unicast {
disable;
rib-group rib-group;
}
}
family iso {
disable;
unicast {
disable;
rib-group rib-group;
}
}
traceoptions {
file filename <files number> <size maximum-file-size> <world-readable |
no-world-readable>;
flag flag <flag-modifier> <disable>;
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.

196 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Description Export routes between routing instances.

This statement enables you to leak routes between VPN routing and forwarding (VRF)
instances that are locally configured on a provider edge (PE) router. Auto export is always
applied on the local PE router, because it applies to only local prefix leaking by evaluating
the export policy of each VRF and determining which route targets can be leaked. The
standard VRF import and export policies affect remote PE prefix leaking.

You can use this statement as an alternative to using the VRF import and export policies.

Options (disable | enable)—Disable or enable auto-export.

Default: Enable

family—Address family.

inet—IP version 4 (IPv4) address family.

multicast—Multicast routing information.

unicast—Unicast routing information.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Technology Overview: Understanding the Auto Export Feature

Documentation

Copyright © 2017, Juniper Networks, Inc. 197

Protocol-Independent Routing Properties Feature Guide

autonomous-system

Syntax autonomous-system autonomous-system <asdot-notation> <loops number> {

independent-domain <no-attrset>;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
asdot-notation option introduced in Junos OS Release 9.3.
asdot-notation option introduced in Junos OS Release 9.3 for EX Series switches.
no-attrset option introduced in Junos OS Release 10.4.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Specify the routing device’s AS number.

An autonomous system (AS) is a set of routing devices that are under a single technical
administration and that generally use a single interior gateway protocol (IGP) and metrics
to propagate routing information within the set of routing devices. An AS appears to other
ASs to have a single, coherent interior routing plan and presents a consistent picture of
what destinations are reachable through it. ASs are identified by a number that is assigned
by the Network Information Center (NIC) in the United States (http://www.isi.edu).

If you are using BGP on the routing device, you must configure an AS number.

The AS path attribute is modified when a route is advertised to an EBGP peer. Each time
a route is advertised to an EBGP peer, the local routing device prepends its AS number
to the existing path attribute, and a value of 1 is added to the AS number.

In Junos OS Release 9.1 and later, the numeric range is extended to provide BGP support
for 4-byte AS numbers as defined in RFC 4893, BGP Support for Four-octet AS Number
Space. RFC 4893 introduces two new optional transitive BGP attributes, AS4_PATH and
AS4_AGGREGATOR. These new attributes are used to propagate 4-byte AS path
information across BGP speakers that do not support 4-byte AS numbers. RFC 4893
also introduces a reserved, well-known, 2-byte AS number, AS 23456. This reserved AS
number is called AS_TRANS in RFC 4893. All releases of Junos OS support 2-byte AS
numbers.

In Junos OS Release 9.3 and later, you can also configure a 4-byte AS number using the
AS-dot notation format of two integer values 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
of 65,546 in plain-number format is represented as 1.10 in the AS-dot notation format.

198 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Options autonomous-system—AS number. Use a number assigned to you by the NIC.

32
Range: 1 through 4,294,967,295 (2 – 1) in plain-number format for 4-byte AS numbers

In this example, the 4-byte AS number 65,546 is represented in plain-number format:

[edit]
routing-options {
autonomous-system 65546;
}
Range: 0.0 through 65535.65535 in AS-dot notation format for 4-byte numbers

In this example, 1.10 is the AS-dot notation format for 65,546:

[edit]
routing-options {
autonomous-system 1.10;
}
Range: 1 through 65,535 in plain-number format for 2-byte AS numbers (this is a subset
of the 4-byte range)

In this example, the 2-byte AS number 60,000 is represented in plain-number format:

[edit]
routing-options {
autonomous-system 60000;
}

asdot-notation—(Optional) Display the configured 4-byte autonomous system number

in the AS-dot notation format.
Default: Even if a 4-byte AS number is configured in the AS-dot notation format, the
default is to display the AS number in the plain-number format.

loops number—(Optional) Specify the number of times detection of the AS number in

the AS_PATH attribute causes the route to be discarded or hidden. For example, if
you configure loops 1, the route is hidden if the AS number is detected in the path
one or more times. This is the default behavior. If you configure loops 2, the route is
hidden if the AS number is detected in the path two or more times.
Range: 1 through 10
Default: 1

NOTE: When you specify the same AS number in more than one routing
instance on the local routing device, you must configure the same number
of loops for the AS number in each instance. For example, if you configure a
value of 3 for the loops statement in a VRF routing instance that uses the
same AS number as that of the master instance, you must also configure a
value of 3 loops for the AS number in the master instance.

Use the independent-domain option if the loops statement must be enabled

only on a subset of routing instances.

Copyright © 2017, Juniper Networks, Inc. 199

Protocol-Independent Routing Properties Feature Guide

The remaining statement is explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Examples: Configuring External BGP Peering

Documentation
• Examples: Configuring Internal BGP Peering

200 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

bfd

Syntax bfd {
traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
flag flag <flag-modifier> <disable>;
}
}

Hierarchy Level [edit logical-systems logical-system-name protocols],

[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols],
[edit protocols],
[edit routing-instances routing-instance-name protocols]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure trace options for Bidirectional Forwarding Protocol (BFD) traffic.

Default If you do not include this statement, no BFD tracing operations are performed.

Options disable—(Optional) Disable the BFD 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.

file filename—Name of the file to receive the output of the tracing operation. Enclose the
name in quotation marks. All files are placed in the /var/log directory . We recommend
that you place global routing protocol tracing output in the routing-log file.

If you specify a maximum number of files, you also must specify a maximum file size with
the size option.
Range: 2 through 1000 files
Default: 2 files

flag flag—Tracing operation to perform. To specify more than one tracing operation,
include multiple flag statements. These are the BFD protocol tracing options:

• adjacency—Trace adjacency messages.

• all—Trace all options for BFD.

• error—Trace all errors.

• event—Trace all events.

Copyright © 2017, Juniper Networks, Inc. 201

Protocol-Independent Routing Properties Feature Guide

• issu—Trace in-service software upgrade (ISSU) packet activity.

• nsr-packet—Trace non-stop-routing (NSR) packet activity.

• nsr-synchronization—Trace NSR synchronization events.

• packet—Trace all packets.

• pipe—Trace pipe messages.

• pipe-detail—Trace pipe messages in detail.

• ppm-packet—Trace packet activity by periodic packet management (PPM).

• state—Trace state transitions.

• timer—Trace timer processing.

match regular-expression—(Optional) Regular expression for lines to be logged.

no-world-readable—(Optional) Prevent any user from reading the log file.

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 KB, xm to specify MB, or xg to specify GB
Range: 10 KB through the maximum file size supported on your system
Default: 128 KB

world-readable—(Optional) Allow any user to read the log file.

Required Privilege routing and trace—To view this statement in the configuration.
Level routing-control and trace–control—To add this statement to the configuration.

Related • Example: Configuring BFD for Static Routes for Faster Network Failure Detection on
Documentation page 116

202 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

bfd-liveness-detection (Routing Options Static Route)

Syntax bfd-liveness-detection {
description Site- xxx;
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
holddown-interval milliseconds;
local-address ip-address;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
minimum-receive-ttl number;
multiplier number;
neighbor address;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options rib routing-table-name static route destination-prefix],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options rib routing-table-name static route destination-prefix qualified-next-hop
(interface-name | address)],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options static route destination-prefix],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options static route destination-prefix qualified-next-hop (interface-name |
address)],
[edit logical-systems logical-system-name routing-options rib routing-table-name static
route destination-prefix],
[edit logical-systems logical-system-name routing-options rib routing-table-name static
route destination-prefix qualified-next-hop (interface-name | address)],
[edit logical-systems logical-system-name routing-options static route destination-prefix],
[edit logical-systems logical-system-name routing-options static route destination-prefix
qualified-next-hop (interface-name | address)],
[edit routing-instances routing-instance-name routing-options rib routing-table-name static
route destination-prefix],
[edit routing-instances routing-instance-name routing-options rib routing-table-name static
route destination-prefix qualified-next-hop (interface-name | address)],
[edit routing-instances routing-instance-name routing-options static route destination-prefix],
[edit routing-instances routing-instance-name routing-options static route destination-prefix
qualified-next-hop (interface-name | address)],
[edit routing-options rib routing-table-name static route destination-prefix],
[edit routing-options rib routing-table-name static route destination-prefix qualified-next-hop
(interface-name | address)],

Copyright © 2017, Juniper Networks, Inc. 203

Protocol-Independent Routing Properties Feature Guide

[edit routing-options static route destination-prefix],

[edit routing-options static route destination-prefix qualified-next-hop (interface-name |
address)]

Release Information Statement introduced before Junos OS Release 7.4.

detection-time threshold and transmit-interval threshold options introduced in Junos OS
Release 8.2.
local-address statement introduced in Junos OS Release 8.2.
minimum-receive-ttl statement introduced in Junos OS Release 8.2.
Support for logical routers introduced in Junos OS Release 8.3.
holddown-interval statement introduced in Junos OS Release 8.5.
no-adaptation statement introduced in Junos OS Release 9.0.
Support for IPv6 static routes introduced in Junos OS Release 9.1.
authentication algorithm, authentication key-chain, and authentication loose-check
statements introduced in Junos OS Release 9.6.
Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Configure bidirectional failure detection timers and authentication criteria for static
routes.

204 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Options authentication algorithm algorithm-name —Configure the algorithm used to authenticate

the specified BFD session: simple-password, keyed-md5, keyed-sha-1,
meticulous-keyed-md5, or meticulous-keyed-sha-1.

authentication key-chain key-chain-name—Associate a security key with the specified

BFD session using the name of the security keychain. The name you specify must
match one of the keychains configured in the authentication-key-chains key-chain
statement at the [edit security] hierarchy level.

authentication loose-check—(Optional) Configure loose authentication checking on the

BFD session. Use only for transitional periods when authentication may not be
configured at both ends of the BFD session.

detection-time threshold milliseconds—Configure a threshold for the adaptation of the

BFD session detection time. When the detection time adapts to a value equal to or
greater than the threshold, a single trap and a single system log message are sent.

holddown-interval milliseconds—Configure an interval specifying how long a BFD session

must remain up before a state change notification is sent. If the BFD session goes
down and then comes back up during the hold-down interval, the timer is restarted.
Range: 0 through 255,000
Default: 0

local-address ip-address—Enable a multihop BFD session and configure the source address
for the BFD session.

minimum-interval milliseconds—Configure the minimum interval after which the local

routing device transmits a hello packet and then expects to receive a reply from the
neighbor with which it has established a BFD session. Optionally, instead of using
this statement, you can configure the minimum transmit and receive intervals
separately using the transmit-interval minimum-interval and minimum-receive-interval
statements.
Range: 1 through 255,000

minimum-receive-interval milliseconds—Configure the minimum interval after which the

routing device expects to receive a reply from a neighbor with which it has established
a BFD session. Optionally, instead of using this statement, you can configure the
minimum receive interval using the minimum-interval statement at the [edit
routing-options static route destination-prefix bfd-liveness-detection] hierarchy level.
Range: 1 through 255,000

minimum-receive-ttl number—Configure the time to live (TTL) for the multihop BFD
session.
Range: 1 through 255
Default: 255

multiplier number—Configure number of hello packets not received by the neighbor that
causes the originating interface to be declared down.
Range: 1 through 255
Default: 3

Copyright © 2017, Juniper Networks, Inc. 205

Protocol-Independent Routing Properties Feature Guide

neighbor address—Configure a next-hop address for the BFD session for a next hop
specified as an interface name.

no-adaptation—Specify for BFD sessions not to adapt to changing network conditions.

We recommend that you not disable BFD adaptation unless it is preferable not to
have BFD adaptation enabled in your network.

transmit-interval threshold milliseconds—Configure the threshold for the adaptation of

the BFD session transmit interval. When the transmit interval adapts to a value
greater than the threshold, a single trap and a single system message are sent. The
interval threshold must be greater than the minimum transmit interval.
Range: 0 through 4,294,967,295

transmit-interval minimum-interval milliseconds—Configure the minimum interval at which

the routing device transmits hello packets to a neighbor with which it has established
a BFD session. Optionally, instead of using this statement, you can configure the
minimum transmit interval using the minimum-interval statement at the [edit
routing-options static route destination-prefix bfd-liveness-detection] hierarchy level.
Range: 1 through 255,000

version—Configure the BFD version to detect: 1 (BFD version 1) or automatic (autodetect

the BFD version).
Default: automatic

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring BFD for Static Routes for Faster Network Failure Detection on
Documentation page 116

• Example: Configuring BFD Authentication for Securing Static Routes on page 124

206 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

brief

Syntax (brief | full);

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options (aggregate | generate) (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options rib routing-table-name (aggregate | generate) (defaults | route)],
[edit logical-systems logical-system-name routing-options (aggregate | generate) (defaults |
route)],
[edit logical-systems logical-system-name routing-options rib routing-table-name (aggregate |
generate) (defaults | route)],
[edit routing-instances routing-instance-name routing-options (aggregate | generate)
(defaults | route)],
[edit routing-instances routing-instance-name routing-options rib routing-table-name
(aggregate | generate) (defaults | route)],
[edit routing-options (aggregate | generate) (defaults | route)],
[edit routing-options rib routing-table-name (aggregate | generate) (defaults | route)]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure all AS numbers from all contributing paths to be included in the aggregate or
generated route’s path.

• brief—Include only the longest common leading sequences from the contributing AS
paths. If this results in AS numbers being omitted from the aggregate route, the BGP
ATOMIC_ATTRIBUTE path attribute is included with the aggregate route.

• full—Include all AS numbers from all contributing paths in the aggregate or generated
route’s path. Include this option when configuring an individual route in the route portion
of the generate statement to override a retain option specified in the defaults portion
of the statement.

Default full

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• Example: Configuring a Conditional Default Route Policy

• Understanding Conditionally Generated Routes

• aggregate on page 192

Copyright © 2017, Juniper Networks, Inc. 207

Protocol-Independent Routing Properties Feature Guide

• generate on page 228

208 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

color

Syntax color {
metric-value;
<type metric_type>
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Fine-grained preference value for a static, aggregate, or generated route.

You can also specify a primary route preference (by including the color statement in the
configuration), and a secondary preference that is used as a tiebreaker (by including the
color2 statement). You can also mark route preferences with additional route tiebreaker
information by specifying a primary route preference and a tiebreaker route preference
(by including the preference and preference2 statements in the configuration).

If the Junos OS routing table contains a dynamic route to a destination that has a better
(lower) preference value than the static, aggregate, or generated route, the dynamic
route is chosen as the active route and is installed in the forwarding table.

Options metric_value—The metric value for an aggregate, a generated, or a static route.

32
Range: 0 through 4,294,967,295 (2 – 1)

type metric_type—(Optional) External metric type for routes exported by OSPF. When
routes are exported to OSPF, type 1 routes are advertised in type 1 externals, and
routes of any other type are advertised in type 2 externals. Note that if a
qualified-next-hop metric value is configured, this value overrides the route metric.
Range: 1 through 16

Copyright © 2017, Juniper Networks, Inc. 209

Protocol-Independent Routing Properties Feature Guide

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• aggregate on page 192

• generate on page 228

• static on page 298

• preference on page 269

210 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

community (Routing Options)

Syntax community ([ community-ids ] | no-advertise | no-export | no-export-subconfed | none |

llgr-stale | no-llgr);

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

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.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
llgr-stale and no-llgr options added in Junos OS Release 15.1.
Support for BGP large community introduced in Junos OS Release 17.3 for MX Series,
PTX Series, and QFX Series.

Description Associate BGP community information with a static, aggregate, or generated route.

NOTE: BGP large community is available only for static route.

Default No BGP community information is associated with static routes.

Options community-ids—One or more community identifiers. The community-ids format varies

according to the type of attribute that you use.

The BGP community attribute format is as-number:community-value:

• as-number—AS number of the community member. It can be a value from 1

through 65,535. The AS number can be a decimal or hexadecimal value.

• community-value—Identifier of the community member. It can be a number from 0

through 65,535.

Copyright © 2017, Juniper Networks, Inc. 211

Protocol-Independent Routing Properties Feature Guide

For more information about BGP community attributes, see the “Configuring the Extended
Communities Attribute” section in the Routing Policies, Firewall Filters, and Traffic
Policers Feature Guide.

For specifying the BGP community attribute only, you also can specify community-ids as
one of the following well-known community names defined in RFC 1997:

• no-advertise—Routes containing this community name are not advertised to other

BGP peers.

• no-export—Routes containing this community name are not advertised outside a BGP
confederation boundary.

• no-export-subconfed—Routes containing this community are advertised to IBGP peers

with the same AS number, but not to members of other confederations.

• llgr-stale—Adds a community to a long-lived stale route when it is readvertised.

• no-llgr—Marks routes which a BGP speaker does not want to be retained by LLGR. The
Notification message feature does not have any associated configuration parameters.

NOTE: Extended community attributes are not supported at the [edit

As defined in RFC 8092, BGP large community uses 12-byte encoding and the format for
BGP large community-ids is:

large: global-administrator:assigned-number:assigned-number

large indicates BGP large community.

global-administrator is the administrator. It is a 4-byte AS number.

assigned-number is a 4-byte value used to identify the local provider. BGP large community
uses two 4-byte assigned number to identify the local provider.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• aggregate on page 192

• generate on page 228

• static on page 298

212 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

confederation

Syntax confederation confederation-autonomous-system members [ autonomous-systems ];

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify the routing device’s confederation AS number.

If you administer multiple ASs that contain a very large number of BGP systems, you can
group them into one or more confederations. Each confederation is identified by its own
AS number, which is called a confederation AS number. To external ASs, a confederation
appears to be a single AS. Thus, the internal topology of the ASs making up the
confederation is hidden.

The BGP path attributes NEXT_HOP, LOCAL_PREF, and MULTI_EXIT_DISC, which normally
are restricted to a single AS, are allowed to be propagated throughout the ASs that are
members of the same confederation.

Because each confederation is treated as if it were a single AS, you can apply the same
routing policy to all the ASs that make up the confederation.

Grouping ASs into confederations reduces the number of BGP connections required to
interconnect ASs.

If you are using BGP, you can enable the local routing device to participate as a member
of an AS confederation. To do this, include the confederation statement.

Specify the AS confederation identifier, along with the peer AS numbers that are members
of the confederation.

Note that peer adjacencies do not form if two BGP neighbors disagree about whether
an adjacency falls within a particular confederation.

Options autonomous-systems—AS numbers of the confederation members.

Range: 1 through 65,535

confederation-autonomous-system—Confederation AS number. Use one of the numbers

assigned to you by the NIC.
Range: 1 through 65,535

Copyright © 2017, Juniper Networks, Inc. 213

Protocol-Independent Routing Properties Feature Guide

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring BGP Confederations

Documentation
• Understanding BGP Confederations

destination-networks

Syntax destination-networks prefix;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options dynamic-tunnels tunnel-name],
[edit logical-systems logical-system-name routing-options dynamic-tunnels tunnel-name
rsvp-te entry],
[edit logical-systems logical-system-name routing-options dynamic-tunnels tunnel-name],
[edit routing-instances routing-instance-name routing-options dynamic-tunnels tunnel-name],
[edit routing-instances routing-instance-name routing-options dynamic-tunnels tunnel-name
rsvp-te entry],
[edit routing-options dynamic-tunnels tunnel-name],
[edit routing-options dynamic-tunnels tunnel-name rsvp-te entry]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Specify the IPv4 prefix range for the destination network. Only tunnels within the specified
IPv4 prefix range can be created.

Options prefix—Destination prefix of the network.

Required Privilege routing—To view this statement in the configuration.

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

Related • Configuring GRE Tunnels for Layer 3 VPNs

Documentation
• Configuring Dynamic Tunnels

• Configuring RSVP Automatic Mesh

214 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

disable (Routing Options)

Syntax disable;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options graceful-restart],
[edit logical-systems logical-system-name routing-options graceful-restart],
[edit routing-instances routing-instance-name routing-options graceful-restart],
[edit routing-options graceful-restart]

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.3 for ACX Series routers.

Description Disable graceful restart.

Required Privilege routing—To view this statement in the configuration.

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

Related • Junos OS High Availability Library for Routing Devices

Documentation

Copyright © 2017, Juniper Networks, Inc. 215

Protocol-Independent Routing Properties Feature Guide

discard

Syntax discard;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Do not forward packets addressed to this destination. Instead, drop the packets, do not
send ICMP unreachable messages to the packets’ originators, and install a reject route
for this destination into the routing table.

To propagate static routes into the routing protocols, include the discard statement when
you define the route, along with a routing policy.

NOTE: In other vendors’ software, a common way to propagate static routes

into routing protocols is to configure the routes so that the next-hop routing
device is the loopback address (commonly, 127.0.0.1). However, configuring
static routes in this way (by including a statement such as route
address/mask-length next-hop 127.0.0.1) does not propagate the static routes,
because the forwarding table ignores static routes whose next-hop routing
device is the loopback address.

Default When an aggregate route becomes active, it is installed in the routing table with a reject
next hop, which means that ICMP unreachable messages are sent.

Required Privilege routing—To view this statement in the configuration.

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

216 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• aggregate on page 192

• generate on page 228

dynamic-tunnels

Syntax dynamic-tunnels tunnel-name {

destination-networks prefix;
gre;
rsvp-te entry-name {
destination-networks network-prefix;
label-switched-path-template (Multicast) {
default-template;
template-name;
}
}
source-address address;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure a dynamic tunnel between two PE routers.

NOTE: ACX Series routers do not support the gre statement.

Options tunnel-name—Name of the dynamic tunnel.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring a Two-Tiered Virtualized Data Center for Large Enterprise Networks
Documentation

Copyright © 2017, Juniper Networks, Inc. 217

Protocol-Independent Routing Properties Feature Guide

export (Routing Options)

Syntax export [ policy-name ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options forwarding-table],
[edit logical-systems logical-system-name routing-options forwarding-table],
[edit routing-instances routing-instance-name routing-options forwarding-table],
[edit routing-options forwarding-table]

Release Information Statement introduced before Junos OS Release 7.4.

Description Apply one or more policies to routes being exported from the routing table into the
forwarding table.

In the export statement, list the name of the routing policy to be evaluated when routes
are being exported from the routing table into the forwarding table. Only active routes
are exported from the routing table.

You can reference the same routing policy one or more times in the same or a different
export statement.

You can apply export policies to routes being exported from the routing table into the
forwarding table for the following features:

• Per-packet load balancing

• Class of service (CoS)

Options policy-name—Name of one or more policies.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Load Balancing BGP Traffic

Documentation

218 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

export-rib

Syntax export-rib routing-table-name;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options rib-groups group-name],
[edit logical-systems logical-system-name routing-options rib-groups group-name],
[edit routing-instances routing-instance-name routing-options rib-groups group-name],
[edit routing-options rib-groups group-name]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Specify the name of the routing table from which Junos OS should export routing
information. For any individual RIB group, only one table can be specified in the export-rib
statement.

The export-rib statement specifies the source table from which routing information is
advertised.

One common use of the export-rib statement is interdomain routing. The export RIB is
the table used when BGP extracts routes to advertise to peers. In multicast interdomain
routing, for example, the export RIB is likely to be inet.2.

Another use of export-rib is dynamic route leaking between the global routing table
(inet.0) and a VRF routing table (instance.inet.0). For example, you can use a RIB group
to copy routes learned in the VRF into the global routing table, inet.0, or copy routes
learned in inet.0 into a VRF. You define the use of this RIB group in the VRF’s BGP
configuration. In a routing policy you can do dynamic filtering of routes. For instance, you
can use an import policy to only copy routes with certain communities into the global
routing table.

For example:

rib-groups {
rib-interface-routes-v4 {
import-rib [ inet.0 VRF.inet.0 ];
}
rib-import-VRF-routes-to-inet0-v4 {
export-rib VRF.inet.0;
import-rib [ VRF.inet.0 inet.0 ];
import-policy rib-import-VRF-routes-to-inet0-v4;
}
rib-import-inet0-routes-to-VRF-v4 {
export-rib inet.0;
import-rib [ inet.0 VRF.inet.0 ];
import-policy rib-import-inet0-routes-to-VRF-v4;
}
}

Copyright © 2017, Juniper Networks, Inc. 219

Protocol-Independent Routing Properties Feature Guide

routing-options {
interface-routes {
rib-group {
inet rib-interface-routes-v4;
}
}
}
protocols {
bgp {
group iBGP-peers {
type internal;
family inet {
unicast {
rib-group rib-import-inet0-routes-to-VRF-v4;
}
}
}
}
}
routing-instances {
VRF {
routing-options {
interface-routes {
rib-group {
inet rib-interface-routes-v4;
}
}
}
protocols {
bgp {
group peersin-VRF {
family inet {
unicast {
rib-group rib-import-VRF-routes-to-inet0-v4;
}
}
}
}
}
}
}

Options routing-table-name—Routing table group name.

Required Privilege routing—To view this statement in the configuration.

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

220 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Related • Example: Exporting Specific Routes from One Routing Table Into Another Routing
Documentation Table on page 58

• Example: Configuring a PIM RPF Routing Table

• Example: Configuring DVMRP to Announce Unicast Routes

• Example: Configuring a Dedicated PIM RPF Routing Table

• Example: Configuring Any-Source Multicast for Draft-Rosen VPNs

• import-rib on page 233

• passive on page 264

Copyright © 2017, Juniper Networks, Inc. 221

Protocol-Independent Routing Properties Feature Guide

fate-sharing

Syntax fate-sharing {
group group-name {
cost value;
from address <to address>;
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options],
[edit routing-options],
[edit routing-instances routing-instance-name routing-options]

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.3 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Specify a backup path in case the primary path becomes unusable.

You specify one or more objects with common characteristics within a group. All objects
are treated as /32 host addresses. The objects can be a LAN interface, a router ID, or a
point-to-point link. Sequence is insignificant.

Changing the fate-sharing database does not affect existing established LSPs until the
next CSPF reoptimization. The fate-sharing database does affect fast-reroute detour
path computations.

Options cost value—Cost assigned to the group.

Range: 1 through 65,535
Default: 1

from address—Address of the router or address of the LAN/NBMA interface. For example,
an Ethernet network with four hosts in the same fate-sharing group would require
you to list all four of the separate from addresses in the group.

group group-name—Each fate-sharing group must have a name, which can have a
maximum of 32 characters, including letters, numbers, periods (.), and hyphens (-).
You can define up to 512 groups.

to address—(Optional) Address of egress router. For point-to-point link objects, you must
specify both a from and a to address.

Required Privilege routing—To view this statement in the configuration.

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

222 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Related • Configuring the Ingress Router for MPLS-Signaled LSPs

Documentation
• MPLS Applications Feature Guide

filter

Syntax filter {
input filter-name;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options rib routing-table-name],
[edit logical-systems logical-system-name routing-options rib routing-table-name],
[edit routing-instances routing-instance-name routing-options rib routing-table-name],
[edit routing-options rib routing-table-name]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify the name of the routing table from which Junos OS should export routing
information.

Options input filter-name—Forwarding table filter name.

Required Privilege routing—To view this statement in the configuration.

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

Related • Configuring Forwarding Table Filters

Documentation
• Applying Forwarding Table Filters

Copyright © 2017, Juniper Networks, Inc. 223

Protocol-Independent Routing Properties Feature Guide

firewall-install-disable

Syntax firewall-install-disable;

Hierarchy Level [edit routing-options flow],

[edit logical-systems logical-system-name routing-options flow],
[edit routing-instances routing-instance-name routing-options flow],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options flow]

Release Information Statement introduced in Junos OS Releases 12.1X48 and 12.3.

Description Disable installing flow-specification firewall filters in the firewall process (dfwd).

Default For PTX Series routers, this statement appears in the default configuration, preventing
installation of flow-specification firewall filters into dfwd. For other models, this setting
is omitted from the default configuration, allowing installation of flow-specification
firewall filters into dfwd.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Enabling BGP to Carry Flow-Specification Routes

Documentation
• Understanding BGP Flow Routes for Traffic Filtering

224 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

flow

Syntax flow {
route name {
match {
match-conditions;
}
term-order (legacy | standard);
then {
actions;
}
}
firewall-install-disable;
term-order (legacy | standard);
validation {
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
}
}
}

Hierarchy Level [edit routing-options],

[edit routing-instances routing-instance-name routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
term-order statement introduced in Junos OS Release 10.0
Statement introduced in Junos OS Release 11.3 for the QFX Series.
firewall-install-disable statement introduced in Junos OS Releases 12.1X48 and 12.3 for
PTX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Configure a flow route.

Default legacy

Options actions—An action to take if conditions match.

firewall-install-disable—(PTX Series routers only) Disable installing flow-specification

firewall filters in the firewall process (dfwd).
Default: For PTX Series routers, the firewall-install-disable statement appears in the
default configuration, preventing installation of flow-specification firewall filters into
dfwd. For other models, this setting is omitted from the default configuration, allowing
installation of flow-specification firewall filters into dfwd.

match-conditions—Match packets to these conditions.

route name—Name of the flow route.

Copyright © 2017, Juniper Networks, Inc. 225

Protocol-Independent Routing Properties Feature Guide

standard—Specify to use version 7 or later of the flow-specification algorithm.

term-order (legacy | standard)—Specify the version of the flow-specification algorithm.

• legacy—Use version 6 of the flow-specification algorithm.

• standard—Use version 7 of the flow-specification algorithm.

then—Actions to take on matching packets.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Enabling BGP to Carry Flow-Specification Routes

Documentation
• Understanding BGP Flow Routes for Traffic Filtering

forwarding-table

Syntax forwarding-table {
chained-composite-next-hop;
export [ policy-name ];
(indirect-next-hop | no-indirect-next-hop);
(indirect-next-hop-change-acknowledgements |
no-indirect-next-hop-change-acknowledgements;)
krt-nexthop-ack-timeout interval;
unicast-reverse-path (active-paths | feasible-paths);
}

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit routing-options]

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 14.1X53-D30 for the QFX Series.

Description Configure information about the routing device’s forwarding table.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Load Balancing BGP Traffic

Documentation

226 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

full

See brief

Copyright © 2017, Juniper Networks, Inc. 227

Protocol-Independent Routing Properties Feature Guide

generate

Syntax generate {
defaults {
generate-options;
}
route destination-prefix {
policy policy-name;
generate-options;
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options rib routing-table-name],
[edit routing-options],
[edit routing-options rib routing-table-name]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure generated routes, which are used as routes of last resort.

Options defaults—(Optional) Specify global generated route options. These options only set
default attributes inherited by all newly created generated routes. These are treated
as global defaults and apply to all the generated routes you configure in the generate
statement.

generate-options—Additional information about generated routes, which is included with

the route when it is installed in the routing table. Specify zero or more of the following
options in generate-options. Each option is explained separately.

• (active | passive);

• as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> <aggregator

as-number in-address>;

• (brief | full);

• community [ community-ids ];

• discard;

• (metric | metric2 | metric3 | metric4) value <type type>;

• (preference | preference2 | color | color2) preference <type type>;

• tag metric type number;

route destination-prefix—Configure a non-default generated route:

228 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

• default—For the default route to the destination. This is equivalent to specifying an IP

address of 0.0.0.0/0.

• destination-prefix/prefix-length—/destination-prefix is the network portion of the IP

address, and prefix-length is the destination prefix length.

The policy statement is explained separately.

Required Privilege routing—To view this statement in the configuration.

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

Copyright © 2017, Juniper Networks, Inc. 229

Protocol-Independent Routing Properties Feature Guide

graceful-restart (Enabling Globally)

Syntax graceful-restart {
disable;
helper-disable;
maximum-helper-recovery-time seconds;
maximum-helper-restart-time seconds;
notify-duration seconds;
recovery-time seconds;
restart-duration seconds;
stale-routes-time seconds;
}

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options],
[edit routing-options],
[edit routing-instances routing-instance-name routing-options]

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.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description You configure the graceful restart routing option globally to enable the feature, but not
to enable graceful restart for all routing protocols in a routing instance. Because all routing
protocols are not usually run on every routing instance, you must also configure graceful
restart for individual routing protocols running on a routing instance, including the main
routing instance. You can, optionally, modify the global settings at the individual protocol
level.

NOTE:
• For VPNs, the graceful-restart statement allows a router whose VPN control
plane is undergoing a restart to continue to forward traffic while recovering
its state from neighboring routers.

• For BGP, if you configure graceful restart after a BGP session has been
established, the BGP session restarts and the peers negotiate graceful
restart capabilities.

• LDP sessions flap when graceful-restart configurations change.

Default Graceful restart is disabled by default.

Options The remaining statements are explained separately. See CLI Explorer.

230 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Required Privilege routing—To view this statement in the configuration.

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

Related • Enabling Graceful Restart

Documentation
• Configuring Routing Protocols Graceful Restart

• Configuring Graceful Restart for MPLS-Related Protocols

• Configuring VPN Graceful Restart

• Configuring Logical System Graceful Restart

• Configuring Graceful Restart for QFabric Systems

import

Syntax import [ policy-names ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options resolution rib],
[edit logical-systems logical-system-name routing-options resolution rib],
[edit routing-instances routing-instance-name routing-options resolution rib],
[edit routing-options resolution rib]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify one or more import policies to use for route resolution.

Options policy-names—Name of one or more import policies.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Route Resolution on PE Routers

Documentation

Copyright © 2017, Juniper Networks, Inc. 231

Protocol-Independent Routing Properties Feature Guide

import-policy

Syntax import-policy [ policy-names ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Apply one or more policies to routes imported into the routing table group. The
import-policy statement complements the import-rib statement and cannot be used
unless you first specify the routing tables to which routes are being imported.

NOTE: On EX Series switches, only dynamically learned routes can be

imported from one routing table group to another.

Options policy-names—Name of one or more policies.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Exporting Specific Routes from One Routing Table Into Another Routing
Documentation Table on page 58

• export-rib on page 219

• passive on page 264

232 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

import-rib

Syntax import-rib [ routing-table-names ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify the name of the routing table into which Junos OS should import routing
information. The first routing table name you enter is the primary routing table. Any
additional names you enter identify secondary routing tables. When a protocol imports
routes, it imports them into the primary and any secondary routing tables. If the primary
route is deleted, the secondary route also is deleted. For IPv4 import routing tables, the
primary routing table must be inet.0 or routing-instance-name.inet.0. For IPv6 import
routing tables, the primary routing table must be inet6.0.

In Junos OS Release 9.5 and later, you can configure an IPv4 import routing table that
includes both IPv4 and IPv6 routing tables. Including both types of routing tables permits
you, for example, to populate an IPv6 routing table with IPv6 addresses that are
compatible with IPv4. In releases prior to Junos OS Release 9.5, you could configure an
import routing table with only either IPv4 or IPv6 routing tables.

NOTE: On EX Series switches, only dynamically learned routes can be

imported from one routing table group to another.

Options routing-table-names—Name of one or more routing tables.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Exporting Specific Routes from One Routing Table Into Another Routing
Documentation Table on page 58

• export-rib on page 219

• passive on page 264

Copyright © 2017, Juniper Networks, Inc. 233

Protocol-Independent Routing Properties Feature Guide

independent-domain

Syntax independent-domain <no-attrset>;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options autonomous-system autonomous-system],
[edit routing-instances routing-instance-name routing-options autonomous-system
autonomous-system]

Release Information Statement introduced before Junos OS Release 7.4.

no-attrset option introduced in Junos OS Release 10.4.

Description Configure an independent AS domain.

The independent domain uses transitive path attribute 128 (attribute set) messages to
tunnel the independent domain’s BGP attributes through the internal BGP (IBGP) core.

This improves the transparency of Layer 3 VPN services for customer networks by
preventing the IBGP routes that originate within an autonomous system (AS) in the
customer network from being sent to a service provider’s AS. Similarly, IBGP routes that
originate within an AS in the service provider’s network are prevented from being sent to
a customer AS.

NOTE: In Junos OS Release 10.3 and later, if BGP receives attribute 128 and
you have not configured an independent domain in any routing instance, BGP
treats the received attribute 128 as an unknown attribute.

NOTE: The [edit logical-systems] hierarchy level is not applicable in ACX

Series routers.

Options no-attrset—(Optional) Disables attribute set messages on the independent AS domain.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Tunneling Layer 3 VPN IPv6 Islands over an IPv4 Core Using IBGP and
Documentation Independent Domains

• Configuring Layer 3 VPNs to Carry IBGP Traffic

• autonomous-system on page 198

234 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

indirect-next-hop

Syntax (indirect-next-hop | no-indirect-next-hop);

Hierarchy Level [edit logical-systems logical-system-name routing-options forwarding-table],

[edit routing-options forwarding-table]

Release Information Statement introduced in Junos OS Release 8.2.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 14.1X53-D30 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Enable indirectly connected next hops for route convergence. This statement is
implemented on the Packet Forward Engine to speed up forwarding information base
(FIB) updates. Configuring this statement significantly speeds convergence times. The
only downside of configuring this statement is that some additional FIB memory overhead
is required. Unless routes have an extremely high number of next hops, this increased
memory usage should not be noticeable.

NOTE:
• When virtual private LAN service (VPLS) is configured on the routing device,
the indirect-next-hop statement is configurable at the [edit routing-options
forwarding-table] hierarchy level. However, this configuration is not
applicable to indirect nexthops specific to VPLS routing instances.

• By default, the Junos Trio Modular Port Concentrator (MPC) chipset on MX

Series routers is enabled with indirectly connected next hops, and this
cannot be disabled using the no-indirect-next-hop statement.

• By default, indirectly connected next hops are enabled on PTX Series

routers.

Default Disabled.

Options indirect-next-hop—Enable indirectly connected next hops.

no-indirect-next-hop—Explicitly disable indirect next hops.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the
Documentation Packet Forwarding Engine on page 139

Copyright © 2017, Juniper Networks, Inc. 235

Protocol-Independent Routing Properties Feature Guide

indirect-next-hop-change-acknowledgements

Syntax (indirect-next-hop-change-acknowledgements |
no-indirect-next-hop-change-acknowledgements);

Hierarchy Level [edit logical-systems logical-system-name routing-options forwarding-table],

[edit routing-options forwarding-table]

Release Information Statement introduced in Junos OS Release 12.2.

Description Configure the routing protocol process (rpd) to request an acknowledgement when
creating a new forwarding next hop.

During an indirect next-hop change sequence, the routing device might create a new
forwarding next hop that is referenced by the indirect next hop. If the
indirect-next-hop-change-acknowledgements statement is configured, the routing protocol
process requests an acknowledgement when creating the new forwarding next hop.
When the routing protocol process receives the acknowledgement, this indicates that
all PICs have received the new forwarding next hop and it is then safe to change the
indirect next hop to reference the new forwarding next hop. This prevents packet loss
when changing the indirect next hop by ensuring that all PICs have consistent state
information for the new forwarding next hop.

The routing protocol process is not requesting an acknowledgement for the indirect next
hop itself. Rather, the routing protocol process is requesting an acknowledgement for
the new forwarding next hop that the indirect next hop is going to reference. In the case
when the forwarding next hop is an existing one (meaning that it is already installed in
the forwarding table), the routing protocol process does not request an acknowledgement,
even if the indirect-next-hop-change-acknowledgements statement is configured.

We recommend that the indirect-next-hop-change-acknowledgements statement be

configured when protection mechanisms are being used. This includes MPLS RSVP
protection such as fast reroute (FRR) as well as interior gateway protocol (IGP) loop-free
alternate (LFA) link or node protection. If there is no protection mechanism being used
in the network, the indirect-next-hop-change-acknowledgements statement does not
provide any benefit and might increase packet loss.

Default Disabled by default in all platforms except PTX Series, where it is enabled by default.

Options indirect-next-hop-change-acknowledgements—Enable acknowledgements.

no-indirect-next-hop-change-acknowledgements—Explicitly disable acknowledgements.

Required Privilege routing—To view this statement in the configuration.

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

236 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Related • Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the
Documentation Packet Forwarding Engine on page 139

• krt-nexthop-ack-timeout on page 245

input (Routing Options RIB)

Syntax input filter-name;

Hierarchy Level [edit logical-systems logical-system-name routing-options rib routing-table-name filter],

[edit routing-options rib routing-table-name filter]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify the name of the input filter.

Options filter-name—Name of the input filter.

Required Privilege routing—To view this statement in the configuration.

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

Related • Configuring Forwarding Table Filters

Documentation
• Applying Forwarding Table Filters

Copyright © 2017, Juniper Networks, Inc. 237

Protocol-Independent Routing Properties Feature Guide

install (Routing Options)

Syntax (install | no-install);

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options static (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options rib routing-table-name static (defaults | route)],
[edit logical-systems logical-system-name routing-options rib routing-table-name static
(defaults | route)],
[edit logical-systems logical-system-name routing-options static (defaults | route)],
[edit routing-instances routing-instance-name routing-options rib routing-table-name static
(defaults | route)],
[edit routing-instances routing-instance-name routing-options static (defaults | route)],
[edit routing-options rib routing-table-name static (defaults | route)]
[edit routing-options static (defaults | route)]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure whether Junos OS installs all static routes into the forwarding table. Even if
you configure a route so it is not installed in the forwarding table, the route is still eligible
to be exported from the routing table to other protocols.

Options install—Explicitly install all static routes into the forwarding table. Include this statement
when configuring an individual route in the route portion of the static statement to
override a no-install option specified in the defaults portion of the statement.

no-install—Do not install the route into the forwarding table, even if it is the route with
the lowest preference.
Default: install

Required Privilege routing—To view this statement in the configuration.

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

Related • static on page 298

Documentation

238 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

instance-export

Syntax instance-export [ policy-names ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Description Apply one or more policies to routes being exported from a routing instance.

Options policy-names—Name of one or more export policies.

Required Privilege routing—To view this statement in the configuration.

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

Related • Routing Policies, Firewall Filters, and Traffic Policers Feature Guide
Documentation

instance-import

Syntax instance-import [ policy-names ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Description Apply one or more policies to routes being imported into a routing instance.

Options policy-names—Name of one or more import policies.

Required Privilege routing—To view this statement in the configuration.

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

Related • Routing Policies, Firewall Filters, and Traffic Policers Feature Guide
Documentation

Copyright © 2017, Juniper Networks, Inc. 239

Protocol-Independent Routing Properties Feature Guide

interface (Multicast Scoping)

Syntax interface [ interface-names ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options multicast scope scope-name],
[edit logical-systems logical-system-name routing-options multicast scope scope-name],
[edit routing-instances routing-instance-name routing-options multicast scope scope-name],
[edit routing-options multicast scope scope-name]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure the set of interfaces for multicast scoping.

Options interface-names—Names of the interfaces on which to configure scoping. Specify the full
interface name, including the physical and logical address components. To configure
all interfaces, you can specify all.

NOTE: You cannot apply a scoping policy to a specific routing instance. All
scoping policies are applied to all routing instances. However, you can apply
the scope statement to a specific routing instance.

Required Privilege routing—To view this statement in the configuration.

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

Related • Examples: Configuring Administrative Scoping

Documentation
• multicast on page 258

240 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

interface (Multicast Static Routes)

Syntax interface interface-names {

disable;
maximum-bandwidth bps;
no-qos-adjust;
reverse-oif-mapping {
no-qos-adjust;
}
subscriber-leave-timer seconds;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options multicast],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options multicast]

Release Information Statement introduced in Junos OS Release 8.1.

Description Enable multicast traffic on an interface.

By default, multicast packets are forwarded by enabling Protocol Independent Multicast

(PIM) on an interface. PIM adds multicast routes into the routing table.

You can also configure multicast packets to be forwarded over a static route, such as a
static route associated with an LSP next hop. Multicast packets are accepted on an
interface and forwarded over a static route in the forwarding table. This is useful when
you want to enable multicast traffic on a specific interface without configuring PIM on
the interface.

You cannot enable multicast traffic on an interface and configure PIM on the same
interface simultaneously.

Static routes must be configured before you can enable multicast on an interface.
Configuring the interface statement alone does not install any routes into the routing
table. This feature relies on the static route configuration.

Options interface-names—Name of one or more interfaces on which to enable multicast traffic.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Copyright © 2017, Juniper Networks, Inc. 241

Protocol-Independent Routing Properties Feature Guide

Related • Example: Defining Interface Bandwidth Maximums

Documentation
• Example: Configuring Multicast with Subscriber VLANs

242 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

interface-routes

Syntax interface-routes {
family (inet | inet6) {
export {
lan;
point-to-point;
}
}
rib-group group-name;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

NOTE: On EX Series switches, only dynamically learned routes can be

imported from one routing table group to another.

Description Associate a routing table group with the routing device’s interfaces, and specify routing
table groups into which interface routes are imported.

By default, IPv4 interface routes (also called direct routes) are imported into routing
table inet.0, and IPv6 interface routes are imported into routing table inet6.0. If you are
configuring alternate routing tables for use by some routing protocols, it might be
necessary to import the interface routes into the alternate routing tables. To define the
routing tables into which interface routes are imported, you create a routing table group
and associate it with the routing device’s interfaces.

To create the routing table groups, include the passive statement at the
[edit routing-options] hierarchy level.

If you have configured a routing table, configure the OSPF primary instance at the [edit
protocols ospf] hierarchy level with the statements needed for your network so that
routes are installed in inet.0 and in the forwarding table. Make sure to include the routing
table group.

To export local routes, include the export statement.

Copyright © 2017, Juniper Networks, Inc. 243

Protocol-Independent Routing Properties Feature Guide

To export LAN routes, include the lan option. To export point-to-point routes, include
the point-to-point option.

Only local routes on point-to-point interfaces configured with a destination address are
exportable.

Options inet—Specify the IPv4 address family.

inet6—Specify the IPv6 address family.

lan—Export LAN routes.

point-to-point—Export point-to-point routes.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Importing Direct and Static Routes Into a Routing Instance on page 53
Documentation
• Example: Configuring Multiple Routing Instances of OSPF

• passive on page 264

244 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

krt-nexthop-ack-timeout

Syntax krt-nexthop-ack-timeout interval;

Hierarchy Level [edit logical-systems logical-system-name routing-options forwarding-table],

[edit routing-options forwarding-table]

Release Information Statement introduced in Junos OS Release 12.2.

Description For indirect next-hop and multicast next-hop change acknowledgements, configure the
time interval for which to wait for the next-hop acknowledgement. The routing protocol
process (rpd) waits for the specified time period before changing the route to point to
the new next hop.

If the acknowledgement is not received within the time period, it is assumed to have been
received and the route is made to point to the new next hop.

Options interval—Kernel next-hop acknowledgement timeout interval.

Range: 1 through 100 seconds
Default: 1 second

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Optimizing Route Reconvergence by Enabling Indirect Next Hops on the
Documentation Packet Forwarding Engine on page 139

• indirect-next-hop-change-acknowledgements on page 236

Copyright © 2017, Juniper Networks, Inc. 245

Protocol-Independent Routing Properties Feature Guide

longest-match (Static Routes)

Syntax longest-match;

Hierarchy Level [edit logical-systems logical-system-name routing-options static route destination-prefix

next-hop address resolve]
[edit routing-instances routing-instance-name routing-options static route destination-prefix
next-hop address resolve],
[edit routing-options static route destination-prefix next-hop address resolve],

Release Information Statement introduced in Junos OS Release 15.1 for EX Series switches.

Description Specify the static route on the device to resolve and determine the packet’s next-hop
interface using the Longest Match Routing Rule (most specific entry), sometimes referred
to as the longest prefix match or maximum prefix length match. The Longest Match
Routing Rule is an algorithm used by IP routers to select an entry from a routing table.
The router uses the longest (prefix) match to determine the egress (outbound) interface
and the address of the next device to which to send a packet. Typically, the static route
prefers the directly connected subnet route for resolving the next hop rather than
performing a longest prefix match with any other available routes.

NOTE: (Required) You must include the resolve next-hop option to specify
the longest-match statement. Next-hop options define additional information
about static routes that are included with the route when it is installed in the
routing table. You alter the default next-hop resolution behavior using the
resolve next-hop option.

The router implements the Longest Match Routing Rule as follows:

1. The router receives a packet.

2. While processing the header, the router compares the destination IP address, bit-by-bit,
with the entries in the routing table.

The entry that has the longest number of network bits that match the IP destination
address is always the best match (or best path) as shown in the following example:

Longest Match Example

• The router receives a packet with a destination IP address of 192.168.1.33.

• The routing table contains the following possible matches:

• 192.168.1.32/28

• 192.168.1.0/24

• 192.168.0.0/16

246 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

To determine the longest match, it’s easiest to convert the IP addresses in

Table 5 on page 247 to binary and compare them.

Table 5: Converted IP Addresses

Address Converted Binary Address

192.168.1.33 (destination IP address) 11000000.10101000.00000001.00100001

192.168.1.32/28 11000000.10101000.00000001.00100000 (<–Best match)

192.168.1.0/24 11000000.10101000.00000001.00000000

192.168.0.0/16 11000000.10101000.00000000.00000000

NOTE: When determining the next-hop interface for customer deployments,

setting the longest-match statement results in traffic loss.

Required Privilege routing—To view this statement in the configuration.

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

Related • Understanding Static Route Preferences and Qualified Next Hops on page 35
Documentation

Copyright © 2017, Juniper Networks, Inc. 247

Protocol-Independent Routing Properties Feature Guide

lsp-next-hop (Static Routes)

Syntax lsp-next-hop lsp-name {

metric metric;
preference preference;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options static route destination-prefix],
[edit logical-systems logical-system-name routing-options static route destination-prefix],
[edit routing-instances routing-instance-name routing-options static route destination-prefix]
[edit routing-options static route destination-prefix]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify an LSP as the next hop for a static route, and configure an independent metric
or preference on that next-hop LSP.

NOTE: The preference and metric configured by means of the lsp-next-hop

statement only apply to the LSP next hops. The LSP next-hop preference
and metric override the route preference and metric (for that specific LSP
next hop), similar to how the route preference overrides the default preference
and metric (for that specific route).

Options lsp-name—Name of the next-hop LSP.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring a Collection of Paths to Create an RSVP-Signaled

Documentation Point-to-Multipoint LSP on page 91

248 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

martians

Syntax martians {
destination-prefix match-type <allow>;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure martian addresses.

Options allow—(Optional) Explicitly allow a subset of a range of addresses that has been
disallowed. The allow option is the only supported action.

destination-prefix—Destination route you are configuring:

• destination-prefix/prefix-length—destination-prefix is the network portion of the IP

address, and prefix-length is the destination prefix length.

• default—Default route to use when routing packets do not match a network or host in
the routing table. This is equivalent to specifying the IP address 0.0.0.0/0.

match-type—Criteria that the destination must match:

• exact—Exactly match the route’s mask length.

• longer—The route’s mask length is greater than the specified mask length.

• orlonger—The route’s mask length is equal to or greater than the specified mask length.

• through destination-prefix—The route matches the first prefix, the route matches the
second prefix for the number of bits in the route, and the number of bits in the route is
less than or equal to the number of bits in the second prefix.

• upto prefix-length—The route’s mask length falls between the two destination prefix
lengths, inclusive.

Copyright © 2017, Juniper Networks, Inc. 249

Protocol-Independent Routing Properties Feature Guide

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Class E Martian Addresses for Routing on page 160
Documentation

250 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

maximum-paths

Syntax maximum-paths path-limit <log-interval seconds> <log-only | threshold value>;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced in Junos OS Release 8.0.

Description Configure a limit for the number of routes installed in a routing table based upon the
route path.

NOTE: The maximum-paths statement is similar to the maximum-prefixes

statement. The maximum-prefixes statement limits the number of unique
destinations in a routing instance. For example, suppose a routing instance
has the following routes:

OSPF 10.10.10.0/24
ISIS 10.10.10.0/24

These are two routes, but only one destination (prefix). The maximum-paths
limit applies the total number of routes (two). The maximum-prefixes limit
applies to the total number of unique prefixes (one).

Options log-interval seconds—(Optional) Minimum time interval (in seconds) between log
messages.
Range: 5 through 86,400

log-only—(Optional) Sets the route limit as an advisory limit. An advisory limit triggers
only a warning, and additional routes are not rejected.

path-limit—Maximum number of routes. If this limit is reached, a warning is triggered and

additional routes are rejected.
32
Range: 1 through 4,294,967,295 (2 – 1)
Default: No default

threshold value—(Optional) Percentage of the maximum number of routes that starts

triggering a warning. You can configure a percentage of the path-limit value that
starts triggering the warnings.
Range: 1 through 100

Copyright © 2017, Juniper Networks, Inc. 251

Protocol-Independent Routing Properties Feature Guide

NOTE: When the number of routes reaches the threshold value, routes are
still installed into the routing table while warning messages are sent. When
the number of routes reaches the path-limit value, then additional routes are
rejected.

Required Privilege routing—To view this statement in the configuration.

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

Related • Limiting the Number of Paths and Prefixes Accepted from CE Routers in Layer 3 VPNs
Documentation

252 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

maximum-prefixes

Syntax maximum-prefixes prefix-limit <log-interval seconds> <log-only | threshold percentage>;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced in Junos OS Release 8.0.

Description Configure a limit for the number of routes installed in a routing table based upon the
route prefix.

Using a prefix limit, you can curtail the number of prefixes received from a CE router in a
VPN. Prefix limits apply only to dynamic routing protocols and are not applicable to static
or interface routes.

NOTE: The maximum-prefixes statement is similar to the maximum-paths

statement. The maximum-prefixes statement limits the number of unique
destinations in a routing instance. For example, suppose a routing instance
has the following routes:

OSPF 10.10.10.0/24
ISIS 10.10.10.0/24

Options log-interval seconds—(Optional) Minimum time interval (in seconds) between log
messages.
Range: 5 through 86,400

log-only—(Optional) Sets the prefix limit as an advisory limit. An advisory limit triggers
only a warning, and additional routes are not rejected.

prefix-limit—Maximum number of route prefixes. If this limit is reached, a warning is

triggered and any additional routes are rejected.
Range: 1 through 4,294,967,295
Default: No default

Copyright © 2017, Juniper Networks, Inc. 253

Protocol-Independent Routing Properties Feature Guide

threshold value—(Optional) Percentage of the maximum number of prefixes that starts

triggering a warning. You can configure a percentage of the prefix-limit value that
starts triggering the warnings.
Range: 1 through 100

NOTE: When the number of routes reaches the threshold value, routes are
still installed into the routing table while warning messages are sent. When
the number of routes reaches the prefix-limit value, then additional routes
are rejected.

Required Privilege routing—To view this statement in the configuration.

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

Related • Limiting the Number of Paths and Prefixes Accepted from CE Routers in Layer 3 VPNs
Documentation

254 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

med-igp-update-interval

Syntax med-igp-update-interval minutes;

Hierarchy Level [edit routing-options]

Release Information Statement introduced in Junos OS Release 9.0

Description Configure a timer for how long to delay updates for the multiple exit discriminator (MED)
path attribute for BGP groups and peers configured with the metric-out igp offset
delay-med-update statement. The timer delays MED updates for the interval configured
unless the MED is lower than the previously advertised attribute or another attribute
associated with the route has changed or if the BGP peer is responding to a refresh route
request.

Options minutes—Interval to delay MED updates.

Range: 10 through 600
Default: 10 minutes

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Associating the MED Path Attribute with the IGP Metric and Delaying MED
Documentation Updates

• metric-out

metric

Syntax metric route-cost;

Hierarchy Level [edit routing-options access route ip-prefix</prefix-length>]

Release Information Statement introduced in Junos OS Release 10.1.

Description Configure the cost for an access route.

Options route-cost—Specific cost you want to assign to the access route.

Required Privilege routing—To view this statement in the configuration.

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

Copyright © 2017, Juniper Networks, Inc. 255

Protocol-Independent Routing Properties Feature Guide

metric (Aggregate, Generated, or Static Route)

Syntax (metric | metric2 | metric3 | metric4) metric <type type>;

Hierarchy Level [edit logical-systems logical-system-name routing-options (aggregate | generate | static)

(defaults | route)],
[edit routing-options (aggregate | generate | static) (defaults | route)]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify the metric value for an aggregate, generated, or static route. You can specify up
to four metric values, starting with metric (for the first metric value) and continuing with
metric2, metric3, and metric4.

Options metric—Metric value.

32
Range: 0 through 4,294,967,295 (2 – 1)

type type—(Optional) Type of route.

When routes are exported to OSPF, type 1 routes are advertised in type 1 externals, and
routes of any other type are advertised in type 2 externals. Note that if a
qualified-next-hop metric value is configured, this value overrides the route metric.
Range: 1 through 16

Required Privilege routing—To view this statement in the configuration.

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

Related • aggregate on page 192

Documentation
• generate on page 228

• static on page 298

• Example: Summarizing Static Routes Through Route Aggregation on page 81

• Understanding Route Aggregation on page 73

256 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

metric (Qualified Next Hop on Static Route)

Syntax metric metric;

Hierarchy Level [edit logical-systems logical-system-name routing-options static route destination-prefix

qualified-next-hop],
[edit routing-options static route destination-prefix qualified-next-hop]

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.3 for ACX Series routers.

Description Metric value for a static route.

Options metric—Metric value.

32
Range: 0 through 4,294,967,295 (2 – 1)

Required Privilege routing—To view this statement in the configuration.

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

Related • qualified-next-hop on page 272

Documentation
• static on page 298

Copyright © 2017, Juniper Networks, Inc. 257

Protocol-Independent Routing Properties Feature Guide

multicast (Routing Options)

Syntax multicast {
forwarding-cache {
threshold suppress value <reuse value>;
}
interface interface-name {
enable;
}
local-address address
scope scope-name {
interface [ interface-names ];
prefix destination-prefix;
}
ssm-groups {
address;
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure generic multicast properties.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Examples: Configuring Administrative Scoping

Documentation
• Example: Configuring Source-Specific Multicast Groups with Any-Source Override

• Examples: Configuring the Multicast Forwarding Cache

• Multicast Protocols Feature Guide

258 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

• (indirect-next-hop on page 235 | no-indirect-next-hop)

next-hop (Access)

Syntax next-hop next-hop;

Hierarchy Level [edit routing-options access route ip-prefix</prefix-length>]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure the next-hop address for an access route. Access routes are typically
unnumbered interfaces.

Options next-hop—Specific next-hop address you want to assign to the access route.

Required Privilege routing—To view this statement in the configuration.

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

next-hop (Access Internal)

Syntax next-hop next-hop;

Hierarchy Level [edit routing-options access-internal route ip-prefix</prefix-length>]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure the next-hop address for an internal access route. Access routes are typically
unnumbered interfaces.

Options next-hop—Specific next-hop address you want to assign to the internal access route.

Required Privilege routing—To view this statement in the configuration.

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

Copyright © 2017, Juniper Networks, Inc. 259

Protocol-Independent Routing Properties Feature Guide

no-delegate-processing

Syntax no-delegate-processing;

Hierarchy Level [edit routing-options ppm]

Release Information Statement introduced in Junos OS Release 10.1 for EX Series switches.

Description Disable distributed periodic packet management (PPM) processing and run all PPM
processing on the Routing Engine.

PPM processing cannot be completely disabled on EX Series switches. You can only
configure whether PPM processing is distributed between the access ports (EX3200 and
EX4200 switches) or the line cards (EX8200 switches) and the Routing Engine or is
handled just on the Routing Engine.

BEST PRACTICE: Generally, you should only disable distributed PPM if Juniper
Networks Customer Service advised you to do so. You should only disable
distributed PPM if you have a compelling reason to disable it.

Default Distributed PPM processing is enabled.

Required Privilege routing—To view this statement in the configuration.

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

260 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

nonstop-routing

Syntax nonstop-routing;

Hierarchy Level [edit routing-options]

NOTE: Although nonstop-routing is also a valid keyword at the logical-systems

hierarchy level, it is not supported.

Release Information Statement introduced in Junos OS Release 8.4.

Statement introduced in Junos OS Release 10.4 for EX Series switches.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 13.2X51-D20 for QFX Series switches

Description For routing platforms with two Routing Engines, configure a master Routing Engine to
switch over gracefully to a backup Routing Engine and to preserve routing protocol
information.

Default disabled

Required Privilege interface—To view this statement in the configuration.

Level interface-control—To add this statement to the configuration.

Related • Configuring Nonstop Active Routing

Documentation

Copyright © 2017, Juniper Networks, Inc. 261

Protocol-Independent Routing Properties Feature Guide

options (Routing Options)

Syntax options {
syslog (level level | upto level level);
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure the types of system logging messages sent about the routing protocols process
to the system message logging file. These messages are also displayed on the system
console. You can log messages at a particular level, or up to and including a particular
level.

Options level level—Severity of the message. It can be one or more of the following levels, in order
of decreasing urgency:

• alert—Conditions that should be corrected immediately, such as a corrupted system

database.

• critical—Critical conditions, such as hard drive errors.

• debug—Software debugging messages.

• emergency—Panic or other conditions that cause the system to become unusable.

• error—Standard error conditions.

• info—Informational messages.

• notice—Conditions that are not error conditions, but might warrant special handling.

• warning—System warning messages.

upto level level—Log all messages up to a particular level.

Required Privilege routing—To view this statement in the configuration.

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

Related • syslog in the Junos OS Administration Library

Documentation

262 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

p2mp-ldp-next-hop

Syntax p2mp-ldp-next-hop {
root-address root-address{
lsp-id id;
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options static route destination-prefix],
[edit logical-systems logical-system-name routing-options static route destination-prefix],
[edit routing-instances routing-instance-name routing-options static route destination-prefix].
[edit routing-options static route destination-prefix]

Release Information Statement introduced in Junos OS Release 13.3.

Description Specify a point-to-multipoint LDP label-switched path (LSP) as the next hop for a static
route, and configure a root and provide an lsp-id on that LDP-signalled label-switched
path.

Options root-address root address— Specify the root address of the point-to-multipoint LSP.

lsp-id id— Specify the generic LSP identifier. The range is 1 through 65535.

Required Privilege routing—To view this statement in the configuration.

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

Copyright © 2017, Juniper Networks, Inc. 263

Protocol-Independent Routing Properties Feature Guide

p2mp-lsp-next-hop

Syntax p2mp-lsp-next-hop {
metric metric;
preference preference;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options static route destination-prefix],
[edit logical-systems logical-system-name routing-options static route destination-prefix],
[edit routing-instances routing-instance-name routing-options static route destination-prefix].
[edit routing-options static route destination-prefix]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Specify a point-to-multipoint LSP as the next hop for a static route, and configure an
independent metric or preference on that next-hop LSP.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Configuring Static LSPs

Documentation
• Example: Configuring a Collection of Paths to Create an RSVP-Signaled
Point-to-Multipoint LSP on page 91

• Example: Configuring an RSVP-Signaled Point-to-Multipoint LSP on Logical Systems

passive (Routing Options)

See active

264 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

policy (Aggregate and Generated Routes)

Syntax policy policy-name;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Associate a routing policy when configuring an aggregate or generated route’s destination
prefix in the routes part of the aggregate or generate statement. This provides the
equivalent of an import routing policy filter for the destination prefix. That is, each potential
contributor to an aggregate route, along with any aggregate options, is passed through
the policy filter. The policy then can accept or reject the route as a contributor to the
aggregate route.

If the contributor is accepted, the policy can modify the default preferences. The
contributor with the numerically smallest prefix becomes the most preferred, or primary,
contributor. A rejected contributor still can contribute to a less specific aggregate route.
If you do not specify a policy filter, all candidate routes contribute to an aggregate route.

The following algorithm is used to compare two generated contributing routes in order
to determine which one is the primary or preferred contributor:

1. Compare the protocol’s preference of the contributing routes. The lower the preference,
the better the route. This is similar to the comparison that is done while determining
the best route for the routing table.

2. Compare the protocol’s preference2 of the contributing routes. The lower preference2
value is better. If only one route has preference2, then this route is preferred.

3. The preference values are the same. Proceed with a numerical comparison of the
prefixes’ values.

a. The primary contributor is the numerically smallest prefix value.

Copyright © 2017, Juniper Networks, Inc. 265

Protocol-Independent Routing Properties Feature Guide

b. If the two prefixes are numerically equal, the primary contributor is the route that
has the smallest prefix length value.

At this point, the two routes are the same. The primary contributor does not change. An
additional next hop is available for the existing primary contributor.

A rejected contributor still can contribute to less specific generated route. If you do not
specify a policy filter, all candidate routes contribute to a generated route.

Options policy-name—Name of a routing policy.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• aggregate on page 192

• generate on page 228

266 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

ppm

Syntax ppm {
no-delegate-processing;
}

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit routing-options]

Release Information Statement introduced in Junos OS Release 9.4.

Statement introduced in Junos OS Release 10.2 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description (M120, M320, MX Series, T Series, TX Matrix routers, M7i and M10i routers with Enhanced
CFEB [CFEB-E], EX Series switches, and QFX Series only) Disable distributed periodic
packet management (PPM) to the Packet Forwarding Engine (on routers), to access
ports (on EX3200 and EX4200 switches, and QFX Series), or to line cards (on EX6200
and EX8200 switches).

After you disable PPM, PPM processing continues to run on the Routing Engine.

In Junos OS Release 8.2, PPM was moved from the Routing Engine to the Packet
Forwarding Engine, access ports, or line cards. The no-delegate-processing statement
disables the default behavior and restores the legacy behavior.

Default Distributed PPM processing is enabled for all protocols that use PPM.

Options no-delegate-processing—Disable PPM to the Packet Forwarding Engine, access ports, or

line cards. Distributed PPM is enabled by default.

redistribution-timer— Ensures that link aggregation (and STP) work properly for the
periodic packet management (PPM) daemons on the aggregation and satellite
devices. A value of 120 is recommended for MXVC-ISSU.

Required Privilege routing—To view this statement in the configuration.

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

Related • Ensuring That Distributed ppm Is Not Disabled

Documentation

Copyright © 2017, Juniper Networks, Inc. 267

Protocol-Independent Routing Properties Feature Guide

precision-timers-max-period

Syntax precision-timers-max-period precision-timers-max-period;

Hierarchy Level [edit routing-options nonstop-routing-options]

Release Information Statement introduced in Junos OS Release 16.1.

Description Support of precision-timers in the kernel is a feature where the kernel takes over
auto-generation of BGP keepalives right after the switchover from standby to master
event occurs. The kernel in the RE continues this auto-generation until the BGP protocol
is able to take over the session or until a maximum period has elapsed since the switchover
event occurred. The maximum period for which the kernel auto-generates keepalives on
behalf of BGP after a switchover event from standby to master ranges from 60 seconds
to 1800 seconds. The default value is 600 seconds.

Required Privilege routing—To view this statement in the configuration.

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

preference (Access)

Syntax preference route-distance;

Hierarchy Level [edit routing-options access route ip-prefix</prefix-length>]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure the distance for an access route.

Options route-distance—Specific distance you want to assign to the access route.

Required Privilege routing—To view this statement in the configuration.

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

268 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

preference (Routing Options)

Syntax preference {
metric-value;
<type metric_type>
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Preference value for a static, aggregate, or generated route. You also can specify a
secondary preference value, as well as color values, which are even finer-grained
preference values.

You can specify a primary route preference (by including the preference statement in
the configuration), and a secondary preference that is used as a tiebreaker (by including
the preference2 statement). You can also mark route preferences with additional route
tiebreaker information by specifying a color and a tiebreaker color (by including the color
and color2 statements in the configuration).

Options metric_value—The metric value for an aggregate, a generated, or a static route to determine
the best route among multiple routes to a destination
32
Range: 0 through 4,294,967,295 (2 – 1)
Default: 5 (for static routes), 130 (for aggregate and generated routes)

type metric_type—(Optional) External metric type for routes exported by OSPF. When
routes are exported to OSPF, type 1 routes are advertised in type 1 externals, and

Copyright © 2017, Juniper Networks, Inc. 269

Protocol-Independent Routing Properties Feature Guide

routes of any other type are advertised in type 2 externals. Note that if a
qualified-next-hop metric value is configured, this value overrides the route metric.

Range: 1 through 16

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• aggregate on page 192

• generate on page 228

• static on page 298

• color on page 209

prefix

Syntax prefix destination-prefix;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure the prefix for multicast scopes.

Options destination-prefix—Address range for the multicast scope.

Required Privilege routing—To view this statement in the configuration.

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

Related • Examples: Configuring Administrative Scoping

Documentation
• Example: Creating a Named Scope for Multicast Scoping

• multicast

270 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

qualified-next-hop (Access)

Syntax qualified-next-hop next-hop;

Hierarchy Level [edit routing-options access route ip-prefix</prefix-length>]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure the qualified next-hop address for an access route.

Options next-hop—Specific qualified next-hop address you want to assign to the access route.

Required Privilege routing—To view this statement in the configuration.

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

qualified-next-hop (Access-Internal)

Syntax qualified-next-hop next-hop;

Hierarchy Level [edit routing-options access-internal route ip-prefix</prefix-length>]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure the qualified next-hop address for an internal access route.

Options next-hop—Specific qualified next-hop address you want to assign to the internal access
route.

Required Privilege routing—To view this statement in the configuration.

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

Copyright © 2017, Juniper Networks, Inc. 271

Protocol-Independent Routing Properties Feature Guide

qualified-next-hop (Static Routes)

Syntax qualified-next-hop (address | interface-name) {

bfd-liveness-detection {
authentication {
algorithm (keyed-md5 | keyed-sha-1 | meticulous-keyed-md5 | meticulous-keyed-sha-1 |
simple-password);
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
holddown-interval milliseconds;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}
interface interface-name;
metric metric;
preference preference;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options static route destination-prefix],
[edit logical-systems logical-system-name routing-options rib inet6.0 static route
destination-prefix],
[edit logical-systems logical-system-name routing-options static route destination-prefix],
[edit routing-instances routing-instance-name routing-options static route destination-prefix],
[edit routing-options rib inet6.0 static route destination-prefix],
[edit routing-options static route destination-prefix]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure a static route with multiple possible next hops, each of which can have its own
preference value, IGP metric that is used when the route is exported into an IGP, and
Bidirectional Forwarding Detection (BFD) settings. If multiple links are operational, the
one with the most preferred next hop is used. The most preferred next hop is the one
with the lowest preference value.

Options address—IPv4, IPv6, or ISO network address of the next hop.

272 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

interface-name—Name of the interface on which to configure an independent metric or

preference for a static route. To configure an unnumbered interface as the next-hop
interface for a static route, specify qualified-next-hop interface-name, where
interface-name is the name of the IPv4 or IPv6 unnumbered interface.

NOTE: For an Ethernet interface to be configured as the qualified next hop

for a static route, it must be an unnumbered interface.

To configure an Ethernet interface as an unnumbered interface, configure

the unnumbered-address <interface-name> statement at the [edit interfaces
<interface-name> unit <logical-unit-number> family <family-name>] hierarchy
level as described in Configuring an Unnumbered Interface.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Enabling BFD on Qualified Next Hops in Static Routes for Route Selection
Documentation on page 130

Copyright © 2017, Juniper Networks, Inc. 273

Protocol-Independent Routing Properties Feature Guide

readvertise

Syntax (readvertise | no-readvertise);

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options rib routing-table-name static (defaults | route)],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options static (defaults | route)],
[edit logical-systems logical-system-name routing-options rib routing-table-name static
(defaults | route)],
[edit logical-systems logical-system-name routing-options static (defaults | route)],
[edit routing-instances routing-instance-name routing-options rib routing-table-name static
(defaults | route)],
[edit routing-instances routing-instance-name routing-options static (defaults | route)],
[edit routing-options rib routing-table-name static (defaults | route)],
[edit routing-options static (defaults | route)]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure whether static routes are eligible to be readvertised by routing protocols:

Default Static routes are eligible to be readvertised (that is, exported from the routing table into
dynamic routing protocols) if a policy to do so is configured. To mark an IPv4 static route
as being ineligible for readvertisement, include the no-readvertise statement.

Options readvertise—Readvertise static routes. Include the readvertise statement when configuring
an individual route in the route portion of the static statement to override a
no-readvertise option specified in the defaults portion of the statement.

no-readvertise—Mark a static route as being ineligible for readvertisement. Include the

no-readvertise option when configuring the route.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Preventing a Static Route from Being Readvertised on page 43

Documentation
• Understanding Static Route Control in Routing and Forwarding Tables on page 42

• static on page 298

274 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

resolution

Syntax resolution {
rib routing-table-name {
import [ policy-names ];
inet-import [ policy-names ];
inet-resolution-ribs [ routing-table-names ];
inet6-import [ policy-names ];
inet6-resolution-ribs [ routing-table-names ];
iso-import [ policy-names ];
iso-resolution-ribs [ routing-table-names ];
resolution-family resolution-family;
resolution-ribs [ routing-table-names ];
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure the router to perform custom route resolution on protocol next hops of routes
in a certain routing table. The protocol next hop is used to determine the forwarding next
hop.

For example, you might want to direct inet.2 route resolution to use topology routing
tables :red.inet.0 and :blue.inet.0 for protocol next-hop IP address lookups. Or you might
want to direct bgp.l3vpn.0 to use the information in inet.0 to resolve routes, thus overriding
the default behavior, which is to use inet.3.

You can specify up to two routing tables in the resolution-ribs statement. The route
resolution scheme first checks the first-listed routing table for the protocol next-hop
address. If the address is found, it uses this entry. If it is not found, the resolution scheme
checks the second-listed routing table. Hence, only one routing table is used for each
protocol next-hop address. For example, if you configure resolution rib bgp.l3vpn.0
resolution-ribs [inet.0 inet.3], inet.0 is checked first and then inet.3 is checked.

NOTE: Customizing route resolution might cause the routing protocol process
(rpd) to consume more memory resources than it ordinarily would. When
you customize route resolution, we recommend that you check the memory
resources by running the show system processes and the show task memory
commands. For more information, see Routing Protocol Process Overview.

Copyright © 2017, Juniper Networks, Inc. 275

Protocol-Independent Routing Properties Feature Guide

The remaining statements are explained separately. See CLI Explorer.

Options inet-import [ policy-names ]—(Optional) Import policy for IPv4 family resolution tree.

inet-resolution-ribs [ routing-table-names—(Optional) Specify routing tables to use for

IPv4 family protocol-next-hop resolution.

inet6-import [ policy-names ]—(Optional) Import policy for IPv6 family resolution tree.

inet6-resolution-ribs [ routing-table-names ]—(Optional) Specify routing tables to use

for IPv6 family protocol-next-hop resolution.

Enabling the inet6-resolution-ribs option causes the static LSP route resolution to
happen over the more preferred resolving route (lowest protocol preference) among
the longest-matching-prefix routes in both the inet6.0 and inet6.3 routing tables.

iso-import [ policy-names ]—(Optional) Import policy for ISO family resolution tree.

iso-resolution-ribs [ routing-table-names ]—(Optional) Specify routing tables to use

for ISO family protocol-next-hop resolution.

resolution-family resolution-family—(Optional) Specify a family of resolution tree.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Route Resolution on PE Routers

Documentation
• Example: Configuring Route Resolution on Route Reflectors

• Understanding Multitopology Routing in Conjunction with PIM

• Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic

over Separate Network Paths

276 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

resolution-ribs

Syntax resolution-ribs [ routing-table-names ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify one or more routing tables to use for route resolution.

This statement enables you to override the default routing tables that Junos OS uses for
route resolution. For example, suppose that the resolution routing table is inet.3, but you
want to allow fallback resolution through inet.0. One example use case is overriding the
bgp.rtarget.0 (family route-target) routing table resolution from using only inet.3 to using
both inet.3 and inet.0.

Options routing-table-names—Name of one or more routing tables.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Route Resolution on PE Routers

Documentation
• Example: Configuring Multitopology Routing to Provide Redundancy for Multicast Traffic
over Separate Network Paths

• Understanding Multitopology Routing in Conjunction with PIM

Copyright © 2017, Juniper Networks, Inc. 277

Protocol-Independent Routing Properties Feature Guide

resolve

Syntax resolve;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Statically configure routes to be resolved to a next hop that is not directly connected.
The route is resolved through the inet.0 and inet.3 routing tables.

NOTE: You cannot configure both resolve and retain options for a statically
configured route because resolved next hops cannot be retained.

Default Static routes can point only to a directly connected next hop.

TIP: We recommend configuring the no-resolve option for individual routes

to override default configuration.

Required Privilege routing—To view this statement in the configuration.

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

Related • static on page 298

Documentation

278 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

restart-duration

Syntax restart-duration seconds;

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Configure the grace period for graceful restart globally.

Additionally, you can individually configure the duration of the graceful restart period for
the End System-to-Intermediate System (ES-IS), Intermediate System-to-Intermediate
System (IS-IS), Open Shortest Path First (OSPF), and OSPFv3 protocols and for Protocol
Independent Multicast (PIM) sparse mode.

Options seconds—Time for the graceful restart period.

Range:
The range of values varies according to whether the graceful restart period is being set
globally or for a particular protocol:

• [edit routing-options graceful-restart] (global setting)—120 through 900

• ES-IS—30 through 300

• IS-IS—30 through 300

• OSPF/OSPFv3—1 through 3600

• PIM—30 through 300

Default:
The default value varies according to whether the graceful restart period is being set
globally or for a particular protocol:

• [edit routing-options graceful-restart] (global setting)—300

• ES-IS—180

• IS-IS—210

• OSPF/OSPFv3—180

• PIM—60

Copyright © 2017, Juniper Networks, Inc. 279

Protocol-Independent Routing Properties Feature Guide

Required Privilege routing—To view this statement in the configuration.

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

Related • Enabling Graceful Restart

Documentation
• Configuring Graceful Restart for MPLS-Related Protocols

• Configuring VPN Graceful Restart

• Configuring Graceful Restart for VPNs

• Configuring Logical System Graceful Restart

restart-duration (Routing Options)

Syntax restart-duration seconds;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Description Configure the restart timer for graceful restart.

Options seconds—Configure the time period for the restart to last.

Range: 120 through 900 seconds
Default: 300 seconds

Required Privilege routing—To view this statement in the configuration.

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

Related • Junos OS High Availability Library for Routing Devices

Documentation

280 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

retain

Syntax (no-retain | retain);

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure statically configured routes to be deleted from or retained in the forwarding
table when the routing protocol process shuts down normally:

NOTE: You cannot configure both retain and resolve options for a statically
configured route because resolved next hops cannot be retained.

Default Statically configured routes are deleted from the forwarding table when the routing
protocol process shuts down normally. Doing this greatly reduces the time required to
restart a system that has a large number of routes in its routing table.

TIP: We recommend configuring the no-retain option for individual routes to

override default configuration.

Options no-retain—Delete statically configured routes from the forwarding table when the routing
protocol process shuts down normally. To explicitly specify that routes be deleted
from the forwarding table, include the no-retain statement. Include this statement
when configuring an individual route in the route portion of the static statement to
override a retain option specified in the defaults portion of the statement.

Copyright © 2017, Juniper Networks, Inc. 281

Protocol-Independent Routing Properties Feature Guide

retain—Have a static route remain in the forwarding table when the routing protocol
process shuts down normally. Doing this greatly reduces the time required to restart
a system that has a large number of routes in its routing table.

Required Privilege routing—To view this statement in the configuration.

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

Related • static on page 298

Documentation

282 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

rib (General)

Syntax rib routing-table-name {

aggregate {
defaults {
... aggregate-options ...
}
route destination-prefix {
policy policy-name;
... aggregate-options ...
}
generate {
defaults {
generate-options;
}
route destination-prefix {
policy policy-name;
generate-options;
}
}
martians {
destination-prefix match-type <allow>;
}
}
static {
defaults {
static-options;
}
rib-group group-name;
route destination-prefix {
next-hop;
static-options;
}
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Create a routing table.

Explicitly creating a routing table with routing-table-name is optional if you are not adding
any static, martian, aggregate, or generated routes to the routing table and if you also
are creating a routing table group.

Copyright © 2017, Juniper Networks, Inc. 283

Protocol-Independent Routing Properties Feature Guide

NOTE: The IPv4 multicast routing table (inet.1) and the IPv6 multicast routing
table (inet6.1) are not supported for this statement.

Default If you do not specify a routing table name with the routing-table-name option, the software
uses the default routing tables, which are inet.0 for unicast routes and inet.1 for the
multicast cache.

Options routing-table-name—Name of the routing table, in the following format:

protocol [.identifier].

In a routing instance, the routing table name must include the routing instance name.
For example, if the routing instance name is link0, the routing table name might be
link0.inet6.0.

• protocol is the protocol family. It can be inet6 for the IPv6 family, inet for the IPv4 family,
iso for the ISO protocol family, or instance-name.iso.0 for an ISO routing instance.

• identifier is a positive integer that specifies the instance of the routing table.

Default: inet.0

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Creating Routing Tables on page 51

Documentation
• passive on page 264

284 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

rib (Route Resolution)

Syntax rib routing-table-name {

import [ policy-names ];
resolution-ribs [ routing-table-names ];
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options resolution],
[edit logical-systems logical-system-name routing-options resolution],
[edit routing-instances routing-instance-name routing-options resolution],
[edit routing-options resolution]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify a routing table name for route resolution.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Route Resolution on PE Routers

Documentation

Copyright © 2017, Juniper Networks, Inc. 285

Protocol-Independent Routing Properties Feature Guide

rib-group (Routing Options)

Syntax rib-group group-name;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options interface-routes],
[edit logical-systems logical-system-name routing-options interface-routes],
[edit logical-systems logical-system-name routing-options rib routing-table-name static],
[edit logical-systems logical-system-name routing-options static],
[edit routing-instances routing-instance-name routing-options interface-routes],
[edit routing-options interface-routes],
[edit routing-options rib routing-table-name static],
[edit routing-options static]

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure which routing table groups interface routes are imported into.

Options group-name—Name of the routing table group. The name must start with a letter and
can include letters, numbers, and hyphens. It generally does not make sense to
specify more than a single routing table group.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Importing Direct and Static Routes Into a Routing Instance on page 53
Documentation
• Example: Exporting Specific Routes from One Routing Table Into Another Routing
Table on page 58

• interface-routes on page 243

• rib-groups on page 287

286 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

rib-groups

Syntax rib-groups {
group-name {
export-rib group-name;
import-policy [ policy-names ];
import-rib [ group-names ];
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Group one or more routing tables to form a routing table group. A routing protocol can
import routes into all the routing tables in the group and can export routes from a single
routing table.

Each routing table group must contain one or more routing tables that Junos OS uses
when importing routes (specified in the import-rib statement) and optionally can contain
one routing table group that Junos OS uses when exporting routes to the routing protocols
(specified in the export-rib statement).

The first routing table you specify is the primary routing table, and any additional routing
tables are the secondary routing tables.

The primary routing table determines the address family of the routing table group. To
configure an IP version 4 (IPv4) routing table group, specify inet.0 as the primary routing
table. To configure an IP version 6 (IPv6) routing table group, specify inet6.0 as the
primary routing table. If you configure an IPv6 routing table group, the primary and all
secondary routing tables must be IPv6 routing tables (inet6.x).

In Junos OS Release 9.5 and later, you can include both IPv4 and IPv6 routing tables in
an IPv4 import routing table group using the import-rib statement. In releases prior to
Junos OS Release 9.5, you can only include either IPv4 or IPv6 routing tables in the same
import-rib statement. The ability to configure an import routing table group with both
IPv4 and IPv6 routing tables enables you, for example, to populate the inet6.3 routing
table with IPv6 addresses that are compatible with IPv4. Specify inet.0 as the primary
routing table, and specify inet6.3 as a secondary routing table.

NOTE: On EX Series switches, only dynamically learned routes can be

imported from one routing table group to another.

Copyright © 2017, Juniper Networks, Inc. 287

Protocol-Independent Routing Properties Feature Guide

NOTE: If you configure an import routing table group that includes both IPv4
and IPv6 routing tables, any corresponding export routing table group must
include only IPv4 routing tables.

If you have configured a routing table, configure the OSPF primary instance at the
[edit protocols ospf] hierarchy level with the statements needed for your network so that
routes are installed in inet.0 and in the forwarding table. Make sure to include the routing
table group. For more information, see Example: Configuring Multiple Routing Instances
of OSPF.

After specifying the routing table from which to import routes, you can apply one or more
policies to control which routes are installed in the routing table group. To apply a policy
to routes being imported into the routing table group, include the import-policy statement.

Options group-name—Name of the routing table group. The name must start with a letter and
can include letters, numbers, and hyphens.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Exporting Specific Routes from One Routing Table Into Another Routing
Documentation Table on page 58

• rib-group on page 286

288 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

route (Access)

Syntax route ip-prefix</prefix-length> {

metric route-cost;
next-hop next-hop;
preference route-distance;
qualified-next-hop next-hop;
tag tag-number;
}

Hierarchy Level [edit routing-options access]

Release Information Statement introduced in Junos OS Release 10.1.

Description Configure the parameters for access routes.

Options ip-prefix</prefix-length>—Specific route prefix that you want to assign to the access
route.

The remaining statements are explained separately.

Required Privilege routing—To view this statement in the configuration.

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

route (Access-Internal)

Syntax route ip-prefix</prefix-length> {

next-hop next-hop;
qualified-next-hop next-hop;
}

Hierarchy Level [edit routing-options access-internal]

Release Information Statement introduced in Junos OS Release 10.1.

Description Configure the parameters for internal access routes.

Options ip-prefix</prefix-length>—Specific route prefix that you want to assign to the internal
access route.

The remaining statements are explained separately.

Required Privilege routing—To view this statement in the configuration.

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

Copyright © 2017, Juniper Networks, Inc. 289

Protocol-Independent Routing Properties Feature Guide

route-distinguisher-id

Syntax route-distinguisher-id ip-address;

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Description Automatically assign a route distinguisher to the routing instance.

If you configure the route-distinguisher statement in addition to the route-distinguisher-id

statement, the value configured for route-distinguisher supersedes the value generated
from route-distinguisher-id.

NOTE: To avoid a conflict in the two route distinguisher values, it is

recommended to ensure that the first half of the route distinguisher obtained
by configuring the route-distinguisher statement is different from the first half
of the route distinguisher obtained by configuring the route-distinguisher-id
statement.

Options ip-address—Address for routing instance.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring BGP Route Target Filtering for VPNs

Documentation
• Configuring Routing Instances on PE Routers in VPNs

290 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

route-record

Syntax route-record;

Hierarchy Level [edit logical-systems logical-system-name routing-options],

[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Export the AS path and routing information to the traffic sampling process.

Before you can perform flow aggregation, the routing protocol process must export the
AS path and routing information to the sampling process.

NOTE: Starting with Junos OS Release 15.1, when you commit a minor
configuration change, the routing protocol process sends only AS paths that
are active routes to the FPCs. Not all known AS paths are sent to the FPC,
thereby considerably reducing the memory and CPU usage, resulting in a
faster route record database update.

Required Privilege routing—To view this statement in the configuration.

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

Related • Enabling Flow Aggregation

Documentation
• Junos OS Services Interfaces Library for Routing Devices

Copyright © 2017, Juniper Networks, Inc. 291

Protocol-Independent Routing Properties Feature Guide

router-id

Syntax router-id address;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options]

Release Information Statement introduced before Junos OS Release 7.4.

Description Specify the routing device’s IP address.

The router identifier is used by BGP and OSPF to identify the routing device from which
a packet originated. The router identifier usually is the IP address of the local routing
device. If you do not configure a router identifier, the IP address of the first interface to
come online is used. This is usually the loopback interface. Otherwise, the first hardware
interface with an IP address is used.

NOTE: We strongly recommend that you configure the router identifier under
the [edit routing-options] hierarchy level to avoid unpredictable behavior if
the interface address on a loopback interface changes.

You must configure a router-id in order for BGP and OSPF to function in a routing instance.
Use the show route instance detail command to display the router-id value for a routing
instance. If the router-id is 0.0.0.0, then the routing instance has no router-id.

For more information about the router identifier in OSPF, see Example: Configuring an
OSPF Router Identifier.

NOTE: If you run OSPF for IPv6 or BGP for IPv6 in a routing instance, you
must configure an IPv4 router identifier (router-id) in the routing instance
itself. In other words, the IPv4 router-id in the main routing instance is not
inherited by other routing instances. Even if you run only IPv6 OSPF or BGP
in a routing instance, the IPv4 router-id must be configured because OSPF
and BGP, even when used exclusively with IPv6, use the IPv4 router-id for
handshaking. If you do not configure the IPv4 router-id in the IPv6 OSPF or
BGP routing instance, then the IPv6 protocols will use invalid IPv4 address
0.0.0.0 and the adjacencies and connections will fail.

292 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

Options address—IP address of the routing device.

Default: Address of the first interface encountered by Junos OS

Required Privilege routing—To view this statement in the configuration.

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

Related • Examples: Configuring External BGP Peering

Documentation
• Examples: Configuring Internal BGP Peering

routing-options

Syntax routing-options { ... }

For information on the complete list of routing-options, see the Protocol-Independent

Routing Properties Feature Guide .

Hierarchy Level [edit],

[edit logical-systems logical-system-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.

Description Configure protocol-independent routing properties.

Required Privilege routing—To view this statement in the configuration.

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

Related • Protocol-Independent Routing Properties Feature Guide

Documentation

Copyright © 2017, Juniper Networks, Inc. 293

Protocol-Independent Routing Properties Feature Guide

scope

Syntax scope scope-name {

interface [ interface-names ];
prefix destination-prefix;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Configure multicast scoping.

Options scope-name—Name of the multicast scope.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Configuring Multicast Snooping

Documentation

294 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

source-address (Routing Options)

Syntax source-address address;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options dynamic-tunnels tunnel-name,
[edit logical-systems logical-system-name routing-options dynamic-tunnels tunnel-name],
[edit routing-instances routing-instance-name routing-options dynamic-tunnels tunnel-name],
[edit routing-options dynamic-tunnels tunnel-name]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Specify the source address for the generic routing encapsulation (GRE) tunnels. The
source address specifies the address used as the source for the local tunnel endpoint.
This address can be any local address on the router, typically the router ID or the loopback
address.

Options address—Name of the source address.

Required Privilege routing—To view this statement in the configuration.

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

Related • Configuring GRE Tunnels for Layer 3 VPNs

Documentation

Copyright © 2017, Juniper Networks, Inc. 295

Protocol-Independent Routing Properties Feature Guide

source-routing

Syntax source-routing {
(ip | ipv6)
}

Hierarchy Level [edit routing-options]

Release Information Statement for IPv6 introduced in Junos OS Release 8.2.

Statement for IPv4 introduced in Junos OS Release 8.5.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Enable source routing.

Source routing allows a sender of a packet to partially or completely specify the route
the packet takes through the network. In contrast, in non-source routing protocols, routers
in the network determine the path based on the packet's destination.

NOTE: We recommend that you not use source routing. Instead, we

recommend that you use policy-based routing or filter-based forwarding to
route packets based on source addresses.

Default Disabled

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Filter-Based Forwarding on the Source Address

Documentation

296 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

ssm-groups

Syntax ssm-groups [ ip-addresses ];

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

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.1 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Configure source-specific multicast (SSM) groups.

By default, the SSM group multicast address is limited to the IP address range from
232.0.0.0 through 232.255.255.255. However, you can extend SSM operations into another
Class D range by including the ssm-groups statement in the configuration. The default
SSM address range from 232.0.0.0 through 232.255.255.255 cannot be used in the
ssm-groups statement. This statement is for adding other multicast addresses to the
default SSM group addresses. This statement does not override the default SSM group
address range.

IGMPv3 supports SSM groups. By utilizing inclusion lists, only sources that are specified
send to the SSM group.

Options ip-addresses—List of one or more additional SSM group addresses separated by a space.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Source-Specific Multicast Groups with Any-Source Override

Documentation

Copyright © 2017, Juniper Networks, Inc. 297

Protocol-Independent Routing Properties Feature Guide

static (Routing Options)

Syntax static {
defaults {
static-options;
}
rib-group group-name;
route destination-prefix {
bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
local-address ip-address;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
minimum-receive-ttl number;
multiplier number;
neighbor address;
no-adaptation;
transmit-interval {
threshold milliseconds;
minimum-interval milliseconds;
}
version (1 | automatic);
}
next-hop address;
next-hop options;
qualified-next-hop address {
bfd-liveness-detection {
authentication {
algorithm (keyed-md5 | keyed-sha-1 | meticulous-keyed-md5 |
meticulous-keyed-sha-1 | simple-password);
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
holddown-interval milliseconds;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}

298 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

metric metric;
preference preference;
}
static-options;
}
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-options rib routing-table-name],
[edit routing-instances routing-instance-name routing-options],
[edit routing-options],
[edit routing-options rib routing-table-name]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.0 for EX Series switches.
Support for BFD authentication introduced in Junos 9.6.
Support for BFD authentication introduced in Junos 9.6 for EX Series switches.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure static routes to be installed in the routing table. You can specify any number
of routes within a single static statement, and you can specify any number of static
options in the configuration.

Copyright © 2017, Juniper Networks, Inc. 299

Protocol-Independent Routing Properties Feature Guide

Options defaults—(Optional) Specify global static route options. These options only set default
attributes inherited by all newly created static routes. These are treated as global
defaults and apply to all the static routes you configure in the static statement.

NOTE: Specifying the global static route options does not create default
routes. These options only set default attributes inherited by all newly created
static routes.

route—Configure individual static routes. In this part of the static statement, you optionally
can configure static route options. These options apply to the individual destination
only and override any options you configured in the defaults part of the static
statement.

• destination-prefix/prefix-length—destination-prefix is the network portion of the IP

address, and prefix-length is the destination prefix length.

When you configure an individual static route in the route part of the static statement,
specify the destination of the route (in route destination-prefix) in one of the following
ways:

• network/mask-length, where network is the network portion of the IP address and

mask-length is the destination prefix length.

• default if this is the default route to the destination. This is equivalent to specifying an
IP address of 0.0.0.0/0.

NOTE: IPv4 packets with a destination of 0.0.0.0 (the obsoleted limited

broadcast address) and IPv6 packets with a destination of 0::0 are
discarded by default. To forward traffic destined to these addresses, you
can add a static route to 0.0.0.0/32 for IPv4 or 0::0/128 for IPv6.

• nsap-prefix—nsap-prefix is the network service access point (NSAP) address for ISO.

• next-hop address—Reach the next-hop routing device by specifying an IP address, an

interface name, or an ISO network entity title (NET).

IPv4 or IPv6 address of the next hop to the destination, specified as:

• IPv4 or IPv6 address of the next hop

• Interface name (for point-to-point interfaces only)

• address or interface-name to specify an IP address of a multipoint interface or an

interface name of a point-to-point interface.

NOTE: If an interface becomes unavailable, all configured static routes

on that interface are withdrawn from the routing table.

300 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

NOTE: Load balancing is not supported on management and internal

Ethernet (fxo) interfaces because this type of interface cannot handle
the routing process. On fxp interfaces, you cannot configure multiple
next hops and enable load balancing.

next-hop options—Additional information for how to manage forwarding of packets to

the next hop.

• discard—Do not forward packets addressed to this destination. Instead, drop the
packets, do not send ICMP (or ICMPv6) unreachable messages to the packets’
originators, and install a reject route for this destination into the routing table.

• iso-net—Reach the next-hop routing device by specifying an ISO NSAP.

Copyright © 2017, Juniper Networks, Inc. 301

Protocol-Independent Routing Properties Feature Guide

• next-table routing-table-name—Name of the next routing table to the destination.

If you use the next-table action, the configuration must include a term qualifier that
specifies a different table than the one specified in the next-table action. In other words,
the term qualifier in the from statement must exclude the table in the next-table action.
In the following example, the first term contains rib vrf-customer2.inet.0 as a matching
condition. The action specifies a next-hop in a different routing table,
vrf-customer1.inet.0. The second term does the opposite by using rib vrf-customer1.inet.0
in the match condition and vrf-customer2.inet.0 In the next-table action.

term 1 {
from {
protocol bgp;
rib vrf-customer2.inet.0;
community customer;
}
then {
next-hop next-table vrf-customer1.inet.0;
}
}
term 2 {
from {
protocol bgp;
rib vrf-customer1.inet.0;
community customer;
}
then {
next-hop next-table vrf-customer2.inet.0;
}
}

NOTE: Within a routing instance, you cannot configure a static route with
the next-table inet.0 statement if any static route in the main routing
instance is already configured with the next-table statement to point to
the inet.0 routing table of the routing instance. For example, if you configure
on the main routing instance a static route 192.168.88.88/32 with the
next-table test.inet.0 statement and the routing instance test is also
configured with a static route 192.168.88.88/32 with the next-table inet.0
statement, the commit operation fails. Instead, you must configure a routing
table group both on the main instance and on the routing instance, which
enables you to install the static route into both routing tables.

302 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

• receive—Install a route for this next-hop destination into the routing table.

The receive option forces the packet to be sent to the Routing Engine.

The receive option can be useful in the following cases:

• For receiving MPLS packets destined to a VRF instance's loopback address

• For receiving packets on a link's subnet address, with zeros in the host portion of the
address

• reject—Do not forward packets addressed to this destination. Instead, drop the packets,
send ICMP (or ICMPv6) unreachable messages to the packets’ originators, and install
a reject route for this destination into the routing table.

static-options—(Optional under route) Additional information about static routes, which

is included with the route when it is installed in the routing table.

You can specify one or more of the following in static-options. Each of the options is
explained separately.

• (active | passive);

• as-path <as-path> <origin (egp | igp | incomplete)> <atomic-aggregate> <aggregator

as-number in-address>;

• community [ community-ids ];

• (install | no-install);

• (metric | metric2 | metric3 | metric4) value <type type>;

• (preference | preference2 | color | color2) preference <type type>;

• (readvertise | no-readvertise);

• (resolve | no-resolve);

• (retain | no-retain);

• tag metric type number;

The remaining statements are explained separately. See CLI Explorer.

Required Privilege routing—To view this statement in the configuration.

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

Related • Understanding Basic Static Routing on page 9

Documentation
• Example: Configuring a Basic Set of Static Routes for Connecting to Stub Networks
on page 10

• Example: Configuring IPv6 Static Routes on page 15

Copyright © 2017, Juniper Networks, Inc. 303

Protocol-Independent Routing Properties Feature Guide

tag (Access)

Syntax tag tag-number;

Hierarchy Level [edit routing-options access route ip-prefix</prefix-length>]

Release Information Statement introduced in Junos OS Release 10.1.

Statement introduced in Junos OS Release 12.3 for ACX Series routers.

Description Configure a tag for an access route.

Options tag-number—Tag number for the access route.

Required Privilege interface—To view this statement in the configuration.

Level interface-control—To add this statement to the configuration.

304 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

tag (Routing Options)

Syntax tag metric type number;

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

Release Information Statement introduced before Junos OS Release 7.4.

Description Associate a tag with a static, aggregate, or generated route.

Default No tag strings are associated with routes.

Options metric—Tag metric.

Range: 0 through 4,294,967,295

type number—Tag type.

Range: 1 through 16

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Summarizing Static Routes Through Route Aggregation on page 81

Documentation
• aggregate on page 192

• generate on page 228

• static on page 298

Copyright © 2017, Juniper Networks, Inc. 305

Protocol-Independent Routing Properties Feature Guide

threshold (Multicast Forwarding Cache)

Syntax threshold {
log-warning value;
suppress value;
reuse value;
mvpn-rpt-suppress value;
mvpn-rpt-reuse value;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options multicast forwarding-cache],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options multicast forwarding-cache family (inet | inet6)],
[edit logical-systems logical-system-name routing-options multicast forwarding-cache],
[edit logical-systems logical-system-name routing-options multicast forwarding-cache
family (inet | inet6)],
[edit routing-instances routing-instance-name routing-options multicast forwarding-cache],
[edit routing-instances routing-instance-name routing-options multicast forwarding-cache
(inet | inet6)],
[edit routing-options multicast forwarding-cache],
[edit routing-options multicast forwarding-cache family (inet | inet6)]

Release Information Statement introduced before Junos OS Release 7.4.

Statement introduced in Junos OS Release 9.2 for EX Series switches.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Configure the suppression, reuse, and warning log message thresholds for multicast
forwarding cache limits. You can configure the thresholds globally for the multicast
forwarding cache or individually for the IPv4 and IPv6 multicast forwarding caches.
Configuring the threshold statement globally for the multicast forwarding cache or
including the family statement to configure the thresholds for the IPv4 and IPv6 multicast
forwarding caches are mutually exclusive.

When general forwarding-cache suppression is active, the multicast forwarding-cache

prevents forwarding traffic on the shared RP tree (RPT). At the same time, MVPN (*,G)
forwarding states are not created for new RPT c-mcast entires, and , (*,G) installed by
BGP-MVPN protocol are deleted. When general forwarding-cache suppression ends,
BGP-MVPN (*,G) entries are re-added in the RIB and restored to the FIB (up to the MVPN
(*,G) limit).

When MVPN RPT suppression is active, for all PE routers in excess of the threshold
(including RP PEs), MVPN will not add new (*,G) forwarding entries to the
forwarding-cache. Changes are visible once the entries in the current forwarding-cache
have timed out or are deleted.

To use mvpn-rpt-suppress and/or mvpn-rpt-reuse, you must first configure the general
suppress threshold. If suppress is configured but mvpn-rpt-suppress is not, both

306 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

mvpn-rpt-suppress and mvpn-rpt-reuse will inherit and use the value set for the general
suppress.

Options reuse or mvpn-rpt-reusevalue (Optional) Value at which to begin creating new multicast
forwarding cache entries. If configured, this number should be less than the suppress
value.
Range: 1 through 200,000

suppress or mvpn-rpt-suppressvalue —Value at which to begin suppressing new multicast

forwarding cache entries. This value is mandatory. This number should be greater
than the reuse value.
Range: 1 through 200,000

Required Privilege routing—To view this statement in the configuration.

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

Related • Examples: Configuring the Multicast Forwarding Cache

Documentation
• show multicast forwarding-cache statistics

Copyright © 2017, Juniper Networks, Inc. 307

Protocol-Independent Routing Properties Feature Guide

traceoptions

Syntax traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <disable>;
}

Hierarchy Level [edit logical-systems logical-system-name routing-instances routing-instance-name

routing-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name
routing-options multicast],
[edit logical-systems logical-system-name routing-options],
[edit logical-systems logical-system-name routing-options multicast],
[edit routing-instances routing-instance-name routing-options],
[edit routing-instances routing-instance-name routing-options multicast],
[edit routing-options],
[edit routing-options flow],
[edit routing-options multicast]

Release Information Statement introduced before Junos OS Release 7.4.

nsr-synchronization flag for BGP, IS-IS, LDP, and OSPF added in Junos OS Release 8.4.
nsr-synchronization and nsr-packet flags for BFD sessions added in Junos OS Release
8.5.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
nsr-synchronization flag for RIP and RIPng added in Junos OS Release 9.0.
nsr-synchronization flag for Layer 2 VPNs and VPLS added in Junos OS Release 9.1.
nsr-synchronization flag for PIM added in Junos OS Release 9.3.
nsr-synchronization flag for MPLS added in Junos OS Release 10.1.
Statement introduced in Junos OS Release 11.3 for the QFX Series.
nsr-synchronization flag for MSDP added in Junos OS Release 12.1.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Define tracing operations that track all routing protocol functionality in the routing device.

To specify more than one tracing operation, include multiple flag statements.

Default If you do not include this statement, no global tracing operations are performed.

Options Values:

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.

file filename—Name 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. We
recommend that you place global routing protocol tracing output in the file
routing-log.

308 Copyright © 2017, Juniper Networks, Inc.

Chapter 11: Configuration Statements

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. Note that if you specify a maximum number of files, you also must
specify a maximum file size with the size option.
Range: 2 through 1000 files
Default: 10 files

flag flag—Tracing operation to perform. To specify more than one tracing operation,
include multiple flag statements. These are the global routing protocol tracing
options:

• all—All tracing operations

• condition-manager—Condition-manager events

• config-internal—Configuration internals

• general—All normal operations and routing table changes (a combination of the normal
and route trace operations)

• graceful-restart—Graceful restart operations

• normal—All normal operations

• nsr-packet—Detailed trace information for BFD nonstop active routing only

• nsr-synchronization—Tracing operations for nonstop active routing

• nsr-synchronization—Nonstop active routing synchronization

• parse—Configuration parsing

• policy—Routing policy operations and actions

• regex-parse—Regular-expression parsing

• route—Routing table changes

• state—State transitions

• task—Interface transactions and processing

• timer—Timer usage

no-world-readable—(Optional) Prevent any user from reading 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. Note that 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 KB, xm to specify MB, or xg to specify GB
Range: 10 KB through the maximum file size supported on your system
Default: 128 KB

Copyright © 2017, Juniper Networks, Inc. 309

Protocol-Independent Routing Properties Feature Guide

world-readable—(Optional) Allow any user to read the log file.

Required Privilege routing and trace—To view this statement in the configuration.
Level routing-control and trace-control—To add this statement to the configuration.

Related • Example: Tracing Global Routing Protocol Operations on page 178

Documentation

unicast-reverse-path

Syntax unicast-reverse-path (active-paths | feasible-paths);

Hierarchy Level [edit logical-systems logical-system-name routing-options forwarding-table],

[edit routing-instances routing-instance-name instance-type name routing-options
forwarding-table],
[edit routing-options forwarding-table]

Release Information Statement introduced before Junos OS Release 7.4.

Support for routing instances added in Junos OS Release 8.3.
Statement introduced in Junos OS Release 12.3 for ACX Series routers.
Statement introduced in Junos OS Release 11.3 for QFX Series switches.

Description Control the operation of unicast reverse-path-forwarding check. This statement enables
the RPF check to be used when routing is asymmetrical.

Options active-paths—Consider only active paths during the unicast reverse-path check.

feasible-paths—Consider all feasible paths during the unicast reverse-path check.

Default: If you omit the unicast-reverse-path statement, only the active paths to a
particular destination are considered.

Required Privilege routing—To view this statement in the configuration.

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

Related • Example: Configuring Unicast Reverse-Path-Forwarding Check on page 150

Documentation
• Enabling Unicast Reverse-Path Forwarding Check for VPNs

310 Copyright © 2017, Juniper Networks, Inc.

CHAPTER 12

Operational Commands

• clear bfd adaptation

• clear bfd session
• show bfd session
• show as-path
• show as-path domain
• show as-path summary
• show interfaces routing summary
• show route
• show route active-path
• show route all
• show route best
• show route brief
• show route cumulative
• show route detail
• show route exact
• show route export
• show route export vrf-target
• show route forwarding-table interface-name
• show route hidden
• show route inactive-path
• show route instance
• show route label-switched-path
• show route localization
• show route martians
• show route next-hop
• show route protocol
• show route range
• show route resolution

Copyright © 2017, Juniper Networks, Inc. 311

Protocol-Independent Routing Properties Feature Guide

• show route snooping

• show route source-gateway
• show route summary
• show route table
• show route terse

312 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

clear bfd adaptation

Syntax clear bfd adaptation

Release Information Command introduced before Junos OS Release 7.4.

Description 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 all—Clear 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 For more information, see the description of the bfd-liveness-detection configuration
statement in the Junos Routing Protocols Configuration Guide.

Required Privilege clear

Level

Related • show bfd session on page 315

Documentation

List of Sample Output clear bfd adaptation on page 313

Output Fields 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

Copyright © 2017, Juniper Networks, Inc. 313

Protocol-Independent Routing Properties Feature Guide

clear bfd session

List of Syntax Syntax on page 314

Syntax (EX Series Switch and QFX Series) on page 314

Syntax clear bfd session

Syntax (EX Series clear bfd session

Switch and QFX <all>
Series) <address session-address>
<discriminator discr-number>

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1 for the QFX Series.

Description Drop one or more Bidirectional Forwarding Detection (BFD) sessions.

Options all—Drop 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 clear

Level

Related • show bfd session on page 315

Documentation

List of Sample Output clear bfd session all on page 314

Output Fields When you enter this command, you are provided feedback on the status of your request.

Sample Output

clear bfd session all

user@host> clear bfd session all

314 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

show bfd session

List of Syntax Syntax on page 315

Syntax (EX Series Switch and QFX Series) on page 315

Syntax show bfd session

Syntax (EX Series show bfd session

Release Information 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.
Option subscriber introduced in Junos OS Release 15.1 for the MX Series.

Description Display information about active Bidirectional Forwarding Detection (BFD) sessions.

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

discriminator discriminator—(Optional) Display information about the BFD session using

the specified local discriminator.

Copyright © 2017, Juniper Networks, Inc. 315

Protocol-Independent Routing Properties Feature Guide

logical-system (all | logical-system-name)—(Optional) Perform this operation on all

logical systems or on a particular logical system.

<subscriber (address destination-address | discriminator discriminator |

extensive)>—(Optional) Display information about all BFD sessions for subscribers,
or for a single BFD subscriber session with a particular destination address, or with
a particular denominator.

Required Privilege view

Level

Related • clear bfd session on page 314

Documentation
• Understanding BFD for Static Routes for Faster Network Failure Detection on page 111

• Example: Configuring BFD for Static Routes for Faster Network Failure Detection on
page 116

• Understanding BFD for OSPF

• Example: Configuring BFD for OSPF

• Understanding BFD for BGP

• Example: Configuring BFD on Internal BGP Peer Sessions

• Understanding Bidirectional Forwarding Detection Authentication for PIM

• Configuring BFD for PIM

• Understanding BFD for IS-IS

List of Sample Output show bfd session on page 320

show bfd session brief on page 321
show bfd session detail on page 321
show bfd session detail (with Authentication) on page 321
show bfd session address extensive on page 321
show bfd session client rsvp-oam on page 322
show bfd session client vpls-oam summary on page 322
show bfd session client vpls-oam instance instance-name on page 322
show bfd session extensive on page 322
show bfd session extensive (with Authentication) on page 323
show bfd session summary on page 323
show bfd session subscriber on page 323
show bfd session subscriber address on page 324
show bfd session subscriber extensive on page 324
show bfd session subscriber discriminator extensive on page 324

Output Fields Table 6 on page 317 describes the output fields for the show bfd session command. Output
fields are listed in the approximate order in which they appear.

316 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Table 6: 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 Time interval, in seconds, used by the transmitting system to send BFD control brief detail extensive
packets. none

Multiplier Negotiated multiplier by which the time interval is multiplied to determine the detail extensive
detection time for the transmitting system.

Session up time How long a BFD session has been established. detail extensive

Client Protocol or process for which the BFD session is active: ISIS, OSPF, DHCP, Static, detail extensive
or VGD.

TX interval Time interval, in seconds, used by the host system to transmit BFD control brief detail extensive
packets. none

RX interval Time interval, in seconds, used by the host system to receive BFD brief detail extensive
control packets. none

Authenticate Indicates that BFD authentication is configured. detail extensive

keychain Name of the security authentication keychain being used by a specific client. 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.

algo BFD authentication algorithm being used for a specific client: keyed-md5, extensive
keyed-sha-1, meticulous-keyed-md5, meticulous-keyed-sha-1, or simple-password.

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.

Copyright © 2017, Juniper Networks, Inc. 317

Protocol-Independent Routing Properties Feature Guide

Table 6: show bfd session Output Fields (continued)

Field Name Field Description Level of Output

mode Level of BFD authentication enforcement being used by a specific client: strict extensive
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.

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

Following are the expected values for Local Diagnostic output field:

• None—No diagnostic
• CtlExpire—Control detection time expired
• EchoExpire—Echo detection time expired
• NbrSignal—Neighbor signalled session down
• FwdPlaneReset—Forwarding plane reset
• PathDown—Path down
• ConcatPathDown—Concatenated path down
• AdminDown—Administratively down

Remote diagnostic Remote diagnostic information about failing BFD sessions. detail extensive

Following are the expected values for Remote Diagnostic output field:

Remote state Reports whether the remote system's BFD packets have been received and detail extensive
whether the remote system is receiving transmitted control packets.

Version BFD version: 0 or 1. extensive

Replicated The replicated flag appears when nonstop routing or graceful Routing Engine detail extensive
switchover is configured and the BFD session has been replicated to the backup
Routing Engine.

Min async interval Minimum amount of time, in seconds, between asynchronous control packet extensive
transmissions across the BFD session.

Min slow interval Minimum amount of time, in seconds, between synchronous control packet extensive
transmissions across the BFD session.

318 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Table 6: show bfd session Output Fields (continued)

Field Name Field Description Level of Output

Adaptive async TX Transmission interval being used because of adaptation. extensive

interval

RX interval Minimum required receive interval. extensive

Local min TX Minimum amount of time, in seconds, between control packet transmissions extensive
interval on the local system.

Local min RX Minimum amount of time, in seconds, between control packet detections on extensive
interval the local system.

Remote min TX Minimum amount of time, in seconds, between control packet transmissions extensive
interval on the remote system.

Remote min TX Minimum amount of time, in seconds, between control packet detections on extensive
interval the remote system.

Threshold Threshold for notification if the transmission interval increases. extensive

transmission
interval

Threshold for Threshold for notification if the detection time increases. extensive
detection time

Local discriminator Authentication code used by the local system to identify that BFD session. extensive

Remote Authentication code used by the remote system to identify that BFD session. extensive
discriminator

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 All levels
at the egress of an LDP FEC, where the BFD session has an LDP Operation,
Administration, and Maintenance (OAM) client.

Remote is The BFD session on the remote peer is running on its Packet Forwarding Engine. extensive
control-plane In this case, when the remote node undergoes a graceful restart, the local peer
independent can help the remote peer with the graceful restart.

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 © 2017, Juniper Networks, Inc. 319

Protocol-Independent Routing Properties Feature Guide

Table 6: show bfd session Output Fields (continued)

Field Name Field Description Level of Output

Authentication Summary status of BFD authentication: extensive

• status—enabled/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.
• keychain—Name of the security authentication keychain associated with the
specified BFD session.
• algo—BFD authentication algorithm being used: keyed-md5, keyed-sha-1,
meticulous-keyed-md5, meticulous-keyed-sha-1, or simple-password.
• mode—Level 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 detail extensive
reroute (FRR) and loop-free alternate (LFA).

sessions Total number of active BFD sessions. All levels

clients Total number of clients that are hosting active BFD sessions. All levels

Cumulative Total number of BFD control packets transmitted per second on all All levels
transmit rate active sessions.

Cumulative receive Total number of BFD control packets received per second on all active sessions. All levels
rate

Multi-hop, Minimum time to live (TTL) accepted if the session is configured for multihop. extensive
min-recv-TTL

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
Transmit
Address State Interface Detect Time Interval Multiplier
10.9.1.33 Up so-7/1/0.0 0.600 0.200 3
10.9.1.29 Up ge-4/0/0.0 0.600 0.200 3

320 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

2 sessions, 2 clients
Cumulative transmit rate 10.0 pps, cumulative receive rate 10.0 pps

show bfd session brief

The output for the show bfd session brief command is identical to that for the show bfd
session command.

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:02
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:04, 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:18
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:12, 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

Copyright © 2017, Juniper Networks, Inc. 321

Protocol-Independent Routing Properties Feature Guide

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
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
Detect Transmit
Address State Interface Time Interval Multiplier

192.168.0.223 Up 540.000 180.000 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 Multiplier

127.0.0.1 Up ae9.0 3.000 1.000 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
Detect Transmit
Address State Interface Time Interval Multiplier
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

322 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

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

show bfd session subscriber

user@host> show bfd session subscriber
Detect Transmit
Address State Interface Time Interval Multiplier
1.0.0.2 Up ae0.0 90.000 30.000 3

Copyright © 2017, Juniper Networks, Inc. 323

Protocol-Independent Routing Properties Feature Guide

1.0.0.6 Up ae0.1 90.000 30.000 3

1.0.0.10 Up ae0.2 90.000 30.000 3
1.0.0.14 Up ae0.3 90.000 30.000 3
1.0.0.18 Up ae0.4 90.000 30.000 3

20 sessions, 20 clients

show bfd session subscriber address

user@host> show bfd session subscriber address 1.0.0.2
Detect Transmit
Address State Interface Time Interval Multiplier
1.0.0.2 Up ae0.0 90.000 30.000 3

1 sessions, 1 clients
Cumulative transmit rate 5.0 pps, cumulative receive rate 5.0 pps

show bfd session subscriber extensive

user@host> show bfd session subscriber extensive
Detect Transmit
Address State Interface Time Interval Multiplier
1.0.0.2 Up ae0.0 90.000 30.000 3

Client DHCP, TX interval 30.000, RX interval 30.000

Session up time 09:11:50
Local diagnostic None, remote diagnostic NbrSignal
Remote state Up, version 1
Replicated
Min async interval 30.000, min slow interval 30.000
Adaptive async TX interval 30.000, RX interval 30.000
Local min TX interval 30.000, minimum RX interval 30.000, multiplier 3
Remote min TX interval 30.000, min RX interval 30.000, multiplier 3
Local discriminator 20, remote discriminator 16
Echo mode disabled/inactive
Remote is control-plane independent
Session ID: 0x1

Detect Transmit
Address State Interface Time Interval Multiplier
1.0.0.6 Up ae0.1 90.000 30.000 3

Client DHCP, TX interval 30.000, RX interval 30.000

Session up time 09:11:50
Local diagnostic None, remote diagnostic NbrSignal
Remote state Up, version 1
Replicated
Min async interval 30.000, min slow interval 30.000
Adaptive async TX interval 30.000, RX interval 30.000
Local min TX interval 30.000, minimum RX interval 30.000, multiplier 3
Remote min TX interval 30.000, min RX interval 30.000, multiplier 3
Local discriminator 21, remote discriminator 17
Echo mode disabled/inactive
Remote is control-plane independent
Session ID: 0x2

show bfd session subscriber discriminator extensive

user@host> show bfd session subscriber discriminator 20 extensive

324 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Detect Transmit
Address State Interface Time Interval Multiplier
1.0.0.2 Up ae0.0 90.000 30.000 3

Client DHCP, TX interval 30.000, RX interval 30.000

1 sessions, 1 clients
Cumulative transmit rate 5.0 pps, cumulative receive rate 5.0 pps

Copyright © 2017, Juniper Networks, Inc. 325

Protocol-Independent Routing Properties Feature Guide

show as-path

List of Syntax Syntax on page 326

Syntax (EX Series Switches) on page 326

Syntax show as-path

Syntax (EX Series show as-path

Switches) <brief | detail>

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.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description 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 none—Display 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 view

Level

Related • show as-path summary on page 334

Documentation

List of Sample Output show as-path on page 327

show as-path detail on page 328

Output Fields Table 7 on page 327 lists the output fields for the show as-path command. Output fields
are listed in the approximate order in which they appear.

326 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Table 7: 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 All levels
path indicate the path origin, providing an indication of the state of the route at
the point at which the AS path originated:

• I—IGP.
• E—EGP.
• ?—Incomplete; typically, the AS path was aggregated.
• Atomic—Route is an aggregate of several route prefixes.
• Aggregator—Routing device has summarized a range of prefixes.

domain Number of independent AS domains. The AS paths of an independent AS detail

domain are not shared with the AS paths and AS path attributes of other
domains, including the master routing instance domain.

neighbor as AS peer address. detail

length Length of the AS path. detail

segments Length of the AS segment descriptor. detail

unique-count Number of unique autonomous systems (ASs) present in the AS path 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

Copyright © 2017, Juniper Networks, Inc. 327

Protocol-Independent Routing Properties Feature Guide

14203 2914 1239 7132 16394 I

14203 2914 1299 8308 34826 I
14203 2914 3320 5603 28682 I
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, unique-count 0, references 54
AS path: 14203 2914 174 31752 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 4,
references 2
AS path: 14203 2914 701 21512 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 4,
references 2
AS path: 14203 2914 1239 26632 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 5,
references 2
AS path: 14203 2914 1239 29704 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 4,
references 2
AS path: 14203 2914 4323 10248 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 6,
references 2
AS path: 14203 2914 4766 23560 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 4,
references 2
AS path: 14203 2914 6395 32776 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 5,

328 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

references 3
AS path: 14203 2914 7911 11272 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 6,
references 2
AS path: 14203 2914 12180 18440 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 3,
references 3
AS path: 14203 2914 17408 17416 I
domain 1, neighbor as: 14203, length 4, segments 1, unique-count 8,
references 3
AS path: 14203 2914 701 702 24586 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 4,
references 3
AS path: 14203 2914 1239 4657 9226 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 5,
references 7
AS path: 14203 2914 1239 7132 16394 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 7,
references 2
AS path: 14203 2914 1299 8308 34826 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 8,
references 2
AS path: 14203 2914 3320 5603 28682 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 4,
references 2
AS path: 14203 2914 3491 1680 33802 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 14,
references 2
AS path: 14203 2914 3549 7908 27658 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 6,
references 2
AS path: 14203 2914 3549 20804 30730 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 24,
references 2
AS path: 14203 2914 7018 2687 9226 I
domain 1, neighbor as: 14203, length 5, segments 1, unique-count 4,
references 3
AS path: 14203 2914 174 9318 9318 23564 I
domain 1, neighbor as: 14203, length 6, segments 1, unique-count 4,
references 2
AS path: 14203 2914 701 3786 3786 23564 I
domain 1, neighbor as: 14203, length 6, segments 1, unique-count 4,
references 2
AS path: 14203 2914 701 4761 4795 9228 I
domain 1, neighbor as: 14203, length 6, segments 1, unique-count 4,
references 14
AS path: 14203 2914 1239 7132 5673 18444 I
domain 1, neighbor as: 14203, length 6, segments 1, unique-count 4,
references 2
AS path: 14203 2914 3491 20485 24588 24588 I
domain 1, neighbor as: 14203, length 6, segments 1, unique-count 4,
references 4
AS path: 14203 2914 5511 2200 1945 2060 I
domain 1, neighbor as: 14203, length 6, segments 1, unique-count 4,
references 2
AS path: 14203 2914 7911 14325 14325 14348 I
domain 1, neighbor as: 14203, length 6, segments 1, unique-count 4,
references 2
AS path: 14203 2914 701 4637 9230 9230 9230 I
domain 1, neighbor as: 14203, length 7, segments 1, unique-count 4,
references 3

Copyright © 2017, Juniper Networks, Inc. 329

Protocol-Independent Routing Properties Feature Guide

AS path: 14203 2914 6395 14 14 14 14 I

domain 1, neighbor as: 14203, length 7, segments 1, unique-count 4,
references 10
...

330 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

show as-path domain

List of Syntax Syntax on page 331

Syntax (EX Series Switches) on page 331

Syntax show as-path domain

<logical-system (all | logical-system-name)>

Syntax (EX Series show as-path domain

Switches)

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description Display autonomous system (AS) path domain information.

Options 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 view

Level

List of Sample Output show as-path domain on page 333

Output Fields Table 8 on page 331 lists the output fields for the show as-path domain command. Output
fields are listed in the approximate order in which they appear

Table 8: 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.

Copyright © 2017, Juniper Networks, Inc. 331

Protocol-Independent Routing Properties Feature Guide

Table 8: show as-path domain Output Fields (continued)

Field Name Field Description

Flags Information about the AS path:

• ASLoop—Path contains an AS loop.

• Atomic—Path includes the ATOMIC_AGGREGATE path attribute.
• Local—Path was created by local aggregation.
• Master—Path was created by the master routing instance.

Local AS AS number of the local routing device.

Loops How many times this AS number can appear in an AS path.

332 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Sample Output

show as-path domain

user@host> show as-path domain
Domain: 1 Primary: 10458
References: 3 Paths: 30383
Flags: Master
Local AS: 10458 Loops: 1

Copyright © 2017, Juniper Networks, Inc. 333

Protocol-Independent Routing Properties Feature Guide

show as-path summary

List of Syntax Syntax on page 334

Syntax (EX Series Switches) on page 334

Syntax show as-path summary

<logical-system (all | logical-system-name)>

Syntax (EX Series show as-path summary

Switches)

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description Display autonomous system (AS) path summary information.

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 view

Level

Related • show as-path on page 326

Documentation

List of Sample Output show as-path summary on page 335

Output Fields Table 9 on page 334 lists the output fields for the show as-path summary command.
Output fields are listed in the approximate order in which they appear.

Table 9: show as-path summary Output Fields

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.

334 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Table 9: show as-path summary Output Fields (continued)

Field Name Field Description

Min Minimum number of AS path entries per bucket.

Avg Average number of AS path entries per bucket.

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 Avg Std deviation
30425 1024 95 12 29 6.481419

Copyright © 2017, Juniper Networks, Inc. 335

Protocol-Independent Routing Properties Feature Guide

show interfaces routing summary

Syntax show interfaces routing summary

<interface-name>
<logical-system (all | logical-system-name)>

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 12.1x48 for PTX Series Packet Transport
Routers.

Description Display a summary of the state of the router interfaces. Use this command for performing
router diagnostics only, when you are determining whether the routing protocols and the
Junos OS differ about the state of an interface.

Options none—Display summary information about the state of all router interfaces on all logical
systems.

interface-name—(Optional) Name of 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 For information about how to configure routing protocols, see the Junos OS Routing
Protocols Library. For information about related operational mode commands for routing
instances and protocols, see the CLI Explorer.

Required Privilege view

Level

List of Sample Output show interfaces routing summary on page 337

show interfaces routing summary (TX Matrix Plus Router) on page 337
show interfaces routing summary (PTX5000 Packet Transport Routers) on page 338

Output Fields Table 10 on page 336 lists the output fields for the show interfaces routing summary
command. Output fields are listed in the approximate order in which they appear.

Table 10: show interfaces routing summary Output Fields

Field Name Field Description

n physical interfaces Number of routing interfaces and number of interfaces in the up

state.

n protocol protocol Type and number of routing protocols and number of related
interfaces interfaces in the up state.

Interface Logical interface name.

336 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Table 10: show interfaces routing summary Output Fields (continued)

Field Name Field Description

Index Logical interface index number, which reflects its initialization

sequence.

Metric Metric value for the interface.

Trans Number of times the interface has transitioned from Down to Up.

Status Interface status (Up or Down) and type.

Sample Output

show interfaces routing summary

user@host> show interfaces routing summary
14 physical interfaces (12 up)
11 INET protocol addresses (11 up)
6 ISO protocol addresses (4 up)
3 MPLS protocol addresses (3 up)
3 CCC protocol addresses (3 up)
Interface Index Metric Trans. Status
so-5/0/3.0 15 0 0 Broadcast PointToPoint Multicast
so-5/0/2.0 14 0 0 Up Broadcast PointToPoint Multicast
so-5/0/1.0 13 0 5 Up Broadcast PointToPoint Multicast
so-5/0/0.0 12 0 2 Up Broadcast PointToPoint Multicast
so-1/2/0.0 11 0 0 Broadcast PointToPoint Multicast
so-1/1/0.0 10 0 5 Up Broadcast PointToPoint Multicast
at-1/0/0.6 9 0 0 Up Broadcast PointToPoint Multicast
at-1/0/0.5 8 0 0 Up Broadcast PointToPoint Multicast
at-1/0/0.4 7 0 0 Up Broadcast PointToPoint Multicast
at-1/0/0.3 6 0 0 Up Broadcast PointToPoint Multicast
at-1/0/0.2 5 0 0 Up Broadcast PointToPoint Multicast
at-1/0/0.0 4 0 0 Up Broadcast PointToPoint Multicast
lo0.0 3 0 0 Up Broadcast Loopback Multicast
fxp1.0 2 0 1 Up Broadcast Multicast
fxp0.0 1 0 0 Up Broadcast Multicast

show interfaces routing summary (TX Matrix Plus Router)

user@host> show interfaces routing summary
9 physical interfaces (9 up)
11 INET protocol addresses (11 up)
6 MPLS protocol addresses (6 up)
4 INET6 protocol addresses (4 up)

Interface Index Metric Trans. Status

ge-23/0/8.0 73 0 0 Up Broadcast Multicast
ge-23/0/7.0 72 0 0 Up Broadcast Multicast
ge-23/0/6.0 71 0 0 Up Broadcast Multicast
ge-7/0/9.0 69 0 0 Up Broadcast Multicast
ge-15/0/9.0 70 0 0 Up Broadcast Multicast
xe-6/1/1.0 68 0 0 Up Broadcast Multicast
lo0.16385 66 0 0 Up Broadcast Loopback Multicast
lo0.16384 65 0 0 Up Broadcast Loopback Multicast

Copyright © 2017, Juniper Networks, Inc. 337

Protocol-Independent Routing Properties Feature Guide

lo0.0 64 0 0 Up Broadcast Loopback Multicast

ixgbe1.0 5 0 0 Up Broadcast Multicast
ixgbe0.0 4 0 0 Up Broadcast Multicast
em0.0 3 0 0 Up Broadcast Multicast

show interfaces routing summary (PTX5000 Packet Transport Routers)

user@host> show interfaces routing summary
7 physical interfaces (68 up)
7 INET protocol addresses (7 up)
2 CCC protocol addresses (2 up)
4 INET6 protocol addresses (4 up)

Interface Index Metric Trans. Status

lo0.16385 66 0 0 Up Broadcast Loopback Multicast
lo0.16384 64 0 0 Up Broadcast Loopback Multicast
lo0.0 65 0 0 Up Broadcast Loopback Multicast
ixgbe1.0 5 0 0 Up Broadcast Multicast
ixgbe0.0 4 0 0 Up Broadcast Multicast
et-5/0/5.32767 72 0 0 Up Broadcast Multicast
et-5/0/5.0 68 0 0 Up Broadcast Multicast
et-5/0/0.32767 67 0 0 Up Broadcast Multicast
et-5/0/0.0 71 0 0 Up Broadcast Multicast
em0.0 3 0 0 Up Broadcast Multicast

338 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

show route

List of Syntax Syntax on page 339

Syntax (EX Series Switches) on page 339

Syntax show route

Syntax (EX Series show route

Switches) <all>
<destination-prefix>
<private>

Release Information 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.
Command introduced in Junos OS Release 15.1R3 on MX Series routers for enhanced
subscriber management.
Option display-client-data introduced in Junos OS Release 16.2R1 on MX80, MX104,
MX240, MX480, MX960, MX2010, MX2020, vMX Series routers.
Options te-ipv4-prefix-ip, te-ipv4-prefix-node-ip, and te-ipv4-prefix-node-iso introduced
in Junos OS Release 17.2R1 on MX Series and PTX Series.

Description Display the active entries in the routing tables.

Options none—Display 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.

display-client-data —(Optional) Display client id and cookie information for routes

installed by the routing protocol process client applications.

te-ipv4-prefix-ip te-ipv4-prefix-ip—(Optional) Display IPv4 address of the

traffic-engineering prefix, without the mask length if present in the routing table.

Copyright © 2017, Juniper Networks, Inc. 339

Protocol-Independent Routing Properties Feature Guide

te-ipv4-prefix-node-ip te-ipv4-prefix-node-ip—(Optional) Display all prefixes that have

originated from the traffic-engineering node. You can filter IPv4 node addresses from
the traffic-engineered routes in the lsdist.0 table.

te-ipv4-prefix-node-iso te-ipv4-prefix-node-iso—(Optional) Display all prefixes that

have originated from the traffic-engineering node. You can filter IPv4 routes with the
specified ISO circuit ID from the lsdist.0 table.

Required Privilege view

Level

Related • Understanding IS-IS Configuration

Documentation
• Example: Configuring IS-IS

• Examples: Configuring Internal BGP Peering

• Examples: Configuring External BGP Peering

• Examples: Configuring OSPF Routing Policy

• Verifying and Managing Junos OS Enhanced Subscriber Management

List of Sample Output show route on page 343

show route (VPN) on page 344
show route (with Destination Prefix) on page 344
show route destination-prefix detail on page 344
show route extensive on page 344
show route extensive ( ECMP) on page 345
show route extensive (Multipath Resolution) on page 345
show route (Enhanced Subscriber Management) on page 346
show route (IPv6 Flow Specification) on page 346
show route display-client-data detail on page 347
show route te-ipv4-prefix-ip on page 347
show route te-ipv4-prefix-ip extensive on page 348
show route te-ipv4-prefix-node-iso on page 350
show route te-ipv4-prefix-node-iso extensive on page 351
show route te-ipv4-prefix-node-iso detail on page 353

Output Fields Table 11 on page 340 describes the output fields for the show route command. Output
fields are listed in the approximate order in which they appear.

Table 11: 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.

340 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Table 11: show route 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:

• 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.
• hidden (routes that are not used because of a routing policy).

destination-prefix 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-address—Address of the neighbor.
• control-word-status—Whether the use of the control word has been negotiated for this virtual
circuit: NoCtrlWord or CtrlWord.
• encapsulation type—Type 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-id—Virtual circuit identifier.
• source—Source of the advertisement: Local or Remote.

[ 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 How long the route been known (for example, 2w4d 13:11:14, or 2 weeks, 4 days, 13 hours, 11 minutes,
hours:minutes:seconds 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.

Copyright © 2017, Juniper Networks, Inc. 341

Protocol-Independent Routing Properties Feature Guide

Table 11: show route Output Fields (continued)

Field Name Field Description

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:

• I—IGP.
• E—EGP.
• ?—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.

encapsulated Extended next-hop encoding capability enabled for the specified BGP community for routing IPv4
traffic over IPv6 tunnels. When BGP receives routes without the tunnel community, V40V6 tunnels
are not created and BGP routes are resolved without encapsulation.

Route Labels Stack of labels carried in the BGP route update.

validation-state (BGP-learned routes) Validation status of the route:

• Invalid—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.
• Unknown—Indicates that the prefix is not among the prefixes or prefix ranges in the database.
• Unverified—Indicates 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.
• Valid—Indicates that the prefix and autonomous system pair are found in the database.

to Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.

If the destination is Discard, traffic is dropped.

342 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Table 11: show route Output Fields (continued)

Field Name Field Description

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:

• 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.
• Balance—Balance 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-name—Name of the LSP used to reach the next hop.
• label-action—MPLS 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).

Private unicast (Enhanced subscriber management for MX Series routers) Indicates that an access-internal route is
managed by enhanced subscriber management. By contrast, access-internal routes not managed
by enhanced subscriber management are displayed with associated next-hop and media access
control (MAC) address information.

balance Distribution of the load based on the underlying operational interface bandwidth for equal-cost
multipaths (ECMP) across the nexthop gateways in percentages.

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

Copyright © 2017, Juniper Networks, Inc. 343

Protocol-Independent Routing Properties Feature Guide

show route (VPN)

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 192.0.2.0

13979:665001.inet.0: 871 destinations, 3556 routes (871 active, 0 holddown, 0

hidden)
+ = Active Route, - = Last Active, * = Both

192.0.2.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 (with 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 destination-prefix detail

user@host> show route 198.51.100.0 detail

inet.0: 15 destinations, 20 routes (15 active, 0 holddown, 0 hidden)

198.51.100.0/24 (2 entries, 2 announced)
*BGP Preference: 170/-101
...
BGP-Static Preference: 4294967292
Next hop type: Discard
Address: 0x9041ae4
Next-hop reference count: 2
State: <NoReadvrt Int Ext AlwaysFlash>
Inactive reason: Route Preference
Local AS: 200
Age: 4d 1:40:40
Validation State: unverified
Task: RT
Announcement bits (1): 2-BGP_RT_Background
AS path: 4 5 6 I

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

344 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

PMSI: Flags 0x0: Label[0:0:0]: PIM-SM: Sender 10.0.0.40 Group

203.0.113.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: 64510 Peer AS: 64511
Age: 3 Metric2: 1
Validation State: unverified
Task: BGP_64510.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:64502:100 encapsulation:0L:14 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

show route extensive ( ECMP)

user@host> show route extensive
*IS-IS Preference: 15
Level: 1
Next hop type: Router, Next hop index: 1048577
Address: 0xXXXXXXXXXX
Next-hop reference count: YY
Next hop: 172.16.50.2 via ae1.0 balance 43%, selected
Session Id: 0x141
Next hop: 192.0.2.2 via ae0.0 balance 57%

show route extensive (Multipath Resolution)

user@host> show route extensive
inet.0: 37 destinations, 37 routes (36 active, 0 holddown, 1 hidden)
10.1.1.2/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.1.1.2/32 -> {indirect(1048574)}
*Static Preference: 5
Next hop type: Indirect, Next hop index: 0
Address: 0xb39d1b0
Next-hop reference count: 2
Next hop type: Router, Next hop index: 581
Next hop: 12.1.1.2 via ge-2/0/1.0, selected
Session Id: 0x144
Next hop: 13.1.1.2 via ge-2/0/2.0, selected
Session Id: 0x145

Copyright © 2017, Juniper Networks, Inc. 345

Protocol-Independent Routing Properties Feature Guide

Protocol next hop: 10.1.1.1

Indirect next hop: 0xb2b20f0 1048574 INH Session ID: 0x143
State: <Active Int Ext>
Age: 2:53 Metric2: 0
Validation State: unverified
Task: RT
Announcement bits (2): 0-KRT 2-Resolve tree 1
AS path: I
Indirect next hops: 1
Protocol next hop: 10.1.1.1
Indirect next hop: 0xb2b20f0 1048574 INH Session ID: 0x143

Indirect path forwarding next hops: 2

Next hop type: Router
Next hop: 12.1.1.2 via ge-2/0/1.0
Session Id: 0x144
Next hop: 13.1.1.2 via ge-2/0/2.0
Session Id: 0x145
10.1.1.1/32 Originating RIB: inet.0
Node path count: 1
Node flags: 1
Forwarding nexthops: 2 (Merged)
Nexthop: 12.1.1.2 via ge-2/0/1.0
Nexthop: 13.1.1.2 via ge-2/0/2.0

show route (Enhanced Subscriber Management)

user@host> show route
inet.0: 41 destinations, 41 routes (40 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

198.51.100.11/24 *[Access-internal/12] 00:00:08

> to #0 10.0.0.1.93.65 via demux0.1073741824
198.51.100.12/24 *[Access-internal/12] 00:00:08
Private unicast

show route (IPv6 Flow Specification)

user@host> show route
inet6.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2001:db8::10:255:185:19/128
*[Direct/0] 05:11:27
> via lo0.0
2001:db8::11:11:11:0/120
*[BGP/170] 00:28:58, localpref 100
AS path: 2000 I, validation-state: unverified
> to 2001:db8::13:14:2:2 via ge-1/1/4.0
2001:db8::13:14:2:0/120*[Direct/0] 00:45:07
> via ge-1/1/4.0
2001:db8::13:14:2:1/128*[Local/0] 00:45:18
Local via ge-1/1/4.0
fe80::2a0:a50f:fc71:71d5/128
*[Direct/0] 05:11:27
> via lo0.0
fe80::5e5e:abff:feb0:933e/128
*[Local/0] 00:45:18
Local via ge-1/1/4.0

346 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

inet6flow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

2001:db8::11:11:11:10/128,*,proto=6,dstport=80,srcport=65535/term:1
*[BGP/170] 00:28:58, localpref 100, from 2001:db8::13:14:2:2
AS path: 2000 I, validation-state: unverified
Fictitious
2001:db8::11:11:11:30/128,*,icmp6-type=128,len=100,dscp=10/term:2
*[BGP/170] 00:20:54, localpref 100, from 2001:db8::13:14:2:2
AS path: 2000 I, validation-state: unverified
Fictitious

show route display-client-data detail

user@host> show route 198.51.100.0/24 display-client-data detail
inet.0: 59 destinations, 70 routes (59 active, 0 holddown, 0 hidden)
198.51.100.0/24 (1 entry, 1 announced)
State: <FlashAll>
*BGP-Static Preference: 5/-101
Next hop type: Indirect, Next hop index: 0
Address: 0xa5c2af8
Next-hop reference count: 2
Next hop type: Router, Next hop index: 1641
Next hop: 192.0.2.1 via ge-2/1/1.0, selected
Session Id: 0x160
Protocol next hop: 192.0.2.1
Indirect next hop: 0xa732cb0 1048621 INH Session ID: 0x17e
State: <Active Int Ext AlwaysFlash NSR-incapable Programmed>
Age: 3:13 Metric2: 0
Validation State: unverified
Announcement bits (3): 0-KRT 5-LDP 6-Resolve tree 3
AS path: I
Client id: 1, Cookie: 1

show route te-ipv4-prefix-ip

user@host> show route te-ipv4-prefix-ip 10.10.10.10
lsdist.0: 283 destinations, 283 routes (283 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L1:0

}/1152
*[IS-IS/15] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0101.0101.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0202.0202.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0303.0303.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0404.0404.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152

Copyright © 2017, Juniper Networks, Inc. 347

Protocol-Independent Routing Properties Feature Guide

*[IS-IS/18] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0505.0505.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0606.0606.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0707.0707.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:01:01
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:01:01
Fictitious

show route te-ipv4-prefix-ip extensive

user@host>show route te-ipv4-prefix-ip 10.10.10.10 extensive
lsdist.0: 298 destinations, 298 routes (298 active, 0 holddown, 0 hidden)
*IS-IS Preference: 15
Level: 1
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State:<Active NotInstall>
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0x40, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0101.0101.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State: <Active NotInstall
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0xe0, Algo: 0>

PREFIX { Node { AS:100 ISO:0100.0202.0202.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:

348 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

State: <Active NotInstall>

Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0303.0303.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0404.0404.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0505.0505.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0606.0606.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0

Copyright © 2017, Juniper Networks, Inc. 349

Protocol-Independent Routing Properties Feature Guide

Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0707.0707.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 298
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 7:58
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0x40, Algo: 0

show route te-ipv4-prefix-node-iso

user@host> show route te-ipv4-prefix-node-iso 0100.0a0a.0a0a.00
lsdist.0: 283 destinations, 283 routes (283 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L1:0

}/1152
*[IS-IS/15] 00:05:20
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:1.1.1.1/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:05:20
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:2.2.2.2/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:05:20
Fictitious

350 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:3.3.3.3/32 } ISIS-L2:0

}/1152
*[IS-IS/18] 00:05:20
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:4.4.4.4/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:05:20
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:5.5.5.5/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:05:20
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:6.6.6.6/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:05:20
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:7.7.7.7/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:05:20
Fictitious
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0
}/1152
*[IS-IS/18] 00:05:20
Fictitious

show route te-ipv4-prefix-node-iso extensive

user@host> show route te-ipv4-prefix-node-iso 0100.0a0a.0a0a.00 extensive
lsdist.0: 283 destinations, 283 routes (283 active, 0 holddown, 0 hidden)
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L1:0
}/1152 (1 entry, 0 announced)
*IS-IS Preference: 15
Level: 1
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:47
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0x40, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:1.1.1.1/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:47
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1001, Flags: 0xe0, Algo: 0

Copyright © 2017, Juniper Networks, Inc. 351

Protocol-Independent Routing Properties Feature Guide

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:2.2.2.2/32 } ISIS-L2:0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:3.3.3.3/32 } ISIS-L2:0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:4.4.4.4/32 } ISIS-L2:0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:5.5.5.5/32 } ISIS-L2:0

352 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

Task: IS-IS
AS path: I
Prefix SID: 1005, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:6.6.6.6/32 } ISIS-L2:0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:7.7.7.7/32 } ISIS-L2:0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

show route te-ipv4-prefix-node-iso detail

user@host> show route te-ipv4-prefix-node-iso 0100.0a0a.0a0a.00 detail
lsdist.0: 283 destinations, 283 routes (283 active, 0 holddown, 0 hidden)
PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L1:0
}/1152 (1 entry, 0 announced)
*IS-IS Preference: 15
Level: 1

Copyright © 2017, Juniper Networks, Inc. 353

Protocol-Independent Routing Properties Feature Guide

Next hop type: Fictitious, Next hop index: 0

Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0x40, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:1.1.1.1/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1001, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:2.2.2.2/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1002, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:3.3.3.3/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1003, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:4.4.4.4/32 } ISIS-L2:0

354 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

}/1152 (1 entry, 0 announced)

*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1004, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:5.5.5.5/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1005, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:6.6.6.6/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1006, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:7.7.7.7/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I

Copyright © 2017, Juniper Networks, Inc. 355

Protocol-Independent Routing Properties Feature Guide

Prefix SID: 1007, Flags: 0xe0, Algo: 0

PREFIX { Node { AS:100 ISO:0100.0a0a.0a0a.00 } { IPv4:10.10.10.10/32 } ISIS-L2:0

}/1152 (1 entry, 0 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Fictitious, Next hop index: 0
Address: 0xa1a2ac4
Next-hop reference count: 283
Next hop:
State: <Active NotInstall>
Local AS: 100
Age: 6:54
Validation State: unverified
Task: IS-IS
AS path: I
Prefix SID: 1000, Flags: 0x40, Algo: 0

356 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

show route active-path

List of Syntax Syntax on page 357

Syntax (EX Series Switches) on page 357

Syntax show route active-path

Syntax (EX Series show route active-path

Switches) <brief | detail | extensive | terse>

Release Information Command introduced in Junos OS Release 8.0.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description Display all active routes for destinations. An active route is a route that is selected as the
best path. Inactive routes are not displayed.

Options none—Display 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 view

Level

List of Sample Output show route active-path on page 357

show route active-path brief on page 358
show route active-path detail on page 358
show route active-path extensive on page 359
show route active-path terse on page 361

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 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 *[Direct/0] 21:33:52

Copyright © 2017, Juniper Networks, Inc. 357

Protocol-Independent Routing Properties Feature Guide

> via lo0.0

10.255.71.50/32 *[IS-IS/15] 00:18:13, metric 10
> to 172.16.100.1 via so-2/1/3.0
172.16.100.1/24 *[Direct/0] 00:18:36
> via so-2/1/3.0
172.16.100.1/32 *[Local/0] 00:18:41
Local via so-2/1/3.0
192.168.64.0/21 *[Direct/0] 21:33:52
> via fxp0.0
192.168.70.19/32 *[Local/0] 21:33:52
Local via fxp0.0

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

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

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

358 Copyright © 2017, Juniper Networks, Inc.

Chapter 12: Operational Commands

AS path: I

172.16.100.1/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: 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)

Protocol-Independent Routing Properties Feature Guide

TSI:
KRT in-kernel 10.255.71.50/32 -> {172.16.100.1}
IS-IS level 2, LSP fragment 0
*IS-IS Preference: 15
Level: 1
Next hop type: Router, Next hop index: 397
Next-hop reference count: 4
Next hop: 172.16.100.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

172.16.100.1/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

172.16.100.1/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

Chapter 12: Operational Commands

State: ‹Active NoReadvrt Int›

Local AS: 200
Age: 21:39:47
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3
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 Destination P Prf Metric 1 Metric 2 Next hop AS path

* 10.255.70.19/32 D 0 >lo0.0
* 10.255.71.50/32 I 15 10 >172.16.100.1.
* 172.16.100.0/24 D 0 >so-2/1/3.0
* 172.16.100.2/32 L 0 Local
* 192.168.64.0/21 D 0 >fxp0.0
* 192.168.70.19/32 L 0 Local

Protocol-Independent Routing Properties Feature Guide

show route all

List of Syntax Syntax on page 362

Syntax (EX Series Switches) on page 362

Syntax show route all

<logical-system (all | logical-system-name)>

Syntax (EX Series show route all

Switches)

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description Display information about all routes in all routing tables, including private, or internal,
tables.

Options none—Display 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 view

Level

Related • show route brief on page 367

Documentation
• show route detail on page 370

List of Sample Output show route all on page 362

Output Fields 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

Chapter 12: Operational Commands

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

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

Protocol-Independent Routing Properties Feature Guide

show route best

List of Syntax Syntax on page 364

Syntax (EX Series Switches) on page 364

Syntax show route best destination-prefix

Syntax (EX Series show route best destination-prefix

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

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.

destination-prefix—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 view

Level

Related • show route brief on page 367

Documentation
• show route detail on page 370

List of Sample Output show route best on page 364

show route best detail on page 365
show route best extensive on page 366
show route best terse on page 366

Sample Output

show route best

user@host> show route best 10.255.70.103

Chapter 12: Operational Commands

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

Protocol-Independent Routing Properties Feature Guide

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

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 P Prf Metric 1 Metric 2 Next hop AS path

* 10.255.70.103/32 O 10 2 >10.31.1.6
so-0/3/0.0

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

Restart Complete
+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

* 10.255.70.103/32 R 7 2 >so-0/3/0.0

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

* 10.0.0.0/8 D 0 >fxp2.0
D 0 >fxp1.0

Chapter 12: Operational Commands

show route brief

List of Syntax Syntax on page 367

Syntax (EX Series Switches) on page 367

Syntax show route brief

<destination-prefix>
<logical-system (all | logical-system-name)>

Syntax (EX Series show route brief

Switches) <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 none—Display 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 view

Level

Related • show route all on page 362

Documentation
• show route best on page 364

List of Sample Output show route brief on page 367

Output Fields 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 *[Static/5] 1w5d 20:30:29

Discard
10.255.245.51/32 *[Direct/0] 2w4d 13:11:14
> via lo0.0

Protocol-Independent Routing Properties Feature Guide

172.16.0.0/12 *[Static/5] 2w4d 13:11:14

> to 192.168.167.254 via fxp0.0
192.168.0.0/18 *[Static/5] 1w5d 20:30:29
> to 192.168.167.254 via fxp0.0
192.168.40.0/22 *[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via fxp0.0
192.168.64.0/18 *[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via fxp0.0
192.168.164.0/22 *[Direct/0] 2w4d 13:11:14
> via fxp0.0
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
172.16.233.5/32 *[OSPF/10] 1w5d 20:30:29, metric 1
MultiRecv

Chapter 12: Operational Commands

show route cumulative

Syntax show route cumulative

Release Information Command introduced in Junos OS Release 13.3.

Description Shows the cumulative number of either IPv4 or IPv6 routes in the VRF table.

Options fabric— Internal fabric state.

logical-system (all | logical-system-name)— (Optional) Show cumulative routes on all

logical systems or on a particular logical system.

vpn-family (inet.0 | inet6.0)— Enter inet.0 for IPv4 routes or inet6.0 for IPv6 routes.

Required Privilege view

Level

Related • show route summary on page 460

Documentation

List of Sample Output show route cumulative on page 369

Field Name Field Description

Output Fields
destinations Number of destinations for which there are VRF routes in the routing table.

routes Number of VRF routes in the routing table:

• active—Number of routes that are active.

• holddown—Number of VRF routes that are in the hold-down state before being declared inactive.
• hidden—Number of VRF routes that are not used because of routing policy.

Sample Output

show route cumulative

user@host> show route cumulative vpn-family inet.0
Total VRF Routes: 720 destinations, 722 routes (720 active, 0 holddown, 0 hidden)

Protocol-Independent Routing Properties Feature Guide

show route detail

List of Syntax Syntax on page 370

Syntax (EX Series Switches) on page 370

Syntax show route detail

<destination-prefix>
<logical-system (all | logical-system-name)>

Syntax (EX Series show route detail

Switches) <destination-prefix>

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 13.2X51-D15 for the QFX Series.
Comand introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description Display detailed information about the active entries in the routing tables.

Options none—Display 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 view

Level

List of Sample Output show route detail on page 381

show route detail (with BGP Multipath) on page 387
show route label detail (Multipoint LDP Inband Signaling for Point-to-Multipoint
LSPs) on page 388
show route label detail (Multipoint LDP with Multicast-Only Fast Reroute) on page 388

Output Fields Table 12 on page 370 describes the output fields for the show route detail command.
Output fields are listed in the approximate order in which they appear.

Table 12: 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.

Chapter 12: Operational Commands

Table 12: show route detail 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:

• 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 Route destination (for example:10.0.0.1/24). The entry value is the number of routes for this destination,
(entry, announced) 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-address—Address of the neighbor.
• control-word-status—Whether the use of the control word has been negotiated for this virtual
circuit: NoCtrlWord or CtrlWord.
• encapsulation type—Type 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-id—Virtual circuit identifier.
• source—Source of the advertisement: Local or Remote.
• source—Source of the advertisement: Local or Remote.

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 2 or more exits this routing
device with one fewer label (the label-popping operation is performed).
• 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-Independent Routing Properties Feature Guide

Table 12: show route detail Output Fields (continued)

Field Name Field Description

[protocol, preference] Protocol from which the route was learned and the preference value for the route.

Preference2 values are signed integers, that is, Preference2 values can be either positive or negative
values. However, Junos OS evaluates Preference2 values as unsigned integers that are represented
by positive values. Based on the Preference2 values, Junos OS evaluates a preferred route differently
in the following scenarios:

• Both Signed Preference2 values

• Route A = -101
• Route B = -156
Where both the Preference2 values are signed, Junos OS evaluates only the unsigned value of
Preference2 and Route A, which has a lower Preference2 value is preferred.
• Unsigned Preference2 values
Now consider both unsigned Preference2 values:

• Route A = 4294967096
• Route B = 200
Here, Junos OS considers the lesser Preference2 value and Route B with a Preference2 value of 200
is preferred because it is less than 4294967096.
• Combination of signed and unsigned Preference2 values
When Preference2 values of two routes are compared, and for one route the Preference2 is a signed
value, and for the other route it is an unsigned value, Junos OS prefers the route with the positive
Preference2 value over the negative Preference2 value. For example, consider the following signed
and unsigned Preference2 values:
• Route A = -200
• Route B = 200
In this case, Route B with a Preference2 value of 200 is preferred although this value is greater than
-200, because Junos OS evaluates only the unsigned value of the 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).

Chapter 12: Operational Commands

Table 12: show route detail Output Fields (continued)

Field Name Field Description

Next-hop type Type of next hop. For a description of possible values for this field, see Table 13 on page 376.

Next-hop reference Number of references made to the next hop.

count

Flood nexthop branches Indicates that the number of flood next-hop branches exceeded the system limit of 32 branches, and
exceed maximum 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:

Label-switched-path Name of the LSP used to reach the next hop.

lsp-path-name

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 14 on page 378.

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.

Protocol-Independent Routing Properties Feature Guide

Table 12: show route detail Output Fields (continued)

Field Name Field Description

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.

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 The number of BGP peers or protocols to which Junos OS has announced this route, followed by the
list of the recipients of the announcement. Junos OS can also announce the route to the KRT for
installing the route into the Packet Forwarding Engine, to a resolve tree, a L2 VC, or even a VPN. For
example, n-Resolve inet indicates that the specified route is used for route resolution for next hops
found in the routing table.

• n—An index used by Juniper Networks customer support only.

• I—IGP.
• E—EGP.
• Recorded—The 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.

Chapter 12: Operational Commands

Table 12: show route detail Output Fields (continued)

Field Name Field Description

validation-state (BGP-learned routes) Validation status of the route:

ORR Generation-ID Displays the optimal route reflection (ORR) generation identifier. ISIS and OSPF interior gateway
protocol (IGP) updates filed whenever any of the corresponding ORR route has its metric valued
changed, or if the ORR route is added or deleted.

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.

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 15 on page 380 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.

Protocol-Independent Routing Properties Feature Guide

Table 12: show route detail Output Fields (continued)

Field Name Field Description

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 The LongLivedStale flag indicates that the route was marked LLGR-stale by this router, as part of the
LongLivedStale operation of LLGR receiver mode. Either this flag or the LongLivedStaleImport flag may be displayed
for a route. Neither of these flags are displayed at the same time as the Stale (ordinary GR stale) flag.

Accepted The LongLivedStaleImport flag indicates that the route was marked LLGR-stale when it was received
LongLivedStaleImport from a peer, or by import policy. Either this flag or the LongLivedStale flag may be displayed for a
route. Neither of these flags are displayed at the same time as the Stale (ordinary GR stale) flag.

Accept all received BGP long-lived graceful restart (LLGR) and LLGR stale routes learned from
configured neighbors and import into the inet.0 routing table

ImportAccepted Accept all received BGP long-lived graceful restart (LLGR) and LLGR stale routes learned from
LongLivedStaleImport configured neighbors and imported into the inet.0 routing table

The LongLivedStaleImport flag indicates that the route was marked LLGR-stale when it was received
from a peer, or by import policy.

Accepted Path currently contributing to BGP multipath.

MultipathContrib

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.

Table 13 on page 376 describes all possible values for the Next-hop Types output field.

Table 13: Next-hop Types Output Field Values

Next-Hop Type Description

Broadcast (bcast) Broadcast next hop.

Deny Deny next hop.

Discard Discard next hop.

Chapter 12: Operational Commands

Table 13: Next-hop Types Output Field Values (continued)

Next-Hop Type Description

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.

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.

Protocol-Independent Routing Properties Feature Guide

Table 13: Next-hop Types Output Field Values (continued)

Next-Hop Type Description

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 14 on page 378 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 14: 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 Cisco nondeterministic MED is enabled, and a path with a
selection 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.

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.

Chapter 12: Operational Commands

Table 14: State Output Field Values (continued)

Value Description

Int Interior route.

Int Ext BGP route received from an internal BGP peer or a BGP
confederation peer.

Interior > Exterior > Exterior via Direct, static, IGP, or EBGP path is available.
Interior

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.

Programmed Route installed programatically by on-box or off-box

applications using API.

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.

Protocol-Independent Routing Properties Feature Guide

Table 14: State Output Field Values (continued)

Value Description

Secondary Route not a primary route.

Unusable path Path is not usable because of one of the following conditions:

• The route is damped.

• The route is rejected by an import policy.
• The route is unresolved.

Update source Last tiebreaker is the lowest IP address value.

Table 15 on page 380 describes the possible values for the Communities output field.

Table 15: 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 Link-bandwidth community value used for unequal-cost load balancing. When BGP has
number:link-bandwidth-number 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.

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.

Chapter 12: Operational Commands

Table 15: Communities Output Field Values (continued)

Value Description

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 Incoming IANA codes with a value above 0x8000. This code of the BGP extended community
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
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
ORR Generation-ID: 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

Protocol-Independent Routing Properties Feature Guide

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
ORR Generation-ID: 1
Task: OSPF
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I

...

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

...

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

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

Chapter 12: Operational Commands

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)

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

Protocol-Independent Routing Properties Feature Guide

Address: 0x92544f0
Next-hop reference count: 2
Next hop: 172.16.0.2 via lt-1/2/0.7 weight 0x1
Label-switched-path R2-to-R200-p2mp
Label operation: Pop
Next hop: 172.16.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
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

Chapter 12: Operational Commands

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)

10.255.70.103:1:3:1/96 (1 entry, 1 announced)

Protocol-Independent Routing Properties Feature Guide

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
Announcement bits (1): 0-LDP
AS path: I
VC Label 100000, MTU 1500, VLAN ID 512

inet.0: 45 destinations, 47 routes (44 active, 0 holddown, 1 hidden)

1.1.1.3/32 (1 entry, 1 announced)
*IS-IS Preference: 18
Level: 2
Next hop type: Router, Next hop index: 580
Address: 0x9db6ed0
Next-hop reference count: 8
Next hop: 10.1.1.6 via lt-1/0/10.5, selected
Session Id: 0x18a

Chapter 12: Operational Commands

State: <Active Int>

Local AS: 2
Age: 1:32 Metric: 10
Validation State: unverified
ORR Generation-ID: 1
Task: IS-IS
Announcement bits (3): 0-KRT 5-Resolve tree 4 6-Resolve_IGP_FRR
task
AS path: I

inet.0: 61 destinations, 77 routes (61 active, 1 holddown, 0 hidden)

1.1.1.1/32 (2 entries, 1 announced)
*OSPF Preference: 10
Next hop type: Router, Next hop index: 673
Address: 0xc008830
Next-hop reference count: 3
Next hop: 10.1.1.1 via ge-0/0/2.0, selected
Session Id: 0x1b7
State: <Active Int>
Local AS: 1
Age: 3:06:59 Metric: 100
Validation State: unverified
ORR Generation-ID: 1
Area: 0.0.0.0
Task: OSPF
Announcement bits (2): 1-KRT 9-Resolve tree 2
AS path: I

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

Protocol-Independent Routing Properties Feature Guide

Task: BGP_2.10.1.1.6+58198
AS path: 2 I
Accepted MultipathContrib
Localpref: 100
Router ID: 172.16.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
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

Chapter 12: Operational Commands

FECs bound to route: P2MP root-addr 172.16.1.1, grp: 232.1.1.1,

src: 192.168.219.11
Primary Upstream : 172.16.1.3:0--172.16.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 : 172.16.1.3:0--172.16.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

Protocol-Independent Routing Properties Feature Guide

show route exact

List of Syntax Syntax on page 390

Syntax (EX Series Switches) on page 390

Syntax show route exact destination-prefix

Syntax (EX Series show route exact destination-prefix

Switches) <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 only the routes that exactly match the specified address or range of addresses.

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.

destination-prefix—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 view

Level

List of Sample Output show route exact on page 390

show route exact detail on page 391
show route exact extensive on page 391
show route exact terse on page 391

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

Chapter 12: Operational Commands

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)

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

Protocol-Independent Routing Properties Feature Guide

show route export

List of Syntax Syntax on page 392

Syntax (EX Series Switches) on page 392

Syntax show route export

<brief | detail>
<instance <instance-name> | routing-table-name>
<logical-system (all | logical-system-name)>

Syntax (EX Series show route export

Switches) <brief | detail>
<instance <instance-name> | routing-table-name>

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description Display policy-based route export information. Policy-based export simplifies the process
of exchanging route information between routing instances.

Options 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 view

Level

List of Sample Output show route export on page 393

show route export detail on page 393
show route export instance detail on page 394

Output Fields Table 16 on page 393 lists the output fields for the show route export command. Output
fields are listed in the approximate order in which they appear.

Chapter 12: Operational Commands

Table 16: 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 brief none
is exported to different tables, the counter will only increment by one.

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 detail
tables that are not exporting any routes.)

Flags (instance keyword only) Flags for this feature on this instance: detail

• config auto-policy—The policy was deduced from the configured IGP export
policies.
• cleanup—Configuration information for this instance is no longer valid.
• config—The instance was explicitly configured.

Options (instance keyword only) Configured option displays the type of routing tables the detail
feature handles:

• unicast—Indicates instance.inet.0.
• multicast—Indicates instance.inet.2.
• unicast multicast—Indicates instance.inet.0 and instance.inet.2.

Import policy (instance keyword only) Policy that route export uses to construct the import-export detail
matrix. Not displayed if the instance type is vrf.

Instance (instance keyword only) Name of the routing instance. detail

Type (instance keyword only) Type of routing instance: forwarding, non-forwarding, or detail
vrf.

Sample Output

show route export

user@host> show route export
Table Export Routes
inet.0 N 0
black.inet.0 Y 3
red.inet.0 Y 4

show route export detail

user@host> show route export detail
inet.0 Routes: 0
black.inet.0 Routes: 3
Import: [ inet.0 ]
red.inet.0 Routes: 4
Import: [ inet.0 ]

Protocol-Independent Routing Properties Feature Guide

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) ]
Instance: black Type: non-forwarding
Instance: red Type: non-forwarding

Chapter 12: Operational Commands

show route export vrf-target

Syntax show route export vrf-target

Release Information Command introduced before Junos OS Release 7.4.

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

Options none—Display 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 view

Level

List of Sample Output show route export vrf-target on page 396

show route export vrf-target community on page 396
show route export vrf-target detail on page 396

Output Fields Table 17 on page 395 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 17: 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

• unicast—Indicates instance.inet.0.
• multicast—Indicates instance.inet.2.
• unicast multicast—Indicates instance.inet.0 and instance.inet.2.

Import Number of routing tables that are currently importing routes with this target brief none
community. Omitted for tables that are not importing routes.

Protocol-Independent Routing Properties Feature Guide

Table 17: 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 brief none
community. Omitted for tables that are not exporting routes.

Target Target communities, family, and options for which auto-export is currently detail
distributing routes.

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 Import Export
69:1 inet unicast 2 2
69:2 inet unicast 2 2

show route export vrf-target community

user@host> show route export vrf-target community target:69:1
Route Target Family Import Export
69:1 inet unicast 2 2

show route export vrf-target detail

user@host> show route export vrf-target detail
Target: 1:12 inet unicast
Import table(s): vrf-11.inet.0 vrf-12.inet.0
Export table(s): vrf-12.inet.0
Target: 1:13 inet unicast
Import table(s): vrf-12.inet.0 vrf-13.inet.0
Export table(s): vrf-13.inet.0

Chapter 12: Operational Commands

show route forwarding-table interface-name

Syntax show route forwarding-table interface-name interface-name

Release Information Command introduced in Junos OS Release 9.6.

Description Display the interfaces in the Routing Engine's forwarding table.

Options none—Display 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 view

Level

List of Sample Output show route forwarding-table interface-name fe-0/1/1 on page 398
show route forwarding-table interface-name all on page 398
show route forwarding-table interface-name all detail on page 399

Output Fields Table 18 on page 397 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 18: 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 Interface’s 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.
• ipaddress—Network address.

Address Address of the interface. The address can be a MAC address, IPv4 address, IPv6 All levels
address, and so on.

IPkts Number of packets received on the interface. All levels

Ierr Number of packets received on the interface with errors. All levels

Protocol-Independent Routing Properties Feature Guide

Table 18: show route forwarding-table interface-name Output Fields (continued)

Field Name Field Description Level of Output

Opkts Number of packets transmitted or sent from the interface. All levels

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 Opkts Oerr Coll
fe-0/1/1 1514 <Link> 00.05.85.88.cc.20 0 0 0 0 0

show route forwarding-table interface-name all

user@host> show route forwarding-table interface-name all
Name Mtu Network Address Ipkts Ierr Opkts Oerr Coll
fxp0 1514 <Link> 00.a0.a5.56.03.83 180965 0 39907 0 0

unit 0 1500 192.168.187.0/ 192.168.187.10

fxp1 1514 <Link> 02.00.00.00.00.04 33010497 0 30110800 0 0

unit 0 1500 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 fe80::/64 fe80::200:ff:fe0
fec0::/64 fec0::a:0:0:4
1500 4
lsi 1496 <Link>
dsc max <Link> 0 0 0 0 0
lo0 max <Link> 8980 0 8980 0 0

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> 1679900 0 1068611 0 0

unit 0 4470 <PtoP> 10.0.60.2 0 0 0 0

0
so-0/0/1 4474 <Link> 0 0 0 0 0

unit 0 4470 <PtoP> 10.0.80.2 0 0 0 0

0
so-0/0/2 4474 <Link> 0 0 0 0 0
so-0/0/3 4474 <Link> 0 0 0 0 0

Chapter 12: Operational Commands

fe-0/1/0 1514 <Link> 00.05.85.88.cc.1f 523120 0 623044 0 0

unit 0 1500 10.0.90.12/30 10.0.90.14 0 0 0 0

0
fe-0/1/1 1514 <Link> 00.05.85.88.cc.20 0 0 0 0 0
fe-0/1/2 1514 <Link> 00.05.85.88.cc.21 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

...

Protocol-Independent Routing Properties Feature Guide

show route hidden

Syntax show route hidden

Release Information Command introduced before Junos OS Release 7.4.

Description Display only hidden route information. A hidden route is unusable, even if it is the best
path.

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.

Required Privilege view

Level

Related • Understanding Hidden Routes

Documentation

List of Sample Output show route hidden on page 400

show route hidden detail on page 401
show route hidden extensive on page 401
show route hidden terse on page 401

Output Fields 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

Chapter 12: Operational Commands

Unusable
10.12.1.0/24 [BGP/170] 03:44:10, localpref 100, from 10.4.4.4
AS path: 100 I
Unusable
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 401.

show route hidden terse

user@host> show route hidden terse

Protocol-Independent Routing Properties Feature Guide

inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)

Restart Complete
+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

127.0.0.1/32 D 0 >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

A Destination P Prf Metric 1 Metric 2 Next hop AS path

10.5.5.5/32 B 170 100 Unusable 100 I
10.12.1.0/24 B 170 100 Unusable 100 I
10.12.80.4/30 B 170 100 Unusable 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 Metric 1 Metric 2 Next hop AS path

10.4.4.4:4:10.5.5.5/32
B 170 100 Unusable 100 I
10.4.4.4:4:10.12.1.0/24
B 170 100 Unusable 100 I
10.4.4.4:4:10.12.80.4/30
B 170 100 Unusable I

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)

Chapter 12: Operational Commands

show route inactive-path

List of Syntax Syntax on page 403

Syntax (EX Series Switches) on page 403

Syntax show route inactive-path

Syntax (EX Series show route inactive-path

Switches) <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 routes for destinations that have no active route. An inactive route is a route that
was not selected as the best path.

Options none—Display 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 view

Level

Related • show route active-path on page 357

Documentation

List of Sample Output show route inactive-path on page 403

show route inactive-path detail on page 404
show route inactive-path extensive on page 405
show route inactive-path terse on page 405

Sample Output

show route inactive-path

user@host> show route inactive-path

inet.0: 25 destinations, 26 routes (24 active, 0 holddown, 1 hidden)

Protocol-Independent Routing Properties Feature Guide

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

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>

Chapter 12: Operational Commands

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)

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

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 P Prf Metric 1 Metric 2 Next hop AS path

10.12.100.12/30 O 10 1 >so-0/3/0.0

private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

10.0.0.0/8 D 0 >fxp1.0

red.inet.0: 6 destinations, 8 routes (4 active, 0 holddown, 3 hidden)

Restart Complete
+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

10.12.80.0/30 B 170 100 >10.12.80.1 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

Protocol-Independent Routing Properties Feature Guide

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)

Chapter 12: Operational Commands

show route instance

List of Syntax Syntax on page 407

Syntax (EX Series Switches and QFX Series) on page 407

Syntax show route instance

Syntax (EX Series show route instance

Switches and QFX <brief | detail | summary>
Series) <instance-name>
<operational>

Release Information Command introduced before Junos OS Release 7.4.

Description Display routing instance information.

Options 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 view

Level

Related • Example: Transporting IPv6 Traffic Across IPv4 Using Filter-Based Tunneling
Documentation
• Example: Configuring the Helper Capability Mode for OSPFv3 Graceful Restart

List of Sample Output show route instance on page 409

show route instance detail (Graceful Restart Complete) on page 409
show route instance detail (Graceful Restart Incomplete) on page 411

Protocol-Independent Routing Properties Feature Guide

show route instance detail (VPLS Routing Instance) on page 413

show route instance operational on page 413
show route instance summary on page 413

Output Fields Table 19 on page 408 lists the output fields for the show route instance command. Output
fields are listed in the approximate order in which they appear.

Table 19: 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, All levels
virtual-router, or vrf.

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 detail
restart is declared complete. The default is 300.

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

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, detail
or low. The default is low.

Restart State Restart state: detail

• Pending:protocol-name—List of protocols that have not yet

completed graceful restart for this routing table.
• Complete—All protocols have restarted for this routing table.

Chapter 12: Operational Commands

Table 19: show route instance Output Fields (continued)

Field Name Field Description Level of Output

Primary rib Primary table for this routing instance. brief none summary

Active/holddown/hidden Number of active, hold-down, and hidden routes. All levels

Sample Output

show route instance

user@host> show route instance
Instance Type
Primary RIB Active/holddown/hidden
master forwarding
inet.0 16/0/1
iso.0 1/0/0
mpls.0 0/0/0
inet6.0 2/0/0
l2circuit.0 0/0/0
__juniper_private1__ forwarding
__juniper_private1__.inet.0 12/0/0
__juniper_private1__.inet6.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, 1 hidden)
Restart Complete
inet.3 : 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
iso.0 : 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
mpls.0 : 19 routes (19 active, 0 holddown, 0 hidden)
Restart Complete
bgp.l3vpn.0 : 10 routes (10 active, 0 holddown, 0 hidden)
Restart Complete
inet6.0 : 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
bgp.l2vpn.0 : 1 routes (1 active, 0 holddown, 0 hidden)
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 hidden)

Protocol-Independent Routing Properties Feature Guide

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:
BGP-L.inet.0 : 4 routes (4 active, 0 holddown, 0 hidden)
Restart Complete
BGP-L.mpls.0 : 3 routes (3 active, 0 holddown, 0 hidden)
Restart Complete
L2VPN:
Router ID: 0.0.0.0
Type: l2vpn State: Active
Restart State: Complete Path selection timeout: 300
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 active, 0 holddown, 0 hidden)
Restart Complete
LDP:
Router ID: 10.69.105.1
Type: vrf State: Active
Restart State: Complete Path selection timeout: 300
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 active, 0 holddown, 0 hidden)
Restart Complete
OSPF:
Router ID: 10.69.101.1
Type: vrf State: Active
Restart State: Complete Path selection timeout: 300
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 active, 0 holddown, 0 hidden)
Restart Complete
RIP:
Router ID: 10.69.102.1
Type: vrf State: Active
Restart State: Complete Path selection timeout: 300
Interfaces:
t3-0/0/0.102
Route-distinguisher: 10.255.14.176:102
Vrf-import: [ RIP-import ]
Vrf-export: [ RIP-export ]

Chapter 12: Operational Commands

Tables:
RIP.inet.0 : 6 routes (6 active, 0 holddown, 0 hidden)
Restart Complete
STATIC:
Router ID: 10.69.100.1
Type: vrf State: Active
Restart State: Complete Path selection timeout: 300
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 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, 1 hidden)
Restart Pending: OSPF LDP
inet.3 : 2 routes (2 active, 0 holddown, 0 hidden)
Restart Pending: OSPF LDP
iso.0 : 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
mpls.0 : 23 routes (23 active, 0 holddown, 0 hidden)
Restart Pending: LDP VPN
bgp.l3vpn.0 : 10 routes (10 active, 0 holddown, 0 hidden)
Restart Pending: BGP VPN
inet6.0 : 2 routes (2 active, 0 holddown, 0 hidden)
Restart Complete
bgp.l2vpn.0 : 1 routes (1 active, 0 holddown, 0 hidden)
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 hidden)
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 hidden)

Protocol-Independent Routing Properties Feature Guide

Restart Pending: VPN

BGP-L.mpls.0 : 2 routes (2 active, 0 holddown, 0 hidden)
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 ]
Vrf-export: [ L2VPN-export ]
Tables:
L2VPN.l2vpn.0 : 2 routes (2 active, 0 holddown, 0 hidden)
Restart Pending: VPN L2VPN
LDP:
Router ID: 10.69.105.1
Type: vrf State: Active
Restart State: Pending Path selection timeout: 300
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 active, 1 holddown, 0 hidden)
Restart Pending: OSPF LDP VPN
OSPF:
Router ID: 10.69.101.1
Type: vrf State: Active
Restart State: Pending Path selection timeout: 300
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 active, 1 holddown, 0 hidden)
Restart Pending: OSPF VPN
RIP:
Router ID: 10.69.102.1
Type: vrf State: Active
Restart State: Pending Path selection timeout: 300
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 active, 2 holddown, 0 hidden)
Restart Pending: RIP VPN
STATIC:
Router ID: 10.69.100.1
Type: vrf State: Active
Restart State: Pending Path selection timeout: 300
Interfaces:
t3-0/0/0.100
Route-distinguisher: 10.255.14.176:100
Vrf-import: [ STATIC-import ]
Vrf-export: [ STATIC-export ]
Tables:

Chapter 12: Operational Commands

STATIC.inet.0 : 4 routes (4 active, 0 holddown, 0 hidden)

Restart Pending: VPN

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
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 Active/holddown/hidden
master forwarding
inet.0 15/0/1
iso.0 1/0/0
mpls.0 35/0/0
l3vpn.0 0/0/0
inet6.0 2/0/0
l2vpn.0 0/0/0
l2circuit.0 0/0/0
BGP-INET vrf
BGP-INET.inet.0 5/0/0
BGP-INET.iso.0 0/0/0
BGP-INET.inet6.0 0/0/0
BGP-L vrf
BGP-L.inet.0 5/0/0
BGP-L.iso.0 0/0/0
BGP-L.mpls.0 4/0/0
BGP-L.inet6.0 0/0/0
L2VPN l2vpn
L2VPN.inet.0 0/0/0
L2VPN.iso.0 0/0/0
L2VPN.inet6.0 0/0/0
L2VPN.l2vpn.0 2/0/0
LDP vrf
LDP.inet.0 4/0/0
LDP.iso.0 0/0/0
LDP.mpls.0 0/0/0

Protocol-Independent Routing Properties Feature Guide

LDP.inet6.0 0/0/0
LDP.l2circuit.0 0/0/0
OSPF vrf
OSPF.inet.0 7/0/0
OSPF.iso.0 0/0/0
OSPF.inet6.0 0/0/0
RIP vrf
RIP.inet.0 6/0/0
RIP.iso.0 0/0/0
RIP.inet6.0 0/0/0
STATIC vrf
STATIC.inet.0 4/0/0
STATIC.iso.0 0/0/0
STATIC.inet6.0 0/0/0

Chapter 12: Operational Commands

show route label-switched-path

List of Syntax Syntax on page 415

Syntax (EX Series Switches) on page 415

Syntax show route label-switched-path path-name

Syntax (EX Series show route label-switched-path path-name

Switches) <brief | detail | extensive | terse>

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.5 for EX Series switches.

Description Display the routes used in an MPLS label-switched path (LSP).

Options brief | detail | extensive | terse—(Optional) Display the specified level of output.

path-name—LSP tunnel name.

logical-system (all | logical-system-name)—(Optional) Perform this operation on all

logical systems or on a particular logical system.

Required Privilege view

Level

List of Sample Output show route label-switched-path on page 415

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 [MPLS/7] 00:00:06, metric 0

> to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny
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

inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

2.2.2.2/32 *[MPLS/7] 00:00:06, metric 0

> to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny

Protocol-Independent Routing Properties Feature Guide

4.4.4.4/32 *[MPLS/7] 00:00:06, metric 0

to 111.222.1.9 via s0-0/0/0, label-switched-path abc
> to 111.222.1.9 via s0-0/0/0, label-switched-path xyz
to 111.222.1.9 via s0-0/0/0, label-switched-path sf-to-ny
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

Chapter 12: Operational Commands

show route localization

Syntax show route localization

Release Information Command introduced in Junos OS Release 11.4 for T-Series routers.
Command introduced in Junos OS Release 12.3 for MX Series routers.

Description (T320, T640, and T1600 routers only) Display route localization details.

Options detail—Display detailed output.

Required Privilege view

Level

Related • Example: Configuring Packet Forwarding Engine FIB Localization

Documentation

Output Fields Table 20 on page 417 lists the output fields for the show route localization command.
Output fields are listed in the approximate order in which they appear.

Table 20: 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

Protocol-Independent Routing Properties Feature Guide

Forwarding Engine addresses

FPC0: 1
FPC1: 2
FPC2: 4, 5
FPC3: 6
FPC4: 8
FPC5: 11
FPC6: 13
FPC7: 15

Chapter 12: Operational Commands

show route martians

List of Syntax Syntax on page 419

Syntax (EX Series Switches) on page 419

Syntax show route martians

<logical-system (all | logical-system-name)>
<table routing-table-name>

Syntax (EX Series show route martians

Switches) <table routing-table-name>

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 martian (invalid and ignored) entries associated with each routing table.

Options none—Display 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 view

Level

Related • Example: Configuring Class E Martian Addresses for Routing on page 160
Documentation
• Understanding Martian Addresses on page 159

List of Sample Output show route martians on page 420

Output Fields Table 21 on page 419 lists the output fields for the show route martians command. Output
fields are listed in the approximate order in which they appear

Table 21: show route martians Output Fields

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.

Protocol-Independent Routing Properties Feature Guide

Table 21: show route martians Output Fields (continued)

Field Name Field Description

status Status of the route: allowed or disallowed.

Sample Output

show route martians

user@host> show route martians

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

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

Chapter 12: Operational Commands

inet6.3:
::1/128 exact -- disallowed
ff00::/8 exact -- disallowed
ff02::/16 exact -- disallowed
...

Protocol-Independent Routing Properties Feature Guide

show route next-hop

List of Syntax Syntax on page 422

Syntax (EX Series Switches) on page 422

Syntax show route next-hop next-hop

Syntax (EX Series show route next-hop next-hop

Switches) <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 entries in the routing table that are being sent to the specified next-hop
address.

Options 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-hop—Next-hop address.

Required Privilege view

Level

List of Sample Output show route next-hop on page 422

show route next-hop detail on page 423
show route next-hop extensive on page 425
show route next-hop terse on page 426

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 *[Static/5] 06:26:25

> to 192.168.71.254 via fxp0.0
10.209.0.0/16 *[Static/5] 06:26:25

Chapter 12: Operational Commands

> to 192.168.71.254 via fxp0.0

172.16.0.0/12 *[Static/5] 06:26:25
> to 192.168.71.254 via fxp0.0
192.168.0.0/16 *[Static/5] 06:26:25
> to 192.168.71.254 via fxp0.0
192.168.102.0/23 *[Static/5] 06:26:25
> to 192.168.71.254 via fxp0.0
207.17.136.0/24 *[Static/5] 06:26:25
> to 192.168.71.254 via fxp0.0
207.17.136.192/32 *[Static/5] 06:26:25
> to 192.168.71.254 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>

Protocol-Independent Routing Properties Feature Guide

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.0.0/16 (1 entry, 1 announced)

192.168.102.0/23 (1 entry, 1 announced)

207.17.136.0/24 (1 entry, 1 announced)

207.17.136.192/32 (1 entry, 1 announced)

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

Chapter 12: Operational Commands

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

Protocol-Independent Routing Properties Feature Guide

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

Chapter 12: Operational Commands

A Destination P Prf Metric 1 Metric 2 Next hop AS path

* 10.10.0.0/16 S 5 >192.168.71.254
* 10.209.0.0/16 S 5 >192.168.71.254
* 172.16.0.0/12 S 5 >192.168.71.254
* 192.168.0.0/16 S 5 >192.168.71.254
* 192.168.102.0/23 S 5 >192.168.71.254
* 207.17.136.0/24 S 5 >192.168.71.254
* 207.17.136.192/32 S 5 >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)

Protocol-Independent Routing Properties Feature Guide

show route protocol

List of Syntax Syntax on page 428

Syntax (EX Series Switches) on page 428

Syntax show route protocol protocol

Syntax (EX Series show route protocol protocol

Switches) <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.
ospf2 and ospf3 options introduced in Junos OS Release 9.2.
ospf2 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.

protocol—Protocol from which the route was learned:

• access—Access route for use by DHCP application

• access-internal—Access-internal route for use by DHCP application

• aggregate—Locally generated aggregate route

• arp—Route learned through the Address Resolution Protocol

• atmvpn—Asynchronous Transfer Mode virtual private network

• bgp—Border Gateway Protocol

• ccc—Circuit cross-connect

• direct—Directly connected route

• dvmrp—Distance Vector Multicast Routing Protocol

• esis—End System-to-Intermediate System

• flow—Locally defined flow-specification route

• frr—Precomputed protection route or backup route used when a link goes down

• isis—Intermediate System-to-Intermediate System

Chapter 12: Operational Commands

• ldp—Label Distribution Protocol

• l2circuit—Layer 2 circuit

• l2vpn—Layer 2 virtual private network

• local—Local address

• mpls—Multiprotocol Label Switching

• msdp—Multicast Source Discovery Protocol

• ospf—Open Shortest Path First versions 2 and 3

• ospf2—Open Shortest Path First versions 2 only

• ospf3—Open Shortest Path First version 3 only

• pim—Protocol Independent Multicast

• rip—Routing Information Protocol

• ripng—Routing Information Protocol next generation

• rsvp—Resource Reservation Protocol

• rtarget—Local route target virtual private network

• static—Statically defined route

• tunnel—Dynamic tunnel

• vpn—Virtual private network

NOTE: EX Series switches run a subset of these protocols. See the switch
CLI for details.

Required Privilege view

Level

List of Sample Output show route protocol access on page 430

show route protocol access-internal extensive on page 430
show route protocol arp on page 430
show route protocol bgp on page 431
show route protocol bgp detail on page 431
show route protocol bgp detail (Labeled Unicast) on page 431
show route protocol bgp extensive on page 432
show route protocol bgp terse on page 433
show route protocol direct on page 433
show route protocol frr on page 434
show route protocol l2circuit detail on page 434
show route protocol l2vpn extensive on page 435
show route protocol ldp on page 436

Protocol-Independent Routing Properties Feature Guide

show route protocol ldp extensive on page 436

show route protocol ospf (Layer 3 VPN) on page 437
show route protocol ospf detail on page 438
show route protocol rip on page 438
show route protocol rip detail on page 438
show route protocol ripng table inet6 on page 439
show route protocol static detail on page 439

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 *[Access/13] 00:00:09

> to 13.160.0.2 via fe-0/0/0.0
13.160.0.4/32 *[Access/13] 00:00:09
> to 13.160.0.2 via fe-0/0/0.0
13.160.0.5/32 *[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 [ARP/4294967293] 00:04:35, from 20.20.1.1

Unusable
20.20.1.4/32 [ARP/4294967293] 00:04:35, from 20.20.1.1
Unusable

Chapter 12: Operational Commands

20.20.1.5/32 [ARP/4294967293] 00:04:32, from 20.20.1.1

Unusable
20.20.1.6/32 [ARP/4294967293] 00:04:34, from 20.20.1.1
Unusable
20.20.1.7/32 [ARP/4294967293] 00:04:35, from 20.20.1.1
Unusable
20.20.1.8/32 [ARP/4294967293] 00:04:35, from 20.20.1.1
Unusable
20.20.1.9/32 [ARP/4294967293] 00:04:35, from 20.20.1.1
Unusable
20.20.1.10/32 [ARP/4294967293] 00:04:35, from 20.20.1.1
Unusable
20.20.1.11/32 [ARP/4294967293] 00:04:33, from 20.20.1.1
Unusable
20.20.1.12/32 [ARP/4294967293] 00:04:33, from 20.20.1.1
Unusable
20.20.1.13/32 [ARP/4294967293] 00:04:33, from 20.20.1.1
Unusable
...

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 detail (Labeled Unicast)

user@host> show route protocol bgp 1.1.1.8/32 detail
inet.0: 45 destinations, 46 routes (45 active, 0 holddown, 0 hidden)
1.1.1.8/32 (2 entries, 2 announced)

Protocol-Independent Routing Properties Feature Guide

State:
*BGP Preference: 1/-101
Next hop type: Indirect, Next hop index: 0
Address: 0xc007f30
Next-hop reference count: 2
Source: 1.1.1.1
Next hop type: Router, Next hop index: 614
Next hop: 20.1.1.2 via ge-0/0/1.0, selected
Label-switched-path lsp1
Label operation: Push 1000126, Push 1000125, Push 1000124, Push 1000123, Push
299872(top)
Label TTL action: prop-ttl, prop-ttl, prop-ttl, prop-ttl, prop-ttl(top)
Load balance label: Label 1000126: None; Label 1000125: None; Label 1000124: None;
Label 1000123: None; Label 299872: None;
Label element ptr: 0xc007860
Label parent element ptr: 0xc0089a0
Label element references: 1
Label element child references: 0
Label element lsp id: 0
Session Id: 0x140
Protocol next hop: 1.1.1.4
Label operation: Push 1000126, Push 1000125, Push 1000124, Push 1000123(top)
Label TTL action: prop-ttl, prop-ttl, prop-ttl, prop-ttl
Load balance label: Label 1000126: None; Label 1000125: None; Label 1000124: None;
Label 1000123: None;
Indirect next hop: 0xae8d300 1048576 INH Session ID: 0x142
State:
Local AS: 5 Peer AS: 5
Age: 22:43 Metric2: 2
Validation State: unverified
Task: BGP_5.1.1.1.1
Announcement bits (2): 0-KRT 7-Resolve tree 2
AS path: I
Accepted
Route Labels: 1000123(top) 1000124 1000125 1000126
Localpref: 100
Router ID: 1.1.1.1

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

Chapter 12: Operational Commands

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 P Prf Metric 1 Metric 2 Next hop AS path

192.168.64.0/21 B 170 100 >172.16.100.1 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

172.16.8.0/24 *[Direct/0] 17w0d 10:31:49

> via fe-1/3/1.0
10.255.165.1/32 *[Direct/0] 25w4d 04:13:18
> via lo0.0
172.16.30.0/24 *[Direct/0] 17w0d 23:06:26
> via fe-1/3/2.0
192.168.164.0/22 *[Direct/0] 25w4d 04:13:20
> via fxp0.0

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

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

2001:db8::10:255:165:1/128
*[Direct/0] 25w4d 04:13:21
> via lo0.0
fe80::2a0:a5ff:fe12:ad7/128

Protocol-Independent Routing Properties Feature Guide

*[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 *[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 16, Push 299792(top)
20.20.1.4/32 *[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 16, Push 299792(top)
20.20.1.5/32 *[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 16, Push 299792(top)
20.20.1.6/32 *[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 16, Push 299792(top)
20.20.1.7/32 *[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 16, Push 299792(top)
20.20.1.8/32 *[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 16, Push 299792(top)
20.20.1.9/32 *[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 16, Push 299792(top)
20.20.1.10/32 *[FRR/200] 00:05:38, from 20.20.1.1
...

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)

*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

Chapter 12: Operational Commands

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
Push 800000 Offset: -4
Indirect next hop: 85142a0 288
State: <Active Int>
Local AS: 69
Age: 7:48
Task: Common L2 VC

Protocol-Independent Routing Properties Feature Guide

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 *[LDP/9] 1d 23:03:35, metric 1

> via t1-4/0/0.0, Push 100000
192.168.17.1/32 *[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 *[LDP/9] 1d 23:03:35, metric 1

> via t1-4/0/0.0, Pop
100064(S=0) *[LDP/9] 1d 23:03:35, metric 1
> via t1-4/0/0.0, Pop
100080 *[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: 64500
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: 64500
Age: 1d 23:03:58 Metric: 1
Task: LDP
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)

Chapter 12: Operational Commands

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: 64500
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: 64500
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: 64500
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 *[OSPF/10] 00:05:18, metric 4

> via t3-3/2/0.0
10.39.1.8/30 [OSPF/10] 00:05:18, metric 2
> via t3-3/2/0.0
10.255.14.171/32 *[OSPF/10] 00:05:18, metric 4
> via t3-3/2/0.0
10.255.14.179/32 *[OSPF/10] 00:05:18, metric 2
> via t3-3/2/0.0
172.16.233.5/32 *[OSPF/10] 20:25:55, metric 1

Protocol-Independent Routing Properties Feature Guide

VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.39.1.16/30 [OSPF/10] 00:05:43, metric 1

> via so-0/2/2.0
10.255.14.173/32 *[OSPF/10] 00:05:43, metric 1
> via so-0/2/2.0
172.16.233.5/32 *[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
172.16.233.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

Chapter 12: 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 *[RIPng/100] 02:13:33, metric 2

> to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0
1111::2/128 *[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0
1111::3/128 *[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0
1111::4/128 *[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0
1111::5/128 *[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via t3-0/2/0.0
1111::6/128 *[RIPng/100] 02:13:33, metric 2
> to fe80::2a0:a5ff:fe3d:56 via 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)

Protocol-Independent Routing Properties Feature Guide

Validation State: unverified

Task: RT
Announcement bits (1): 0-KRT
AS path: I

Chapter 12: Operational Commands

show route range

List of Syntax Syntax on page 441

Syntax (EX Series Switches) on page 441

Syntax show route range

Syntax (EX Series show route range

Switches) <brief | detail | extensive | terse>
<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 routing table entries using a prefix range.

Options none—Display 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-prefix—Destination 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 view

Level

List of Sample Output show route range on page 441

show route range destination-prefix on page 442
show route range detail on page 442
show route range extensive on page 443
show route range terse on page 444

Sample Output

show route range

user@host> show route range

inet.0: 11 destinations, 11 routes (10 active, 0 holddown, 1 hidden)

Protocol-Independent Routing Properties Feature Guide

+ = Active Route, - = Last Active, * = Both

10.10.0.0/16 *[Static/5] 00:30:01

> to 192.168.71.254 via fxp0.0
10.209.0.0/16 *[Static/5] 00:30:01
> to 192.168.71.254 via fxp0.0
10.255.71.14/32 *[Direct/0] 00:30:01
> via lo0.0
172.16.0.0/12 *[Static/5] 00:30:01
> to 192.168.71.254 via fxp0.0
192.168.0.0/16 *[Static/5] 00:30:01
> to 192.168.71.254 via fxp0.0
192.168.64.0/21 *[Direct/0] 00:30:01
> via fxp0.0
192.168.71.14/32 *[Local/0] 00:30:01
Local via fxp0.0
192.168.102.0/23 *[Static/5] 00:30:01
> to 192.168.71.254 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 *[Static/5] 00:31:14

> to 192.168.71.254 via fxp0.0
192.168.64.0/21 *[Direct/0] 00:31:14
> via fxp0.0
192.168.71.14/32 *[Local/0] 00:31:14
Local via fxp0.0
192.168.102.0/23 *[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

Chapter 12: Operational Commands

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

Protocol-Independent Routing Properties Feature Guide

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>
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 P Prf Metric 1 Metric 2 Next hop AS path

* 10.10.0.0/16 S 5 >192.168.71.254
* 10.209.0.0/16 S 5 >192.168.71.254
* 10.255.71.14/32 D 0 >lo0.0
* 172.16.0.0/12 S 5 >192.168.71.254
* 192.168.0.0/16 S 5 >192.168.71.254
* 192.168.64.0/21 D 0 >fxp0.0
* 192.168.71.14/32 L 0 Local
* 192.168.102.0/23 S 5 >192.168.71.254
* 207.17.136.0/24 S 5 >192.168.71.254
* 207.17.136.192/32 S 5 >192.168.71.254

__juniper_private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0

hidden)
+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

* 10.0.0.0/8 D 0 >fxp2.0
D 0 >fxp1.0
* 10.0.0.4/32 L 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 AS path
47.0005.80ff.f800.0000.0108.0001.0102.5507.1014/152
* D 0 >lo0.0

inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

A Destination P Prf Metric 1 Metric 2 Next hop AS path

abcd::10:255:71:14/128
* D 0 >lo0.0
fe80::280:42ff:fe11:226f/128
* D 0 >lo0.0

__juniper_private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0

hidden)
+ = Active Route, - = Last Active, * = Both

Chapter 12: Operational Commands

A Destination P Prf Metric 1 Metric 2 Next hop AS path

fe80::280:42ff:fe11:226f/128
* D 0 >lo0.16385

Protocol-Independent Routing Properties Feature Guide

show route resolution

List of Syntax Syntax on page 446

Syntax (EX Series Switches) on page 446

Syntax show route resolution

Syntax (EX Series show route resolution

Switches) <brief | detail | extensive | summary>
<index index>
<prefix>
<table routing-table-name>
<unresolved>

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 entries in the next-hop resolution database. This database provides for
recursive resolution of next hops through other prefixes in the routing table.

Options none—Display 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 view

Level

Related • Example: Configuring Route Resolution on PE Routers

Documentation

Chapter 12: Operational Commands

List of Sample Output show route resolution detail on page 448

show route resolution detail (Multipath Resolution) on page 449
show route resolution summary on page 449
show route resolution unresolved on page 449

Protocol-Independent Routing Properties Feature Guide

Output Fields Table 22 on page 448 describes the output fields for the show route resolution command.
Output fields are listed in the approximate order in which they appear.

Table 22: 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 Routing tables used for next-hop resolution.

tables

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 Number of forwarding next hops. The forwarding next hop is the network layer
hops address of the directly reachable neighboring system (if applicable) and the
interface used to reach it.

Merged—Merged next hops when recursive resolution of multipath is configured.

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

Chapter 12: Operational Commands

Forwarding nexthops: 1
10.31.1.5/32 Originating RIB: inet.0
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 detail (Multipath Resolution)

user@host> show route resolution detail
regress@RT1_re# run show route resolution detail 10.1.1.2
Tree Index: 1, Nodes 36, Reference Count 3
Contributing routing tables: inet.0 inet.3
Policy: [ abc ]
10.1.1.2/32 Originating RIB: inet.0
Node path count: 1
Next hop subtype: INDIRECT
Indirect next hops: 2
Protocol next hop: 10.1.1.1
Inode flags: 0x206 path flags: 0x08
Path fnh link: 0xc9321c0 path inh link: 0x0
Indirect next hop: 0xb2b20f0 1048574 INH Session ID: 0x143
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 12.1.1.2 via ge-2/0/1.0
Session Id: 0x144
Next hop: 13.1.1.2 via ge-2/0/2.0
Session Id: 0x145

10.1.1.1/32 Originating RIB: inet.0

Node path count: 1
Node flags: 1
Forwarding nexthops: 1 (Merged)
Nexthop: 12.1.1.2 via ge-2/0/1.0

Nexthop: 13.1.1.2 via ge-2/0/2.0

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-Independent Routing Properties Feature Guide

Protocol Nexthop: 10.255.70.103 Push 800008

Indirect nexthop: 0 -
Tree Index 2

Chapter 12: Operational Commands

show route snooping

Syntax show route snooping

Release Information Command introduced in Junos OS Release 8.5.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description Display the entries in the routing table that were learned from snooping.

Options none—Display 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 view

Level

List of Sample Output show route snooping detail on page 452

show route snooping logical-system all on page 452

Protocol-Independent Routing Properties Feature Guide

Sample Output

show route snooping detail

user@host> show route snooping detail
__+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)

Chapter 12: Operational Commands

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
Multicast (IPv4) Composite

<snip>

Protocol-Independent Routing Properties Feature Guide

show route source-gateway

List of Syntax Syntax on page 454

Syntax (EX Series Switches) on page 454

Syntax show route source-gateway address

Syntax (EX Series show route source-gateway address

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

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.

address—IP 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 view

Level

List of Sample Output show route source-gateway on page 454

show route source-gateway detail on page 455
show route source-gateway extensive on page 457

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

Chapter 12: Operational Commands

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

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

Protocol-Independent Routing Properties Feature Guide

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

Chapter 12: Operational Commands

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

Protocol-Independent Routing Properties Feature Guide

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

Chapter 12: Operational Commands

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

Protocol-Independent Routing Properties Feature Guide

show route summary

List of Syntax Syntax on page 460

Syntax (EX Series Switches) on page 460

Syntax show route summary

<logical-system (all | logical-system-name)>
<table routing-table-name>

Syntax (EX Series show route summary

Switches)

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Description 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 none—Display 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 view

Level

List of Sample Output show route summary on page 462

show route summary table on page 462
show route summary table (with Route Limits Configured for the Routing
Table) on page 463

Output Fields Table 23 on page 461 lists the output fields for the show route summary command. Output
fields are listed in the approximate order in which they appear.

Chapter 12: Operational Commands

Table 23: show route summary Output Fields

Field Name Field Description

Router ID Address of the local routing device.

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:

• active—Number of routes that are active.

• holddown—Number of routes that are in the hold-down state before
being declared inactive.
• hidden—Number of routes that are not used because of routing policy.

Restart complete All protocols have restarted for this routing table.

Restart state:

• Pending:protocol-name—List of protocols that have not yet completed

graceful restart for this routing table.
• Complete—All protocols have restarted for this routing table.

For example, if the output shows-

• LDP.inet.0: 5 routes (4 active, 1 holddown, 0 hidden)

Restart Pending: OSPF LDP VPN

This indicates that OSPF, LDP, and VPN protocols did not restart for
LDP.inet.0 routing table.
• vpls_1.l2vpn.0: 1 destinations, 1 routes (1 active, 0
holddown, 0 hidden)
Restart Complete

This indicates that all protocols have restarted for vpls_1.l2vpn.0 routing
table.

Limit/Threshold 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.

• destinations—The 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.
• routes—The 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.

Protocol-Independent Routing Properties Feature Guide

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)

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

Chapter 12: Operational Commands

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
OSPF: 4 routes, 3 active
BGP: 4 routes, 4 active
IGMP: 1 routes, 1 active
PIM: 2 routes, 2 active

Protocol-Independent Routing Properties Feature Guide

show route table

List of Syntax Syntax on page 464

Syntax (EX Series Switches and QFX Series Switches) on page 464

Syntax show route table routing-table-name

Syntax (EX Series show route table routing-table-name

Switches and QFX <brief | detail | extensive | terse>
Series Switches)

Release Information Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 14.1X53-D15 for QFX Series switches.
Show route table evpn statement introduced in Junos OS Release 15.1X53-D30 for QFX
Series switches.

Description Display the route entries in a particular routing table.

Options 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-name—Display route entries for all routing tables whose names begin with
this string (for example, inet.0 and inet6.0 are both displayed when you run the show
route table inet command).

Required Privilege view

Level

Related • show route summary on page 460

Documentation

List of Sample Output show route table bgp.l2.vpn on page 475

show route table bgp.l3vpn.0 on page 475
show route table bgp.l3vpn.0 detail on page 476
show route table bgp.rtarget.0 (When Proxy BGP Route Target Filtering Is
Configured) on page 477
show route table bgp.evpn.0 on page 477
show route table evpna.evpn.0 on page 478
show route table inet.0 on page 478
show route table inet.3 on page 479
show route table inet.3 protocol ospf on page 479
show route table inet6.0 on page 479
show route table inet6.3 on page 479

Chapter 12: Operational Commands

show route table inetflow detail on page 480

show route table lsdist.0 extensive on page 480
show route table l2circuit.0 on page 482
show route table mpls on page 482
show route table mpls extensive on page 482
show route table mpls.0 on page 483
show route table mpls.0 detail (PTX Series) on page 484
show route table mpls.0 ccc ge-0/0/1.1004 detail on page 484
show route table mpls.0 protocol evpn on page 485
show route table mpls.0 protocol ospf on page 491
show route table mpls.0 extensive (PTX Series) on page 492
show route table mpls.0 (RSVP Route—Transit LSP) on page 492
show route table vpls_1 detail on page 493
show route table vpn-a on page 493
show route table vpn-a.mdt.0 on page 493
show route table VPN-A detail on page 494
show route table VPN-AB.inet.0 on page 494
show route table VPN_blue.mvpn-inet6.0 on page 495
show route table vrf1.mvpn.0 extensive on page 495
show route table inetflow detail on page 495
show route table bgp.evpn.0 extensive |no-more (EVPN) on page 498

Output Fields Table 11 on page 340 describes the output fields for the show route table command. Output
fields are listed in the approximate order in which they appear.

Table 24: show route table Output Fields

Field Name Field Description

routing-table-name Name of the routing table (for example, inet.0).

Restart complete All protocols have restarted for this routing table.

Restart state:

• Pending:protocol-name—List of protocols that have not yet completed graceful restart for this
routing table.
• Complete—All protocols have restarted for this routing table.

For example, if the output shows-

• LDP.inet.0 : 5 routes (4 active, 1 holddown, 0 hidden)

Restart Pending: OSPF LDP VPN

This indicates that OSPF, LDP, and VPN protocols did not restart for the LDP.inet.0 routing table.
• vpls_1.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete

This indicates that all protocols have restarted for the vpls_1.l2vpn.0 routing table.

number destinations Number of destinations for which there are routes in the routing table.

Protocol-Independent Routing Properties Feature Guide

Table 24: show route table 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:

• 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)

• MPLS-label (for example, 80001).

• inclusive multicast Ethernet tag route—Type of route destination represented by (for example,
3:100.100.100.10:100::0::10::100.100.100.10/384):
• route distinguisher—(8 octets) Route distinguisher (RD) must be the RD of the EVPN instance
(EVI) that is advertising the NLRI.
• Ethernet tag ID—(4 octets) Identifier of the Ethernet tag. Can set to 0 or to a valid Ethernet tag
value.
• IP address length—(1 octet) Length of IP address in bits.
• originating router’s IP address—(4 or 16 octets) Must set to the provider edge (PE) device’s IP
address. This address should be common for all EVIs on the PE device, and may be the PE device's
loopback address.

Chapter 12: Operational Commands

Table 24: show route table Output Fields (continued)

Field Name Field Description

[protocol, preference] Protocol from which the route was learned and the preference value for the route.

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 13 on page 376.

Next-hop reference Number of references made to the next hop.

count

Flood nexthop Indicates that the number of flood next-hop branches exceeded the system limit of 32 branches, and
branches exceed only a subset of the flood next-hop branches were installed in the kernel.
maximum message

Source IP address of the route source.

Next hop Network layer address of the directly reachable neighboring system.

Label-switched-path Name of the LSP used to reach the next hop.

lsp-path-name

Protocol-Independent Routing Properties Feature Guide

Table 24: show route table Output Fields (continued)

Field Name Field Description

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 14 on page 378.

Local AS AS number of the local routing devices.

Age How long the route has been known.

AIGP Accumulated interior gateway protocol (AIGP) BGP attribute.

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.

Task Name of the protocol that has added the route.

Announcement bits The number of BGP peers or protocols to which Junos OS has announced this route, followed by the
list of the recipients of the announcement. Junos OS can also announce the route to the kernel routing
table (KRT) for installing the route into the Packet Forwarding Engine, to a resolve tree, a Layer 2 VC,
or even a VPN. For example, n-Resolve inet indicates that the specified route is used for route resolution
for next hops found in the routing table.

• n—An index used by Juniper Networks customer support only.

Chapter 12: Operational Commands

Table 24: show route table Output Fields (continued)

Field Name Field Description

• I—IGP.
• E—EGP.
• Recorded—The 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:

validation-state (BGP-learned routes) Validation status of the route:

FECs bound to route Indicates point-to-multipoint root address, multicast source address, and multicast group address
when multipoint LDP (M-LDP) inband signaling is configured.

Primary Upstream When multipoint LDP with multicast-only fast reroute (MoFRR) is configured, indicates 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, indicates 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.

Protocol-Independent Routing Properties Feature Guide

Table 24: show route table Output Fields (continued)

Field Name Field Description

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 15 on page 380 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 The LongLivedStale flag indicates that the route was marked LLGR-stale by this router, as part of the
LongLivedStale operation of LLGR receiver mode. Either this flag or the LongLivedStaleImport flag might be displayed
for a route. Neither of these flags is displayed at the same time as the Stale (ordinary GR stale) flag.

Accepted The LongLivedStaleImport flag indicates that the route was marked LLGR-stale when it was received
LongLivedStaleImport from a peer, or by import policy. Either this flag or the LongLivedStale flag might be displayed for a
route. Neither of these flags is displayed at the same time as the Stale (ordinary GR stale) flag.

Accept all received BGP long-lived graceful restart (LLGR) and LLGR stale routes learned from
configured neighbors and import into the inet.0 routing table

ImportAccepted Accept all received BGP long-lived graceful restart (LLGR) and LLGR stale routes learned from
LongLivedStaleImport configured neighbors and imported into the inet.0 routing table

The LongLivedStaleImport flag indicates that the route was marked LLGR-stale when it was received
from a peer, or by import policy.

Accepted Path currently contributing to BGP multipath.

MultipathContrib

Localpref Local preference value included in the route.

Router ID BGP router ID as advertised by the neighbor in the open message.

Chapter 12: Operational Commands

Table 24: show route table Output Fields (continued)

Field Name Field Description

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.

Table 13 on page 376 describes all possible values for the Next-hop Types output field.

Table 25: Next-hop Types Output Field Values

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,

Hold Next hop is waiting to be resolved into a unicast or

multicast type.

Indexed (idxd) Indexed next hop.

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.

Protocol-Independent Routing Properties Feature Guide

Table 25: Next-hop Types Output Field Values (continued)

Next-Hop Type Description

Resolve (rslv) Resolving next hop.

Routed multicast (mcrt) Regular multicast next hop.

Router A specific node or set of nodes to which the routing device

forwards packets that match the route prefix.

To qualify as a 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 14 on page 378 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 26: 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 Cisco nondeterministic MED is enabled, and a path with a
selection 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.

Chapter 12: Operational Commands

Table 26: State Output Field Values (continued)

Value Description

Ext BGP route received from an external BGP neighbor.

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 Direct, static, IGP, or EBGP path is available.
Interior

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.

Protocol-Independent Routing Properties Feature Guide

Table 26: State Output Field Values (continued)

Value Description

Pending Route pending because of a hold-down configured on another

route.

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:

• The route is damped.

• The route is rejected by an import policy.
• The route is unresolved.

Update source Last tiebreaker is the lowest IP address value.

Table 15 on page 380 describes the possible values for the Communities output field.

Table 27: Communities Output Field Values

Value Description

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.

Chapter 12: Operational Commands

Table 27: Communities Output Field Values (continued)

Value Description

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.

origin (Used with VPNs) Identifies where the route came from.

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 Incoming IANA codes with a value above 0x8000. This code of the BGP extended community
community attribute is accepted, but it is not recognized.

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

Protocol-Independent Routing Properties Feature Guide

*[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:172.16.4.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
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)

Chapter 12: Operational Commands

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>
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 bgp.evpn.0

user@host> show route table bgp.evpn.0
bgp.evpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2:100.100.100.2:100::0::00:26:88:5f:67:b0/304
*[BGP/170] 11:00:05, localpref 100, from 100.100.100.2
AS path: I, validation-state: unverified
> to 100.64.12.2 via xe-2/2/0.0, label-switched-path R0toR1
2:100.100.100.2:100::0::00:51:51:51:51:51/304
*[BGP/170] 11:00:05, localpref 100, from 100.100.100.2
AS path: I, validation-state: unverified
> to 100.64.12.2 via xe-2/2/0.0, label-switched-path R0toR1

Protocol-Independent Routing Properties Feature Guide

2:100.100.100.3:100::0::00:52:52:52:52:52/304
*[BGP/170] 10:59:58, localpref 100, from 100.100.100.3
AS path: I, validation-state: unverified
> to 100.64.13.3 via ge-2/0/8.0, label-switched-path R0toR2
2:100.100.100.3:100::0::a8:d0:e5:5b:01:c8/304
*[BGP/170] 10:59:58, localpref 100, from 100.100.100.3
AS path: I, validation-state: unverified
> to 100.64.13.3 via ge-2/0/8.0, label-switched-path R0toR2
3:100.100.100.2:100::1000::100.100.100.2/304
*[BGP/170] 11:00:16, localpref 100, from 100.100.100.2
AS path: I, validation-state: unverified
> to 100.64.12.2 via xe-2/2/0.0, label-switched-path R0toR1
3:100.100.100.2:100::2000::100.100.100.2/304
*[BGP/170] 11:00:16, localpref 100, from 100.100.100.2
AS path: I, validation-state: unverified
> to 100.64.12.2 via xe-2/2/0.0, label-switched-path R0toR1

show route table evpna.evpn.0

user@host> show route table evpna.evpn.0
evpna.evpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

3:100.100.100.10:100::0::10::100.100.100.10/384
*[EVPN/170] 01:37:09
Indirect
3:100.100.100.2:100::2000::100.100.100.2/304
*[EVPN/170] 01:37:12
Indirect

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 *[Static/5] 00:51:57

> to 172.16.5.254 via fxp0.0
10.0.0.1/32 *[Direct/0] 00:51:58
> via at-5/3/0.0
10.0.0.2/32 *[Local/0] 00:51:58
Local
10.12.12.21/32 *[Local/0] 00:51:57
Reject
10.13.13.13/32 *[Direct/0] 00:51:58
> via t3-5/2/1.0
10.13.13.14/32 *[Local/0] 00:51:58
Local
10.13.13.21/32 *[Local/0] 00:51:58
Local
10.13.13.22/32 *[Direct/0] 00:33:59
> via t3-5/2/0.0
127.0.0.1/32 [Direct/0] 00:51:58
> via lo0.0
10.222.5.0/24 *[Direct/0] 00:51:58
> via fxp0.0
10.222.5.81/32 *[Local/0] 00:51:58
Local

Chapter 12: Operational Commands

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

10.0.0.5/32 *[LDP/9] 00:25:43, metric 10, tag 200

to 10.2.94.2 via lt-1/2/0.49
> to 10.2.3.2 via lt-1/2/0.23

show route table inet.3 protocol ospf

user@host> show route table inet.3 protocol ospf
inet.3: 9 destinations, 18 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.1.20/32 [L-OSPF/10] 1d 00:00:56, metric 2

> to 10.0.10.70 via lt-1/2/0.14, Push 800020
to 10.0.6.60 via lt-1/2/0.12, Push 800020, Push 800030(top)
1.1.1.30/32 [L-OSPF/10] 1d 00:01:01, metric 3
> to 10.0.10.70 via lt-1/2/0.14, Push 800030
to 10.0.6.60 via lt-1/2/0.12, Push 800030
1.1.1.40/32 [L-OSPF/10] 1d 00:01:01, metric 4
> to 10.0.10.70 via lt-1/2/0.14, Push 800040
to 10.0.6.60 via lt-1/2/0.12, Push 800040
1.1.1.50/32 [L-OSPF/10] 1d 00:01:01, metric 5
> to 10.0.10.70 via lt-1/2/0.14, Push 800050
to 10.0.6.60 via lt-1/2/0.12, Push 800050
1.1.1.60/32 [L-OSPF/10] 1d 00:01:01, metric 6
> to 10.0.10.70 via lt-1/2/0.14, Push 800060
to 10.0.6.60 via lt-1/2/0.12, Pop

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

Protocol-Independent Routing Properties Feature Guide

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: 64502 Peer AS: 64500
Age: 4
Task: BGP_64500.10.12.99.5+3792
Announcement bits (1): 0-Flow
AS path: 64500 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: 64502
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 lsdist.0 extensive

user@host> show route table lsdist.0 extensive
lsdist.0: 10 destinations, 10 routes (10 active, 0 holddown, 0 hidden)
NODE { AS:4170512532 BGP-LS ID:4170512532 ISO:3245.3412.3456.00 ISIS-L1:0 }/1152
(1 entry, 1 announced)
TSI:
Page 0 idx 0, (group ibgp type Internal) Type 1 val 0xa62f378 (adv_entry)
Advertised metrics:
Nexthop: Self
Localpref: 100
AS path: [4170512532] I
Communities:
Path NODE { AS:4170512532 BGP-LS ID:4170512532 ISO:3245.3412.3456.00 ISIS-L1:0 }
Vector len 4. Val: 0
*IS-IS Preference: 15
Level: 1
Next hop type: Fictitious, Next hop index: 0
Address: 0x95dfc64
Next-hop reference count: 9
State: <Active NotInstall>
Local AS: 4170512532
Age: 6:05
Validation State: unverified
Task: IS-IS
Announcement bits (1): 0-BGP_RT_Background
AS path: I
IPv4 Router-ids:
128.220.11.197
Area membership:

Chapter 12: Operational Commands

47 00 05 80 ff f8 00 00 00 01 08 00 01
SPRING-Capabilities: - SRGB block [Start: 800000,
Range: 256, Flags: 0xc0]
SPRING-Algorithms:
- Algo: 0
LINK { Local { AS:4170512532 BGP-LS ID:4170512532 ISO:3245.3412.3456.00 }.{
IPv4:8.65.1.105 } Remote { AS:4170512532 BGP-LS ID:4170512532 ISO:4284.3300.5067)
TSI:
Page 0 idx 0, (group ibgp type Internal) Type 1 val 0xa62f3cc (adv_entry)
Advertised metrics:
Nexthop: Self
Localpref: 100
AS path: [4170512532] I
Communities:
Path LINK { Local { AS:4170512532 BGP-LS ID:4170512532 ISO:3245.3412.3456.00 }.{
IPv4:8.65.1.105 } Remote { AS:4170512532 BGP-LS ID:4170512532 ISO:4284.33000
*IS-IS Preference: 15
Level: 1
Next hop type: Fictitious, Next hop index: 0
Address: 0x95dfc64
Next-hop reference count: 9
State: <Active NotInstall>
Local AS: 4170512532
Age: 6:05
Validation State: unverified
Task: IS-IS
Announcement bits (1): 0-BGP_RT_Background
AS path: I
Color: 32768
Maximum bandwidth: 1000Mbps
Reservable bandwidth: 1000Mbps
Unreserved bandwidth by priority:
0 1000Mbps
1 1000Mbps
2 1000Mbps
3 1000Mbps
4 1000Mbps
5 1000Mbps
6 1000Mbps
7 1000Mbps
Metric: 10
TE Metric: 10
LAN IPV4 Adj-SID - Label: 299776, Flags: 0x30,
Weight: 0, Nbr: 10.220.1.83

PREFIX { Node { AS:4170512532 BGP-LS ID:4170512532 ISO:3245.3412.3456.00 } {

IPv4:128.220.11.197/32 } ISIS-L1:0 }/1152 (1 entry, 1 announced) TSI: Page 0 idx
0, (group ibgp type Internal) Type 1 val 0xa62f43c (adv_entry)
Advertised metrics:
Nexthop: Self
Localpref: 100
AS path: [4170512532] I
Communities:
Path PREFIX { Node { AS:4170512532 BGP-LS ID:4170512532 ISO:3245.3412.3456.00 }
{ IPv4:128.220.11.197/32 } ISIS-L1:0 } Vector len 4. Val: 0
*IS-IS Preference: 15
Level: 1
Next hop type: Fictitious, Next hop index: 0
Address: 0x95dfc64
Next-hop reference count: 9
State:<Active NotInstall>

Protocol-Independent Routing Properties Feature Guide

Local AS: 4170512532

Age: 6:05
Validation State: unverified
Task: IS-IS
Announcement bits (1): 0-BGP_RT_Background
AS path: I
Prefix SID: 67, Flags: 0x40, Algo: 0

show route table l2circuit.0

user@host> show route table l2circuit.0
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 100049
via so-0/1/3.0, Push 100049
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 100049
via so-0/1/3.0, Push 100049
10.1.1.195:CtrlWord:1:2:Remote/96
*[LDP/9] 00:50:14
Discard

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 *[MPLS/0] 00:13:55, metric 1

Receive
1 *[MPLS/0] 00:13:55, metric 1
Receive
2 *[MPLS/0] 00:13:55, metric 1
Receive
1024 *[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

Chapter 12: Operational Commands

show route table mpls.0

user@host> show route table mpls.0
mpls.0: 18 destinations, 19 routes (18 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0 *[MPLS/0] 11:39:56, metric 1

to table inet.0
0(S=0) *[MPLS/0] 11:39:56, metric 1
to table mpls.0
1 *[MPLS/0] 11:39:56, metric 1
Receive
2 *[MPLS/0] 11:39:56, metric 1
to table inet6.0
2(S=0) *[MPLS/0] 11:39:56, metric 1
to table mpls.0
13 *[MPLS/0] 11:39:56, metric 1
Receive
303168 *[EVPN/7] 11:00:49, routing-instance pbbn10, route-type
Ingress-MAC, ISID 0
to table pbbn10.evpn-mac.0
303184 *[EVPN/7] 11:00:53, routing-instance pbbn10, route-type
Ingress-IM, ISID 1000
to table pbbn10.evpn-mac.0
[EVPN/7] 11:00:53, routing-instance pbbn10, route-type
Ingress-IM, ISID 2000
to table pbbn10.evpn-mac.0
303264 *[EVPN/7] 11:00:53, remote-pe 100.100.100.2, routing-instance
pbbn10, route-type Egress-IM, ISID 1000
> to 100.1.12.2 via xe-2/2/0.0, label-switched-path R0toR1
303280 *[EVPN/7] 11:00:53, remote-pe 100.100.100.2, routing-instance
pbbn10, route-type Egress-IM, ISID 2000
> to 100.1.12.2 via xe-2/2/0.0, label-switched-path R0toR1
303328 *[EVPN/7] 11:00:49, remote-pe 100.100.100.2, routing-instance
pbbn10, route-type Egress-MAC, ISID 0
> to 100.1.12.2 via xe-2/2/0.0, label-switched-path R0toR1
303344 *[EVPN/7] 11:00:49, remote-pe 100.100.100.2, routing-instance
pbbn10, route-type Egress-MAC, ISID 0
> to 100.1.12.2 via xe-2/2/0.0, label-switched-path R0toR1
303360 *[EVPN/7] 11:00:47, routing-instance pbbn10, route-type
Egress-MAC, ISID 0, BMAC 00:26:88:5f:67:b0
> to 100.1.12.2 via xe-2/2/0.0, label-switched-path R0toR1
303376 *[EVPN/7] 11:00:47, routing-instance pbbn10, route-type
Egress-MAC, ISID 0, BMAC 00:51:51:51:51:51
> to 100.1.12.2 via xe-2/2/0.0, label-switched-path R0toR1
303392 *[EVPN/7] 11:00:35, remote-pe 100.100.100.3, routing-instance
pbbn10, route-type Egress-MAC, ISID 0
> to 100.1.13.3 via ge-2/0/8.0, label-switched-path R0toR2
303408 *[EVPN/7] 11:00:35, remote-pe 100.100.100.3, routing-instance
pbbn10, route-type Egress-MAC, ISID 0
> to 100.1.13.3 via ge-2/0/8.0, label-switched-path R0toR2
303424 *[EVPN/7] 11:00:33, routing-instance pbbn10, route-type
Egress-MAC, ISID 0, BMAC a8:d0:e5:5b:01:c8
> to 100.1.13.3 via ge-2/0/8.0, label-switched-path R0toR2
303440 *[EVPN/7] 11:00:33, routing-instance pbbn10, route-type
Egress-MAC, ISID 0, BMAC 00:52:52:52:52:52
> to 100.1.13.3 via ge-2/0/8.0, label-switched-path R0toR2

Protocol-Independent Routing Properties Feature Guide

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: 10.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 ccc ge-0/0/1.1004 detail

user@host>show route table mpls.0 ccc ge-0/0/1.1004 detail
mpls.0: 121 destinations, 121 routes (121 active, 0 holddown, 0 hidden)
ge-0/0/1.1004 (1 entry, 1 announced)
*EVPN Preference: 7
Next hop type: List, Next hop index: 1048577
Address: 0xdc14770
Next-hop reference count: 3
Next hop: ELNH Address 0xd011e30
Next hop type: Indirect, Next hop index: 0
Address: 0xd011e30
Next-hop reference count: 3
Protocol next hop: 100.100.100.1
Label operation: Push 301952
Composite next hop: 0xd011dc0 754 INH Session ID: 0x146
Indirect next hop: 0xb69a890 1048615 INH Session ID: 0x146
Next hop type: Router, Next hop index: 735
Address: 0xd00e530
Next-hop reference count: 23
Next hop: 100.46.1.2 via ge-0/0/5.0
Label-switched-path pe4_to_pe1
Label operation: Push 300320
Label TTL action: prop-ttl
Load balance label: Label 300320: None;
Label element ptr: 0xd00e580
Label parent element ptr: 0x0
Label element references: 18
Label element child references: 16
Label element lsp id: 5
Next hop: ELNH Address 0xd012070
Next hop type: Indirect, Next hop index: 0
Address: 0xd012070

Chapter 12: Operational Commands

Next-hop reference count: 3

Protocol next hop: 100.100.100.2
Label operation: Push 301888
Composite next hop: 0xd012000 755 INH Session ID: 0x143
Indirect next hop: 0xb69a9a0 1048641 INH Session ID: 0x143
Next hop type: Router, Next hop index: 716
Address: 0xd00e710
Next-hop reference count: 23
Next hop: 100.46.1.2 via ge-0/0/5.0
Label-switched-path pe4_to_pe2
Label operation: Push 300304
Label TTL action: prop-ttl
Load balance label: Label 300304: None;
Label element ptr: 0xd00e760
Label parent element ptr: 0x0
Label element references: 15
Label element child references: 13
Label element lsp id: 6
Next hop: ELNH Address 0xd0121f0, selected
Next hop type: Indirect, Next hop index: 0
Address: 0xd0121f0
Next-hop reference count: 3
Protocol next hop: 100.100.100.3
Label operation: Push 301984
Composite next hop: 0xd012180 756 INH Session ID: 0x145
Indirect next hop: 0xb69aab0 1048642 INH Session ID: 0x145
Next hop type: Router, Next hop index: 801
Address: 0xd010ed0
Next-hop reference count: 32
Next hop: 100.46.1.2 via ge-0/0/5.0
Label-switched-path pe4_to_pe3
Label operation: Push 300336
Label TTL action: prop-ttl
Load balance label: Label 300336: None;
Label element ptr: 0xd0108c0
Label parent element ptr: 0x0
Label element references: 22
Label element child references: 20
Label element lsp id: 7
State: < Active Int >
Age: 2:06:50
Validation State: unverified
Task: evpn global task
Announcement bits (1): 1-KRT
AS path: I

show route table mpls.0 protocol evpn

user@host>show route table mpls.0 protocol evpn
mpls.0: 121 destinations, 121 routes (121 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

299872 *[EVPN/7] 02:30:58, routing-instance mhevpn, route-type

Ingress-IM, vlan-id 10
to table mhevpn.evpn-mac.0
300016 *[EVPN/7] 02:30:38, routing-instance VS-1, route-type
Ingress-IM, vlan-id 110
to table VS-1.evpn-mac.0
300032 *[EVPN/7] 02:30:38, routing-instance VS-1, route-type
Ingress-IM, vlan-id 120
to table VS-1.evpn-mac.0

Protocol-Independent Routing Properties Feature Guide

300048 *[EVPN/7] 02:30:38, routing-instance VS-1, route-type

Ingress-IM, vlan-id 130
to table VS-1.evpn-mac.0
300064 *[EVPN/7] 02:30:38, routing-instance VS-2, route-type
Ingress-IM, vlan-id 210
to table VS-2.evpn-mac.0
300080 *[EVPN/7] 02:30:38, routing-instance VS-2, route-type
Ingress-IM, vlan-id 220
to table VS-2.evpn-mac.0
300096 *[EVPN/7] 02:30:38, routing-instance VS-2, route-type
Ingress-IM, vlan-id 230
to table VS-2.evpn-mac.0
300112 *[EVPN/7] 02:27:06, routing-instance mhevpn, route-type
Egress-MAC, ESI 00:44:44:44:44:44:44:44:44:44
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
300128 *[EVPN/7] 02:29:22, routing-instance mhevpn, route-type
Ingress-Aliasing
to table mhevpn.evpn-mac.0
300144 *[EVPN/7] 02:27:06, routing-instance VS-1, route-type
Egress-MAC, ESI 00:44:44:44:44:44:44:44:44:44
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
300160 *[EVPN/7] 02:29:22, routing-instance VS-1, route-type
Ingress-Aliasing
to table VS-1.evpn-mac.0
300176 *[EVPN/7] 02:27:07, routing-instance VS-2, route-type
Egress-MAC, ESI 00:44:44:44:44:44:44:44:44:44
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
300192 *[EVPN/7] 02:29:22, routing-instance VS-2, route-type
Ingress-Aliasing
to table VS-2.evpn-mac.0
300208 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-1, route-type Egress-IM, vlan-id 120
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300224 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
mhevpn, route-type Egress-IM, vlan-id 10
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300240 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-1, route-type Egress-IM, vlan-id 110
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300256 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-1, route-type Egress-IM, vlan-id 130
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300272 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-2, route-type Egress-IM, vlan-id 210
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300288 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-2, route-type Egress-IM, vlan-id 220
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300304 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-2, route-type Egress-IM, vlan-id 230
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300320 *[EVPN/7] 02:27:06, routing-instance VS-1, route-type
Egress-MAC, ESI 00:11:11:11:11:11:11:11:11:11
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

300336 *[EVPN/7] 02:27:06, routing-instance VS-1, route-type
Egress-MAC, ESI 00:33:33:33:33:33:33:33:33:33
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

Chapter 12: Operational Commands

> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

300368 *[EVPN/7] 02:27:07, routing-instance VS-2, route-type
Egress-MAC, ESI 00:33:33:33:33:33:33:33:33:33
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

300384 *[EVPN/7] 02:27:07, routing-instance VS-2, route-type
Egress-MAC, ESI 00:11:11:11:11:11:11:11:11:11
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

300416 *[EVPN/7] 02:27:06, routing-instance mhevpn, route-type
Egress-MAC, ESI 00:33:33:33:33:33:33:33:33:33
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

300432 *[EVPN/7] 02:27:06, routing-instance mhevpn, route-type
Egress-MAC, ESI 00:11:11:11:11:11:11:11:11:11
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

300480 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-1, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300496 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-2, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300560 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-1, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300592 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
VS-2, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
300608 *[EVPN/7] 02:29:23
> via ge-0/0/1.1001, Pop
300624 *[EVPN/7] 02:29:23
> via ge-0/0/1.2001, Pop
301232 *[EVPN/7] 02:29:17
> via ge-0/0/1.1002, Pop
301296 *[EVPN/7] 02:29:10
> via ge-0/0/1.1003, Pop
301312 *[EVPN/7] 02:27:06
> via ae10.2003, Pop
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301360 *[EVPN/7] 02:29:01
> via ge-0/0/1.1004, Pop
301408 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
vpws1004, route-type Egress, vlan-id 2004
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
301456 *[EVPN/7] 02:27:06
> via ae10.1010, Pop
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301552 *[EVPN/7] 02:27:07, routing-instance VS-1, route-type
Egress-MAC, ESI 00:22:22:22:22:22:22:22:22:22
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301568 *[EVPN/7] 02:27:07, routing-instance VS-2, route-type

Protocol-Independent Routing Properties Feature Guide

Egress-MAC, ESI 00:22:22:22:22:22:22:22:22:22

> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301648 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
vpws1010, route-type Egress, vlan-id 2010
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
301664 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
mhevpn, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
301680 *[EVPN/7] 02:27:07, remote-pe 100.100.100.2, routing-instance
mhevpn, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
301696 *[EVPN/7] 02:27:07, routing-instance mhevpn, route-type
Egress-MAC, ESI 00:22:22:22:22:22:22:22:22:22
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301712 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-2, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301728 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-1, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301744 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-2, route-type Egress-IM, vlan-id 230
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301760 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
vpws1010, route-type Egress, vlan-id 2010
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301776 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
mhevpn, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301792 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-1, route-type Egress-IM, vlan-id 130
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301808 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
vpws1004, route-type Egress, vlan-id 2004
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301824 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
mhevpn, route-type Egress-IM, vlan-id 10
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301840 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
vpws1002, route-type Egress, vlan-id 2002
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301856 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
vpws1003, route-type Egress, vlan-id 2003
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301872 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
vpws1003, route-type Egress Protection, vlan-id 2003
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301888 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
vpws1010, route-type Egress Protection, vlan-id 1010
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301904 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-2, route-type Egress-IM, vlan-id 220
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301920 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-2, route-type Egress-IM, vlan-id 210
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
301936 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-IM, vlan-id 230
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301952 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-SH, vlan-id 230

Chapter 12: Operational Commands

> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

301968 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-IM, vlan-id 220
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
301984 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-SH, vlan-id 220
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302000 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-IM, vlan-id 210
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302016 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-SH, vlan-id 210
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302032 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-2, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302048 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-2, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302064 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302080 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-2, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302096 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-1, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302112 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-1, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302128 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302144 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302160 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-1, route-type Egress-IM, vlan-id 120
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302176 *[EVPN/7] 02:27:07, remote-pe 100.100.100.1, routing-instance
VS-1, route-type Egress-IM, vlan-id 110
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302192 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-IM, vlan-id 130
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302208 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-SH, vlan-id 130
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302224 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-IM, vlan-id 120
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302240 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-SH, vlan-id 120
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302256 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-IM, vlan-id 110
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302272 *[EVPN/7] 02:27:07, remote-pe 100.100.100.3, routing-instance
VS-1, route-type Egress-SH, vlan-id 110
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

Protocol-Independent Routing Properties Feature Guide

302288 *[EVPN/7] 02:27:06, remote-pe 100.100.100.1, routing-instance

mhevpn, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302304 *[EVPN/7] 02:27:06, remote-pe 100.100.100.1, routing-instance
mhevpn, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302320 *[EVPN/7] 02:27:06, remote-pe 100.100.100.3, routing-instance
mhevpn, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302336 *[EVPN/7] 02:27:06, remote-pe 100.100.100.3, routing-instance
mhevpn, route-type Egress-MAC
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302352 *[EVPN/7] 02:27:06, remote-pe 100.100.100.3, routing-instance
vpws1004, route-type Egress, vlan-id 2004
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302368 *[EVPN/7] 02:27:06, remote-pe 100.100.100.3, routing-instance
mhevpn, route-type Egress-IM, vlan-id 10
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302384 *[EVPN/7] 02:27:06, remote-pe 100.100.100.3, routing-instance
mhevpn, route-type Egress-SH, vlan-id 10
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302400 *[EVPN/7] 02:26:21
> via ge-0/0/1.3001, Pop
302432 *[EVPN/7] 02:26:21, remote-pe 100.100.100.3, routing-instance
vpws3001, route-type Egress, vlan-id 40000
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302448 *[EVPN/7] 02:26:21, remote-pe 100.100.100.1, routing-instance
vpws3001, route-type Egress, vlan-id 40000
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302464 *[EVPN/7] 02:26:20, remote-pe 100.100.100.2, routing-instance
vpws3001, route-type Egress, vlan-id 40000
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
302480 *[EVPN/7] 02:26:14
> via ge-0/0/1.3016, Pop
302512 *[EVPN/7] 02:26:14, remote-pe 100.100.100.1, routing-instance
vpws3016, route-type Egress, vlan-id 40016
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302528 *[EVPN/7] 02:26:14, remote-pe 100.100.100.2, routing-instance
vpws3016, route-type Egress, vlan-id 40016
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
302560 *[EVPN/7] 02:26:06
> via ae10.3011, Pop
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302592 *[EVPN/7] 02:26:07, remote-pe 100.100.100.1, routing-instance
vpws3011, route-type Egress, vlan-id 401100
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
302608 *[EVPN/7] 02:26:07, remote-pe 100.100.100.2, routing-instance
vpws3011, route-type Egress, vlan-id 401100
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
302624 *[EVPN/7] 02:26:07, remote-pe 100.100.100.3, routing-instance
vpws3011, route-type Egress Protection, vlan-id 301100
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302656 *[EVPN/7] 02:25:59
> via ae10.3006, Pop
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302688 *[EVPN/7] 02:26:00, remote-pe 100.100.100.2, routing-instance
vpws3006, route-type Egress, vlan-id 400600
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2
302704 *[EVPN/7] 02:26:00, remote-pe 100.100.100.1, routing-instance
vpws3006, route-type Egress, vlan-id 400600
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

Chapter 12: Operational Commands

302720 *[EVPN/7] 02:25:59, remote-pe 100.100.100.3, routing-instance

vpws3006, route-type Egress, vlan-id 400600
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
302736 *[EVPN/7] 02:25:59, remote-pe 100.100.100.3, routing-instance
vpws3006, route-type Egress Protection, vlan-id 300600
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
ge-0/0/1.1001 *[EVPN/7] 02:29:23
> via ge-0/0/1.2001
ge-0/0/1.2001 *[EVPN/7] 02:29:23
> via ge-0/0/1.1001
ge-0/0/1.1002 *[EVPN/7] 02:27:06
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3
ae10.2003 *[EVPN/7] 02:29:10
> via ge-0/0/1.1003
ge-0/0/1.1003 *[EVPN/7] 02:27:06
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

> via ae10.2003

ge-0/0/1.1004 *[EVPN/7] 02:27:06
to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

ae10.1010 *[EVPN/7] 02:27:06
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
ge-0/0/1.3001 *[EVPN/7] 02:26:20
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

ge-0/0/1.3016 *[EVPN/7] 02:26:13
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
ae10.3011 *[EVPN/7] 02:26:06
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1
ae10.3006 *[EVPN/7] 02:25:59
> to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe1

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe2

to 100.46.1.2 via ge-0/0/5.0, label-switched-path pe4_to_pe3

show route table mpls.0 protocol ospf

user@host> show route table mpls.0 protocol ospf
mpls.0: 29 destinations, 29 routes (29 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

299952 *[L-OSPF/10] 23:59:42, metric 0

> to 10.0.10.70 via lt-1/2/0.14, Pop
to 10.0.6.60 via lt-1/2/0.12, Swap 800070, Push 800030(top)
299952(S=0) *[L-OSPF/10] 23:59:42, metric 0
> to 10.0.10.70 via lt-1/2/0.14, Pop
to 10.0.6.60 via lt-1/2/0.12, Swap 800070, Push 800030(top)
299968 *[L-OSPF/10] 23:59:48, metric 0
> to 10.0.6.60 via lt-1/2/0.12, Pop

Protocol-Independent Routing Properties Feature Guide

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: 10.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: 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: 10.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: 10.0.0.1 via ge-0/0/1.0

show route table mpls.0 (RSVP Route—Transit 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 *[MPLS/0] 00:37:31, metric 1

Receive
1 *[MPLS/0] 00:37:31, metric 1
Receive
2 *[MPLS/0] 00:37:31, metric 1
Receive
13 *[MPLS/0] 00:37:31, metric 1
Receive
300352 *[RSVP/7/1] 00:08:00, metric 1

Chapter 12: Operational Commands

> to 10.64.0.106 via ge-1/0/1.0, label-switched-path lsp1_p2p

300352(S=0) *[RSVP/7/1] 00:08:00, metric 1
> to 10.64.0.106 via ge-1/0/1.0, label-switched-path lsp1_p2p
300384 *[RSVP/7/2] 00:05:20, metric 1
> to 10.64.1.106 via ge-1/0/0.0, Pop
300384(S=0) *[RSVP/7/2] 00:05:20, metric 1
> to 10.64.1.106 via ge-1/0/0.0, 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

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

Protocol-Independent Routing Properties Feature Guide

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)
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 *[OSPF/10] 00:07:24, metric 1

> via so-7/3/1.0
10.39.1.4/30 *[Direct/0] 00:08:42
> via so-5/1/0.0
10.39.1.6/32 *[Local/0] 00:08:46
Local
10.255.71.16/32 *[Static/5] 00:07:24
> via so-2/0/0.0
10.255.71.17/32 *[BGP/170] 00:07:24, 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.18/32 *[BGP/170] 00:07:24, MED 1, localpref 100, from
10.255.71.15
AS path: I
> via so-2/1/0.0, Push 100021, Push 100011(top)
10.255.245.245/32 *[BGP/170] 00:08:35, localpref 100
AS path: 2 I
> to 10.39.1.5 via so-5/1/0.0
10.255.245.246/32 *[OSPF/10] 00:07:24, metric 1
> via so-7/3/1.0

Chapter 12: Operational Commands

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:65536: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:65536: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:65536:10.255.2.204/432
*[MVPN/70] 00:57:23, metric2 1
Indirect
5:10.255.2.202:65536: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:65536:64500:128:::10.12.53.12:128:ffff::1/432
*[PIM/105] 00:02:37
Multicast (IPv6)
7:10.255.2.202:65536:64500: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

Protocol-Independent Routing Properties Feature Guide

AS path: 64500 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: 64502
Age: 6:30
Task: RT Flow
Announcement bits (2): 0-Flow 1-BGP.0.0.0.0+179
AS path: I
Communities: 1:1

user@host> 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

10.1.1.2:100:10.1.1.2/96 AD
*[VPLS/170] 1d 03:11:03, metric2 1
Indirect
10.1.1.4:100:10.1.1.4/96 AD
*[BGP/170] 1d 03:11:02, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/1.5
10.1.1.2:100:1:0/96 MH
*[VPLS/170] 1d 03:11:03, metric2 1
Indirect
10.1.1.4:100:1:0/96 MH
*[BGP/170] 1d 03:11:02, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/1.5
10.1.1.4:NoCtrlWord:5:100:100:10.1.1.2:10.1.1.4/176
*[VPLS/7] 1d 03:11:02, metric2 1
> via ge-1/2/1.5
10.1.1.4:NoCtrlWord:5:100:100:10.1.1.4:10.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)
10.0.0.0/32 (3 entries, 1 announced)
State: <OnList CalcForwarding>
TSI:
KRT in-kernel 10.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 10.0.0.0 from 10.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

Chapter 12: Operational Commands

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: 10.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_172.16.2.0.0+34549
AS path: I
Communities: target:2:1
Import Accepted
VPN Label: 16
Localpref: 0
Router ID: 10.2.0.0
Primary Routing Table bgp.l3vpn.0
Composite next hops: 1
Protocol next hop: 10.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
BGP Preference: 170/-1
Route Distinguisher: 2:1
Next hop type: Indirect
Address: 0x9347028
Next-hop reference count: 3
Source: 10.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: 10.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_172.16.3.0.0+32805
Announcement bits (2): 0-KRT 1-BGP_RT_Background
AS path: I
Communities: target:2:1
Import Accepted

Protocol-Independent Routing Properties Feature Guide

VPN Label: 16
Localpref: 0
Router ID: 10.3.0.0
Primary Routing Table bgp.l3vpn.0
Composite next hops: 1
Protocol next hop: 10.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
10.3.0.0/32 Originating RIB: inet.3
Metric: 70 Node path count: 1
Forwarding nexthops: 1
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: 10.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: 10.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

show route table bgp.evpn.0 extensive |no-more (EVPN)

show route table bgp.evpn.0 extensive | no-more
bgp.evpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
2:1000:10::100::00:aa:aa:aa:aa:aa/304 (1 entry, 0 announced)
*BGP Preference: 170/-101
Route Distinguisher: 1000:10
Next hop type: Indirect
Address: 0x9420fd0
Next-hop reference count: 12

Chapter 12: Operational Commands

Source: 10.2.3.4
Protocol next hop: 10.2.3.4
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
State: Local AS: 17 Peer AS:17 Age:21:12 Metric2:1 Validation State:
unverified
Task: BGP_17.1.2.3.4+50756
AS path: I
Communities: target:1111:8388708 encapsulation0:0:0:0:3
Import Accepted
Route Label: 100
ESI: 00:00:00:00:00:00:00:00:00:00
Localpref: 100
Router ID: 10.2.3.4
Secondary Tables: default-switch.evpn.0
Indirect next hops: 1
Protocol next hop: 10.2.3.4 Metric: 1
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.10.10.1 via xe-0/0/1.0
Session Id: 0x2
1.2.3.4/32 Originating RIB: inet.0
Metric: 1 Node path count: 1
Forwarding nexthops: 2
Nexthop: 10.92.78.102 via em0.0

2:1000:10::200::00:bb:bb:bb:bb:bb/304 (1 entry, 0 announced)

*BGP Preference: 170/-101
Route Distinguisher: 1000:10
Next hop type: Indirect
Address: 0x9420fd0
Next-hop reference count: 12
Source: 10.2.3.4
Protocol next hop: 10.2.3.4
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
State: Local AS:17 Peer AS:17 Age:19:43 Metric2:1 Validation
State:unverified
Task: BGP_17.1.2.3.4+50756
AS path: I
Communities: target:2222:22 encapsulation0:0:0:0:3
Import Accepted
Route Label: 200
ESI: 00:00:00:00:00:00:00:00:00:00
Localpref: 100
Router ID: 10.2.3.4
Secondary Tables: default-switch.evpn.0
Indirect next hops: 1
Protocol next hop: 10.2.3.4 Metric: 1
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.10.10.1 via xe-0/0/1.0
Session Id: 0x2
10.2.3.4/32 Originating RIB: inet.0
Metric: 1 Node path count: 1
Forwarding nexthops: 2
Nexthop: 10.92.78.102 via em0.0

2:1000:10::300::00:cc:cc:cc:cc:cc/304 (1 entry, 0 announced)

*BGP Preference: 170/-101
Route Distinguisher: 1000:10

Protocol-Independent Routing Properties Feature Guide

Next hop type: Indirect

Address: 0x9420fd0
Next-hop reference count: 12
Source: 10.2.3.4
Protocol next hop: 10.2.3.4
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
State: Local AS:17 Peer AS:17 Age:17:21 Metric2:1 Validation State:
unverified Task: BGP 17,1,2,3,4+50756
AS path: I
Communities: target:3333:33 encapsulation0:0:0:0:3
Import Accepted
Route Label: 300
ESI: 00:00:00:00:00:00:00:00:00:00
Localpref: 100
Router ID: 10.2.3.4
Secondary Tables: default-switch.evpn.0
Indirect next hops: 1
Protocol next hop: 10.2.3.4 Metric: 1
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.10.10.1 via xe-0/0/1.0
Session Id: 0x2
10.2.3.4/32 Originating RIB: inet.0
Metric: 1 Node path count: 1
Forwarding nexthops: 2
Nexthop: 10.92.78.102 via em0.0

3:1000:10::100::1.2.3.4/304 (1 entry, 0 announced)

*BGP Preference: 170/-101
Route Distinguisher: 1000:10
PMSI: Flags 0x0: Label 100: Type INGRESS-REPLICATION 1.2.3.4
Next hop type: Indirect
Address: 0x9420fd0
Next-hop reference count: 12
Source: 10.2.3.4
Protocol next hop: 10.2.3.4
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
State: Local AS:17 Peer AS:17 Age:37:01 Metric2:1 Validation State:
unverified Task: BGP 17.1.2.3.4+50756
AS path: I
Communities: target:1111:8388708 encapsulation0:0:0:0:3
Import Accepted
Localpref: 100
Router ID: 10.2.3.4
Secondary Tables: default-switch.evpn.0
Indirect next hops: 1
Protocol next hop: 10.2.3.4 Metric: 1
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.10.10.1 via xe-0/0/1.0
Session Id: 0x2
10.2.3.4/32 Originating RIB: inet.0
Metric: 1 Node path count: 1
Forwarding nexthops: 2
Nexthop: 10.92.78.102 via em0.0

3:1000:10::200::1.2.3.4/304 (1 entry, 0 announced)

*BGP Preference: 170/-101
Route Distinguisher: 1000:10

Chapter 12: Operational Commands

PMSI: Flags 0x0: Label 200: Type INGRESS-REPLICATION 1.2.3.4

Next hop type: Indirect
Address: 0x9420fd0
Next-hop reference count: 12
Source: 10.2.3.4
Protocol next hop: 10.2.3.4
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
State: Local AS: 17 Peer AS: 17 Age:35:22 Metric2:1 Validation
State:unverified Task: BGP 17.1.2.3.4+50756
AS path:I Communities: target:2222:22 encapsulation):0:0:0:0:3

Import Accepted
Localpref: 100
Router ID: 10.2.3.4
Secondary Tables: default-switch.evpn.0
Indirect next hops: 1
Protocol next hop: 10.2.3.4 Metric: 1
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.10.10.1 via xe-0/0/1.0
Session Id: 0x2
10.2.3.4/32 Originating RIB: inet.0
Metric: 1 Node path count: 1
Forwarding nexthops: 2
Nexthop: 10.92.78.102 via em0.0

3:1000:10::300::1.2.3.4/304 (1 entry, 0 announced)

*BGP Preference: 170/-101
Route Distinguisher: 1000:10
PMSI: Flags 0x0: Label 300: Type INGRESS-REPLICATION 1.2.3.4
Next hop type: Indirect
Address: 0x9420fd0
Next-hop reference count: 12
Source: 10.2.3.4
Protocol next hop: 10.2.3.4
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
State: Local AS: 17 Peer AS: 17 Age 35:22 Metric2:1 Validation State:
unverified Task: BGP 17.1.2.3.4+5075
6 AS path: I Communities: target:3333:33 encapsulation0:0:0:0:3
Import Accepted Localpref:100
Router ID: 10.2.3.4
Secondary Tables: default-switch.evpn.0
Indirect next hops: 1
Protocol next hop: 10.2.3.4 Metric: 1
Indirect next hop: 0x2 no-forward INH Session ID: 0x0
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.10.10.1 via xe-0/0/1.0
Session Id: 0x2
10.2.3.4/32 Originating RIB: inet.0
Metric: 1 Node path count: 1
Forwarding nexthops: 2
Nexthop: 10.92.78.102 via em0.0

Protocol-Independent Routing Properties Feature Guide

show route terse

List of Syntax Syntax on page 502

Syntax (EX Series Switches) on page 502

Syntax show route terse

<logical-system (all | logical-system-name)>

Syntax (EX Series show route terse

Switches)

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 none—Display 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 view

Level

List of Sample Output show route terse on page 504

Output Fields Table 28 on page 502 describes the output fields for the show route terse command.
Output fields are listed in the approximate order in which they appear.

Table 28: 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.

Chapter 12: Operational Commands

Table 28: show route terse 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:

• 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 key Key for the state of the route:

A Active route. An asterisk (*) indicates this is the active route.

V Validation status of the route:

• ?—Not evaluated. Indicates that the route was not learned through BGP.
• I—Invalid. 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.
• N—Unknown. Indicates that the prefix is not among the prefixes or prefix ranges in the database.
• V—Valid. Indicates that the prefix and autonomous system pair are found in the database.

Destination Destination of the route.

P Protocol through which the route was learned:

• A—Aggregate
• B—BGP
• C—CCC
• D—Direct
• G—GMPLS
• I—IS-IS
• L—L2CKT, L2VPN, LDP, Local
• K—Kernel
• M—MPLS, MSDP
• O—OSPF
• P—PIM
• R—RIP, RIPng
• S—Static
• T—Tunnel

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.

Protocol-Independent Routing Properties Feature Guide

Table 28: show route terse Output Fields (continued)

Field Name Field Description

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.

Next hop Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.

• I—IGP.
• E—EGP.
• ?—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 P Prf Metric 1 Metric 2 Next hop AS path

* ? 172.16.1.1/32 O 10 1 >10.0.0.2
? B 170 100 I
unverified >10.0.0.2
* ? 172.16.1.1/32 D 0 >lo0.2
* V 2.2.0.2/32 B 170 110 200 I
valid >10.0.0.2
* ? 10.0.0.0/30 D 0 >lt-1/2/0.1
? B 170 100 I
unverified >10.0.0.2
* ? 10.0.0.1/32 L 0 Local
* ? 10.0.0.4/30 B 170 100 I
unverified >10.0.0.2
* ? 10.0.0.8/30 B 170 100 I
unverified >10.0.0.2
* I 172.16.1.1/32 B 170 90 200 I
invalid >10.0.0.2
* N 192.168.2.3/32 B 170 100 200 I
unknown >10.0.0.2
* ? 172.16.233.5/32 O 10 1 MultiRecv

FortiGate Infrastructure 7.2 Study Guide-Online
No ratings yet
FortiGate Infrastructure 7.2 Study Guide-Online
388 pages
Operators Telco Cloud - White Paper: 1. Executive Summary
No ratings yet
Operators Telco Cloud - White Paper: 1. Executive Summary
9 pages
BRKARC-3472 NX-OSRouting and Layer 3 Switching
No ratings yet
BRKARC-3472 NX-OSRouting and Layer 3 Switching
132 pages
Nevada Highways Map (2010)
No ratings yet
Nevada Highways Map (2010)
187 pages
Grayson v. Hsin, 4th Cir. (2011)
No ratings yet
Grayson v. Hsin, 4th Cir. (2011)
6 pages
GT Walsheim Font Family at Specimen
No ratings yet
GT Walsheim Font Family at Specimen
24 pages
BGP LS
100% (1)
BGP LS
23 pages
Linux
No ratings yet
Linux
146 pages
Final
No ratings yet
Final
8 pages
Warren L. Dela Cerna: Objectives
No ratings yet
Warren L. Dela Cerna: Objectives
4 pages
Asian Age Delhi 07 Dec 2022
No ratings yet
Asian Age Delhi 07 Dec 2022
8 pages
Resumes Um Anc
No ratings yet
Resumes Um Anc
3 pages
Hexnode Plan Comparisions
No ratings yet
Hexnode Plan Comparisions
27 pages
Equi Valencia S Comando S Cisco Hua We I
No ratings yet
Equi Valencia S Comando S Cisco Hua We I
77 pages
Royal Consulate General of
No ratings yet
Royal Consulate General of
45 pages
Vip Hawaii Flight Advisory
No ratings yet
Vip Hawaii Flight Advisory
3 pages
James Bond Rachana Sangraha Bangla
No ratings yet
James Bond Rachana Sangraha Bangla
719 pages
Foundstone Hacme Books User and Solution Guide V2.0e
No ratings yet
Foundstone Hacme Books User and Solution Guide V2.0e
31 pages
Amcrest Quick Start Guide +WIFI v.1.0.4
No ratings yet
Amcrest Quick Start Guide +WIFI v.1.0.4
18 pages
WPS0!03!02 TCP-IP Protocol and Subnet Planning ISSUE1.0 - 20061229 - A
No ratings yet
WPS0!03!02 TCP-IP Protocol and Subnet Planning ISSUE1.0 - 20061229 - A
31 pages
Questionnaire
No ratings yet
Questionnaire
6 pages
Detroit Lakes City Council 5-Year Plan and Special Assessment Policy, June 20, 2023
No ratings yet
Detroit Lakes City Council 5-Year Plan and Special Assessment Policy, June 20, 2023
58 pages
Supply PDF
100% (1)
Supply PDF
140 pages
Logcat Prev CSC Log
No ratings yet
Logcat Prev CSC Log
179 pages
December 9, 2015 Tribune-Phonograph
No ratings yet
December 9, 2015 Tribune-Phonograph
22 pages
Sathi A Das 2003
No ratings yet
Sathi A Das 2003
10 pages
Priynka S Project
No ratings yet
Priynka S Project
70 pages
Willy Wonka: Vermont Tire & Service
No ratings yet
Willy Wonka: Vermont Tire & Service
35 pages
Lecture 2 Introduction To Global and ASEAN Wildfire, Smoke Haze Tracking System
No ratings yet
Lecture 2 Introduction To Global and ASEAN Wildfire, Smoke Haze Tracking System
186 pages
Deposit Slip
No ratings yet
Deposit Slip
1 page
Finall Project
No ratings yet
Finall Project
51 pages
Lordofwar Ocr Part2
No ratings yet
Lordofwar Ocr Part2
900 pages
FTA Highlights 7
No ratings yet
FTA Highlights 7
50 pages
Frewfgwsg
No ratings yet
Frewfgwsg
874 pages
Assigning Dynamic Names Within A Financial Model Section 03/25
100% (1)
Assigning Dynamic Names Within A Financial Model Section 03/25
3 pages
Gmail - Confirmation of Your Reservation - Ibis Budget Sydney East No
No ratings yet
Gmail - Confirmation of Your Reservation - Ibis Budget Sydney East No
5 pages
Wakounig - Organizing A New Telco - Detecon Whitepaper - Neu
No ratings yet
Wakounig - Organizing A New Telco - Detecon Whitepaper - Neu
19 pages
Westermo MG 6101-3201 Weos PDF
No ratings yet
Westermo MG 6101-3201 Weos PDF
1,196 pages
Proposed Amendments To Pinehurst's Municipal Code
No ratings yet
Proposed Amendments To Pinehurst's Municipal Code
22 pages
The Beer Catalogue (1st)
No ratings yet
The Beer Catalogue (1st)
53 pages
Project Work: Indian Financial System (Ifs)
No ratings yet
Project Work: Indian Financial System (Ifs)
20 pages
August-Current Affairs-Part-3
No ratings yet
August-Current Affairs-Part-3
9 pages
Services PVT LTD Scheme Doc Care
No ratings yet
Services PVT LTD Scheme Doc Care
30 pages
Cmat GK 500 PDF
100% (1)
Cmat GK 500 PDF
133 pages
Merritt Morning Market 3867 - Sept 1
No ratings yet
Merritt Morning Market 3867 - Sept 1
2 pages
Client UserManual
No ratings yet
Client UserManual
22 pages
Your New Barratt London Home: Reservation Guide
No ratings yet
Your New Barratt London Home: Reservation Guide
17 pages
Company Profile of Ncell Pvt. Ltd.
100% (1)
Company Profile of Ncell Pvt. Ltd.
22 pages
IoT Unit-4
No ratings yet
IoT Unit-4
16 pages
Jim Corbett National Park - Wiki
No ratings yet
Jim Corbett National Park - Wiki
53 pages
Siva Teja
No ratings yet
Siva Teja
3 pages
EMTECH Reviewer
No ratings yet
EMTECH Reviewer
7 pages
BRKDCT 2081
No ratings yet
BRKDCT 2081
97 pages
1 Theories
No ratings yet
1 Theories
61 pages
Chương 6
No ratings yet
Chương 6
108 pages
Tawan Part 2 by Tahir Javed Mughal
No ratings yet
Tawan Part 2 by Tahir Javed Mughal
1,163 pages
Bharti Airtel LTD.: Company Overview
No ratings yet
Bharti Airtel LTD.: Company Overview
3 pages
Nine Building Blocks of The Business Model
No ratings yet
Nine Building Blocks of The Business Model
3 pages
Config Guide Routing Multitopology Routing
No ratings yet
Config Guide Routing Multitopology Routing
198 pages
Config Guide Routing Overview
No ratings yet
Config Guide Routing Overview
74 pages
Juniper OS Getting Started Guide For Routing Devices
No ratings yet
Juniper OS Getting Started Guide For Routing Devices
62 pages
Junos® OS Getting Started Guide For Routing Devices
No ratings yet
Junos® OS Getting Started Guide For Routing Devices
398 pages
Juniper Book-Swconfigip-Services
No ratings yet
Juniper Book-Swconfigip-Services
404 pages
Ipv4 Addressing
No ratings yet
Ipv4 Addressing
9 pages
VLSM Exercise
No ratings yet
VLSM Exercise
3 pages
FWC-21
No ratings yet
FWC-21
118 pages
ROUTE v7 Chapter 1 Exam - CCNP v7 Exam Module Question & Answer
83% (6)
ROUTE v7 Chapter 1 Exam - CCNP v7 Exam Module Question & Answer
5 pages
OSPF Commands
No ratings yet
OSPF Commands
2 pages
BRKSP 2551 1
No ratings yet
BRKSP 2551 1
86 pages
4a0-106.exam.118q: Website: VCE To PDF Converter: Facebook: Twitter
No ratings yet
4a0-106.exam.118q: Website: VCE To PDF Converter: Facebook: Twitter
90 pages
Hsdpa R99
No ratings yet
Hsdpa R99
6 pages
Wcdma
91% (11)
Wcdma
102 pages
GPRS
No ratings yet
GPRS
44 pages
Establishing BGP Sessions
No ratings yet
Establishing BGP Sessions
23 pages
Ccna 2 Module 6
100% (4)
Ccna 2 Module 6
9 pages
Agrawal Sameer-Ram.R Vivek Shankar
No ratings yet
Agrawal Sameer-Ram.R Vivek Shankar
14 pages
Routing Protocols
No ratings yet
Routing Protocols
43 pages
IGP Troubleshooting
No ratings yet
IGP Troubleshooting
15 pages
OSPF Practical Lab
No ratings yet
OSPF Practical Lab
19 pages
Protocols Notes) Basic Networking Interview Questions & Answers 1. Define Network?
No ratings yet
Protocols Notes) Basic Networking Interview Questions & Answers 1. Define Network?
99 pages
VLSM (Variable Length Subnet Mask)
No ratings yet
VLSM (Variable Length Subnet Mask)
11 pages
Ccna Exam 2 Version 4.02
No ratings yet
Ccna Exam 2 Version 4.02
97 pages
Chapter 1-2
No ratings yet
Chapter 1-2
29 pages
OSPF Packet Types
No ratings yet
OSPF Packet Types
10 pages
STT Tên TR M Đ T Long Lat 144 144 144 144 144 144 144 144 144 Mã TR M 4G Mã TR M 4G E/// VNPT Asp Config Existing Config New VNPT (Boq)
No ratings yet
STT Tên TR M Đ T Long Lat 144 144 144 144 144 144 144 144 144 Mã TR M 4G Mã TR M 4G E/// VNPT Asp Config Existing Config New VNPT (Boq)
12 pages
Lab 4 - Static Routing
No ratings yet
Lab 4 - Static Routing
5 pages
CCNP-enterprise-enarsi-Course OUtline
No ratings yet
CCNP-enterprise-enarsi-Course OUtline
4 pages
Static Routing and Basic Router Configurations
100% (1)
Static Routing and Basic Router Configurations
11 pages
Itcertnotes - Manipulating Routing Updates
No ratings yet
Itcertnotes - Manipulating Routing Updates
11 pages
7.2.2.4 Packet Tracer - Configuring Basic EIGRP With IPv4 Instructions IG
No ratings yet
7.2.2.4 Packet Tracer - Configuring Basic EIGRP With IPv4 Instructions IG
5 pages